Opened 5 months ago

Closed 5 months ago

Last modified 5 months ago

#29018 closed Bug (invalid)

The 'E' date filter format should return lowercase months for Spanish

Reported by: Michael Terry Owned by: nobody
Component: Internationalization Version: master
Severity: Normal Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

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

Change History (3)

comment:1 Changed 5 months ago by Tim Graham

Resolution: invalid
Status: newclosed

Thanks for the report, however, translations are handled at Transifex rather than in this tracker. If a code change is needed instead of a translation update, please reopen this ticket with details.

comment:2 Changed 5 months ago 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

comment:3 Changed 5 months ago 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.

Note: See TracTickets for help on using tickets.
Back to Top