Django Language Code

[Rowena]

Currently, the built-in django i18n framework allows for languages with codes such as 'en', 'fr', etc. consistent with ISO 639 and 639-1. Given the rising popularity of this platform, however, this will not be sufficient for long. We recently developed a django application supporting Wolof, Pulaar, and Dyuola (three West African tribal language), none of which has a 2-letter language code.

For consistency and standard compliance, Django should support either the 2-letter ISO 639-1 stanard OR ISO 639-2 and 639-3 for specifying the language of i18n.

[Alex Gaynor]

This represents a large new feature/change and thus isn't in scope for 1.1.

[Ramiro Morales]

Can you point specific places where Django isn't working with this?. Our parsing of the Accept-Language HTTP header complies with the eight characters max. as dictated by RFC2616 and in other places we split locale specificacions by '-' or '_' without imposing any two-letter limit.

Have you tried creating a translation to a locale with a long name and found issues?. Even better, can you contribute (the beginnings of) a Django translation to such a language?. It would greatly help as a test bench of this.

[Russell Keith-Magee]

I just tried a microtranslation for Klingon (ISO639-2 code 'tlh'), and it worked fine. If you can provide a specific reason why you can't provide an ISO639-2 translation, or why ISO639-2 translations can't sit alongside ISO639-1 translations, please reopen.