Curly apostrophes mess with the “nocase” mechanism
It seems that curly apostrophes mess with the “nocase” mechanism; most likely a citeproc-js bug.
The following – one straight apostrophe, followed by a curly one – in a Zotero title field:
Blah <span class="nocase">you're</span> <span class="nocase">you’re</span>
is rendered as
Blah you’re <span class="nocase">you’re</span>
(Expected, of course, Blah you’re you’re
.)
In addition, it seems that straight (!) quotation marks ("
) cause problems, too – but not (!) curly ones, (e.g., “
).
-
fbennettIf this is still an issue and the processor appears to be at fault, I can look into it if a test item is available. To submit an item, join the public Jurism Test Submission group, sync, create a collection named for the style that shows the error, drop the item into it, and sync again.