...@cpan.org
Von: Eric Demerling
Gesendet: Montag, 2. März 2015 14:23
An: Brad Appleton; Marek Rouchal
Betreff: Fwd: getopt
Brad and Marek your Pod programme is worth it weight in unobtainium (if you
are a Avatar fan). I am using it in ALL my current programmes and any I
maintain. I am writing
?
-Marek
Von meinem Samsung Galaxy Smartphone gesendet.
Ursprüngliche Nachricht
Von: Randy Stauner rwstau...@cpan.org
Datum:08.01.2015 19:26 (GMT+01:00)
An: David E. Wheeler da...@justatheory.com
Cc: Marek Rouchal ma...@rouchal.net, Karl Williamson
pub...@khwilliamson.com
IIRC the first liberal rx is to detect start of POD just like the Perl
(language) parser does, i.e. it pauses parsing for instructions until the next
=cut
I think POD parsers should do the same. If the matched pod-start sequence does
not match any of the known commands, it's an error condition,
I feel that the content's of an =item should be contained within that
=item's item-bullet event, instead of partially in, partially out.
+1
-Marek
Von: Marc Green [mailto:pongu...@gmail.com]
Gesendet: Sonntag, 19. Februar 2012 06:33
An: pod-people@perl.org
Betreff: On verbatim
from _extending_ its meaning.
-Marek
-Ursprüngliche Nachricht-
Von: 'Patrice Dumas' [mailto:pertu...@free.fr]
Gesendet: Sonntag, 29. Januar 2012 18:46
An: pod-people@perl.org
Betreff: Re: pod checker that finds missing internal links?
On Sun, Jan 29, 2012 at 04:29:32PM +0100, Marek
AFAIK Z never has any content, and is used only to
put something into a place where some content is expected
but without actually putting any readable content there...
something like:
Z I want to start a line with whitespace but it should
not be interpreted as a verbatim block
Xkeyword is, as
podchecker _does_ detect wrong internal links. If you
put any of the following links in the POD you quoted
below, podchecker (as of Pod-Parser-1.38 and higher)
will flag it as an error:
L/open FILEHANDLE,MODE,EXPRESSION
Lopen FILEHANDLE,MODE,EXPRESSION
L/open FILEHANDLE,MODE,EXPRESSION
It is
Well guys,
if this is the case, then it will be up to me again to remove this
error detection from Pod::Parser and release a 1.51. Would be nice
if this was the final verdict on this matter...
Stay tuned...
-Marek
Original-Nachricht
Datum: Mon, 23 Jan 2012 11:27:54 -0700
For the record: I won't object at all if one of the next Perl core releases
will not contain Pod-Parser any more. Like Sean Burke put it - time to give
it a Viking funeral J However, Pod::Checker (including the podchecker
script) should then be rewritten to use Pod::Simple, and I believe
I agree, too and would like to add that any formatter should flag that as an
error, especially podchecker.
-Marek
-Ursprüngliche Nachricht-
Von: David E. Wheeler [mailto:da...@kineticode.com]
Gesendet: Sonntag, 26. Juni 2011 06:19
An: Marc Green
Cc: pod-people@perl.org
Betreff: Re:
Right - some POD formatters use heuristics like /^\d+/ on what follows =item
to detect whether this is a numbered list. In the specific case of HTML
output, you have 2 choices:
1. always use the full text behind =item and generate a definition list
(dl,dt,dd), except with =item * which should
Hi Marc,
IIRC C stands for code, which means for renderers to set the included
ext in a fixed-width font (courier-like). It is by no means a hyperlink. I
know
that some POD tools tried to apply some artificial intelligence to check
whether text in B or C or I could be a reference to a
=PodParser-1.15w=1
No idea whether Brad Appleton, Marek Rouchal, or someone else initiated
these changes
On Sat, May 29, 2010 at 01:01:35PM -0700, Russ Allbery wrote:
karl williamson pub...@khwilliamson.com writes:
And in fact, recommends not using L to anything other than another
pod
My 2c: allow Ltext|URL in future POD. Rendering depends on the
Output formatter, there are IMHO two options:
1. (preferred) render as clickable hyperlink to URL, showing text (only)
2. render as text (URL) for text outputs.
Can URI be used to safely detect whether URL is an absolute URL?
HTH,
Dear all,
when writing Marek::Pod::HTML I saw any combinations
of markup in =headN and =item, and also any kind of
markup in L... (with and without |, i.e. alternative
text). This made me implement the link-resolving part
of the formatter like this: Both on the source and
the destination side,
Dear all,
it is correct that Pod::Text should be used whenever there
is Pod to be converted to ASCII/Latin-1/... :-)
However Pod::PlainText is part of the Pod::Parser
distribution right from the start (AFAIK), so I'd
hesitate to drop it.
On the other hand it is true that it is used for the tests
Hello Hugo,
please find answers in the text below.
Cheers,
Marek
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
I had a go at integrating this into the core, but ran across some
test failures.
First, the core version of t/pod/find.t is substantially
My Marek::Pod::HTML has also a ps output option,
which - you guessed it - uses HTML::FormatPS
-Marek
-Original Message-
From: Sean M. Burke [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, November 20, 2002 10:02 AM
To: [EMAIL PROTECTED]
Subject: pod2ps
Does anyone have a favorite
Hi Ed,
I tried getting the latest File::Spec on CPAN, but it didn't have the
necessary methods. IIRC. It looks like newer File::Specs are bundled
with perl but not available on CPAN.
thanks for pointing this out. I filed a request to
update File::Spec on CPAN, see
Dear Perl gurus,
I noticed that some changes have been done to e.g.
lib/Pod/Checker.pm
in the perl-5.8.0 distribution, relative to PodParser-1.18
on CPAN.
Who did these changes? There is one that seems
to me rather arbitrary and IMHO requires a clarification:
collapsing newlines to blanks in
Hello Sean and *,
you may want to hava a look at Pod::Compiler. It basically does what you
have in mind, altough the tree it creates is not XML but a set of Pod::*
objects defined in Pod::objects. But this could be changed quite easily
(...if I had enough time for that, sorry to say so). But
I'm finally starting to implement this in Pod::Man and Pod::Text, and here
are the nits that I've found so far in perlpodspec.
Note that EEltnumber Imust not be interpreted as simply codepoint
Inumber in the current/native character set. It always means only
the character represented by
Sean,
I like the idea. However it seems to me that we both did up to 70% of the
same work - i.e. parsing POD and turning it into a more structured
representation. See Pod::Compiler for what I did on this
subject. Attaching a XML backend to it should be a matter of one day max.
I guess that you
Hello,
you may want to give the extenstion MarekPodHtml-0.43.tar.gz a try. It is
more robust than the "old" pod2html. Be sure to specify all files to
convert on the command line (see the manpage), otherwise the links are not
active.
Cheers,
Marek
On Tue, 3 Apr 2001 [EMAIL PROTECTED] wrote:
I
Dear all,
after fiddling with details for a long time, I'm now confident enough to
upload Pod-Compiler-0.10.tar.gz to CPAN. Should reach your favorite mirror
soon.
What is it? This package, based on Pod::Parser and Tree::DAG_Node compiles
a POD document into an object tree, printing (or not)
On Fri, 1 Sep 2000, Tom Christiansen wrote:
TCYou should write your pod as close to plain text as you possible
TCcan, with as few explicit markups as you can get away with. It
TCis up to the individual conversion to decide how things in your
TCtext should be represented. That
###
# Pod/Compiler.pm -- compiles POD into an object tree
#
# Copyright (C) 2000 by Marek Rouchal. All rights reserved.
# This package is free software; you can redistribute it and/or modify
# it under the same terms as Perl itself.
##
On 3 Sep 2000, Russ Allbery wrote:
RA * lib/Pod/Text.pm: Add sol and verbar to the escapes.
RA * lib/Pod/Man.pm: Likewise.
RA * lib/Pod/Man.pm (cmd_item): Fix the regex for stripping bullets
RA from index entries so that it doesn't strip a leading 'o'.
Dear all,
I'd like to
On Thu, 3 Aug 2000, Brad Appleton wrote:
BABesides, I think there is still need for a Pod::Translator
BAof Pod::Compiler module that uses (or is subclassed from)
BAPod::Parser to be the *real* base parser that people use (the
BAone that actually knows the commands, just not necessarily
BAthe
Dear all,
today I've uploaded MarekPodHtml-0.41.tar.gz to CPAN. This is an update of
0.40 that fixes a bug that the conversion ran into when converting all of
the Perl PODs locally installed as suggested by me earlier.
What is this all about?
I think the existing pod2html is broken. I wanted
30 matches
Mail list logo
