On Wed, Oct 01, 2008 at 11:26:23AM -0700, Russ Allbery wrote: > Niko Tyni <[EMAIL PROTECTED]> writes: > > >> 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) ? > > Sorry, I meant only the pod2man --utf8 change in perldoc. I think that > the behavior of pod2man, while not ideal, is still basically okay for > lenny, although I'll be releasing a new version of podlators that will > implement the changes described in my previous mail.
Thanks, we're on the same page then. I'll revert the perldoc change. Does this documentation patch for lenny look OK to you? (I suppose it should be duplicated in pod2man.PL too.) diff --git a/lib/Pod/Man.pm b/lib/Pod/Man.pm index 961171b..a3eac5a 100644 --- a/lib/Pod/Man.pm +++ b/lib/Pod/Man.pm @@ -1592,6 +1592,13 @@ 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 using this option currently only works properly on UTF-8 +encoded POD files that use the C<=encoding> POD command. If the option +is enabled 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. +This is a bug that will be fixed in later versions. + =back The standard Pod::Simple method parse_file() takes one argument naming the @@ -1627,6 +1634,9 @@ invalid. A quote specification must be one, two, or four characters long. =head1 BUGS +As mentioned earlier in this document, the C<utf8> option is currently +broken on non-UTF-8 input. + There is currently no way to turn off the guesswork that tries to format unmarked text appropriately, and sometimes it isn't wanted (particularly when using POD to document something other than Perl). Most of the work -- Niko Tyni [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
