On Tue, 2018-05-29 at 15:20 +1000, Ron Savage wrote:
> On 29/05/18 13:49, Karl Williamson wrote:
> > The question is what to do?
> >
> > 1) We could leave things as they always have been, to let sleeping
> > dogs
> > lie. It's worked for so long that we're not seriously going to
> > stop
> >
On Wed, 2014-06-25 at 18:05 +, John E Guillory wrote:
Hello,
I thought I wasn’t this new to perl but …
How does one use pod::simple::text to print out a section of POD, say
the DESCRIPTION section?
Pod::Simple provides some core POD parsing functionality which is shared
by a number of
On Wed, 2012-10-10 at 08:53 -0700, David E. Wheeler wrote:
Pod People,
See the forwarded complaint below.
The complaint that:
In perldoc POD I can't find any hint that 0 is an invalid
indentation.
is a bit bogus because the formal specification for POD is in 'perldoc
perlpodspec'
On Mon, 2012-08-27 at 10:17 -0700, David E. Wheeler wrote:
Pod People,
In https://rt.cpan.org/Ticket/Display.html?id=79232, Saven Rezic
writes:
Pod::Simple currently (e.g. with version 3.23) complains if a Pod
document has latin-1 characters in it but no =encoding command
specified. I
On Wed, 2012-06-06 at 16:55 +1200, Grant McLean wrote:
I'm considering a patch to make Test::Pod treat the new missing
=encoding warning differently to other warnings.
OK I've been convinced it's not worth bothering with :-)
Regards
Grant
On Mon, 2012-04-30 at 14:24 +0200, Johan Vromans wrote:
Grant McLean gr...@mclean.net.nz writes:
OK, so I went ahead and implemented both the warning and the heuristic
to guess Latin-1 vs UTF-8 (only when no encoding was specified). The
resulting patch is here:
https://github.com
On Fri, 2012-04-27 at 09:17 -0700, David E. Wheeler wrote:
On Apr 27, 2012, at 12:10 AM, Grant McLean wrote:
OK, so I went ahead and implemented both the warning and the heuristic
to guess Latin-1 vs UTF-8 (only when no encoding was specified). The
resulting patch is here:
https
Hi POD people
There's been a discussion on #metacpan about non-ASCII characters in POD
being rendered incorrectly on the metacpan.org web site.
The short story is that some people use utf8 characters without
including: =encoding utf8. Apparently the metacpan tool chain assumes
latin1 encoding,
On Tue, 2009-10-20 at 14:19 +0100, Mitch Gower wrote:
The pod to html conversion used on search.cpan.org seems to produce
quite nice output. What tool is being used there, and is it publicly
available? I couldn't see any evidence in the html itself of what's
being used.
As far as I know,
Hi pod-people
The documentation for the perldoc command refers to a -X switch which
causes the module/POD lookup to use a pre-generated index rather than
crawling @INC.
I haven't been able to locate a utility for generating the pod.idx file
which is referred to by the code behind the -X option.
10 matches
Mail list logo