-
Notifications
You must be signed in to change notification settings - Fork 315
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Inconsistent ISO Codes #941
Comments
Weird bonus facts I learned researching this: * The 15897 codes are essentially 3166-1 codes appended to 639-1 codes, and then the POSIX implementation of the standard uses ** The subdivision code for Catalonia is |
Thanks for the great investigation. I remember something like this was an issue back when #503 was being developed indeed, but as it never got finished, we never followed up either. I'm not sure I get the direction you're suggesting us to move to, though, but again I'm no expert in the mess that these language codes are. |
This explains why some of the codes were harder for me to find via Google than others, last time I was working on translations here. I forget which codes were the harder ones. +1 for choosing one system and sticking to it. @Foggalong any suggestions? |
If you want to use a standard then since it's languages using one of the two language based standards, 693-2 or 15897, would be the best bet; I don't know how likely it is there'd be a sudden influx of translations but those would be best for really future proofing. Honestly though, as you say, having a consistent system is the most important thing. Even if it's just grabbing a complete list of locales from somewhere else and using that as the reference for translators would help remove the inconsistency. |
I don't really like Sadly |
While digging around for #940 I found this very minor and very nerdy issue; the translation docs say
CODE
should be the 'short country code' but the actual values are a hodgepodge of four different systems (something again just inherited from the original project).sr
for Serbian (whose country code isrs
) orar
for Arabic (whose country code isma
).cz
for Czechia (whose language code iscs
) orkr
for South Korea (Korean's language code isko
).pt_br
,zh-cn
, andzh-tw
(though not consistently, e.g.en_gb
orko-kr
).* To complicate further, the filenames for these are just the 639-1 codes.cat
which is an ISO 639-2 code; the 639-1 code isca
and its ISO 3166-2 sub-division code ises-ct
.**None of the current translations clash, but it could happen if someone were to submit Argentine Spanish, Canadian French or English, anything from Suriname, etc. If it doesn't otherwise cause issues, I'd suggest maybe moving over to a locale-based coding system (epecially if it were being looked at as part of #503) but either way the documentation needs updating to reflect what option people should actually be using.
The text was updated successfully, but these errors were encountered: