On Sat, Aug 31, 2013 at 6:30 AM, Justin Hill <[email protected]> wrote:
> https://github.com/django/django/tree/master/django/conf/locale > > Does anyone have an idea as to why Australia doesn't have a locale format? > en_GB is there, but no en_CA, or en_AU. My code is in seven countries and > my forms are working in all of them except Australia and Canada. It's > looking for an en_AU format folder that doesn't exists and falling back to > the defaults. My users wonder why they can't enter dates in their native > date format. > > Translations are working for things that are different like US: 'zip > code', CA: 'postal code', AU: 'postcode' > > Same would apply to Canada en_CA. But they aren't complaining because > their date format matches the default yyyy-mm-dd. > > I'm going to go the route of making my own format file ( > https://docs.djangoproject.com/en/dev/topics/i18n/formatting/#creating-custom-format-files), > but just seems odd that this would be necessary for such well known > countries. > > Am I doing it wrong? > > Hi Justin, There's no conspiracy here - it's just a lack of contributors. Which, I grant, is ironic, given the number of core team members that are Australian :-) If you were to provide a patch that contained locale definitions for en_CA and en_AU, I suspect they'd get merged into trunk fairly quickly. Based on our current point in the release cycle, that would put the new locales in the 1.7 release. Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django users" 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-users. For more options, visit https://groups.google.com/groups/opt_out.
