On Tue, Sep 30, 2008 at 08:22:35PM -0700, Russ Allbery wrote: > You got it exactly right. Basically, podlators has been papering over > this bug incorrectly, but in a way that happens to do the right thing with > a common POD problem.
> So if you're using UTF-8, starting the POD with: > > =encoding UTF-8 > > is required. If you add that, the current version of Pod::Man (and > previous versions, as it turns out, mostly by chance) will do the right > thing. 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'm leaning on reverting that and reopening #492037 until the issue is sorted out in Pod-Perldoc upstream. Adding a way to enable or disable the '--utf8' option on the perldoc command line is one possibility, but it might as well cause even further trouble if upstream chooses a different implementation. -- Niko Tyni [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
