Hello Guillem, thanks for the report. I agree that we should move on to Pod::Simple. I started a discussion with the pod-people for guidance, but the ball seems to be on my side now. Too bad I cannot get it rolling right now :(
https://www.nntp.perl.org/group/perl.pod-people/2020/05/msg2106.html Any help would be really appreciated here... Thanks, Mt. On Fri, Jun 05, 2020 at 03:27:49AM +0200, Guillem Jover wrote: > Package: po4a > Version: 0.59.1-1 > Severity: normal > > Hi! > > The POD parser marks the format name in =begin/=for/=end tags as > translatable, but this text should not be translated as it is part of > the syntax. I've very briefly checked the po4a and Pod::Parser code > and didn't see an obvious way to handle this, but then realized that > Pod::Parser is being phased out in favor of Pod::Simple, which does > seem to support handling these tags explicitly. > > Here's a test case: > > ,--- format.pod --- > =head1 Title > > =begin format-block > > Some format-specific text. > > =end format-block > > Some B<POD> text. > > =for format-for More format-specific text. > `--- > > ,--- po4a-gettextize -f pod -m format.pod --- > […] > #. type: =head1 > #: format.pod:1 > msgid "Title" > msgstr "" > > #. type: =end > #: format.pod:3 format.pod:7 > msgid "format-block" > msgstr "" > > #. type: textblock > #: format.pod:5 > msgid "Some format-specific text." > msgstr "" > > #. type: textblock > #: format.pod:9 > msgid "Some B<POD> text." > msgstr "" > > #. type: =for > #: format.pod:11 > msgid "format-for More format-specific text." > msgstr "" > `--- > > Both «format-block» and «format-for» should not be appearing here. :) > > Thanks, > Guillem -- L'enseignement des résultats de la science n'est jamais un enseignement scientifique. -- Gaston Bachelard.
signature.asc
Description: PGP signature