On Fri, Dec 10, 2021 at 11:28:57AM +0000, Marco Ciampa wrote:
> This string:
>
> #. type: textblock
> #: lib/Locale/Po4a/Xml.pm:68
> msgid ""
> "By default, Processing Instructions (i.e., C<<? ... ?>> tags) are handled as
> "
> "inline tags. Pass this option if you want the PI to be handled as breaking "
> "tag. Note that unprocessed PHP tags are handled as Processing Instructions "
> "by the parser."
Perhaps I'm missing something here, but it seems to me that it's the docs
sources that are wrong here since perldocs gives the same wrong results:
perldoc Locale::Po4a::Xml
break-pi
By default, Processing Instructions (i.e., "<? ... ?"> tags) are
handled as inline tags. Pass this option if you want the PI to be
handled as breaking tag. Note that unprocessed PHP tags are handled
as Processing Instructions by the parser.
(translated)
man Locale::Po4a::Xml
break-pi
Per impostazione predefinita, le istruzioni di elaborazione (ovvero
i tag "<? ... ?">) vengono gestite
come tag in linea. Passare questa opzione se si vuole che il PI
venga gestito come tag di rottura. Si noti
che i tag PHP non elaborati vengono gestiti come istruzioni di
elaborazione dall'analizzatore.
(untranslated)
export LANG=en
man Locale::Po4a::Xml
break-pi
By default, Processing Instructions (i.e., "<? ... ?"> tags) are
handled as inline tags. Pass this option if you want the PI to be
handled as breaking tag. Note that unprocessed PHP tags are
handled as Processing Instructions by the parser.
so it seems to me that po4a is right, it's the module docs that are wrong
here... am I right?
Changing the source string from this:
"By default, Processing Instructions (i.e., C<<? ... ?>> tags) are handled as "
to this:
By default, Processing Instructions (i.e., C<E<lt>? ... ?E<gt>> tags) are
handled as "
seems to fix it both in perldoc and in po4a translations.
May I commit the fix here (and wherever I find similar issues)?
--
Saluton,
Marco Ciampa
_______________________________________________
Devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
