[bug #65973] xgettext: Comment at or before ... is not UTF-8 encoded. Program terminates

[Bruno Haible]

Update of bug #65973 (group gettext):

                Category:        Translator tools => Programmer tools       
                  Status:                    None => Not a Bug              
             Assigned to:                    None => haible                 
             Open/Closed:                    Open => Closed                 

    _______________________________________________________

Follow-up Comment #1:

In 2005, I would have recommended that you split the xgettext invocation into
several invocations: one invocation for the source files in UTF-8 encoding,
one invocation for the source files in ISO-8859-1 encoding, one invocation for
the source files in GBK encoding, and so on, plus at the end one more xgettext
invocation that combines these partial .pot files.

But we are now past the year 2020, and UTF-8 is well supported by all
programming tools. Therefore I would recommend that you convert your sources
to UTF-8.

> because of multilingual team that have been working for the same project for
many years.

Multilingual support, nowadays, is best achieved by using UTF-8 everywhere.
Having different files in different encodings only leads to extra complexity.
The rest of the world has already abandoned this extra complexity and is using
the simpler approach.


    _______________________________________________________

Reply to this item at:

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

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

signature.asc
Description: PGP signature