Hi, On Sun, Nov 22, 2009 at 06:23:05PM +0000, 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). 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) 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

On Mon, 23 Nov 2009 16:25:27 +0000 Neil Williams <codehelp(a)debian.org&gt; wrote: Forget that, I've done some testing (thanks to Robert's example) and I'll fix this issue in my next commit. 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/

Nicolas François writes: 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&gt; Nicolas FranA~Xois <nicolas.francois(a)centraliens.net&gt; Polish version: AUTORZY Yves Rütschlé <po4a(a)rutschle.net&gt; Nicolas François <nicolas.francois(a)centraliens.net&gt; 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&gt;\n&quot; " Nicolas François <nicolas.francois(a)centraliens.net&gt;\n&quot; "\n" msgstr "" " Yves Rütschlé <po4a(a)rutschle.net&gt;\n&quot; " Nicolas François <nicolas.francois(a)centraliens.net&gt;\n&quot; "\n" Regards, robert

Neil Williams writes: 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. 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. 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 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