Hello,
I have a question for Rintze and Sebastian but I think that it’s
interesting enough to be asked here in the list. Sorry for the length
of it, I wanted to explain all the problem…
I’m debugging a locales problem… and Frank and I are reading the
specification differently.
I’ll explain using an example which I hope that will be clearer.
Let’s say that we have vancouver.csl, which has:
presented at
available
sect.
(and similar for “fr” and “de”)
I instantiate citeproc-js indicating that I want to use es-ES
At the moment for, in vancouver.csl in the bibliography I have:
The output is:
a) “retrieved” term is translated as “available” (using the in-style
locale translation)
b) “from” term is translated as “a partir de” (from locales-esES.xml)
(so it says “available a partir de”)
I expected all in Spanish. My logic was:
-try to use the in-style locale in Spanish for the term
-if not available try to localize the term using locale-es-ES.xml
-if not available there: use the default in-style locale
-else the locale-{default}.xml
(step number 3 would be optional but perhaps nice to have)
Basically, I expect that I could overwrite the locales-es-ES.xml in
the in-style locale section, based on each term (not all the es-ES
terms but only a set of terms).
The spec says:
http://citationstyles.org/downloads/specification.html#locale
"
Localization data, by default drawn from the “locales-xx-XX.xml”
locale files, may be redefined or supplemented with cs:locale
elements, which should be placed directly after the cs:info element.
"
Do you agree that this should happen? Or something else? (e.g. use the
default in-style translation before trying to use locale-es-ES?)
Thank you!–
Carles Pina | Software Engineer
Mendeley Limited | London, UK | www.mendeley.com
Registered in England and Wales | Company Number 6419015
