Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.bugs.dist > #1200787

Bug#1072643: Po4a needs to announce stricter parsing of config files

From Martin Quinson <Martin.Quinson@ens-rennes.fr>
Newsgroups linux.debian.bugs.dist
Subject Bug#1072643: Po4a needs to announce stricter parsing of config files
Date 2024-06-13 15:00 +0200
Message-ID <IOSdz-2EMv-3@gated-at.bofh.it> (permalink)
References (2 earlier) <IOOCZ-2Cfy-5@gated-at.bofh.it> <ILMHo-EWO-11@gated-at.bofh.it> <IOPz3-2CXU-13@gated-at.bofh.it> <ILMHo-EWO-11@gated-at.bofh.it> <IOPz3-2CXU-13@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


[Multipart message — attachments visible in raw view] - view raw

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

Back to linux.debian.bugs.dist | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Bug#1072643: Po4a needs to announce stricter parsing of config files Helge Kreutzmann <debian@helgefjell.de> - 2024-06-13 11:10 +0200
  Bug#1072643: Po4a needs to announce stricter parsing of config files Santiago Vila <sanvila@debian.org> - 2024-06-13 12:10 +0200
    Bug#1072643: Po4a needs to announce stricter parsing of config files Martin Quinson <Martin.Quinson@ens-rennes.fr> - 2024-06-13 15:00 +0200
      Bug#1072643: Po4a needs to announce stricter parsing of config files Helge Kreutzmann <debian@helgefjell.de> - 2024-06-23 11:30 +0200

csiph-web