[bug #20923] msgen may produce a PO file with charset set to CHARSET

[Bruno Haible]

Update of bug #20923 (group gettext):

                  Status:               Confirmed => Fixed                  
             Open/Closed:                    Open => Closed                 
                 Summary: xgettext generates .pot files with charset set to
CHARSET => msgen may produce a PO file with charset set to CHARSET

    _______________________________________________________

Follow-up Comment #5:

It is OK that xgettext produces an ASCII-encoded .pot file with
charset=CHARSET, since it is the translator's choice which encoding to use for
this file. (Yes, still in 2024.) If xgettext would produce output with
charset=ASCII, this would cause trouble with the editor used by the
translator. If xgettext would produce output with charset=UTF-8 (but only
ASCII characters), it would be an undue restriction of choice for the
translator.

msgfmt still produces the warning:

en.po: warning: Charset "CHARSET" is not a portable encoding name.
                Message conversion to user's charset might not work.

and rightfully so, since the charset in the header entry is used for charset
conversion at run time.

Therefore, really, msgen needs to set ASCII as charset, just like 'msginit
--no-translator -l en' does.

Fixed through
https://git.savannah.gnu.org/gitweb/?p=gettext.git;a=commitdiff;h=eeab24002b569910c5d244435bd774f3cdeaed0b
.

(, , , )


    _______________________________________________________

Reply to this item at:

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

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

signature.asc
Description: PGP signature