1 Jul 20, 2009 15:17
Regional -> Edit a lang
In the locale field: there shouldn't be a suffix -utf8
Rationale: the "Locale field" is used as the value of "lang=" in all pages.
Thus a locale field with the value "en-US-utf8" is illegal.
In short what's allowed in the "lang=" attribute:
en = Generic English
en-US = US English
en-GB = Great Britain English
en-PH = Philippine English
fil = Filipino language
fil-Tglg = Filipino language written in Baybayin/Moro script
bik-bto = Bikolano language of the Iriga dialect
bik-bto-Tglg = Bikolano language of the Iriga dialect written in Baybayin/Moro script
phi-Tglg-mrw = Maranao Philippine Language written in Baybayin/Moro script
Legal format: language-script-region-variant-extension-privateuse
And so on.
This makes the language "English (US) utf8" wrong because it has a "Locale field" value of "en-US-utf8".
Official Centralized Lang Subtag Registry: http://www.iana.org/assignments/language-subtag-registry
Official Centralized Macrolanguage subtag list: http://www.sil.org/iso639-3/macrolanguages.asp
A solution if suffixing -utf8 is needed, separate the two functions.
Create a new field or something for the "lang=" attribute value.
While another field for the -utf8 suffixes.
Normally it shouldn't be a problem at all, but we can not control browsers. There is a risk that current or future browsers may change the way they read illegal "lang=" attribute values. The specification wasn't clear, it simply said that it is at the browser's hand to just drop illegal suffixes or they can opt to ignore the whole value of that lang attribute!! (They should stop writing specifications that doesn't define such cases.)