I was lax about the handling of apostrophes in the rich text parser of
citeproc-js, assuming them to be equivalent to a closing inner-quote.
Not true for French, apparently:
The parser can handle the case correctly, if there is an “apostrophe”
term in the locale files. Happy to make the change myself; is it okay
to add this?
Frank
Do “apostrophes” localize? If the symbol would be the same for all locales,
it wouldn’t make much sense to include it.
RintzeOn Wed, Nov 10, 2010 at 6:45 PM, Frank Bennett <@Frank_Bennett>wrote:
It wouldn’t, would it. I’ll make it a static character. If it needs
to localize, someone will tell us. Let’s close this one for the
present.
Frank
It wouldn’t, would it. I’ll make it a static character. If it needs
to localize, someone will tell us. Let’s close this one for the
present.Frank
Turns out there are variants of apostrophe:
However, I think we can safely ignore this. Armenian apostrophes will
almost certainly be coded as such in the Unicode source. The parser
only needs to deal with them when they are entered in typewriter
style, and that will almost certainly only happen in roman-like
locales.
So sticking with Plan B for the time being.