10:43 a.m.
Hi,
The Polish man pages generated from POD are unreadable, e.g. (from
Locale::PO4A::Man(3), please also note its strange header, but this
is another problem):
_build::pod::3::pUseriC_build::pod::3::pl::lib::Locale::Po4a::Man(3)
NAZWA
Locale::Po4a::Man - Konwersja stron podrAeXcznika z/do
plikA~Xw PO
OPIS
Celem projektu po4a ("po for anything") jest uAaXatwienie
tAaXumaczeAaX (oraz, co ciekawsze, zarzAeXdzania
tAaXumaczeniami) przy uAaXyciu narzAeXdzi gettext w tych
obszarach, gdzie nie byAaXy uAaXywane, jak na przykAaXad w
obszarze dokumentacji.
The problem seems to be caused by po4a-build not passing --utf8 to
pod2man, and by po4a, which doesn't include any `==encoding' line in
translated PODs.
I was able to work-around this in po4a-build by defining a following
simple pod2man function there, and then rebuilding po4a:
pod2man()
{
i=`expr $# - 1`
file=`eval echo '$'$i`
case $file in
*_build*)
sed -e '1,/=head1/s/=head1/=encoding
UTF-8\n\n&/' $file > $file.tmp
cp $file.tmp $file
/usr/bin/pod2man --utf8 "$@"
;;
*)
/usr/bin/pod2man "$@"
;;
esac
}
Regards,
robert
12:23 p.m.
New subject: [Po4a-devel] Polish man pages broken again in po4a 0.37
On Sun, 22 Nov 2009 17:43:25 +0100
Robert Luberda <robert(a)debian.org> wrote:
The Polish man pages generated from POD are unreadable, e.g. (from
Locale::PO4A::Man(3)
Why is the utf-8 switch optional in your patch? Is there a problem with
using UTF-8 by default for all builds? If there is, then relying on a
mystery directory containing _build isn't going to be a usable solution.
I can make it a configuration setting in the po4a-build.conf file - the
question is which way should it default? UTF-8 on or off?
, please also note its strange header, but this
is another problem):
_build::pod::3::pUseriC_build::pod::3::pl::lib::Locale::Po4a::Man(3)
That's something else to fix in po4a - it doesn't go wrong with the
untranslated manpage.
Possibly a bug in pod2man, when generating the .IX and .TH ?
.IX Title "Locale::Po4a::BibTeX 3"
.TH Locale::Po4a::BibTeX 3 "2009-11-22" "perl v5.10.1" "User
Contributed Perl Documentation"
Looks like the appearance of 'pl' in the middle, breaks some reg exp
that pod2man uses to build the .IX.
--
Neil Williams
=============
http://www.data-freedom.org/
http://www.linux.codehelp.co.uk/
http://e-mail.is-not-s.ms/
4:40 p.m.
New subject: [Po4a-devel] Polish man pages broken again in po4a 0.37
Hi,
On Sun, Nov 22, 2009 at 06:23:05PM +0000, codehelp(a)debian.org wrote:
On Sun, 22 Nov 2009 17:43:25 +0100
Robert Luberda <robert(a)debian.org> wrote:
> The Polish man pages generated from POD are unreadable, e.g. (from
> Locale::PO4A::Man(3)
Why is the utf-8 switch optional in your patch? Is there a problem with
using UTF-8 by default for all builds? If there is, then relying on a
mystery directory containing _build isn't going to be a usable solution.
I committed a change for the Pod module that adds the =encoding line
automatically (or let's say in a more reliable way).
It used to be only based on the -L option. Now it also takes into account
the encoding of the PO file (the same algorithm is used to define the
output document encoding).
I can make it a configuration setting in the po4a-build.conf file -
the
question is which way should it default? UTF-8 on or off?
I would propose to use the --utf8 option by default.
This might be a problem on the build machines without a recent pod2man.
This might also be an issue for the users of the generated manpages if
they have an old 'man' command.
I would propose to have a --man-no-utf8 option (this could be use for
setting options to the POD or MAN modules)
>, please also note its strange header, but this
> is another problem):
>
> _build::pod::3::pUseriC_build::pod::3::pl::lib::Locale::Po4a::Man(3)
That's something else to fix in po4a - it doesn't go wrong with the
untranslated manpage.
Possibly a bug in pod2man, when generating the .IX and .TH ?
It might be a pod2man bug. Looking at the --name option, it should strip
out the path prefix if the file ends with .pm (actually, I'm not sure it
is the case).
The attached patch should fix this.
In the previous releases, the --center title was also set to avoid the
"User Contributed Perl Documentation" title.
This could be fixed with two options in the config file
PODCENTERTITLE="Po4a Tools"
PODCENTERPODIR="po/pod"
Best Regards,
--
Nekral
10:25 a.m.
New subject: [Po4a-devel] Polish man pages broken again in po4a 0.37
On Sun, 22 Nov 2009 23:40:44 +0100
Nicolas François <nicolas.francois(a)centraliens.net> wrote:
I committed a change for the Pod module that adds the =encoding line
automatically (or let's say in a more reliable way).
It used to be only based on the -L option. Now it also takes into
account the encoding of the PO file (the same algorithm is used to
define the output document encoding).
With that change, is there any need for po4a-build to do anything with
utf-8?
> I can make it a configuration setting in the po4a-build.conf
file -
> the question is which way should it default? UTF-8 on or off?
I would propose to use the --utf8 option by default.
This was only for the workaround originally devised by Robert. The fix
in po4a supersedes that change.
In the previous releases, the --center title was also set to avoid the
"User Contributed Perl Documentation" title.
This could be fixed with two options in the config file
PODCENTERTITLE="Po4a Tools"
PODCENTERPODIR="po/pod"
The config file isn't translated, I'm not sure where to put the string
as marked up for translation, other than possibly using an existing
string within the POD and POT. It's a bit like the "translator-credits"
special string in compiled languages. The string to be replaced by
eval_gettext would already have to exist in the POT and PO files.
In our case, "Po4a Tools" is translated. I'll extend this to allow
arbitrary options to pass to po4a and pod2man. Wishlist bug filed as a
reminder for me.
--
Neil Williams
=============
http://www.data-freedom.org/
http://www.linux.codehelp.co.uk/
http://e-mail.is-not-s.ms/
11:15 a.m.
New subject: [Po4a-devel] Polish man pages broken again in po4a 0.37
On Mon, 23 Nov 2009 16:25:27 +0000
Neil Williams <codehelp(a)debian.org> wrote:
> I committed a change for the Pod module that adds the =encoding
line
> automatically (or let's say in a more reliable way).
> It used to be only based on the -L option. Now it also takes into
> account the encoding of the PO file (the same algorithm is used to
> define the output document encoding).
With that change, is there any need for po4a-build to do anything with
utf-8?
Forget that, I've done some testing (thanks to Robert's example) and
I'll fix this issue in my next commit.
> > I can make it a configuration setting in the
po4a-build.conf file
> > - the question is which way should it default? UTF-8 on or off?
>
> I would propose to use the --utf8 option by default.
OK. With so few packages using po4a-build right now, I think I'll put
the default in place for 0.37.1 and make it configurable along with the
support for other options to pass to po4a or pod2man.
With that change, are we OK for me to release 0.37.1 tonight?
--
Neil Williams
=============
http://www.data-freedom.org/
http://www.linux.codehelp.co.uk/
http://e-mail.is-not-s.ms/
2:39 p.m.
New subject: [Po4a-devel] Polish man pages broken again in po4a 0.37
Nicolas François writes:
On Mon, Nov 23, 2009 at 05:15:46PM +0000, codehelp(a)debian.org wrote:
> With that change, are we OK for me to release 0.37.1 tonight?
Yes.
Hi,
I've just updated my working copy from CVS, rebuilt and the Polish pages
looks perfect. Many thanks for fixing the issue!
However there's a minor problem with UTF8-encoded names appearing in
original PODs, see Locale::Po4a::Xhtml(3) for example:
English version:
AUTHORS
Yves RA~XtschlA~X <po4a(a)rutschle.net>
Nicolas FranA~Xois <nicolas.francois(a)centraliens.net>
Polish version:
AUTORZY
Yves Rütschlé <po4a(a)rutschle.net>
Nicolas François <nicolas.francois(a)centraliens.net>
For the English version this is most probably caused by missing
=encoding line in the original POD. I've got no idea, why Polish
translation also got it wrong, the pl.po file seems to be correct:
# type: verbatim
#. type: verbatim
#: lib/Locale/Po4a/Xhtml.pm:81
#, no-wrap
msgid ""
" Yves Rütschlé <po4a(a)rutschle.net>\n"
" Nicolas François <nicolas.francois(a)centraliens.net>\n"
"\n"
msgstr ""
" Yves Rütschlé <po4a(a)rutschle.net>\n"
" Nicolas François <nicolas.francois(a)centraliens.net>\n"
"\n"
Regards,
robert
9:56 p.m.
New subject: [Po4a-devel] Polish man pages broken again in po4a 0.37
Hello,
On Mon, Nov 23, 2009 at 09:39:19PM +0100, robert(a)debian.org wrote:
However there's a minor problem with UTF8-encoded names appearing in
original PODs, see Locale::Po4a::Xhtml(3) for example:
English version:
AUTHORS
Yves RA~XtschlA~X <po4a(a)rutschle.net>
Nicolas FranA~Xois <nicolas.francois(a)centraliens.net>
Polish version:
AUTORZY
Yves Rütschlé <po4a(a)rutschle.net>
Nicolas François <nicolas.francois(a)centraliens.net>
For the English version this is most probably caused by missing
=encoding line in the original POD. I've got no idea, why Polish
translation also got it wrong, the pl.po file seems to be correct:
I've added the =encoding lines. This fixed the English version.
I added the detection of these =encoding lines in the Pod module so that
it is no more necessary to provide the input encoding (this works with XML
and POD file, but it would still be nice to be able to provide the input
encoding to po4a-build for the other format (Man could also be fixed)).
(Note: the file was wrongly detected as an ISO-8859-1 file, due to a
remaining of the processing of a previous file; this is also fixed)
So this should be fixed in the current repository.
Best Regards,
--
Nekral
4:37 p.m.
New subject: [Po4a-devel] Polish man pages broken again in po4a 0.37
Neil Williams writes:
Why is the utf-8 switch optional in your patch? Is there a problem with
using UTF-8 by default for all builds? If there is, then relying on a
mystery directory containing _build isn't going to be a usable solution.
Oh, it wasn't a real patch. It was my way of generating valid man pages
to check them before committing my translation update to repository.
The point of the switch is to catch only the generated files, but not
the original ones, to add the `=encoding UTF-8' line to them. I've added
the switch after my first attempt of working around the problem had
broken a lot of files in my local copy of po4a.
I can make it a configuration setting in the po4a-build.conf file - the
question is which way should it default? UTF-8 on or off?
If depends on the encoding of a document, and should be on when po4a
generates an UTF-8 file, and off otherwise. It shouldn't be very hard to
find out the encoding of translated documents, but the original,
English, documents might require a configuration option (I can bet such
an option would be off for most English documents).
I think the =encoding line should be added by po4a itself, not
po4a-build. Without such a line pod2man will never generate correctly
encoded UTF-8 man page, quoting pod2man(1):
Be aware that, when using this option, the input encoding
of your POD source must be properly declared unless it is
US-ASCII or Latin-1. POD input without an "=encoding"
command will be assumed to be in Latin-1, and if it's
actually in UTF-8, the output will be double-encoded.
>
_build::pod::3::pUseriC_build::pod::3::pl::lib::Locale::Po4a::Man(3)
That's something else to fix in po4a - it doesn't go wrong with the
untranslated manpage.
Possibly a bug in pod2man, when generating the .IX and .TH ?
I've just found the following comment in /usr/share/perl/5.10.1/Pod/Man.pm:
#...... Lose
# anything up to the first off:
#
# */lib/*perl*/ standard or site_perl module
# */*perl*/lib/ from -Dprefix=/opt/perl
# */*perl*/ random module hierarchy
#
# .......
# and strip off an initial component of "lib" or "blib/lib" since
And po4a-build calls pod2man like this:
pod2man lib/Locale/Po4a/Text.pm _build/po4a/man/man3/Locale::Po4a::Text.3
for the original files, and accordingly to the above comment the initial
lib gets stripped, but for the translation the call is:
pod2man _build/pod/3/pl/lib/Locale/Po4a/Text.pm
_build/po4a/man/pl/man3/Locale::Po4a::Text.3
Looks like the appearance of 'pl' in the middle, breaks some reg exp
that pod2man uses to build the .IX.
Possibly changing pl to perl would be sufficient. OTOH you know the name
of the man page, why can't you use it and call e.g.:
pod2man -s 3 --name Locale::Po4a::Text other_args
Regards,
robert
9:57 a.m.
New subject: [Po4a-devel] Polish man pages broken again in po4a 0.37
On Sun, 22 Nov 2009 23:37:52 +0100
Robert Luberda <robert(a)debian.org> wrote:
>>
_build::pod::3::pUseriC_build::pod::3::pl::lib::Locale::Po4a::Man
>> (3)
>
And po4a-build calls pod2man like this:
pod2man lib/Locale/Po4a/Text.pm
_build/po4a/man/man3/Locale::Po4a::Text.3
Possibly changing pl to perl would be sufficient. OTOH you know the
name of the man page, why can't you use it and call e.g.:
pod2man -s 3 --name Locale::Po4a::Text other_args
Indeed. po4a-build does have that name.
Changed to:
pod2man -n $name -s 3 $BASEDIR/pod/3/$l/$file \
$BASEDIR/$POD/man/$l/man3/$name.3
$l == language code, like 'pl'.
Gives:
pod2man -n Locale::Po4a::Wml -s 3 \
_build/pod/3/pl/lib/Locale/Po4a/Wml.pm \
_build/po4a/man/pl/man3/Locale::Po4a::Wml.3
Gives a manpage containing, e.g.:
Locale::Po4a::BibTeX(3) User Contributed Perl Documentation
Locale::Po4a::BibTeX(3)
This is only needed for man (3).
--
Neil Williams
=============
http://www.data-freedom.org/
http://www.linux.codehelp.co.uk/
http://e-mail.is-not-s.ms/
5474
days inactive
5509
days old
9 comments
3 participants
participants (3)
-
Neil Williams -
Nicolas François -
Robert Luberda