On Wed, Oct 01, 2008 at 02:10:53AM -0700, Russ Allbery wrote: > Niko Tyni <[EMAIL PROTECTED]> writes: > > > Any estimate on how widespread this POD problem is? Is the hardcoded > > 'pod2man --utf8' in the Lenny perldoc going to cause more grief than > > it's worth?
> I looked at this some more, and there's a deeper problem. If you run the > current pod2man with --utf8 on an input POD file that doesn't declare an > =encoding of UTF-8, any use of S<> in that POD file will result in invalid > UTF-8, even if there's no use of high-bit characters in the input POD at > all. Thanks for the follow-up. I see the problem. sid% pod2man --utf8 /usr/share/perl/5.10/pod/perlrun.pod|iconv --from utf8 --to latin1 >/dev/null iconv: illegal input sequence at position 2097 > I think that for lenny you may want to back out of the --utf8 change and > give it some time to settle. Are you referring to backing out the whole Pod::Man update (#480997) or just the hardcoded 'pod2man --utf8' in perldoc (#492037) ? It looks to me like having the 'pod2man --utf8' option available in lenny, even if it's broken without '=encoding utf8', is OK, as long as it's not on by default. The pod2man manual page should probably be updated to note the issue. I think reverting just the perldoc change is the least disruptive choice for Lenny. -- Niko Tyni [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
