Hello,

On Tue, May 19, 2020 at 01:53:05AM +0200, Guillem Jover wrote:
> 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 :
>
> > > 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.
[...]
> > 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?

Ahem, sorry, I read it too quickly earlier. In this case, I tend to
blame libtext-wrapi18n-perl but I'll have to do some more tests before
reassigning.

> > 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. :)

Ah. You mean you're not only translating the doc, you also want to
display it to the users? Ok, fair enough, I forgot about this little
detail :)

Thanks for your interest into po4a,
Mt.

-- 
La moitié des chercheurs passe son temps à remplir des demandes que
l’autre moitié perd beaucoup de temps à lire.   -- André Brahic

Attachment: signature.asc
Description: PGP signature

Reply via email to