[Django] #29018: The 'E' date filter format should return lowercase months for Spanish
Django
------------------------------------------------+------------------------
Reporter: Michael Terry | Owner: nobody
Type: Bug | Status: new
Component: Internationalization | Version: master
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
------------------------------------------------+------------------------
Template code like the following:
{{ now|date:'E' }}
should return a month like "March" for English but "marzo" for Spanish (no
uppercase). I guess 'F' could continue to be uppercase. But 'E'
certainly should respect the locale preferences.
Wikipedia mentions this rule [1]. Apparently it's also on the Royal
Spanish Academy's site, but I'm not good enough at Spanish to navigate it.
Python's strftime('%B') uses lowercase in Spanish. So does python-babel
and similar projects. Even Django used to (and rejected a request to make
it uppercase in ticket:11173) before commit
6ca475d540361090e8b28154ce5391de718d5c63 in 2013 (which I suspect was a
mistake, but I didn't follow why those changes were made in the 1.5
branch).
I suspect the fix is to update the Spanish translation for all the "alt.
month" contexts to use lowercase.
[1] https://en.wikipedia.org/wiki/Date_and_time_notation_in_Spain
--
Ticket URL: <https://code.djangoproject.com/ticket/29018>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Django
Reporter: mikix | Owner: nobody
Type: Bug | Status: closed
Component: | Version: master
Internationalization |
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
Changes (by Tim Graham):
* status: new => closed
* resolution: => invalid
Comment:
Thanks for the report, however, translations are handled at
[https://docs.djangoproject.com/en/dev/internals/contributing/localizing/#translations
Transifex] rather than in this tracker. If a code change is needed instead
of a translation update, please reopen this ticket with details.
--
Ticket URL: <https://code.djangoproject.com/ticket/29018#comment:1>
Django
Reporter: Michael Terry | Owner: nobody
Component: | Version: master
Internationalization |
Severity: Normal | Resolution: invalid
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
Comment (by Michael Terry):
I've emailed the django-i18n list about this, in an attempt to discuss it
with the Spanish team. I couldn't find a specific list for just them.
https://groups.google.com/forum/#!topic/django-i18n/NzbFpJHtpfI
--
Ticket URL: <https://code.djangoproject.com/ticket/29018#comment:2>
Django
Reporter: Michael Terry | Owner: nobody
Component: | Version: master
Internationalization |
Severity: Normal | Resolution: invalid
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
Comment (by Ramiro Morales):
I've just fixed the es_AR translations on Transifex according to Michael
proposal and taking in account the regression introduced in 1.5. These
changes won't be visible to users until 2.1 gets released though.
--
Ticket URL: <https://code.djangoproject.com/ticket/29018#comment:3>