Our translation coordinator just flagged a regression for Spanish month names, which were previously lower-case (see https://code.djangoproject.com/ticket/7461) through 1.4.x:
https://github.com/django/django/blob/stable/1.4.x/django/conf/locale/es/LC_MESSAGES/django.po#L1080 and were converted to upper-case in 1.5: https://github.com/django/django/blob/stable/1.5.x/django/conf/locale/es/LC_MESSAGES/django.po#L1080 as part of a large commit which didn't appear to be linked to a ticket: https://github.com/django/django/commit/6ca475d540361090e8b28154ce5391de718d5c63 The question I had was whether it was intentional to convert both the default and "alt. month" contexts. In similar languages, we're using the alternate month when the date occurs in the middle of a phrase (e.g. "F j, Y" is translated to "j \d\e E, Y" but "F Y" is unmodified) so the month name is correctly capitalized at the start of a sentence but not when it's in the middle. Without the alternate versions, there appears to be no way to correctly format long dates without writing code or overriding the translated month names. Thanks, Chris -- You received this message because you are subscribed to the Google Groups "Django internationalization and localization" 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-i18n. For more options, visit https://groups.google.com/groups/opt_out.
