2008/1/19, Amed Çeko Jiyan amedcj@gmail.com:
- As Frederik says, we use "kmr" for Kurmanji and "ckb" for Sorani. We use
these codes in GNOME and some other projects.
- you are right, "ku" is not a country code. We can not ku_KU in any
projects. SO we use ku_TR for some projects. Why projects need country code? Do countries support projects? No. It would be great to use only language codes for all projects.
Languages don't support projects either - people who speak/read/write them do. :p But country is good for stuff like Portuguese/Brazillian Portuguese and American/English/Irish/Australian/Canadian/South African/... English, where there's little argument that it's the same language and just varying dialects. (A language/locale code can also be written like en-GB-LONDON, if one wants to be that specific, though there are some more guidelines with regards to that. Check RFC 4646, which Gabor linked to, for more on this.)
A funny thing in relation to this is Norwegian, which has *3* ISO 639 2-letter codes: no, nb, and nn. The first (no) being generic Norwegian, which could mean either nb or nn, and the two latter (nb and nn) are, respectively, Bokmål and Nynorsk. But that's a completely different situation that you should research for yourself. One of those little amusing things in linguistics (IMHO). =)
As you see from Kurdish Google, iso639 2 makes problems for us. It would be better to use "kmr" and "ckb"
That is good Drupal will use iso639 3.
When I was inquiring about starting the Scots translation (which I still have to get out of the vapor ware state...), I'm pretty sure I was told it wouldn't be a problem to use "sco" (there isn't really any alternative code I could use), so I'm guessing that it shouldn't be a problem here either. But I am by no means an authority on Drupal's relations to ISO 639 codes, so, yeah. :)