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