Hello Martin,
Am Thu, Jun 13, 2024 at 02:54:15PM +0200 schrieb Martin Quinson:
> Le jeudi 13 juin 2024 à 12:07 +0200, Santiago Vila a écrit :
> > Hi. I'm reading the upstream NEWS file and found this:
> > 
> >   * Greatly simplify the code by using PerlIO instead of messing up
> >     with encodings manually.
> >   * This is a very intrusive change, and even if all tests of our
> >     comprehensive suite pass, I still expect issues with this on some
> >     corner cases, such as projects not using UTF-8 but a mixture of
> >     encodings. Please report any issue, and accept my apologies.
> > 
> > Simple question: Am I right to think that the problem happens
> > when a .po file is encoded using a given charset but declares
> > (in the charset= line) another different charset?
> 
> By definition, I fixed all the known issues, but I'm not confident with corner
> cases that are less tested. I mean that I don't know where the remaining issue
> will come from.
> 
> Checking on the code about your question, if the charset=??? line does not
> match the provided charset, the file is re-read with the charset from the file
> (with a warning). That should be OK (and I never heard of issues here).
> 
> We have some issues when the msgid contain UTF chars, but they are related to
> gettext, not po4a itself. https://savannah.gnu.org/bugs/?65104
> 
> In addition, I tried to draft the information I'll add to the README.Debian
> here: https://github.com/mquinson/po4a/blob/master/NEWS#L14
> 
> Your advice about it is very welcome, please.

I think for README.Debian this is fine, but maybe you can add a NEWS
file as well, something like:

--- snip --- snip -- snip ---

Po4a (since version 0.70) is more strict about encoding issues. If you
experience trouble with translations, read README.Debian for more
information and double check all encondings used in PO files.

You also might want to consider converting legacy encodings to UTF-8.

--- snip --- snip -- snip ---

You might of course drop the last sentence, but I think legacy
encoding should be phased out in 2024 whereever possible.

Maybe you could upload 0.73 to Debian with such a NEWS (and
README.Debian) in the next days?

Greetings

             Helge
-- 
      Dr. Helge Kreutzmann                     deb...@helgefjell.de
           Dipl.-Phys.                   http://www.helgefjell.de/debian.php
        64bit GNU powered                     gpg signed mail preferred
           Help keep free software "libre": http://www.ffii.de/

Attachment: signature.asc
Description: PGP signature

Reply via email to