compile-messages.py parse error for utf-8 files with signature

[Wonlay]

If your po files are saved in utf-8 encoding with byte order marks, the compile-messages.py will fails with:
LC_MESSAGES/django.po:1:2: parse error
msgfmt: found 1 fatal error

Maybe we can remove the byte order marks before running msgfmt.

[Wonlay]

My patch create a temp file for the .po file, if the file has the unicode byte order marks.
And, generate the .mo file from the tmp file.

[Malcolm Tredinnick]

This patch is massive overkill. PO files for Django must be saved as UTF-8, so that is the only thing you need to worry about.

What broken piece of software is including a BOM when saving in UTF-8 format anyway? It's totally redundant. I'd probably prefer that we just say people should save things without the BOM so that we can just use the tools correctly, rather than having to work around oddities in particular external programs. It's very annoying to have to work around something that just adds extra bytes out the front of a file for precisely no added benefit.

[Ramiro Morales]

Patch implementing requirements outlined by Malcom

[Ramiro Morales]

I've just uplaoded a patch that implements rejection of .po files that contain a BOM and adds a note documenting that behavior to the relevant section of i18n docs.

[James Bennett]

UTF-8 with a BOM is, as far as I know, so rare that there's probably no urgent need to deal with it in Django.

[Ramiro Morales]

(In [14126]) [1.2.X] Fixed #6073 -- Made compilemessages 18n management command reject PO files with BOM.

Backport of [14125] from trunk

[Jacob]

Milestone 1.3 deleted