On Sat, Sep 27, 2014 at 3:13 PM, Ramiro Morales <[email protected]> wrote:
> > I wonder if this also has implications for checking whether a given > > locale is present on the system. It looks to me like we also do this > > case-sensitively right now, but we should do it case-insensitively. This > > might be a bit of work, since it would mean that rather than just > > checking for the existence of a particular locale directory as we do > > now, we would need to read in all the available locale names into memory > > (presuming we can't/don't want to enforce that all locales on disk are > > lower-cased or whatever). > > The names of directories with translations on disk are actually GNU > gettext locale names[1] as opposed to language names[1] (the ones in > the Accept-Language HTTP header and discussed above.) It does specify that the part after the underscore separator must be a > ISO 3166 country code. See [2] and [3]. > > So, for me, this indicates Django current behavior with these file > system dir names is correct. But perhaps I'm missing something? I guess it is "correct", meaning that all software/frameworks I know do use case-sensitive filenames. BCP47 suggests consistency as well [1]: "Although case distinctions do not carry meaning in language tags, consistent formatting and presentation of language tags will aid users." Regarding the names themselves, BCP47 has been gaining ground and IMHO it handles language names a bit better. But that is not a reason to change anything. Regards, Apostolis [1]: http://tools.ietf.org/html/bcp47 -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAEa3b%2Bp6TW4oETt7nhVtAPXfj9eRQHRMt8GvOmDYz1ERjQ42_w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
