[bug #65104] msgmerge fails to merge utf8 PO file against an iso-8859-1 POT file

[Bruno Haible]

Update of bug #65104 (group gettext):

                  Status:                    None => Answer Provided        
             Assigned to:                    None => haible                 
             Open/Closed:                    Open => Closed                 

    _______________________________________________________

Follow-up Comment #1:

Thanks for the report.

The problem is that iso8859.pot is used as a POT file, contains non-ASCII
characters, but is not in UTF-8 encoding.

Since, by https://www.gnu.org/software/gettext/manual/html_node/Creating.html,
a translator is supposed to be able to copy the POT file to a PO file and use
that as a starting point for her translation, the file ought to be in UTF-8
encoding. If it is in ISO-8859-1 encoding, how would e.g. a Bulgarian or
Chinese translator do this? Most likely she would produce mojibake, then
convert the POT file to UTF-8 and start over. Translators should not encounter
such hassles.

I am therefore adding an error message for this case, in
https://git.savannah.gnu.org/gitweb/?p=gettext.git;a=commitdiff;h=bd94293cc8ee0ba818cff4209ab4c4466c25189a
.

Your example will now produce this error message:

$ LC_ALL=C msgmerge utf8.po iso8859.pot 
msgmerge: iso8859.pot: The file contains non-ASCII characters but the present
charset "ISO-8859-1" is not UTF-8.




    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?65104>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/

signature.asc
Description: PGP signature