JanHusarcik
commented
6 years ago Hi Rodolfo,
what I'm arguing in this example is using not specific enough language tag is bad and showing it on sr and en.
I'm in no way suggesting someone should use e.g. ru_Cyrl_RU, due to its redundancy.
I'm, also referencing https://www.w3.org/International/questions/qa-choosing-language-tags (and others) in the good example, which complements the bad one.
What I can do is to include additional references:
- Language subtag registry: https://www.iana.org/assignments/language-subtag-registry/language-subtag-registry
- Picking the Right Language Identifier: http://cldr.unicode.org/index/cldr-spec/picking-the-right-language-code
Would that work for you?
Jan
DavidFatDavidF
At https://github.com/GALAglobal/TAPICC/tree/master/docs/T1/WG3/wd01/extraction_examples/language_tags it is mentioned that using simplified language tags is bad. That is an incorrect assumption.
Identifying language variants is not always necessary or desirable. There are some languages that are used mainly in one country, like Japanese for example and providing the country is redundant.
In most cases, "ja" is enough for Japanese and "ja-JA" is simply redundant. Same thing happens with many other languages.
As indicated by W3.org:
Always bear in mind that the golden rule is to keep your language tag as short as possible. Only add further subtags to your language tag if they are needed to distinguish the language from something else in the context where your content is used.
Check https://www.w3.org/International/questions/qa-choosing-language-tags