fbennett
About
- Username
- fbennett
- Joined
- Roles
- Member
Comments
-
Yes, Fn#5 in the example is ambiguous, and thedisambiguate condition will be true. Ambiguity is based on the "subsequent" form of the cite, as a general principle, regardless of the context within which cites actually appear.
-
Thanks, I'll take a look today.
-
I'll assume for the present that this failure was connected to the syntax issues in the style that emerged in another thread. If a valid style still fails to apply locale-specific punctuation-in-quote values, post again to this thread and I'll take …
-
It's handled as an institution. The details are at pp. 35 & 36 of the MLZ book.
-
It's hard to say without looking directly at the style code and test items that failed; but certainly evaluating the position condition early in the processing chain will make your code more compact, which is a good thing.
-
Did the code you posted above work correctly for you? It still doesn't disambiguate in mine. Is there a chance that it's because I'm using the special MLZ that you provided to deal with the other issue from last week? I didn't build a test before po…
-
Spaces in affixes are allowed in regular CSL and I think they'll likely remain allowed. ♫ You say tomato and I say tomahto ... ♫ :-)
-
The CSL-m validator reports many syntax errors for the style code posted to the gist above. Here is a version with the more serious errors fixed: https://gist.github.com/fbennett/8606502 The most glaring errors were an apostrophe character between …
-
Hang in there. It's Saturday here, and we''re past the main pressures of term. I'll take a look and we'll get to the bottom of it.
-
It could be a processor bug -- I'll check later today.
-
If you can post the full style code to http://gist.github.com, I can take a look.
-
Have you validated your style?
-
This has been well tested in the processor. Loo king at your code there, it won't actually diambiguate anything, since you are applying the same string to all entries. Try testing with real data.
-
You can set multiple cs:locale nodes in a style, by using different xml:lang attributes on each. It's documented here.
-
With multiple layouts, each alternative layout but the last specifies a primary and zero or more subsidiary locales. When the item language matches a layout, the locale for rendering is set to the layout's primary locale (its first-listed language c…
-
It renders as a name, so try something like this, instead of the cs:text node: Formatting controls for institution names are documented here.
-
As stated on the CitationStylist site, the MLZ Oscola style is written in CSL-m, an extended version of the Citation Style Language. CSL-m is supported only (as far as I know) by Multilingual Zotero (MLZ), which is distributed via the same site. (T…
-
Looking at this one now. I should be sending a debugging-friendly client version to you by private mail soon.
-
Fixing this in the database is not terribly burdensome. There is a right-click menu option on the title field that will convert the field content to sentence case (or title case, which is supported, but not recommended for database storage). Fixing…
-
@rintze: You're right. I was misremembering.
-
Sorry for the delay. I seem to have a break in the action this evening. Which style are you using? In MLZ CMS Full Note, the institution renders from the CSL-m authority variable, but it only comes through if there is no other author for the item. …
-
Yes, that is a limitation.
-
Isn't it best to fix that in the database?
-
@wonblee: Okay, I wasn't sure if it was just a sync issue. This is the first time I've see this error, and the code for creator storage hasn't changed in quite a long time. I'll send you a client version later today that provides a little feedback …
-
I don't have access to the log behind the Report ID. What exactly is happening?
-
Can you give an example?
-
That would indeed be handy. It might be awhile before it's implemented -- the coding will not be easy.
-
It's mapped to CSL-m "authority", which renders as an institution name.
-
Sure, send me a zotero.org DM.
-
I thought we fixed this (see Oct. 19 note above). Are you using the latest release?
Upgrade Storage