-=| Louis Bettens, 20.09.2013 22:21:54 +0200 |=- > Howdy perl group! [added to cc]
> That's because of a unicode character in a proper name. I tried
> adding a "=encoding utf8" line and it solved the problem. Patch
> coming.
> This only seems to happen in the latest versions because I had to
> run "pbuilder update" in order to reproduce the bug. Did pod2man get
> more severe lately?
Yes. Perl 5.18 and accompanying POD modules became more strict.
> Note that on my system, the resulting man page has accents
> flattened, that is to say ö becomes oe and ù becomes u.
That's expected. See pod2man(1):
-u, --utf8
By default, pod2man produces the most conservative possible *roff
output to try to ensure that it will work with as many different
*roff implementations as possible. Many *roff implementations
cannot handle non-ASCII characters, so this means all non-ASCII
characters are converted either to a *roff escape sequence that
tries to create a properly accented character (at least for troff
output) or to "X".
This option says to instead output literal UTF-8 characters. If
your *roff implementation can handle it, this is the best output
format to use and avoids corruption of documents containing non-
ASCII characters. However, be warned that *roff source with
literal UTF-8 characters is not supported by many implementations
and may even result in segfaults and other bad behavior.
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. See perlpod(1) for more information on the
"=encoding" command.
Thanks for the quick fix!
dam
signature.asc
Description: Digital signature
