Django: Ticket #11787: additional fieldshttps://code.djangoproject.com/ticket/11787
<p>
I wonder if the following fields do not belong here, too:
</p>
<ul><li>money sign (printable and iso) =&gt; EUR and €
</li><li>money format (even negative)
</li><li>number format (even negative)
</li><li>date format(s)
</li><li>timezones available in the country
</li></ul><p>
maybe even:
</p>
<ul><li>country names in local language
</li><li>international phone number prefixes
</li></ul>en-usDjangohttps://www.djangoproject.com/s/img/site/hdr_logo.gifhttps://code.djangoproject.com/ticket/11787
Trac 1.2Russell Keith-MageeWed, 03 Feb 2010 14:12:22 GMTstatus changed; resolution sethttps://code.djangoproject.com/ticket/11787#comment:1
https://code.djangoproject.com/ticket/11787#comment:1
<ul>
<li><strong>status</strong>
changed from <em>new</em> to <em>closed</em>
</li>
<li><strong>resolution</strong>
set to <em>wontfix</em>
</li>
</ul>
<p>
I'm going to mark this wontfix, on the basis that the valid choices for these fields aren't something we can really specify on a universal basis - for example, what choices should Django make available for a "MoneySignField"? $ + €? Should we differentiate between AU $ and US $ and CA $ and NZ $ and HK $? What about Rupees? Baht?
</p>
<p>
This is something that should be determined on a per-project basis, and it isn't so hard to implement that putting it in Django will save that much effort.
</p>
Ticket