Hi! On Mon, 2020-05-18 at 22:12:04 +0200, Martin Quinson wrote: > ----- Le 18 Mai 20, à 18:58, Guillem Jover guil...@debian.org a écrit : > > Package: po4a > > Version: 0.58.1 > > Severity: normal
> > When there is a closing parenthesis at the end of line, po4a parses it > > and injects two spaces in the msgid text. I've noticed this when > > reviewing the generated «.po» files from both troff and POD source. > > > > Here's a test case: > > > > ,--- test.pod --- > > =head1 NAME > > > > test - some test > > > > =head1 DESCRIPTION > > > > Some B<text>(5) > > some other (parenthetical text) > > which produce (only when at the end of line) double spacing, > > in the generated (.po) > > file. > > `--- > > > > ,--- sh --- > > $ po4a-gettextize -f pod -m test.pod > > […] > > #. type: textblock > > #: test.pod:7 > > msgid "" > > "Some B<text>(5) some other (parenthetical text) which produce (only when > > " > > "at the end of line) double spacing, in the generated (.po) file." > > msgstr "" > > `--- > > > > Of course one problem that fixing this is that it will imply probably > > tons of fuzzying, which might even flip-flop depending on the po4a > > version used, so perhaps an explicit option would be required here to > > control the behavior, not sure. :/ > actually, the POD parser in po4a is implemented with a third party > library. I cannot do anything unless I completely reimplement the > parser myself. But this affects also the man parser, so I assumed this would be a problem with po4a itself, otherwise I'm happy to get this reassigned to perl, as Pod::Parser seems to the external module used? Here's the equivalent man test case: ,-- test.man --- .TH test 5 "2020-05-19" "1.0" "test case" .SH NAME test \- some test .SH DESCRIPTION Some \fBtext\fP(5) some other (parenthetical text) which produce (only when at the end of line) double spacing, in the generated (.po) file. `--- ,--- sh --- $ po4a-gettextize -f man -m test.man […] #. type: Plain text #: test.man:9 msgid "" "Some B<text>(5) some other (parenthetical text) which produce (only when " "at the end of line) double spacing, in the generated (.po) file." msgstr "" `--- > I would rather advise to use asciidoc for a newly written documentation. > I'm considering converting the po4a doc to this format, actually. For more complex documentation asciidoc would also be my preference. But for man pages I think POD is fairly adequate, in terms of format complexity, availability and dependency weight. For dpkg there's also the additional constraint of not wanting to have to require new stuff, and perl is already a build dependency. :) Thanks, Guillem
