GNU gettext - Bugs: bug #18345, msgfmt fails with UTF-8 encoded...
You are not allowed to post comments on this tracker with your current authentication level.
bug #18345: msgfmt fails with UTF-8 encoded files start start with a BOM
Submitter: | None | ||
Submitted: | Wed 22 Nov 2006 09:55:35 AM UTC | ||
Category: | Translator tools | Severity: | 3 - Normal |
Item Group: | None | Status: | Not a Bug |
Privacy: | Public | Assigned to: | haible |
Open/Closed: | Closed |
Wed 29 Aug 2007 10:52:55 PM UTC, comment #1: |
Bruno Haible <haible> |
Wed 22 Nov 2006 09:55:35 AM UTC, original submission:
The msgfmt utility fails when the .po file it is passed is encoded in UTF-8 and starts with a UTF-8 Byte-Order-Mark.
|
Anonymous |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 5 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2016-11-26 | haible | Category | None | Translator tools | |
2008-03-06 | haible | Status | Invalid | Not a Bug | |
2007-09-30 | haible | Open/Closed | Open | Closed | |
2007-09-02 | haible | Assigned to | None | haible | |
2007-08-29 | haible | Status | None | Invalid |
Powered by Savane 3.13-02a9.
Corresponding source code
The PO file format has a means for specifying the encoding
(through the 'charset' field in the header entry, see
http://www.gnu.org/software/gettext/manual/gettext.html#Header-Entry)
Therefore, an UTF-8 BOM must*not be used in these files, says
the RFC that defines UTF-8: see
http://www.faqs.org/rfcs/rfc3629.html section 6.
Therefore your PO file starting with an UTF-8 BOM is invalid.
Just like XML files starting with an UTF-8 BOM are invalid.