Hello Guillem, actually, the POD parser in po4a is implemented with a third party library. I cannot do anything unless I completely reimplement the parser myself.
I would rather advise to use asciidoc for a newly written documentation. I'm considering converting the po4a doc to this format, actually. Sorry, Mt. ----- Le 18 Mai 20, à 18:58, Guillem Jover guil...@debian.org a écrit : > Package: po4a > Version: 0.58.1 > Severity: normal > > Hi! > > 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. :/ > > Thanks, > Guillem
