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. Mt
signature.asc
Description: This is a digitally signed message part
