Frank and I aren’t really sure about the reason that xml:lang and
default-locale are both included in CSL. Couldn’t xml:lang be used instead
of default-locale to indicate the style locale? And if default-locale is
here to stay, are there any cases where xml:lang won’t be set to ‘en’?
Rintze
It’s a little suspect for me too.
But xml:lang I believe means to apply to the content of the file. But
there’s admittedly little, if any, language-specific content. If we
switch to using a URI to identify the license, then there’s none I
guess.
Bruce
Frank and I aren’t really sure about the reason that xml:lang and
default-locale are both included in CSL. Couldn’t xml:lang be used instead
of default-locale to indicate the style locale? And if default-locale is
here to stay, are there any cases where xml:lang won’t be set to ‘en’?It’s a little suspect for me too.
But xml:lang I believe means to apply to the content of the file. But
there’s admittedly little, if any, language-specific content. If we
switch to using a URI to identify the license, then there’s none I
guess.
Rintze and I are wondering whether xml:lang can be dropped from the
style node, retaining default-locale to indicate the preferred
presentation language for the style. xml:lang seems to be set
separately on the rights node, which would cover the license language
issue.
For the migration to 1.0, there are styles currently in the repository
that use xml:lang set to a language other than English, with the
intention of setting the preferred presentation language. If moving
this preference to default-locale and dropping xml:lang from the style
node is okay, then to cover these cases, the value of xml:lang should
be mapped to default-locale by the update.xsl script.
Frank
Rintze and I are wondering whether xml:lang can be dropped from the
style node, retaining default-locale to indicate the preferred
presentation language for the style.
That’s fine.
xml:lang seems to be set
separately on the rights node, which would cover the license language
issue.
Am still wondering about using URIs for the license.
For the migration to 1.0, there are styles currently in the repository
that use xml:lang set to a language other than English, with the
intention of setting the preferred presentation language. If moving
this preference to default-locale and dropping xml:lang from the style
node is okay, then to cover these cases, the value of xml:lang should
be mapped to default-locale by the update.xsl script.
Hmm … is that not rather dangerous?
Bruce
Rintze and I are wondering whether xml:lang can be dropped from the
style node, retaining default-locale to indicate the preferred
presentation language for the style.That’s fine.
xml:lang seems to be set
separately on the rights node, which would cover the license language
issue.Am still wondering about using URIs for the license.
For the migration to 1.0, there are styles currently in the repository
that use xml:lang set to a language other than English, with the
intention of setting the preferred presentation language. If moving
this preference to default-locale and dropping xml:lang from the style
node is okay, then to cover these cases, the value of xml:lang should
be mapped to default-locale by the update.xsl script.Hmm … is that not rather dangerous?
The number of exceptions is small, so you could do it by hand as well.
Only nine styles are affected: one French, two Spanish, and six
German. Here’s the list, for reference:
harvard7de.csl
immunity.csl
law1_de.csl
mhra_note_without_bibliography.csl
sp-legal.csl
tah-gkw.csl
tah-leviathan.csl
tah-soz.csl
vienna-legal.csl
Frank