Curly apostrophes mess with the “nocase” mechanism

nickbart

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., “).

  • fbennett
    If 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.

This is an old discussion that has not been active in a long time. Before commenting here, you should strongly consider starting a new discussion instead. If you think the content of this discussion is still relevant, you can link to it from your new discussion.

Sign In or Register to comment.