Bugzilla – Bug 313357
monoresgen produces invalid PO files
Last modified: 2007-09-15 21:24:23 UTC
---- Reported by bruno@clisp.org 2003-12-12 09:41:32 MST ---- Description of Problem: monoresgen produces invalid PO files. Steps to reproduce the problem: Install mono-0.28 and gettext >= 0.11.5. Store hello1.de.resx (attached). $ monoresgen hello1.de.resx de.po $ cat de.po $ msgcat de.po Actual Results: $ cat de.po msgid "Hello World!" msgstr "Hallöchen Welt!" $ msgcat de.po msgcat: input file `de.po' doesn't contain a header entry with a charset specification Expected Results: $ cat de.po msgid "" msgstr "" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" msgid "Hello World!" msgstr "Hallöchen Welt!" $ msgcat de.po msgid "" msgstr "" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" msgid "Hello World!" msgstr "Hallöchen Welt!" How often does this happen? Reproducible. Additional Information: The PO file format is specified in the GNU gettext documentation, section 'PO Files' and 'Header Entry'. A PO file with non-ASCII characters needs a header entry, to specify the encoding of the PO file. ---- Additional Comments From bruno@clisp.org 2003-12-12 09:42:25 MST ---- Created an attachment (id=165300) hello1.de.resx (german resource source code) ---- Additional Comments From gonzalo@ximian.com 2003-12-12 13:13:38 MST ---- Fixed in CVS. Imported an attachment (id=165300) Unknown bug field "cf_version_details" encountered while moving bug <cf_version_details>mono 0.28</cf_version_details> Unknown operating system SUSE 9.0. Setting to default OS "Other".