maintained using Git; see the instructions on the above
page to access the Git repository.
Please let me know of any problems or feature requests not already listed
in the TODO file.
--
#!/usr/bin/perl -- Russ Allbery, Just Another Perl Hacker
$^=q;@!>~|{>krw>yn{u<$$<[~|| 0gFzD gD,
.org/project/perl/versions
Thank you! This is very useful.
--
#!/usr/bin/perl -- Russ Allbery, Just Another Perl Hacker
$^=q;@!>~|{>krw>yn{u<$$<[~|| 0gFzD gD,
00Fz, 0,,( 0hF 0g)F/=, 0> "L$/GEIFewe{,$/ 0C$~> "@=,m,|,(e 0.), 01,pnn,y{
rw} >;,$0=q,$,,($_=$^)=~y,$/ C-~><@=\n\r,-~$:-u/ #y,d,s,(\$.),$1,gee,print
Shawn H Corey writes:
> On 2024-03-15 14:38, Russ Allbery wrote:
>> If you would be happy with a PR to remove that bullet point, we're just
>> vigorously agreeing. 🙂 Otherwise, I'm not sure what you're asking for
>> instead.
> I guess I wasn&
nd a bug report.
For perlpodspec, based on this discussion, I propose the following fairly
minimal change. (I've never had a reason to submit a PR against Perl
before; now seems like a good time to start.)
>From ac979b8560449d363d1b3309ef5b80aa00b4b8f2 Mon Sep 17 00:00:00 2001
From
in a couple of weeks, but my track record on
accurate predictions is not great.
--
#!/usr/bin/perl -- Russ Allbery, Just Another Perl Hacker
$^=q;@!>~|{>krw>yn{u<$$<[~|| 0gFzD gD,
00Fz, 0,,( 0hF 0g)F/=, 0> "L$/GEIFewe{,$/ 0C$~> "@=,m,|,(e 0.), 01,pnn,y{
rw} >;
Shawn H Corey writes:
> On 2024-03-15 12:44, Russ Allbery wrote:
>> Shawn H Corey writes:
>>> I think it should be an option. Sometimes it is necessary to know that
>>> a change in appearance is caused by changes to a module and not to the
>>> generating do
o always do it still be okay? The way I was thinking of it
is that what formatters put into comments is generally up to them; by
default, they *can* include anything they want. Removing the requirement
thus just leaves the decision unconstrained.
--
#!/usr/bin/perl -- Russ Allbery, Just Another Pe
ments is not wrong, but I don't
think it needs to be said in the specification document and it's mostly
covered by the next bullet point anyway.)
--
#!/usr/bin/perl -- Russ Allbery, Just Another Perl Hacker
$^=q;@!>~|{>krw>yn{u<$$<[~|| 0gFzD gD,
00Fz, 0,,( 0hF 0g)F/
"Paul \"LeoNerd\" Evans" writes:
> Russ Allbery wrote:
>> One of the things I've wanted from nearly the start was some way of
>> marking up metasyntactic variables. POD is full of things like:
>>
>> perl
>>
>> or:
>>
"Paul \"LeoNerd\" Evans" writes:
> Russ Allbery wrote:
>> There are a few things that I've wanted to have in POD
>> for a while, although nothing that rose to the level of wanting to do
>> the work required to get it widely supported.
> Ah
e
work required to get it widely supported.
--
#!/usr/bin/perl -- Russ Allbery, Just Another Perl Hacker
$^=q;@!>~|{>krw>yn{u<$$<[~|| 0gFzD gD,
00Fz, 0,,( 0hF 0g)F/=, 0> "L$/GEIFewe{,$/ 0C$~> "@=,m,|,(e 0.), 01,pnn,y{
rw} >;,$0=q,$,,($_=$^)=~y,$/ C-~><@=\n\r,-~$:-u/ #y,d,s,(\$.),$1,gee,print
ANSI escape
sequences, Pod::Text::Color provides that, although it's quite
conservative and limited. There is a Pod::Text::Color::Delight module on
CPAN that is much more aggressive about coloring things and may be more
appealing.
--
#!/usr/bin/perl -- Russ Allbery, Just Another Perl Hacker
Leon Timmermans writes:
> On Fri, Nov 25, 2022 at 11:53 PM Russ Allbery wrote:
>> - Drop support for Perl 5.8. The minimum required version is Perl 5.10.
> It turns out that that part of the change made Module::Build
> uninstallable on 5.8, which makes half of CPAN uninstal
Leon Timmermans writes:
> On Fri, Nov 25, 2022 at 11:53 PM Russ Allbery wrote:
>> - Drop support for Perl 5.8. The minimum required version is Perl 5.10.
> It turns out that that part of the change made Module::Build
> uninstallable on 5.8, which makes half of CPAN uninstal
sing Git; see the instructions on the above
page to access the Git repository.
Please let me know of any problems or feature requests not already listed
in the TODO file.
--
#!/usr/bin/perl -- Russ Allbery, Just Another Perl Hacker
$^=q;@!>~|{>krw>yn{u<$$<[~|| 0gFzD gD,
00Fz, 0,,( 0
s after each sentence when reflowing,
and therefore if you want formatted Pod::Man output to consistently
have one space after each sentence, you will have to avoid ending a
sentence at the end of a line in the middle of a paragraph.
--
#!/usr/bin/perl -- Russ Allbery, Just Another P
ing a YAML module
into Perl core is going to be unappealing, but POD parsing currently lives
in core.
--
#!/usr/bin/perl -- Russ Allbery, Just Another Perl Hacker
$^=q;@!>~|{>krw>yn{u<$$<[~|| 0gFzD gD,
00Fz, 0,,( 0hF 0g)F/=, 0> "L$/GEIFewe{,$/ 0C$~> "@=,m,|,(e 0.), 01,pnn,y{
rw} >;,$0=q,$,,($_=$^)=~y,$/ C-~><@=\n\r,-~$:-u/ #y,d,s,(\$.),$1,gee,print
ough, and
I'm not volunteering to implement eqn support in Pod::Man)
--
#!/usr/bin/perl -- Russ Allbery, Just Another Perl Hacker
$^=q;@!>~|{>krw>yn{u<$$<[~|| 0gFzD gD,
00Fz, 0,,( 0hF 0g)F/=, 0> "L$/GEIFewe{,$/ 0C$~> "@=,m,|,(e 0.), 01,pnn,y{
rw} >;,$0=q,$,,($_=$^)=~y,$/ C-~><@=\n\r,-~$:-u/ #y,d,s,(\$.),$1,gee,print
cleanest way from the
perspective of a POD formatter is probably to add =imagetitle as well
(valid only inside an =image/=endimage pair) rather than trying to parse
the argument to =image.
--
#!/usr/bin/perl -- Russ Allbery, Just Another Perl Hacker
$^=q;@!>~|{>krw>yn{u<$$<[~|| 0gF
to implement something similar
> to --add-command of xgettext.
Yes, call the code_handler() method and pass it a callback. That callback
will be called for each non-POD block in the source file, and can then do
what it wants with them.
--
#!/usr/bin/perl -- Russ Allbery, Just Another Per
maintained using Git; see the instructions on the above
page to access the Git repository.
Please let me know of any problems or feature requests not already listed
in the TODO file.
--
#!/usr/bin/perl -- Russ Allbery, Just Another Perl Hacker
$^=q;@!>~|{>krw>yn{u<$$<[~|| 0gFzD gD,
e TODO file.
--
#!/usr/bin/perl -- Russ Allbery, Just Another Perl Hacker
$^=q;@!>~|{>krw>yn{u<$$<[~|| 0gFzD gD,
00Fz, 0,,( 0hF 0g)F/=, 0> "L$/GEIFewe{,$/ 0C$~> "@=,m,|,(e 0.), 01,pnn,y{
rw} >;,$0=q,$,,($_=$^)=~y,$/ C-~><@=\n\r,-~$:-u/ #y,d,s,(\$.),$1,gee,print
the code that tries to generate links and cares about the
places where this ambiguity might cause problems.
--
#!/usr/bin/perl -- Russ Allbery, Just Another Perl Hacker
$^=q;@!>~|{>krw>yn{u<$$<[~|| 0gFzD gD,
00Fz, 0,,( 0hF 0g)F/=, 0> "L$/GEIFewe{,$/ 0C$~> "@=,m,|,(e 0.), 01,pnn,y{
rw} >;,$0=q,$,,($_=$^)=~y,$/ C-~><@=\n\r,-~$:-u/ #y,d,s,(\$.),$1,gee,print
99, so I suspect it was in Tom Christiansen's original
pod2man script.
So, the short answer is "very, very, very long-standing backward
compatibility."
--
#!/usr/bin/perl -- Russ Allbery, Just Another Perl Hacker
$^=q;@!>~|{>krw>yn{u<$$<[~|| 0gFzD gD,
00Fz, 0,,( 0hF 0
ifier headers to all substantial source files.
--
#!/usr/bin/perl -- Russ Allbery, Just Another Perl Hacker
$^=q;@!>~|{>krw>yn{u<$$<[~|| 0gFzD gD,
00Fz, 0,,( 0hF 0g)F/=, 0> "L$/GEIFewe{,$/ 0C$~> "@=,m,|,(e 0.), 01,pnn,y{
rw} >;,$0=q,$,,($_=$^)=~y,$/ C-~><@=\n\r,-~$:-u/ #y,d,s,(\$.),$1,gee,print
Russ Allbery (ea...@eyrie.org) <http://www.eyrie.org/~eagle/>
(Or you can leave it; it's not
too large.)
--
#!/usr/bin/perl -- Russ Allbery, Just Another Perl Hacker
$^=q;@!>~|{>krw>yn{u<$$<[~|| 0gFzD gD,
00Fz, 0,,( 0hF 0g)F/=, 0> "L$/GEIFewe{,$/ 0C$~> "@=,m,|,(e 0.), 01,pnn,y{
rw} >;,$0=q,$,,($_=$^)=~y,$/ C-~><@=\n\r,-~$:-u/ #y,d,s,(\$.),$1,gee,print
y.
Note to Perl core maintainers who are incorporating this update: feel free
to remove the docs/metadata directory when importing, as this is source to
generate the README file and web pages. (Or you can leave it; it's not
too large.)
--
#!/usr/bin/perl -- Russ Allbery, Just Another Perl H
rquote options (and corresponding
--lquote and --rquote flags to pod2man) to set the left and right
quotes for C<> text independently. (#103298)
Remove test for nested L<> markup, since an upcoming version of
Pod::Simple will drop support for this. (#114075)
-
standard error, but not to throw an exception. "pod" says to
include a POD ERRORS section in the resulting documentation
summarizing the errors. "none" ignores POD errors entirely, as
much as possible.
The default is "die".
(Now
efault to fail on generation. (I'd really
rather not reverse that decision at this point.)
--
#!/usr/bin/perl -- Russ Allbery, Just Another Perl Hacker
$^=q;@!>~|{>krw>yn{u<$$<[~|| 0gFzD gD,
00Fz, 0,,( 0hF 0g)F/=, 0> "L$/GEIFewe{,$/ 0C$~> "@=,m,|,(e 0.),
bin/perl -- Russ Allbery, Just Another Perl Hacker
$^=q;@!>~|{>krw>yn{u<$$<[~|| 0gFzD gD,
00Fz, 0,,( 0hF 0g)F/=, 0> "L$/GEIFewe{,$/ 0C$~> "@=,m,|,(e 0.), 01,pnn,y{
rw} >;,$0=q,$,,($_=$^)=~y,$/ C-~><@=\n\r,-~$:-u/ #y,d,s,(\$.),$1,gee,print
; Unless there's a need for Encode to be present when padlators is made,
> I propose that the code in Pod::Man::new() which warns if Encode isn't
> present, only does so if !$ENV{PERL_CORE}.
This is a great idea. Thanks! Now implemented, and will be in the next
podlators re
to require Encode as a prerequisite for
podlators when building core. Is there any way to do that?
--
#!/usr/bin/perl -- Russ Allbery, Just Another Perl Hacker
$^=q;@!>~|{>krw>yn{u<$$<[~|| 0gFzD gD,
00Fz, 0,,( 0hF 0g)F/=, 0> "L$/GEIFewe{,$/ 0C$~> "@=,m,|,(e 0.), 01,pnn,y{
rw} >;,$0=q,$,,($_=$^)=~y,$/ C-~><@=\n\r,-~$:-u/ #y,d,s,(\$.),$1,gee,print
see the instructions on the above
page to access the Git repository.
Please let me know of any problems or feature requests not already listed
in the TODO file.
--
#!/usr/bin/perl -- Russ Allbery, Just Another Perl Hacker
$^=q;@!>~|{>krw>yn{u<$$<[~|| 0gFzD gD,
00Fz, 0,,( 0hF 0g
rlpodstyle.pod in core (*not*
> cpan/podlators/pod/...), and the other being the minor tweaks to
> Makefile.PL, that now look like the following. You can probably just
> apply this with -p2.
Thanks! I'll apply this, fix the naming of the file, and put out another
release.
--
#!/us
considerably. I removed the *.pod suffix to work around problems with
Module::Build, and it shouldn't be necessary now that the package is only
using ExtUtils::MakeMaker again.
--
#!/usr/bin/perl -- Russ Allbery, Just Another Perl Hacker
$^=q;@!>~|{>krw>yn{u<$$<[~|| 0gFzD gD,
nt to do this from Makefile.PL?
--
#!/usr/bin/perl -- Russ Allbery, Just Another Perl Hacker
$^=q;@!>~|{>krw>yn{u<$$<[~|| 0gFzD gD,
00Fz, 0,,( 0hF 0g)F/=, 0> "L$/GEIFewe{,$/ 0C$~> "@=,m,|,(e 0.), 01,pnn,y{
rw} >;,$0=q,$,,($_=$^)=~y,$/ C-~><@=\n\r,-~$:-u/ #y,d,s,(\$.),$1,gee,print
ed using Git; see the instructions on the above
page to access the Git repository.
Please let me know of any problems or feature requests not already listed
in the TODO file.
--
#!/usr/bin/perl -- Russ Allbery, Just Another Perl Hacker
$^=q;@!>~|{>krw>yn{u<$$<[~|| 0gFzD gD,
00Fz, 0,
Windows, .com on VMS).
Ah! Thank you. I hadn't understood that.
I'll re-add the .PL wrappers (with better documentation of why they're
required) directly in podlators and put out a new release. Then hopefully
core can just use the same wrappers that come with the podlators CPAN
dist
"Craig A. Berry" writes:
> On Sun, Jan 3, 2016 at 12:39 AM, Russ Allbery wrote:
>> I'm pleased to announce release 4.04 of podlators. This fixes some
>> test portability and merges changes made as part of the import into
>> blead.
>> Please let me kn
dy listed
in the TODO file.
--
Russ Allbery (ea...@eyrie.org) <http://www.eyrie.org/~eagle/>
ess the Git repository.
Please let me know of any problems or feature requests not already listed
in the TODO file.
--
Russ Allbery (ea...@eyrie.org) <http://www.eyrie.org/~eagle/>
problems or feature requests not already listed
in the TODO file.
--
Russ Allbery (ea...@eyrie.org) <http://www.eyrie.org/~eagle/>
see the instructions
on the above page to access the Git repository.
Please let me know of any problems or feature requests not already listed
in the TODO file.
--
Russ Allbery (ea...@eyrie.org) <http://www.eyrie.org/~eagle/>
e been uploaded to Debian unstable.
Please let me know of any problems or feature requests not already listed
in the TODO file.
--
Russ Allbery (ea...@eyrie.org) <http://www.eyrie.org/~eagle/>
has entered CPAN as
file: $CPAN/authors/id/R/RR/RRA/podlators-2.5.3.tar.gz
size: 104823 bytes
md5: b7418e350400592021ff2de1d6212edd
Changes since the previous release:
2013-10-05 Russ Allbery
* VERSION: podlators 2.5.3 released.
* t/man-empty.t: Skip errors test if Pod::S
-2.5.2.tar.gz
size: 104911 bytes
md5: debcce4412596dc1301c0df8c86415cf
Changes since previous release:
2013-09-22 Russ Allbery
* VERSION: podlators 2.5.2 released.
* lib/Pod/Man.pm (_handle_element_start): Merge the two formatting
hashes and move the data to the top of
bytes
md5: 9f79d07cf4ac26fd46be1d91a05a82aa
Changes from the previous release:
2013-02-27 Russ Allbery
* VERSION: podlators 2.5.1 released.
* t/color.t: Add Z<> to tag width test to avoid triggering the new
Pod::Parser warning about numeric items in description
and then warning is strange. But I probably haven't thought
through it.
--
Russ Allbery (r...@stanford.edu) <http://www.eyrie.org/~eagle/>
ailures.
> In general, I think that this is an improvement, as one should not
> usually mix =item formats. I can see that your case is completely
> legitimate, though. You can fix it by wrapping those items in C<>s.
Better (since it doesn't change the formatting):
=i
e as the
podlators test suite including a test for handling of mismatched item
types, since that sounds like the kind of edge case that I'd test, and not
expecting the new warning.
--
Russ Allbery (r...@stanford.edu) <http://www.eyrie.org/~eagle/>
Karl Williamson writes:
> On 01/26/2013 02:23 PM, Russ Allbery wrote:
>> Karl Williamson writes:
>>> With Pod::Parser, you just do
>>> parse_from_file($in_fh, $out_fh)
>>> and it outputs the pod to $out_fh. Pod::Simple has a method of the same
>>&
u flush $out_fh? Pod::Parser did that but Pod::Simple doesn't, so
it's possible if you're doing something short that the entire output was
still buffered.
Pod::Man and Pod::Text use this Pod::Simple method and do have test suites
for it and it seems to work.
--
Russ Allbery (r...@s
rl/podlators-2.5.0.tar.gz
has entered CPAN as
file: $CPAN/authors/id/R/RR/RRA/podlators-2.5.0.tar.gz
size: 101497 bytes
md5: 964f19e1ab23420a2f7c8753943b8a03
Changes from the previous release:
2013-01-02 Russ Allbery
* VERSION: podlators 2.5.0 released.
* lib/Pod/Man.
ly doing anyone any good.
--
Russ Allbery (r...@stanford.edu) <http://www.eyrie.org/~eagle/>
"David E. Wheeler" writes:
> On Jun 7, 2012, at 10:20 AM, Russ Allbery wrote:
>> That seems like something that maybe we could all agree could be done,
>> no? This seems broader than just POD tests; the test failures may be
>> due to some minor bit of functiona
"David E. Wheeler" writes:
> On Jun 7, 2012, at 10:06 AM, Russ Allbery wrote:
>>> Basically every tool that does CPAN installs will refuse to install if
>>> the test suite fails, and this isn't going to be viewed as buggy or
>>> changed.
>> Do
ng to be viewed as buggy or
> changed.
Do they at least tell people how to install the module anyway if the test
failure doesn't look serious?
--
Russ Allbery (r...@stanford.edu) <http://www.eyrie.org/~eagle/>
;t care about the failure, just ignore it and install the module
anyway.
Is there some tool involved that's refusing to install modules if the test
suite fails? If so, I think that tool is what's buggy here, and that tool
should be fixed so that it's possible to install modules with fai
from previous release:
2012-06-01 Russ Allbery
* VERSION: podlators 2.4.2 released.
* t/text-encoding.t: Remove the test of a POD document without an
encoding. We previously tested that this interpreted the document
as ISO 8859-1, but Pod::Simple behavior has
ed CPAN as
file: $CPAN/authors/id/R/RR/RRA/podlators-2.4.1.tar.gz
size: 96520 bytes
md5: 78f9279c552d50692f02ce3744e89639
Changes from the previous release:
2012-05-30 Russ Allbery
* VERSION: podlators 2.4.1 released.
* lib/Pod/Man.pm (parse_file): Override the Pod::Simple
ux
Works for me with:
windlord:~> perldoc -V
Perldoc v3.15_04, under perl v5.014002 for linux
I'm starting to suspect something weird going on with a newer version of
perldoc.
--
Russ Allbery (r...@stanford.edu) <http://www.eyrie.org/~eagle/>
Shawn H Corey writes:
> On 12-04-30 12:33 PM, Russ Allbery wrote:
>> Which pod2foo are you running that made that verbatim? Neither
>> pod2text nor pod2man from podlators as distributed on CPAN do.
> I just type: perldoc perldoc
That uses Pod::Man by default, at least on
running that made that verbatim? Neither pod2text
nor pod2man from podlators as distributed on CPAN do.
--
Russ Allbery (r...@stanford.edu) <http://www.eyrie.org/~eagle/>
Shawn H Corey writes:
> On 12-04-30 11:19 AM, Russ Allbery wrote:
>> I suspect indentation wasn't the goal, but rather preserving
>> formatting. There currently isn't any way in POD to preserve line
>> breaks and allow inline formatting, which gets a little ann
, but it's not really something to rely
upon.)
--
Russ Allbery (r...@stanford.edu) <http://www.eyrie.org/~eagle/>
hat's what POD historically has been.
The DWIM heuristic here would probably be something like checking to see
if all of the =item's in an =over block are =item 1, and if so,
automatically renumbering. But that requires read-ahead in the parsing.
--
Russ Allbery (r...@stanford.edu)
Shawn H Corey writes:
> On 12-04-26 11:57 AM, Russ Allbery wrote:
>> 1. If the =item tags are numeric, ignore the value of the numbers and just
>> renumber them. This is similar to what other markup languages do, but
>> it has the significant problem of making it a
is a small price to pay.
In retrospect, it would have been nice to have different =item commands
for numeric and bulleted lists, but, well, POD always made tradeoff
decisions in favor of reducing the size of the language.
--
Russ Allbery (r...@stanford.edu) <http://www.eyrie.org/~eagle/>
Grant McLean writes:
> My thoughts on the second issue are that we could modify Pod::Simple to
> 'whine' if it sees non-ASCII bytes but no =encoding. This in turn would
> cause Test::Pod to pick up the error and help people fix it.
I would be in favor of that.
Shawn H Corey writes:
> On 12-04-25 11:22 AM, Russ Allbery wrote:
>> I think a better approach would have been to add a new command
>> (=formatted or something) that had these semantics rather than changing
>> the interpretation of existing verbatim paragraphs.
> It wo
ts in ways
that could be destructive. (For example, it would not format perlpodspec
correctly!)
--
Russ Allbery (r...@stanford.edu) <http://www.eyrie.org/~eagle/>
se a lot of people are using perldoc and the default behavior of it,
> which is to page thru nroff-formatted non-hypertext.
> Yes, it's the lowest common denominator.
> It's also a *very* common denominator.
No, actually, please *do* that, as Pod::Text and Pod::Man (including
perldoc) have handled this properly since forever. This will render as:
my friend's web site <http://stuff.com/>
which is just fine.
Really, please, start using this right now. I think the tools will be
fine. The core tools are already fine.
--
Russ Allbery (r...@stanford.edu) <http://www.eyrie.org/~eagle/>
erbatimFormatted*
>> --over-bullet
>> --Document
It looks like I work around this in Pod::Man and Pod::Text by accident,
and in a way that might actually break if this were fixed. Hrm. I can't
tell for sure. I *think* it would be okay anyway, but I'm not positive.
I'm not sure how the method calls would change if this behavior were
changed.
Basically, at present, I'm assuming that all the paragraphs are inside the
item until I see another item, whether they're passed in as the text of
the item or not.
--
Russ Allbery (r...@stanford.edu) <http://www.eyrie.org/~eagle/>
enerate an index.
> I guess that candidate converters that could use X<..> are converters to
> formats where index entries exist, such as DocBook and maybe LaTeX.
And *roff, although admittedly there probably aren't that many people who
use Pod::Man to generate printable documents rath
y the fact that I, as
maintainer of Pod::Man, have supported anchor text for URL L<> links from
the beginning and opposed this restriction from the start.
The restriction has nothing to do with targetting man pages.
--
Russ Allbery (r...@stanford.edu) <http://www.eyrie.org/~eagle/>
The parsing issues are not that
serious.
I think this syntax should be undeprecated and declared officially
blessed.
--
Russ Allbery (r...@stanford.edu) <http://www.eyrie.org/~eagle/>
s that it was more intended to be like the warnings flag to a
compiler or like use warnings in Perl: something to warn about stuff
that's technically syntactically valid but probably in error.
--
Russ Allbery (r...@stanford.edu) <http://www.eyrie.org/~eagle/>
quot;..."=end" regions. Such an itemless "=over"
> ... "=back" region in Pod is equivalent in meaning to a
> "..." element in HTML."
> Given that there is clearly a use for =itemless =over/=back blocks,
> should it still be a warning? I think no, and instead, Pod::Checker
> should warn about an empty =over/=back block, one that contains nothing
> but whitespace.
I agree -- this one should definitely go.
Thank you for your work on this!
--
Russ Allbery (r...@stanford.edu) <http://www.eyrie.org/~eagle/>
re are some bugs open in RT.)
--
Russ Allbery (r...@stanford.edu) <http://www.eyrie.org/~eagle/>
se, and I'm not sure what Pod::Simple does.
--
Russ Allbery (r...@stanford.edu) <http://www.eyrie.org/~eagle/>
th
minor or moderate eye problems that make "average" fonts pretty
unappealing and annoying, or even unreadable. And the first example made
the "Like" column mostly unuseful if one can't widen the screen. (Forced
line wrapping on a narrow screen isn't *too* bad for te
y uses Pod::Simple and remove
the old one.
--
Russ Allbery (r...@stanford.edu) <http://www.eyrie.org/~eagle/>
ing is actually:
> | =head2 Switch statements
> | X X X X X
> Everything up to the paragraph separator is part of the headline.
Yeah, but they're still basically trailing whitespace. I think this is a
(minor) bug in whatever module generated that HTML. It should strip
trailing white
formats. Which is what I was assuming
that Karl was doing.
--
Russ Allbery (r...@stanford.edu) <http://www.eyrie.org/~eagle/>
meone feels energetic, they could then improve that.
--
Russ Allbery (r...@stanford.edu) <http://www.eyrie.org/~eagle/>
c.).
I don't object to supporting it in Pod::Text and Pod::Man, but I'd have to
ask someone else to write the initial implementation. I think support in
Pod::Man at least would be fairly important before deciding to add tables
to Perl's core documentation, but the research
0.tar.gz
size: 94197 bytes
md5: 12f9440cb0dda67cf089d7a4b28f7329
Changes since the previous release:
2010-10-10 Russ Allbery
* VERSION: podlators 2.4.0 released.
* scripts/pod2man: Remove the code to generate the #! line and
supporting code and instead rely on ExtU
"David E. Wheeler" writes:
> 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 " where isn't a bullet or a
>> number produces an unorde
x27;s
because "=item " where isn't a bullet or a number
produces an unordered list. perlpodspec does say that, although I admit I
had to read it a couple of times.
--
Russ Allbery (r...@stanford.edu) <http://www.eyrie.org/~eagle/>
elpful in getting pod2man switched over.
> 6) But I similarly-and-worse forgot to produce a /drop-in/ pod2man
> replacement.
That's okay, I did that. :)
--
Russ Allbery (r...@stanford.edu) <http://www.eyrie.org/~eagle/>
latter is a
description list. I think pod2html is wrong here.
--
Russ Allbery (r...@stanford.edu) <http://www.eyrie.org/~eagle/>
se.
So this is a bad thing to deprecate.
--
Russ Allbery (r...@stanford.edu) <http://www.eyrie.org/~eagle/>
S: I know I can embed HTML but the man pages can't display those.
I'm afraid man pages also can't display color.
Did you already know about Pod::Text::Color?
--
Russ Allbery (r...@stanford.edu) <http://www.eyrie.org/~eagle/>
Allison Randal writes:
> Russ Allbery wrote:
>> This is not the sort of thing that one gets to change retroactively,
>> I'm afraid, no matter how nice it would be for consistency.
> Agreed on keeping Perl 5 pod changes minimal, but I thought it always
> worked that wa
always have since the syntax was introduced, and changing that is a huge
failure of backward compatibility with existing documents. Likewise with
not forcing people to escape every angle bracket, only the ones that look
like formatting codes.
This is not the sort of thing that one gets to change
with Pod::Text subclasses, suppresses formatting in the NAME
section of man pages, and fixes a few other bugs. Note that Pod::Simple
3.06 or later is now required.
Changes since previous release:
2009-12-28 Russ Allbery
* VERSION: podlators 2.3.0 released.
* lib/Pod/Man.pm
t support
preserve_whitespace, so I don't believe there's anything that needs to be
changed in it.
--
Russ Allbery (r...@stanford.edu) <http://www.eyrie.org/~eagle/>
and what the hell is going on.
I think that would be awesome. I end up having to read source code
whenever I have to interact with it since the documentation for people
writing POD translators leaves a lot to be desired.
--
Russ Allbery (r...@stanford.edu) <http://www.eyrie.org/~eagle/>
1 - 100 of 258 matches
Mail list logo
