As I stumble past this list, which I don't follow much anymore, I'll
give a few responses to, but not definitive answers to, some issues
that are either because of things in perlpodspec, or because of things
not in Perlpodspec.
Here goes...
On 02/19/2012 02:19 PM, Marc Green wrote:
Hello Pod People,
When given the following input, Pod::Simple does not warn that the
[text] portion of the 2nd and 3rd =item is invalid.
In passing, I'll note that the =over ... =item ... =back code was some
of the hardest notions/code in
On 02/09/2012 04:34 AM, David Cantrell wrote:
I doubt you'll ever see a distribution which has POD in both Foo/Bar.pm
and Foo/Bar.pod, because the perldoc tool will only see one or the other
when a user types 'perldoc Foo::Bar'.
+1 !
...by which I mean that I took this as a given: when Perl
On 02/20/2012 06:58 PM, Florent Angly wrote:
Hi Sean,
You are right that Pod::Simple has problems with multiline POD strings
contained into a variable or heredoc section:
https://rt.cpan.org/Ticket/Display.html?id=36404
https://rt.cpan.org/Ticket/Display.html?id=69390
Oh now I remember...
On 07/22/2010 02:12 PM, David E. Wheeler wrote:
On Jul 22, 2010, at 2:38 PM, Russ Allbery wrote:
That's not because =item * Stuff is being specially recognized. That's
because =item anything where anything isn't a bullet or a number
produces an unordered list. perlpodspec does say that,
On 07/21/2010 09:29 AM, Russ Allbery wrote:
6) But I similarly-and-worse forgot to produce a /drop-in/ pod2man
replacement.
That's okay, I did that. :)
Wow, cool, thanks!
See what I mean about my mind being stoner Swiss cheese!
Oy, pod2html, Pod::Simple::HTMLLegacy, Pod::Simple::HTML,
Preamble:
Making pod2html use Pod::Simple::HTMLLegacy /might/ actually be
simpler than patching Pod::HTML or Pod::Parser or whatever.
About my bungling:
On 07/20/2010 01:00 PM, Ricardo Signes wrote:
I would like to see pod2html (as a Pod::Html-based thing) be replaced with
Pod::Simple, which
Ohyeah, I forgot to tell everyone: I used mesmerism and psychic
extortion to make Adriano take over maintenance of perldoc.
Tadaaa!
On 04/23/2008 04:23 AM, Adriano Ferreira wrote:
Some days ago the following development releases of Pod-Perldoc (and
their corresponding changes) reached CPAN:
My previous message, about Perldoc, reminded me of the long-forgotten
time when I actually wrote Perl under MSWin, and that reminded me:
I have/had some magic thingy under MSWin to make Perldoc by default save
output to an RTF temp file and then open Wordpad (as write.exe) on it as
a
, but then you have
to figure out how to turn that into something that will make sense in a
img src=_ for whatever purposes the user has in mind. This is all
in the way of combining a desire to make implemantational notes, with a
harrowing lack of caffeine.
--
Sean M. Burke http
within the sound of my
voice: you know you want to do this!
--
Sean M. Burke http://search.cpan.org/~sburke/
Dear Pod People,
I think it's been at least a year since I've been able to happily sit
down and really maintain any of my CPAN modules. I can't put my finger
on why, but they all just seem too complex to me now, so that dealing
with them seems about as thrilling a prospect as doing tax forms
at several sites, including
search.cpan.org. It works. Sorry about the meager state of its docs tho.
--
Sean M. Burkehttp://search.cpan.org/~sburke/
.
What do manpage formatters insist on there being? Like do they complain if
there's no NAME [sic] section?
--
Sean M. Burkehttp://search.cpan.org/~sburke/
At 01:19 PM 2004-09-29, John McNamara wrote:
$new-code_handler
(
sub {
Wow, that's pretty zippy. I forgot all about that code_handler stuff.
--
Sean M. Burkehttp://search.cpan.org/~sburke/
At 11:19 AM 2004-09-23, Thomas Klausner wrote:
Which appearantly never happend (I never asked again, so I don't blame
anybody..)
Sorry, I've been really really really really really really busy.
--
Sean M. Burkehttp://search.cpan.org/~sburke/
that basically done for the next release of Pod-Simple.
--
Sean M. Burkehttp://search.cpan.org/~sburke/
with a superset of Pod feeding into a bunch of XML tools?
--
Sean M. Burkehttp://search.cpan.org/~sburke/
expand
foo to the list (foo/5.8.0/MSWin32-x86-multi-thread, foo/5.8.0,
foo/MSWin32-x86-multi-thread, foo) ?
I could presume that cases where that's desireable are actually so rare as
to be unheard-of and thus irrelevent, but I figure I'd actually ask folks.
--
Sean M. Burkehttp
at most. Watch the skies
for a new Pod-Simple release.
And finally, I've just added the code (for the next release) that'll make
Pod::Simple::Search skip qw(RCS CVS SCCS .svn) directories. So, thanks!
--
Sean M. Burkehttp://search.cpan.org/~sburke/
/.)
And it does the HTMLification with the newly spiffy Pod::Simple::HTML
module that's in the new Pod::Simple dist from a day or two ago.
--
Sean M. Burkehttp://search.cpan.org/~sburke/
OK, new Pod-Simple is entering CPAN, from
http://interglacial.com/temp/Pod-Simple-3.01.tar.gz
Here's the notes from the changelog for this release,
plus the recent release before that, which I may have
forgotten to mention here:
2004-05-24 Sean M. Burke [EMAIL PROTECTED]
* Release 3.01
(DESCRIPTION)
That makes the modern Pod processors happier.
--
Sean M. Burkehttp://search.cpan.org/~sburke/
sort of things are you trying to do? I might be able to
suggest a better way to do what you want.
--
Sean M. Burkehttp://search.cpan.org/~sburke/
It just occurred to me that I can never ever remember whether hex entities
in Pod are like Exab or like E0xab and so goddammit, I think I should
just change perlpodspec, perlpod, and Pod::Escapes to support both
formats. Anyone object?
--
Sean M. Burkehttp://search.cpan.org/~sburke/
At 02:05 AM 2003-11-07, Slaven Rezic wrote:
Is a =cut without a starting pod directive supposed to start a Pod section?
Don't do that.
--
Sean M. Burkehttp://search.cpan.org/~sburke/
At 01:14 AM 2003-10-20, Graham Barr wrote:
On 20 Oct 2003, at 1:58, Sean M. Burke wrote:
I'm having no luck trying to track down what flakiness in perl 5.6's
Unicode support is causing all the complaints and ickyness in
Pod::Simple. It works just fine under perl 5.8, but under 5.6 there's
to the *roff of choice.)
Now I'm off to cure the ills of Pod::Simple's =encoding things, whole .t's
currently scream like a banshee with 5.6 and old Encode versions. Watch
the skies, everyone!
--
Sean M. Burkehttp://search.cpan.org/~sburke/
, as well
as some particular corner cases.
Would folks find that useful?
--
Sean M. Burkehttp://search.cpan.org/~sburke/
task from writing, that in actual
book-publishing, indexing is a job on its own.
--
Sean M. Burkehttp://search.cpan.org/~sburke/
it?
Once I'm thru messing with it in the next few days, I can cook up an
archive of the code, and the test corpus, and all the differences
(hopefully insignificant) between the output it makes and the output
Pod::Man makes, given the same input.
--
Sean M. Burkehttp://search.cpan.org
that approach
--
Sean M. Burkehttp://search.cpan.org/~sburke/
this!
--
Sean M. Burkehttp://search.cpan.org/~sburke/
At 01:00 PM 2003-09-05 -0700, Russ Allbery wrote:
This has in my experience always been an error. I'd automatically close
and additional issue a warning when run through a checker/lint tool.
Okay, I've now implemented this. It'll be in the next Pod-Simple release.
--
Sean M. Burkehttp
of people apparently having a =head1 inside an =over are actually
mistakes and that they really meant to close the =over.
--
Sean M. Burkehttp://search.cpan.org/~sburke/
I have released new version of Pod::Simple that implements =encoding.
ChangeLog:
2003-09-01 Sean M. Burke [EMAIL PROTECTED]
* Release 2.01
* Moved all version numbers up to 2.01 for reasons of Tibetan
numerology.
* Implemented =encoding. Thanks a million
care why 1. and not 1) ? Is this some Hegelian
dialectic? YOW -- Is my aura being AUDITED?
--
Sean M. Burkehttp://search.cpan.org/~sburke/
At 05:06 AM 2003-09-02 -0700, Michael G Schwern wrote:
Yeah, maybe. In general, I don't consider the rejection of illegal
forms
to be a high priority for parser. DWIM is vastly more important.
DWIMness be built into the spec.
That is, to say the least, a foregone conclusion.
--
Sean M
(plus the rare-as-hen's teeth UCS-32 encoding)
might not be easy to implement, so I'm thinking of just leaving them out
for the moment.
--
Sean M. Burkehttp://search.cpan.org/~sburke/
! Thanks for running all these tests!
--
Sean M. Burkehttp://search.cpan.org/~sburke/
There's a new Pod::Simple version entering CPAN. Here's my changelog entry
for it:
2003-08-12 Sean M. Burke [EMAIL PROTECTED]
* Release 0.97
* Loooking goood. Not smelling so much like beta anymore!
* I think this might be the last version before I go
putting use utf8 all over the place
At 04:32 PM 2003-07-26 +0100, Sagar Shah wrote:
So i've got two options of a base:
1) Meta::Lang::Pod::DocBook
2) Pod::XML
I say choose option three: Pod::Simple. Look at Pod::Simple::XMLOutStream
for an example.
--
Sean M. Burkehttp://search.cpan.org/~sburke/
a stylesheet to
transform into XML, but introduces an extra processing step... and there
might be issues with ids on sections
Sounds good to me. I'd be thrilled to see a modern DocBook converter.
What Pod parser module will your converter be based on?
--
Sean M. Burkehttp://search.cpan.org/~sburke/
that the decent number of people
still labouring with 5.005 installs of perl could at least have a nice
modern perldoc if they wanted it.
Can anyone see any reason not to do this?
--
Sean M. Burkehttp://search.cpan.org/~sburke/
(I've seen the Perl 6 RFC).
I think this idea would be really good for Perl 6, because, in my opinion,
POD is lacking.
Lacking how?
--
Sean M. Burkehttp://search.cpan.org/~sburke/
to die here; but that seemed pointless.
+}
}
return;
}
--
Sean M. Burkehttp://search.cpan.org/~sburke/
that it's an unknown switch; if true,
that would be a very compelling reason not to have Pod::Perldoc::ToMan add
the -c switch.
What does everyone think?
--
Sean M. Burkehttp://search.cpan.org/~sburke/
Oop, one more assumption I'd like to be able to make:
* Unless a Pod file starts with a BOM, the Pod processor will assume that
it's in Latin-1 or UTF8, unless/until there's an =encoding directive
seen. So if you're writing a Pod file in any other encoding, you /must/
have an =encoding
::Perldoc. Having it be an external program for the
forseeable future would at least make it clear to people that this
preprocessing step is not part of Pod itself.
Thoughts? Suggestions?
(As I return to just fretting over the implementation of =encoding ...)
--
Sean M. Burkehttp
), and he says that he sees
xml:lang=und as reasonable; we don't see any better alternatives for
signalling this isn't in any human language (so shouldn't be spellchecked,
etc), but I need to specify a language tag to keep the higher-element's
language tag from applying here.
--
Sean M. Burke
similar to lookup entries in perlop. This would be
especially useful for the oddly classified entries like m// and y//.
I think that would be wonderful!
What UNCONDITIONALLY ENCOURAGING AND HELPFUL things do the Pod-People have
to say?
--
Sean M. Burkehttp://search.cpan.org/~sburke/
of
that distinctions that you consider worth expressing.
In any case, maybe it would help if I put into perlpodspec the =extend
things I've been implementing in Pod::Simple, so that you can use them. I
suppose it might help if you could define code for methodnames, arguments, etc.
--
Sean M. Burke
, the problem you point out is not very compelling, at least not as
you've described it. I am always on the lookout for a solution to this
problem; but for the time being, think of it as an inadvertent tax on ISA
hierarchy deepness.
--
Sean M. Burke [EMAIL PROTECTED] http://search.cpan.org
At 07:58 AM 2003-01-25 +0100, Philip Newton wrote:
On Fri, 24 Jan 2003 18:19:14 -0900, [EMAIL PROTECTED] (Sean M. Burke)
wrote:
Someone mentioned to me that people on p5p were talking about perldoc
under
MSWin going kookoo when using more as the pager. I've just tried
reproducing
At 1/25/2003 12:58 PM +0200, Burak Gürsoy wrote:
Under Win98 Win2k with ActivePerl 5.8 b804, this problem exists for me,
also, someone in the perl-win32-users list mentioned this prob yesterday.
Using old perldoc, or new Pod::Perldoc-based perldoc?
--
Sean M. Burke [EMAIL PROTECTED] http
mentions at http://nntp.x.perl.org/group/perl.perl5.porters/ (via a bit of
LWP automation).
--
Sean M. Burke [EMAIL PROTECTED] http://search.cpan.org/~sburke/
Pod::Simple 0.96 is entering CPAN. A few new minor features -- but almost
every file has changed because I documented things! Pod::Simple and
Pod::Simple::Subclassing are about the only things whole docs still have
TODOs in them.
--
Sean M. Burkehttp://search.cpan.org/author/sburke/
better ideas!
--
Sean M. Burkehttp://search.cpan.org/author/sburke/
it for the poor impoverished Pod::Parser user(s), since of course
Pod::Simple takes care of E... expansion automatically.
--
Sean M. Burkehttp://search.cpan.org/author/sburke/
they're not talking about Pod at all, but just
some some appalling old version of Pod::Html or Pod::Man. It's like
complaining that Perl doesn't have objects since you never know when you'll
be using Perl 4.
--
Sean M. Burkehttp://search.cpan.org/author/sburke/
edition). Patches welcome!
--
Sean M. Burkehttp://search.cpan.org/author/sburke/
Pod::Perldoc 3.05 alpha is entering CPAN now, and also available at:
http://members.spinn.net/~sburke/Pod-Perldoc-3.05.tar.gz
Changes:
2002-11-11 Sean M. Burke [EMAIL PROTECTED]
* Release 3.05 alpha.
* Corrected the logic that suppresses warnings during require's
to be called in get_token ?
Oops, that's a bug in get_token. It's supposed to just halt processing of
the file, just as if there were an EOF there -- the die is not supposed to
happen. I'll provide a fix in a bit.
--
Sean M. Burkehttp://search.cpan.org/author/sburke/
of the
errata section, which is clearly the best way to do it. I'll make a
block-starting =cut be just a no-op except for inserting a note in the errata.
Thanks for catching this! I think I forgot to put in any tests for this (yet)!
--
Sean M. Burkehttp://search.cpan.org/author/sburke/
Lperlpie/I like pie blah blah
and later you insert some text earlier in the paragraph and then rewrap it,
and voila, it could end up spanning lines.
--
Sean M. Burkehttp://search.cpan.org/author/sburke/
disaster somewhere somehow?
--
Sean M. Burkehttp://search.cpan.org/author/sburke/
/another/ perlpodspec-compliant Pod-parser. Doing the first one,
Pod::Simple, was plenty hard enough. I can't think of a motivation that'd
be worth the bother of doing it all over again.
--
Sean M. Burkehttp://search.cpan.org/author/sburke/
At 11:13 2002-10-13 +0200, Johan Vromans wrote:
Plus, I'm thinking of my perl books site. [...] it would be nice to
be able to have things map to book-title, author-name, etc.
You're about to wake a sleeping dog.
Which one? Is it a chiwowwow dog?
I like puppies.
--
Sean M. Burkehttp
Oh, just FYI, I forgot to mention that you can just do:
=extend Y C,I
(with out the terminal foo,bar,baz list)
That means: whenever I do Y..., treat it as if I just did CI
It's just a degenerate case of =extend Y C,I list, except with an empty list.
--
Sean M. Burkehttp
(going on 25)
seconds for a browser to open when I just want to quickly know the answer
to what's the sixth parameter from stat() mean?.
--
Sean M. Burkehttp://www.spinn.net/~sburke/
under).
--
Sean M. Burkehttp://www.spinn.net/~sburke/
tasks, I may have overlooked
useful features.
Now, everyone, Try It And See.
--
Sean M. Burkehttp://www.spinn.net/~sburke/
At 22:31 2002-04-07 -0700, Russ Allbery wrote:
pod2man turns off hyphenation globally, always. It was making far
Excellent! Maybe I'll just have pod2rtf do the same.
--
Sean M. Burkehttp://www.spinn.net/~sburke/
-prevention is my /only/ criterion in considering
what is good for Pod.)
--
Sean M. Burkehttp://www.spinn.net/~sburke/
is
released. I know that this won't help older perls, but it's better than
nothing.
Perlpodspec isn't even implemented yet, in time for 5.8.0 (for which I take
blame). Wanting extensions to it to be implemented is dazzling optimism.
--
Sean M. Burke[EMAIL PROTECTED]http
At 17:58 2002-03-22 -0800, William R Ward wrote:
The documentation for die (in Perl 5.6.1) looks like this:
[...]However, EXPR is not part of the signature for this function!
pod-people isn't the right list for this. But I'm not sure which list would
be the right one. Ideas, anyone?
--
Sean M
At 11:13 2002-01-04 -0500, Adam Turoff wrote:
The best idea Larry has blessed so far is the =use clause that
optionally makes Pod behave differently.
Where was that discussed?
I'd like to read what he said.
At 11:13 2002-01-04 -0500, Adam Turoff wrote:
[...]
Like many XML folks, I trust James implicitly when it comes to markup
languages; if he says that adding a macro facility such as =equate is a
bad idea in a markup language, then it's a Bad Idea(tm).
First off, I don't trust him implicitly any
::Thing::1.0::user::install/intro
That's if I understand your problem correctly.
--
Sean M. Burke[EMAIL PROTECTED]http://www.spinn.net/~sburke/
paraI like harpsichord music./para
Or something like this?
section2
head2Turn-Ons/head
paraI like harpsichord music./para
/section2
The first way /merely/ recapitulates the Pod, which is fine by me.
But would anyone like the latter? What are the practical benefits of it?
--
Sean M. Burke
verbatim paragraph of under 15 lines long gets a \keep, which
keeps it from being broken across pages.
* things that look like Perl symbols (things containing $,@,%,:,,,\,(, or
*, basically) get wrapped in the do not spellcheck this code ({\noproof
})
--
Sean M. Burke[EMAIL PROTECTED
, LOCK_EX;
#: ^^^
And maybe itals with something like
# So only one instance gets to access this at a time!
#: /
(as to how to do bold-and-ital, I dunno... %?
Thoughts, anyone?
--
Sean M. Burke[EMAIL PROTECTED]http://www.spinn.net/~sburke/
Pod::HTML::Shazbot (or Pod::HTML::Plugins::Shazbot). I'm not sure that
that's /definitely too/ complicated, but it's certainly more complicated
than it looks.
--
Sean M. Burke[EMAIL PROTECTED]http://www.spinn.net/~sburke/
At 11:13 2002-01-04 -0500, Adam Turoff wrote:
The best idea Larry has blessed so far is the =use clause that
optionally makes Pod behave differently.
Where was that discussed?
I'd like to read what he said.
--
Sean M. Burke[EMAIL PROTECTED]http://www.spinn.net/~sburke/
Shazbot: ~!
such that Dyow turns into Shazbot: yow!.
--
Sean M. Burke[EMAIL PROTECTED]http://www.spinn.net/~sburke/
only by offers of money -- that is to say,
my queue is not accessible to Devil's advocates, only is occasionally
mutable by Ba'al's accountants.
--
Sean M. Burke [EMAIL PROTECTED] http://www.spinn.net/~sburke/
,
and tree-based processing models. Moreover, this avoids having to actually
write and maintain a Pod-specific tree node class. Plus there's safety in
numbers, since everyone and their dog is processing XML these days, so It
Has To Work.
Thoughts, anyone?
--
Sean M. Burke[EMAIL PROTECTED]http
like:
=equate N C,I
...and if you don't know what an Nfoo bar is, pretend I used a CIfoo
bar instead.
I can imagine applying this-all to directives too, but I have the intuition
that that might be stretching the concept too far.
--
Sean M. Burke[EMAIL PROTECTED]http://www.spinn.net
further DWIMmity beyond what perlpodspec
requires, that can always be encouraged as a matter of extra error-tolerance.
--
Sean M. Burke[EMAIL PROTECTED]http://www.spinn.net/~sburke/
anything other than Pod::Parser observe this ==foo syntax?
I'm tempted to say that clearly no-one is very attached to it since it's
not in old perlpod, and no-one mentioned it not being in new perlpod or
perlpodspec.
--
Sean M. Burke[EMAIL PROTECTED]http://www.spinn.net/~sburke/
Does anyone use Pod::InputObjects / Pod::ParseTree?
Not can imagine using, but actually use?
--
Sean M. Burke[EMAIL PROTECTED]http://www.spinn.net/~sburke/
At 07:04 PM 2001-11-02 -0800, Russ Allbery wrote:
Sean M Burke [EMAIL PROTECTED] writes:
[...quoting Pod::Parser]
if ((! length $paragraph) ($textline =~ /^==/)) {
## '==' denotes a one-line command paragraph
[...]It was discussed a few times on perl5-porters in the past
if future Pod::Parser versions would accept ==foo lines
as commands only if explicitly requested to do so.
I'd like to strongly deprecate ==foo lines for use in normal Pod (as
opposed to in other languages in the set of Podlike things, which I have no
real interest in).
--
Sean M. Burke [EMAIL
of the methods from
Pod::InputObjects.
OK, you or Brad might be able to answer this then:
Why is it that a paragraph node doesn't have children, but has an
HTML::ParseTree object that has children? It seems an odd bit of
indirection, and I can't make out the motivation for it.
--
Sean M. Burke
, jargon,
or stopwords, this means you'll have ungrammatical sentences, what with
words being missing and all. And you don't need a grammar checker to
tell you that.
COPYRIGHT AND DISCLAIMER
Copyright (c) 2001 Sean M. Burke. All rights reserved.
This library is free software; you can redistribute
warnings, notably the one about lines
consisting of all whitespace.
I think that that will have to do until Pod::* authors have the time to
bring their modules up to spec.
--
Sean M. Burke [EMAIL PROTECTED] http://www.spinn.net/~sburke/
: or.
In other words, LPod::Parser is likely to be rendered simply as
Pod::Parser, but I don't know what to do with Lperlfunc/die or
LTheory of MIMEs.
As if they were:
Ldie in perlfunc|perlfunc/die
LTheory of MIMEs|Theory of MIMEs
--
Sean M. Burke [EMAIL PROTECTED] http://www.spinn.net/~sburke/
of the files I mention a Pod::Escapes. It's not
vaporware -- it's a module I'm going to put on CPAN at the first spare moment.
--
Sean M. Burke[EMAIL PROTECTED]http://www.spinn.net/~sburke/
/PODs: Embedded Documentation,
Lperlnewmod, Lperldoc, Lpod2html, Lpod2man, Lpodchecker.
=head1 AUTHOR
Larry Wall, Sean M. Burke
=cut
--
Sean M. Burke[EMAIL PROTECTED]http://www.spinn.net/~sburke/
formatter that emits only the plaintext output that a
spellchecker should pay attention to -- i.e., like pod2text minus verbatim
blocks, C... content, things $like_this, etc. It's called, of course,
Pod::Spell.
--
Sean M. Burke [EMAIL PROTECTED] http://www.spinn.net/~sburke/
1 - 100 of 108 matches
Mail list logo
