bad encoding in django.po french file

[fredz@…]

django/conf/locale/fr/LC_MESSAGES/django.po
line 15 :
should have "Content-Type: text/plain; charset=UTF-8\n"
instead of "Content-Type: text/plain; charset=ISO-8859-1\n"

the django.mo file should be rebuild

[Ramiro Morales]

Hi fredz,

What's the reason of this suggestion?. I ask because I maintain the Agentinean spanish transalation and so far they are coded and tagged as ISO-8859-1 (inherited from the generic Spanish transalation). Is there anything in the Django documentation that suggest/mandates this?.

I'm no opposing the idea, I just want to know so I can change es_AR message catalogs to UTF-8 too if necessary.

A quick overview of the charset headers of some European language django.po files now (SVN revision 3083):

lang	charset
cs	utf-8
cy	utf-8
da	utf-8
de	iso-8859-1
es	iso-8859-1
fr	iso-8859-1
it	utf-8
nl	utf-8
pl	utf-8

[fredz <fredz@…>]

In fact, the file fr/LC_MESSAGES/django.po is utf-8 encoded but has a iso-latin header !
You are right, it would be better to translate django.po in iso-latin.
I can do it if you want, but I have no access

[fredz <fredz@…>]

po file converted to iso-8859-1

[fredz <fredz@…>]

corresponding mo file (msgfmt -o django.mo django.po)

[Ramiro Morales]

Fredz,

It seems Django (or more correctly the gettext tools) doesn't enforce any charset. From ​http://www.djangoproject.com/documentation/i18n/#message-files:

-x8-
Mind your charset

When creating a .po file with your favorite text editor, first edit the charset line (search for "CHARSET") and set it to the charset you'll be using to edit the content. Generally, utf-8 should work for most languages, but gettext should handle any charset you throw at it.
-8x-

So it IMHO this ticket can be closed. If you read this and agree please do so.

Regards,

[hugo]

in the spirit of "do the least possible damage by doing the least possible work" ;-) - I just changed the charset denotation in the file to utf-8, as the file itself is utf-8.

[hugo]

(In [3090]) fixed #2090: fixed bad charset header in po file