Upgrade StorageAutomatically choose whether hyphen, en dash, or em dash should be used
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.
We're running into some back-and-forth adjustments to cope with irregular input, and it may take a few iterations to get the compromises right. This is being forced back to hyphen because the numbers don't form a range. For some sources, this would be a leaf number (odd, I know, but the meaning would be something like "page 38 of segment 135"). I gave priority to that case, and built in an override of -- for an explicit en-dash, and \- for an explicit hyphen, to cope with situations where it fails.
Since users in the field have already run into problems with that logic, it should be adjusted. There are a couple of possible responses. First, we could just convert all hyphens to en-dash (retaining the possibility of override, so leaf numbers would need to be marked up explicitly, which is simpler to explain and not really a problem). Second, we could retain the current behavior, but treat en-dash as an explicit delimiter, never falling back to hyphen.
Of the two choices, the first seems better. It's simpler to code, and simpler to explain, and more flexible (if, say, we run into a style that requires hyphens for ranges, the discriminate treatment of en-dash in the input won't get in the way or cause confusion).
If that all sounds right, I can make the adjustment in a fresh release.
I've just discovered the replacement in z3.0 of hyphens by en-dashes for page range. This is certainly correct in English but not in French (fr-FR at least).
In French typography, we use (non-breaking) hyphens for ranges/intervals, e.g.:
year: 1945-1983
pages: p. 65-82.
It's U+2011 (non-breaking hyphen) [or U+2010 (hyphen)].
En-dashes (–) are only used "when the bounds of the interval are compounds terms" (see the example with Napoléon Bonaparte below).
Source:
http://marcautret.free.fr/sigma/pratik/typo/tiret/index.php http://aitia.revues.org/205#tocto1n3 http://www.mus.ulaval.ca/roberge/gdrm/08-annee.htm
I would guess the solution would be to disable this for all French locales, right?
Anyway, that should be disabled for fr-FR at least (and perhaps for fr-CA too: http://www.druide.com/points_de_langue_28.html (canadian website))
Would it work to force the range delimiter into the locale behind the scenes? That would produce the expected behavior for the fr domains in the short term, and it will migrate smoothly if this is added to CSL locales in the future.
http://www.bib.umontreal.ca/InfoSphere/sciences_humaines/module7/regles-generales.html#VolumeNumPages
And one of Gracile's other sources:
http://www.mus.ulaval.ca/roberge/gdrm/08-annee.htm
is the Universi†é de Laval in Quebec City.
Finally, it is also followed by the entire Université du Québec system:
http://www.bibliotheques.uqam.ca/infosphere/fichiers_communs/module7/regles_biblio.html#vol
That's three for three.
This is a provisional fix; presumably this will eventually be configurable through a normal locale term, like quotes.
(http://www.misq.org/manuscript-guidelines) that requires the short - for the page number range in its style. What should be done?
Thanks
<locale>This is not yet part of the official CSL specification, so it won't validate, but it will work.<terms>
<term name="page-range-delimiter">-</term>
</terms>
</locale>
I pasted it right behind the info tag and before the macro tags. Is there anything else I should consider?
Thanks!
https://gist.github.com/e5768ca36ef08c5acc11
http://citationstyles.org/downloads/upgrade-notes.html#updating-csl-0-8-styles
but: It still doesn't work for me. I uploaded the updated code:
https://gist.github.com/14c0062b5815f8ab8447
Do you have another idea?