Upgrade Storagefbennett
About
- Username
- fbennett
- Joined
- Roles
- Member
Comments
-
I am working on an experimental version of the Bluebook style. I've set up a list of existing issues on a separate forum thread. The experimental code, which is still very incomplete and requires patches to run, is available for inspection, and wi…
-
Issues down the road Initially I am concentrating on setting up full citation output for secondary resources (books, articles, manuscripts, electronic resources). The next step will be to get back-references working. I plan to hold off dealing wi…
-
Ah. I see that there is a already a ticket for this. I am using OO, so the ticket covers my case. I see that a fix was scheduled for Zotero Sync Preview, and that the ticket is now marked closed. In future, I'll try to be more careful about chec…
-
Oops. Actually, turns out there was a little gotcha in the new quoting code. Apparently there are some vars (JS vars typed numeric?) that don't have the *.match method used to apply the regexp, and it can cause cite editing or creation to block wh…
-
Thanks, this works like a charm! I'll keep this escape trick as a last-ditch resort. I'm about 50 cites into the "books" section of the Bluebook, about 1/3 of the way through that bit. Doing these test cases is certainly proving helpful. I'll be…
-
I understand your reluctance. Partly I'm reacting to the unknown; the Bluebook is a mass of exceptions and special cases, and I'm fearful that without an escape mechanism, I will end up playing even uglier incompatibility games (with weird field as…
-
Further further to the is-quoted thing. The example I gave could be handled by a failure of is-numeric. But there are other cases where it would be useful. For example, in the locator, a user might want to force a correct singular-form prefix whe…
-
Further to the quoted-escape thing, quoted content would admittedly be incorrect for some other styles. It's sort of a choose-your-poison thing. But you would be able to more easily collect a body of information on practice, by checking databases …
-
This would be used to force literal interpretation of strings, suppressing the prefix or suffix that would ordinarily be attached to it. This would allow override in exceptional cases where the default processing of a style does the wrong thing, bu…
-
@Rintze: I agree, recognizing enclosing quotes as an escape would be a good solution.
-
Sorry, in the above, "293 tbl. T.10" is Locator: not Page.
-
@Rintze: Ive just put up a patch against Zotero Sync Preview 1.5 under a ticket kindly opened by Dan, that addresses this issue. Here's a breakdown of the actual data entered for the citation elements: Title: The Bluebook: A Uniform System of Citat…
-
Done.
-
Sure thing. Have a good trip; I'm grateful for the time you've taken out for advice on this. No cause for alarm, I'm not working under any sort of deadline; fiddling with code is just my way of thinking out loud. Dan has opened a ticket, I'll pos…
-
I have modified the code of Zotero 1.5 to accomplish this on my laptop. Can provide as a patch to anyone interested.
-
Final note on this. There were problems in the code above, but they have now been solved. Can offer a patch to anyone interested.
-
Okay, here's a patch for the chrome directory that addresses this issue. Not sure what side effects adding these two fields to _zoteroNumberFieldMap might produce, but it's been tested to make sure it enables conditionality. If this is an acceptab…
-
Further news on this. The is-numeric test works correctly when applied to the editor field. From looking at the CSL spec and the Zotero code, it looks like CSL permits it against all fields, but Zotero only applies to a subset of "numeric" fields.…
-
Hmm. I was assuming that is-numeric was working with other fields, but I just checked with the note field, and it always reports false on that one as well. This is with Zotero 1.5 Sync Preview, maybe is-numeric is broken in that version?
-
Getting there, but there's still a hitch. The locator field is always identified as non-numeric. Here's the test code: This is just a simple case for testing (the logic is backwards), but it always produc…
-
The Vatican analogy is spot on (the Ecclesiastical Courts predate the common law, after all!). And no worries. I didn't know about the is-numeric condition. Growing pains. I'll have a go. No problem about trade-offs; I have quite a knack for wr…
-
Unfortunately, the use of a bare number to indicate pages is already a well established convention in the target community. The change you suggest would be a major one, and my intuition is that it would not be accepted. Strict adherence to Blueboo…
-
I'll chime in here as well. For full flexibility with international and comparative material, it would be nice to see two fields, "jurisdiction" and "jurisdiction-level". The first would indicate the rulemaking framework within which the decision …
-
Exactly what the doctor ordered. Thanks again.
-
It does work, I've just figured out the CSL syntax (hurray!). The problem is that the unique term identifier ("editor", "translator") sometimes needs to map through to a singular or to a plural version in each of the formats being defined ("verb",…
-
Nice! I didn't realize that custom terms were possible. But would it be correct that customized plural-sensitive terms are not yet supported? Or am I missing something (again)?
-
As a follow-on to this, I wonder whether a CSL-based facility for remapping the labels (for editor, translator, the various locators, etc.) within a style file is possible. This would greatly simplify the fine-tuning of styles that diverge in small…
-
One thing that will be a considerable problem is the handling of singular and plural locators -- i.e. markers for pages (p. vs. pp.), notes (n. vs. nn.), paragraphs (the marker or markers), sections (ditto), etc. As I understand it, in normal opera…
-
Thanks to Bruce for comments. There are some small organizational issues in my current crack at the style file that I'll try to sort out before "officially" offering it up. The main thing to note is that the style file in its current state (and in…
-
@bdarcus: I've refactored the published Bluebook style file with a view to simplifying individual macros, as a first step toward extending the style to cope with all cites in the "Typical Legal Citations Analyzed" section at the front of the Bluebo…