Skip Menu |

This queue is for tickets about the Pod-Perldoc CPAN distribution.

Report information
The Basics
Id: 26121
Status: resolved
Priority: 0/
Queue: Pod-Perldoc

People
Owner: Nobody in particular
Requestors: krishnoid [...] wapacut.com
Cc:
AdminCc:

Bug Information
Severity: Important
Broken in: 3.14
Fixed in: (no value)



Subject: can't handle =encoding utf8
If I look at the perl6 pods in: http://svn.perl.org/perl6/doc/trunk I try using perldoc (5.8.8) on them and get: ---------------------------------------- S05.pod:1: Unknown command paragraph "=encoding utf8" <standard input>:173: warning: can't find numbered character 160 <standard input>:177: warning: can't find numbered character 160 <standard input>:447: warning: can't find numbered character 160 <standard input>:798: warning: can't find numbered character 160 ... ---------------------------------------- I'm kind of surprised that =encoding isn't supported by perldoc, since its mentioned in perlpod. I figure this is a bug in Pod::Perldoc or perlpod, so I'm starting here.
Subject: Re: [rt.cpan.org #26121] can't handle =encoding utf8
Date: Thu, 05 Apr 2007 13:18:50 -0800
To: bug-Pod-Perldoc [...] rt.cpan.org, krishnoid [...] wapacut.com
From: "Sean M. Burke" <sburke [...] cpan.org>
Show quoted text
> I'm kind of surprised that =encoding isn't supported by perldoc, since > its mentioned in perlpod. I figure this is a bug in Pod::Perldoc or > perlpod, so I'm starting here.
Upgrade your Pod::Simple and retry.
From: krishnoid [...] wapacut.com
On Thu Apr 05 17:19:14 2007, SBURKE wrote: Show quoted text
> > I'm kind of surprised that =encoding isn't supported by perldoc, since > > its mentioned in perlpod. I figure this is a bug in Pod::Perldoc or > > perlpod, so I'm starting here.
> > Upgrade your Pod::Simple and retry. >
Tried, identical errors. Here's all the info I think relevant to this: * perl 5.8.8 and perl-doc 5.8.8 Ubuntu packages installed * perl-doc doesn't install Pod::Simple or Pod::Escapes, and yet perldoc S05.pm produces the errors and mostly formats S05 (e.g.) ok. * cpan install Pod::Simple pulls in Pod::Escapes, and I still get identical errors * > grep -i version /usr/share/perl/5.8/Pod/Perldoc.pm $VERSION = '3.14'; * > grep -i version /usr/share/perl5/Pod/Simple.pm $VERSION = '3.04'; * > grep -i version /usr/share/perl5/Pod/Escapes.pm $VERSION = '1.04'; * Also tested with: Show quoted text
> grep -i version
/home/krishna/cvswork/perllib/local/share/perl/5.8.8/Pod/Simple.pm $VERSION = '3.05'; Did a 'sudo aptitude remove libpod-simple-perl' so I know it's picking up this Simple.pm if/when it does within perldoc. Identical errors. * Ubuntu 6.10, installed items only from the main distribution. Other than the items installed above from CPAN for testing, all modules were installed using 'sudo aptitude install'. If you have access to an Ubuntu system of any revision, I'd like to know if you can view the synopses per the svn URL I provided. If you have a set of perl versions/perl module versions that can format the synopses without errors, I'd like to know what they are (and hopefully get them fixed or a minimum version number documented in perlpod to handle =encoding, etc). If this is a problem with Ubuntu's packaging system, I sincerely apologize for taking your time. But I'd think that since the core perlpod documentation in 5.8.8 mentions =encoding, and the base perldoc program can't handle it (but can work ok without Pod::Simple or Pod::Escape), I suspected there's a bug in either the documentation or a missing feature in the code.
CC: Allison Randal <allison [...] oreilly.com>
Subject: Re: [rt.cpan.org #26121] can't handle =encoding utf8
Date: Thu, 05 Apr 2007 14:48:37 -0800
To: bug-Pod-Perldoc [...] rt.cpan.org
From: "Sean M. Burke" <sburke [...] cpan.org>
On 04/05/2007 02:36 PM, krishnoid@wapacut.com via RT wrote: Show quoted text
> Tried, identical errors. Here's all the info I think relevant to this:
OK, I'm officially lost then. All-updated Pod::* modules should make this all better, but since apparently not, then I'm boggled and running away. Allison, do you know who to forward this ticket to? I've lost track of who actually owns Perldoc now.
I'm looking at this, but it's truly odd. It's not giving the errors in this report, but it's not doing the right thing either. Instead of mojibake, which I would have expected if their was a problem, I'm getting a translation. "Ingy döt Net" turns into "Ingy doet Net". Who's doing that?
I think this may be fixed now, although we need testing. Using groff 1.20.1 or later and using the various utf8 switches with Pod::Man and groff seemed to have solved it. I think the Pod::Simple stuff is doing what it's supposed to do.
Given the state of groff and other *roff formatters and UTF8 support, this is about as good as it can get for now.