perl.pod-people http://www.nntp.perl.org/group/perl.pod-people/ ... Copyright 1998-2017 perl.org Tue, 27 Jun 2017 17:25:26 +0000 ask@perl.org Re: pod embedded in pod by Shawn H Corey On Thu, 13 Apr 2017 11:36:23 +0000 <br/>RAPPAZ Francois via pod-people &lt;pod-people@perl.org&gt; wrote: <br/> <br/>&gt; How can I embed pod directives in a pod directive so that they are <br/>&gt; displayed as plain text ? I have tried =begin pod or =begin text <br/>&gt; without success. Should I use E&lt;61&gt; instead of = ? <br/>&gt; <br/>&gt; Thanks <br/>&gt; <br/>&gt; Fran&ccedil;ois <br/>&gt; <br/> <br/>Usually embedded POD is done in a verbatim paragraph since these will <br/>be rendered in a monospace font. <br/> <br/>=head1 Embedding POD in a POD <br/> <br/> =head1 This is not a heading. <br/> This is a verbatim paragraph. <br/> This will be displayed in a monospace font. <br/> <br/>This is a regular paragraph. <br/> <br/>=cut <br/> <br/> <br/>-- <br/>Don&#39;t stop where the ink does. <br/> <br/> Shawn H Corey <br/> http://www.nntp.perl.org/group/perl.pod-people/2017/04/msg2070.html Thu, 13 Apr 2017 12:51:38 +0000 Re: pod embedded in pod by Peter Karman RAPPAZ Francois via pod-people wrote on 4/13/17 6:36 AM:<br/>&gt; How can I embed pod directives in a pod directive so that they are displayed as<br/>&gt; plain text ? I have tried =begin pod or =begin text without success. Should I<br/>&gt; use E&lt;61&gt; instead of = ?<br/>&gt;<br/><br/>can you just indent the embedded pod like this?<br/><br/>=pod<br/><br/>example of pod within pod<br/><br/> =pod<br/><br/> =over<br/><br/> =item foo<br/><br/> =item bar<br/><br/> =cut<br/><br/>this was an example. thanks.<br/><br/>=cut<br/><br/>-- <br/>Peter Karman . https://karpet.github.io . https://keybase.io/peterkarman<br/> http://www.nntp.perl.org/group/perl.pod-people/2017/04/msg2069.html Thu, 13 Apr 2017 12:45:58 +0000 pod embedded in pod by RAPPAZ Francois via pod-people How can I embed pod directives in a pod directive so that they are displayed as plain text ? I have tried =begin pod or =begin text without success. Should I use E&lt;61&gt; instead of = ? <br/> <br/>Thanks <br/> <br/>Fran&ccedil;ois <br/> http://www.nntp.perl.org/group/perl.pod-people/2017/04/msg2068.html Thu, 13 Apr 2017 11:44:50 +0000 Re: Pod::Simple::Select by Karl Williamson On 03/30/2017 06:17 AM, RAPPAZ Francois via pod-people wrote: <br/>&gt; At the end, I got the idea of <br/>&gt; <br/>&gt; - Subclassing Pod::Simple to detect the start line of pod <br/>&gt; directive that I want to select and extract from a pod file. The end <br/>&gt; line is when a cut is met or when another directive given in the select <br/>&gt; method begins <br/>&gt; <br/>&gt; - Having a $parser -&gt;select({ head1 =&gt;[&ldquo;Name&rdquo;, <br/>&gt; &ldquo;this\\s*is\\s*a\\s*title&rdquo; ], head2=&gt;{&ldquo;foo&rdquo;, &ldquo;bar&rdquo;} }) method, to give <br/>&gt; pod directive to select section of the pod. Here the selected pod <br/>&gt; directives would be <br/>&gt; <br/>&gt; =head1 Name <br/>&gt; &hellip;. <br/>&gt; =head2 Foo <br/>&gt; &hellip; <br/>&gt; =head 1 This is a title <br/>&gt; &hellip;.. <br/>&gt; =head2 bar <br/>&gt; &hellip;. <br/>&gt; <br/>&gt; - Having all the entries for a pod directive given in -&gt;select <br/>&gt; and found in the file, stored with the start line and line and the <br/>&gt; corresponding array ref given in select. That should not eat too much <br/>&gt; memory. <br/>&gt; <br/>&gt; - Using Tie::File to extract the line ( start &hellip; end) for each <br/>&gt; pod directive found in the file. Since Tie::File does not load the file <br/>&gt; into memory, this should work even for big files. <br/>&gt; <br/>&gt; <br/>&gt; <br/>&gt; For the few simple test I have made, it works&hellip; even if one has something <br/>&gt; like <br/>&gt; <br/>&gt; =head2 This get C&lt;complicated&gt; <br/>&gt; <br/>&gt; <br/>&gt; <br/>&gt; Have I reinvented the wheel or is it worth to make a <br/>&gt; Pode::Simple::Select module with these ~190 lines of codes ? <br/>&gt; <br/>&gt; Thanks <br/>&gt; <br/>&gt; <br/>&gt; <br/>&gt; Fran&ccedil;ois <br/>&gt; <br/>&gt; <br/>&gt; <br/> <br/>I don&#39;t know without delving deeper into things. But I have worked on <br/>code to extract just the pod from a file containing other content, and <br/>that isn&#39;t as simple as it might seem, requiring changes in the heart of <br/>Pod::Simple to get it all right. I shelved this work, but expect to <br/>complete it in the next 2 months. <br/> <br/>So your idea may work, but there may be edge cases which it fails in. <br/> http://www.nntp.perl.org/group/perl.pod-people/2017/03/msg2067.html Thu, 30 Mar 2017 18:17:39 +0000 Pod::Simple::Select by RAPPAZ Francois via pod-people At the end, I got the idea of <br/> <br/>- Subclassing Pod::Simple to detect the start line of pod directive that I want to select and extract from a pod file. The end line is when a cut is met or when another directive given in the select method begins <br/> <br/>- Having a $parser -&gt;select({ head1 =&gt;[&quot;Name&quot;, &quot;this\\s*is\\s*a\\s*title&quot; ], head2=&gt;{&quot;foo&quot;, &quot;bar&quot;} }) method, to give pod directive to select section of the pod. Here the selected pod directives would be <br/> <br/>=head1 Name <br/> .... <br/>=head2 Foo <br/> ... <br/>=head 1 This is a title <br/> ..... <br/>=head2 bar <br/> .... <br/> <br/> <br/>- Having all the entries for a pod directive given in -&gt;select and found in the file, stored with the start line and line and the corresponding array ref given in select. That should not eat too much memory. <br/> <br/>- Using Tie::File to extract the line ( start ... end) for each pod directive found in the file. Since Tie::File does not load the file into memory, this should work even for big files. <br/> <br/> <br/>For the few simple test I have made, it works... even if one has something like <br/>=head2 This get C&lt;complicated&gt; <br/> <br/>Have I reinvented the wheel or is it worth to make a Pode::Simple::Select module with these ~190 lines of codes ? <br/>Thanks <br/> <br/>Fran&ccedil;ois <br/> http://www.nntp.perl.org/group/perl.pod-people/2017/03/msg2066.html Thu, 30 Mar 2017 12:18:43 +0000 Re: raw_data with Pod::Simple::PullParser by Ron Savage Hi Francois<br/><br/>Do what works. If you&#39;re only parsing your own POD, then what you&#39;re <br/>doing now should be OK.<br/><br/>I would like (one day!) to write a BNF for POD and use Marpa:<br/><br/>http://savage.net.au/Marpa.html<br/><br/>About 10 of the Perl packages there are mine.<br/><br/>If you intend to create a module fit for CPAN, then of course it&#39;s a <br/>bigger decision as to the internal structure of your code.<br/><br/>On 29/03/17 17:09, RAPPAZ Francois via pod-people wrote:<br/>&gt; Hi Ron,<br/>&gt;<br/>&gt; Thanks for the suggestion.<br/>&gt;<br/>&gt; At the end, reading the pod file and capturing the key from head1 is easy (below). I could use a Pod::Simple::SimpleTree , but I would still to have the output as raw pod. Probably using a parser to select pars of pod is not a good idea ?<br/>&gt;<br/>&gt; Fran&ccedil;ois<br/>&gt;<br/>&gt; my $fname = shift;<br/>&gt; my $mod;<br/>&gt; open $mod, &quot;&lt;$fname&quot; or die &quot;Can&#39;t open $fname $! \n&quot;;<br/>&gt; my %data;<br/>&gt; my $data_ar;<br/>&gt; my $key;<br/>&gt; my $ispod;<br/>&gt; for my $line (&lt;$mod&gt;) {<br/>&gt; chomp $line;<br/>&gt; if ( $line =~ /^=cut/ ) { $ispod = 0; }<br/>&gt; if ( $line =~ /^=head1\s*(.+)$/i ) {<br/>&gt; $ispod = 1;<br/>&gt; if ($key) { #$key read from the previous =head1<br/>&gt; $data{$key} = $data_ar; #store the array of lines as an array ref<br/>&gt; $data_ar = undef; # and prepare a new array<br/>&gt; }<br/>&gt; $key = $1; #now fetch the new value for $key<br/>&gt; }<br/>&gt; push @{$data_ar}, $line if ($ispod) ; #store the line in the array if we are in a pod section<br/>&gt;<br/>&gt; }<br/>&gt; close $mod;<br/>&gt; $data{$key} = $data_ar; #fetch the lines from the last =head1 read<br/>&gt; =for comment<br/>&gt; for $key ( keys %data ) {<br/>&gt; print &quot;*$key*\n&quot;;<br/>&gt; print join( &quot;\n&quot;, @{ $data{$key} } ), &quot;\n&quot;;<br/>&gt;<br/>&gt; }<br/>&gt; =cut<br/>&gt; return %data;<br/>&gt;<br/>&gt; -----Original Message-----<br/>&gt; From: Ron Savage [mailto:ron@savage.net.au]<br/>&gt; Sent: 28 March 2017 23:36<br/>&gt; To: pod-people@perl.org<br/>&gt; Subject: Re: raw_data with Pod::Simple::PullParser<br/>&gt;<br/>&gt; Hi Fran&ccedil;ois<br/>&gt;<br/>&gt; Can&#39;t help specifically but I do suggest you use a tree rather than a hash. It just makes much more sense to me to store the pod that way.<br/>&gt;<br/>&gt; --<br/>&gt; Ron Savage - savage.net.au<br/>&gt;<br/><br/>-- <br/>Ron Savage - savage.net.au<br/> http://www.nntp.perl.org/group/perl.pod-people/2017/03/msg2065.html Wed, 29 Mar 2017 06:18:21 +0000 RE: raw_data with Pod::Simple::PullParser by RAPPAZ Francois via pod-people Hi Ron, <br/> <br/>Thanks for the suggestion. <br/> <br/>At the end, reading the pod file and capturing the key from head1 is easy (below). I could use a Pod::Simple::SimpleTree , but I would still to have the output as raw pod. Probably using a parser to select pars of pod is not a good idea ? <br/> <br/>Fran&ccedil;ois <br/> <br/>my $fname = shift; <br/> my $mod; <br/> open $mod, &quot;&lt;$fname&quot; or die &quot;Can&#39;t open $fname $! \n&quot;; <br/> my %data; <br/> my $data_ar; <br/> my $key; <br/> my $ispod; <br/> for my $line (&lt;$mod&gt;) { <br/> chomp $line; <br/> if ( $line =~ /^=cut/ ) { $ispod = 0; } <br/> if ( $line =~ /^=head1\s*(.+)$/i ) { <br/> $ispod = 1; <br/> if ($key) { #$key read from the previous =head1 <br/> $data{$key} = $data_ar; #store the array of lines as an array ref <br/> $data_ar = undef; # and prepare a new array <br/> } <br/> $key = $1; #now fetch the new value for $key <br/> } <br/> push @{$data_ar}, $line if ($ispod) ; #store the line in the array if we are in a pod section <br/> <br/> } <br/> close $mod; <br/> $data{$key} = $data_ar; #fetch the lines from the last =head1 read <br/>=for comment <br/> for $key ( keys %data ) { <br/> print &quot;*$key*\n&quot;; <br/> print join( &quot;\n&quot;, @{ $data{$key} } ), &quot;\n&quot;; <br/> <br/> } <br/>=cut <br/> return %data; <br/> <br/>-----Original Message----- <br/>From: Ron Savage [mailto:ron@savage.net.au] <br/>Sent: 28 March 2017 23:36 <br/>To: pod-people@perl.org <br/>Subject: Re: raw_data with Pod::Simple::PullParser <br/> <br/>Hi Fran&ccedil;ois <br/> <br/>Can&#39;t help specifically but I do suggest you use a tree rather than a hash. It just makes much more sense to me to store the pod that way. <br/> <br/>-- <br/>Ron Savage - savage.net.au <br/> http://www.nntp.perl.org/group/perl.pod-people/2017/03/msg2064.html Wed, 29 Mar 2017 06:09:48 +0000 Re: raw_data with Pod::Simple::PullParser by Ron Savage Hi Fran&ccedil;ois<br/><br/>Can&#39;t help specifically but I do suggest you use a tree rather than a <br/>hash. It just makes much more sense to me to store the pod that way.<br/><br/>-- <br/>Ron Savage - savage.net.au<br/> http://www.nntp.perl.org/group/perl.pod-people/2017/03/msg2063.html Tue, 28 Mar 2017 21:36:50 +0000 raw_data with Pod::Simple::PullParser by RAPPAZ Francois via pod-people I have a small file of pod documentation and I would like to have a hash with keys being the head1 text (NAME, VERSION, AUTHOR etc) and value being the raw data of the lines read up to the next =head1. <br/> <br/>I have subclassed Pod::Simple::PullParser to have the text value after head1, but my problem is to have the unparsed lines (including this =head1 XXX) <br/> <br/>I saw that there is a raw_mode in the the _accessorize list in Pod::Simple and I have tried this code in my subclass <br/> <br/>package Myparser; <br/>use base qw(Pod::Simple::PullParser); <br/>... <br/>sub new { <br/> my $self = shift; <br/> my $new = $self-&gt;SUPER::new(@_); <br/> $new-&gt;{&#39;output_fh&#39;} ||= *STDOUT{IO}; <br/> $new-&gt;_accessorize(&#39;raw_mode&#39;=&gt;1); <br/> return $new; <br/> <br/>} <br/> <br/>But this does not seems to change the ouput of $token-&gt;text for example. <br/> <br/>Thanks for any help <br/> <br/>Fran&ccedil;ois <br/> http://www.nntp.perl.org/group/perl.pod-people/2017/03/msg2062.html Tue, 28 Mar 2017 09:33:39 +0000 Re: podlators 4.09 released by Steve Hay via pod-people On 5 November 2016 at 22:04, Russ Allbery &lt;rra@cpan.org&gt; wrote:<br/>&gt; Wow, I somehow completely mangled the From line of that. Just in case<br/>&gt; this didn&#39;t get through:<br/>&gt;<br/>&gt; I&#39;m pleased to announce release 4.09 of podlators.<br/>&gt;<br/><br/>Thanks, applied in commit a7ea90b1451006596c4574b1e65894f0bda1bafc.<br/> http://www.nntp.perl.org/group/perl.pod-people/2016/11/msg2061.html Tue, 08 Nov 2016 14:41:18 +0000 Re: podlators 4.09 released by Russ Allbery Wow, I somehow completely mangled the From line of that. Just in case<br/>this didn&#39;t get through:<br/><br/>I&#39;m pleased to announce release 4.09 of podlators.<br/><br/>podlators contains Pod::Man and Pod::Text modules which convert POD<br/>input to *roff source output, suitable for man pages, or plain text. It<br/>also includes several subclasses of Pod::Text for formatted output to<br/>terminals with various capabilities. It is the source package for the<br/>Pod::Man and Pod::Text modules included with Perl.<br/><br/>Changes from previous release:<br/><br/> [Pod::Text] Use Pod::Simple&#39;s logic to determine the native code<br/> points for NO BREAK SPACE and SOFT HYPHEN instead of hard-coding the<br/> ASCII values. Hopefully fixes the case of mysterious disappearing<br/> open brackets on EBCDIC systems. (#118240)<br/><br/>You can download it from:<br/><br/> &lt;http://www.eyrie.org/~eagle/software/podlators/&gt;<br/><br/>or from CPAN. This package is maintained using Git; see the instructions<br/>on the above page to access the Git repository.<br/><br/>Note to Perl core maintainers who are incorporating this update: feel free<br/>to remove the docs/metadata directory when importing, as this is source to<br/>generate the README file and web pages. (Or you can leave it; it&#39;s not<br/>too large.)<br/><br/>-- <br/>#!/usr/bin/perl -- Russ Allbery, Just Another Perl Hacker<br/>$^=q;@!&gt;~|{&gt;krw&gt;yn{u&lt;$$&lt;[~||&lt;Juukn{=,&lt;S~|}&lt;Jwx}qn{&lt;Yn{u&lt;Qjltn{ &gt; 0gFzD gD,<br/> 00Fz, 0,,( 0hF 0g)F/=, 0&gt; &quot;L$/GEIFewe{,$/ 0C$~&gt; &quot;@=,m,|,(e 0.), 01,pnn,y{<br/>rw} &gt;;,$0=q,$,,($_=$^)=~y,$/ C-~&gt;&lt;@=\n\r,-~$:-u/ #y,d,s,(\$.),$1,gee,print<br/> http://www.nntp.perl.org/group/perl.pod-people/2016/11/msg2060.html Sat, 05 Nov 2016 22:04:37 +0000 podlators 4.09 released by Russ I&#39;m pleased to announce release 4.09 of podlators.<br/><br/>podlators contains Pod::Man and Pod::Text modules which convert POD<br/>input to *roff source output, suitable for man pages, or plain text. It<br/>also includes several subclasses of Pod::Text for formatted output to<br/>terminals with various capabilities. It is the source package for the<br/>Pod::Man and Pod::Text modules included with Perl.<br/><br/>Changes from previous release:<br/><br/> [Pod::Text] Use Pod::Simple&#39;s logic to determine the native code<br/> points for NO BREAK SPACE and SOFT HYPHEN instead of hard-coding the<br/> ASCII values. Hopefully fixes the case of mysterious disappearing<br/> open brackets on EBCDIC systems. (#118240)<br/><br/>You can download it from:<br/><br/> &lt;http://www.eyrie.org/~eagle/software/podlators/&gt;<br/><br/>or from CPAN. This package is maintained using Git; see the instructions<br/>on the above page to access the Git repository.<br/><br/>Note to Perl core maintainers who are incorporating this update: feel free<br/>to remove the docs/metadata directory when importing, as this is source to<br/>generate the README file and web pages. (Or you can leave it; it&#39;s not<br/>too large.)<br/><br/>-- <br/>#!/usr/bin/perl -- Russ Allbery, Just Another Perl Hacker<br/>$^=q;@!&gt;~|{&gt;krw&gt;yn{u&lt;$$&lt;[~||&lt;Juukn{=,&lt;S~|}&lt;Jwx}qn{&lt;Yn{u&lt;Qjltn{ &gt; 0gFzD gD,<br/> 00Fz, 0,,( 0hF 0g)F/=, 0&gt; &quot;L$/GEIFewe{,$/ 0C$~&gt; &quot;@=,m,|,(e 0.), 01,pnn,y{<br/>rw} &gt;;,$0=q,$,,($_=$^)=~y,$/ C-~&gt;&lt;@=\n\r,-~$:-u/ #y,d,s,(\$.),$1,gee,print<br/> http://www.nntp.perl.org/group/perl.pod-people/2016/11/msg2059.html Sat, 05 Nov 2016 21:43:08 +0000 podlators 4.08 released by Russ Allbery The URL<br/><br/> https://archives.eyrie.org/software/perl/podlators-4.08.tar.gz<br/><br/>has entered CPAN as<br/><br/> file: $CPAN/authors/id/R/RR/RRA/podlators-4.08.tar.gz<br/> size: 125283 bytes<br/> md5: e74b689d34855a07685508650fcfeb6d<br/> sha1: c120f62524c437313405478fdfb00608a068172d<br/><br/>Changes since the previous release:<br/><br/> [Pod::Man] Partially revert change in 4.00 to require the name option<br/> (--name to pod2man) when generating man pages from standard input.<br/> Historically, pod2man silently tolerated this, and there turned out to<br/> be a lot of software that depended on this, making the change too<br/> disruptive. Instead, silently set the man page title to STDIN in this<br/> case, but warn about it in the documentation. (#117990)<br/><br/> [Pod::Man] Fix rendering bug for &quot;TRUE (1)&quot;, which was recognized as<br/> needing small caps and then erroneously as a man page reference,<br/> resulting in escaped nroff. (Found by Dan Jacobson with the<br/> XML::LibXML::Element man page.) (Debian Bug#836831)<br/><br/> [Pod::Man] Fix rendering bug causing &quot;\s0(1)&quot; to be mistakenly marked<br/> as a man page reference, later confusing backslash escaping.<br/><br/> [Pod::Man] Add new lquote and rquote options (and corresponding<br/> --lquote and --rquote flags to pod2man) to set the left and right<br/> quotes for C&lt;&gt; text independently. (#103298)<br/><br/> Remove test for nested L&lt;&gt; markup, since an upcoming version of<br/> Pod::Simple will drop support for this. (#114075)<br/><br/>-- <br/>Russ Allbery (eagle@eyrie.org) &lt;http://www.eyrie.org/~eagle/&gt;<br/> http://www.nntp.perl.org/group/perl.pod-people/2016/09/msg2058.html Sun, 25 Sep 2016 02:42:16 +0000 Re: Pod::Simple output as POD by David E. Wheeler On May 13, 2016, at 7:00 PM, Ron Savage &lt;ron@savage.net.au&gt; wrote: <br/> <br/>&gt; So make it -J JustPod, or is that parameter list sacrosanct? <br/>&gt; <br/>&gt; Perhaps leave -M, and add -J, which defaults to a value of JustPod. <br/> <br/>You pass the name of the formatting module to -M. I see no reason to change it. <br/> <br/>D= http://www.nntp.perl.org/group/perl.pod-people/2016/05/msg2057.html Sun, 15 May 2016 03:20:51 +0000 Re: Pod::Simple output as POD by Ron Savage Hi David<br/><br/>On 12/05/16 10:39, David E. Wheeler wrote:<br/>&gt; On May 11, 2016, at 5:29 PM, Karl Williamson &lt;public@khwilliamson.com&gt; wrote:<br/><br/>&gt; Like John, I don&rsquo;t much care. I agree that Pod::Simple::Pod lacks necessary information. ExtractPod seems fine to me. Uh, though there is this:<br/>&gt;<br/>&gt; perldoc [-h] [-D] [-t] [-u] [-m] [-l] [-F]<br/>&gt; [-i] [-V] [-T] [-r]<br/>&gt; [-d destination_file]<br/>&gt; [-o formatname]<br/>&gt; [-M FormatterClassName]<br/>&gt; [-w formatteroption:value]<br/>&gt; [-n nroff-replacement]<br/>&gt; [-X]<br/>&gt; [-L language_code]<br/>&gt; PageName|ModuleName|ProgramName|URL<br/>&gt;<br/>&gt; So the formatter arg to -M would be:<br/>&gt;<br/>&gt; perldoc -M ExtractPod<br/>&gt;<br/>&gt; Which also seems a little weird. Maybe Pod::Simple::PodFormat?<br/><br/>So make it -J JustPod, or is that parameter list sacrosanct?<br/><br/>Perhaps leave -M, and add -J, which defaults to a value of JustPod.<br/><br/>-- <br/>Ron Savage - savage.net.au<br/> http://www.nntp.perl.org/group/perl.pod-people/2016/05/msg2056.html Sat, 14 May 2016 02:01:11 +0000 Re: Pod::Simple output as POD by David E. Wheeler On May 13, 2016, at 11:03 AM, Karl Williamson &lt;public@khwilliamson.com&gt; wrote: <br/> <br/>&gt; If we wanted to be cute, we could call it Pod::Simple::SimplyPod, with you know, only one, natural, ingredient, and no harmful additives. <br/> <br/>But is it organic? Or Biodynamic? <br/> <br/>D <br/> http://www.nntp.perl.org/group/perl.pod-people/2016/05/msg2055.html Fri, 13 May 2016 18:25:18 +0000 Re: Pod::Simple output as POD by Karl Williamson On 05/11/2016 07:38 PM, John SJ Anderson wrote: <br/>&gt; <br/>&gt;&gt; On May 11, 2016, at 17:52, Ron Savage &lt;ron@savage.net.au&gt; wrote: <br/>&gt;&gt; On 12/05/16 10:39, David E. Wheeler wrote: <br/>&gt;&gt; <br/>&gt;&gt;&gt; Which also seems a little weird. Maybe Pod::Simple::PodFormat? <br/>&gt;&gt; <br/>&gt;&gt; Pod::Simple::ExtractPod is good, but possible is Pod::Simple::JustPod. <br/>&gt; <br/>&gt; With only a _tiny_ bit of my tongue in my cheek, I&rsquo;ll throw out Pod::Simple::PlainOldPOD ... <br/>&gt; <br/>&gt; 8^) <br/>&gt; <br/>&gt; j. <br/>&gt; <br/> <br/>I&#39;m leaning towards Pod::Simple::JustPod. I think that captures the <br/>essence, and seems to me to fit the paradigm of the output format. <br/> <br/>If we wanted to be cute, we could call it Pod::Simple::SimplyPod, with <br/>you know, only one, natural, ingredient, and no harmful additives. <br/> http://www.nntp.perl.org/group/perl.pod-people/2016/05/msg2054.html Fri, 13 May 2016 18:03:49 +0000 Re: Pod::Simple output as POD by John SJ Anderson <br/>&gt; On May 11, 2016, at 17:52, Ron Savage &lt;ron@savage.net.au&gt; wrote: <br/>&gt; On 12/05/16 10:39, David E. Wheeler wrote: <br/>&gt; <br/>&gt;&gt; Which also seems a little weird. Maybe Pod::Simple::PodFormat? <br/>&gt; <br/>&gt; Pod::Simple::ExtractPod is good, but possible is Pod::Simple::JustPod. <br/> <br/>With only a _tiny_ bit of my tongue in my cheek, I&rsquo;ll throw out Pod::Simple::PlainOldPOD ... <br/> <br/>8^) <br/> <br/>j. http://www.nntp.perl.org/group/perl.pod-people/2016/05/msg2053.html Thu, 12 May 2016 14:47:29 +0000 Re: Pod::Simple output as POD by Ron Savage Hi<br/><br/>On 12/05/16 10:39, David E. Wheeler wrote:<br/>&gt; On May 11, 2016, at 5:29 PM, Karl Williamson &lt;public@khwilliamson.com&gt; wrote:<br/><br/>&gt; Which also seems a little weird. Maybe Pod::Simple::PodFormat?<br/><br/>Pod::Simple::ExtractPod is good, but possible is Pod::Simple::JustPod.<br/><br/>-- <br/>Ron Savage - savage.net.au<br/> http://www.nntp.perl.org/group/perl.pod-people/2016/05/msg2052.html Thu, 12 May 2016 00:52:46 +0000 Re: Pod::Simple output as POD by David E. Wheeler On May 11, 2016, at 5:29 PM, Karl Williamson &lt;public@khwilliamson.com&gt; wrote: <br/> <br/>&gt;&gt; My only comment on &lsquo;ExtractPod&rsquo; as a name would be that all the other modules in the Pod::Simple dist that do similar things are simply named &lsquo;Pod::Simple::$FORMAT&rsquo;, (e.g., Pod::Simple::HTML, Pod::Simple::RTF, etc.) <br/> <br/>Probably should have been Pod::Simple::Format::*. :-( <br/> <br/>&gt;&gt; At the end of the day, you&rsquo;ve done the work to get it out the door and as far as I&rsquo;m concerned, you can call it whatever you like. 8^) <br/>&gt; <br/>&gt; It&#39;s more a matter of what is the least worst name to help people at a glance know what it does. I imagine that if it were named simply &#39;Pod&#39; that people would think. &quot;I&#39;ve already got Pod input, why would I want Pod output&quot;, and either investigate, or blow it off. So that&#39;s why I came up with ExtractPod, but I&#39;d like to hear other opinions. <br/> <br/>Like John, I don&rsquo;t much care. I agree that Pod::Simple::Pod lacks necessary information. ExtractPod seems fine to me. Uh, though there is this: <br/> <br/> perldoc [-h] [-D] [-t] [-u] [-m] [-l] [-F] <br/> [-i] [-V] [-T] [-r] <br/> [-d destination_file] <br/> [-o formatname] <br/> [-M FormatterClassName] <br/> [-w formatteroption:value] <br/> [-n nroff-replacement] <br/> [-X] <br/> [-L language_code] <br/> PageName|ModuleName|ProgramName|URL <br/> <br/>So the formatter arg to -M would be: <br/> <br/> perldoc -M ExtractPod <br/> <br/>Which also seems a little weird. Maybe Pod::Simple::PodFormat? <br/> <br/>Anyway, I&rsquo;ve no strong opinions. <br/> <br/>Best, <br/> <br/>David <br/> http://www.nntp.perl.org/group/perl.pod-people/2016/05/msg2051.html Thu, 12 May 2016 00:40:13 +0000 Re: Pod::Simple output as POD by Karl Williamson On 05/10/2016 12:26 PM, John SJ Anderson wrote: <br/>&gt; <br/>&gt;&gt; On May 8, 2016, at 21:04, Karl Williamson &lt;public@khwilliamson.com&gt; wrote: <br/>&gt;&gt; <br/>&gt;&gt; I have taken on the task of completing this, and am nearly done. I&#39;m writing because I wonder what other use-cases there are for this module besides extracting pod from a file that also contains other things. I can&#39;t think of any. And if there are no significant ones, I wonder if the name should instead be Pod::Simple::ExtractPod, instead of Pod::Simple::Pod? <br/>&gt; <br/>&gt; From what I recall, that was also my use case (IIRC, I was trying to automate producing a GitHub Pages-hosted version of the POD during a Dzil release process). <br/>&gt; <br/>&gt; My only comment on &lsquo;ExtractPod&rsquo; as a name would be that all the other modules in the Pod::Simple dist that do similar things are simply named &lsquo;Pod::Simple::$FORMAT&rsquo;, (e.g., Pod::Simple::HTML, Pod::Simple::RTF, etc.) <br/>&gt; <br/>&gt; At the end of the day, you&rsquo;ve done the work to get it out the door and as far as I&rsquo;m concerned, you can call it whatever you like. 8^) <br/> <br/>It&#39;s more a matter of what is the least worst name to help people at a <br/>glance know what it does. I imagine that if it were named simply &#39;Pod&#39; <br/>that people would think. &quot;I&#39;ve already got Pod input, why would I want <br/>Pod output&quot;, and either investigate, or blow it off. So that&#39;s why I <br/>came up with ExtractPod, but I&#39;d like to hear other opinions. <br/>&gt; <br/>&gt; (Karl, sorry for the mostly duplicated response to your earlier message to me.) <br/>&gt; <br/>&gt; thanks, <br/>&gt; john. <br/>&gt; <br/>&gt; <br/> <br/> http://www.nntp.perl.org/group/perl.pod-people/2016/05/msg2050.html Thu, 12 May 2016 00:30:01 +0000 Re: Pod::Simple output as POD by John SJ Anderson <br/>&gt; On May 8, 2016, at 21:04, Karl Williamson &lt;public@khwilliamson.com&gt; wrote: <br/>&gt; <br/>&gt; I have taken on the task of completing this, and am nearly done. I&#39;m writing because I wonder what other use-cases there are for this module besides extracting pod from a file that also contains other things. I can&#39;t think of any. And if there are no significant ones, I wonder if the name should instead be Pod::Simple::ExtractPod, instead of Pod::Simple::Pod? <br/> <br/>From what I recall, that was also my use case (IIRC, I was trying to automate producing a GitHub Pages-hosted version of the POD during a Dzil release process). <br/> <br/>My only comment on &lsquo;ExtractPod&rsquo; as a name would be that all the other modules in the Pod::Simple dist that do similar things are simply named &lsquo;Pod::Simple::$FORMAT&rsquo;, (e.g., Pod::Simple::HTML, Pod::Simple::RTF, etc.) <br/> <br/>At the end of the day, you&rsquo;ve done the work to get it out the door and as far as I&rsquo;m concerned, you can call it whatever you like. 8^) <br/> <br/>(Karl, sorry for the mostly duplicated response to your earlier message to me.) <br/> <br/>thanks, <br/>john. <br/> <br/> http://www.nntp.perl.org/group/perl.pod-people/2016/05/msg2049.html Tue, 10 May 2016 18:27:09 +0000 Re: Pod::Simple output as POD by Karl Williamson On 08/12/2014 02:25 PM, John SJ Anderson wrote:<br/>&gt; Jim -<br/>&gt;<br/>&gt; The current state of that code is that I think it mostly works, but it<br/>&gt; needs tests (or it needs the tests to be finished). It&#39;s been a while<br/>&gt; since I touched it, I&#39;m not sure when I&#39;m going to be able to get back<br/>&gt; to it, but I would be perfectly happy if somebody wanted to grab it<br/>&gt; and wrap it up.<br/>&gt;<br/>&gt; chrs,<br/>&gt; john.<br/><br/>I have taken on the task of completing this, and am nearly done. I&#39;m <br/>writing because I wonder what other use-cases there are for this module <br/>besides extracting pod from a file that also contains other things. I <br/>can&#39;t think of any. And if there are no significant ones, I wonder if <br/>the name should instead be Pod::Simple::ExtractPod, instead of <br/>Pod::Simple::Pod?<br/><br/>&gt;<br/>&gt;<br/>&gt; On Tue, Aug 12, 2014 at 9:06 AM, James E Keenan &lt;jkeen@verizon.net&gt; wrote:<br/>&gt;&gt; I am writing concerning https://rt.perl.org/Ticket/Display.html?id=116467.<br/>&gt;&gt; The objective of this ticket is to revise t/porting/podcheck.t so that it no<br/>&gt;&gt; longer depends on CPAN module Pod::Parser. The latter has been designated<br/>&gt;&gt; &quot;legacy code&quot; but we cannot remove it from the core distribution until<br/>&gt;&gt; podcheck.t no longer depends on it, either directly (calls to<br/>&gt;&gt; parse_from_filehandle) or indirectly (via an older version of Pod::Checker<br/>&gt;&gt; which depends on Pod::Parser rather than Pod::Simple).<br/>&gt;&gt;<br/>&gt;&gt; While studying podcheck.t recently I noticed that we could get substantially<br/>&gt;&gt; closer to our goal if we took the following subroutine from podcheck.t:<br/>&gt;&gt;<br/>&gt;&gt; #####<br/>&gt;&gt; sub extract_pod { # Extracts just the pod from a file; returns undef if<br/>&gt;&gt; file<br/>&gt;&gt; # doesn&#39;t exist<br/>&gt;&gt; my $filename = shift;<br/>&gt;&gt;<br/>&gt;&gt; my @pod;<br/>&gt;&gt;<br/>&gt;&gt; # Arrange for the output of Pod::Parser to be collected in an array we<br/>&gt;&gt; can<br/>&gt;&gt; # look at instead of being printed<br/>&gt;&gt; tie *ALREADY_FH, &#39;Tie_Array_to_FH&#39;, \@pod;<br/>&gt;&gt; if (open my $in_fh, &#39;&lt;:bytes&#39;, $filename) {<br/>&gt;&gt; my $parser = Pod::Parser-&gt;new();<br/>&gt;&gt; $parser-&gt;parse_from_filehandle($in_fh, *ALREADY_FH);<br/>&gt;&gt; close $in_fh;<br/>&gt;&gt;<br/>&gt;&gt; return join &quot;&quot;, @pod<br/>&gt;&gt; }<br/>&gt;&gt; ...<br/>&gt;&gt; #####<br/>&gt;&gt;<br/>&gt;&gt; ... and could rewrite the &#39;if&#39; block using a Pod::Simple-based call.<br/>&gt;&gt; However, AFAICT there is nothing in the latest CPAN release of Pod::Simple<br/>&gt;&gt; by which one could simple extract the POD from a file and return it as a<br/>&gt;&gt; single string, POD-formatting intact and otherwise unmodified.<br/>&gt;&gt;<br/>&gt;&gt; Karl Williamson noted<br/>&gt;&gt; (https://rt.perl.org/Ticket/Display.html?id=116467#txn-1304150) that there<br/>&gt;&gt; have been some efforts in this direction, citing:<br/>&gt;&gt; https://github.com/genehack/pod-simple/tree/add-pod-simple-pod. Could you<br/>&gt;&gt; advise as to the current state of development of this fork and whether it is<br/>&gt;&gt; likely to be of benefit to P5P in this instance?<br/>&gt;&gt;<br/>&gt;&gt; Thank you very much.<br/>&gt;&gt; Jim Keenan<br/>&gt;&gt;<br/>&gt;<br/><br/> http://www.nntp.perl.org/group/perl.pod-people/2016/05/msg2048.html Mon, 09 May 2016 04:04:56 +0000 Re: Working on CPAN Testers fails for Pod::Simple::Search by Neil Bowers &gt;&gt; Anyone object to making Neil a committer and co-maint on Pod-Simple? (I&rsquo;m <br/>&gt;&gt; hoping Neil doesn&rsquo;t object.) The canonical repository is here: <br/>&gt; <br/>&gt; No objection, and I preemptively overrule Neil&#39;s potential objection. <br/> <br/>Ha! <br/> <br/>Ok. <br/> <br/> http://www.nntp.perl.org/group/perl.pod-people/2016/04/msg2047.html Sat, 30 Apr 2016 13:26:44 +0000 Re: Pod::Simple issues by Russ Allbery Karl Williamson &lt;public@khwilliamson.com&gt; writes:<br/><br/>&gt; I&#39;m not sure I understand what &quot;fail on generation&quot; means. I think it<br/>&gt; might mean just not generate a pod, rather than generate one with an error<br/>&gt; section.<br/><br/>Correct -- it will exit with an error message.<br/><br/>lothlorien:~$ cat &gt; foo.pod<br/>=item foo<br/><br/>Invalid POD.<br/>lothlorien:~$ pod2man foo.pod &gt; foo.1<br/>foo.pod around line 1: &#39;=item&#39; outside of any &#39;=over&#39;<br/>foo.pod around line 1: =over without closing =back<br/>POD document had syntax errors at /usr/bin/pod2man line 68.<br/>lothlorien:~$ echo $?<br/>255<br/><br/>&gt; What I was intending was to add a scream() call. The only failure that I<br/>&gt; saw in Pod::Simple that stopped parsing was when it was clear the<br/>&gt; encoding of the pod was not understandable, so there was no point in<br/>&gt; continuing. So I don&#39;t understand what you do, unless it is to die on<br/>&gt; pod errors, or some such.<br/><br/>Correct, the scripts die on POD errors, unless the --errors flag is used<br/>to request some other behavior.<br/><br/> -errors=style<br/> Set the error handling style. &quot;die&quot; says to throw an exception on<br/> any POD formatting error. &quot;stderr&quot; says to report errors on<br/> standard error, but not to throw an exception. &quot;pod&quot; says to<br/> include a POD ERRORS section in the resulting documentation<br/> summarizing the errors. &quot;none&quot; ignores POD errors entirely, as<br/> much as possible.<br/><br/> The default is &quot;die&quot;.<br/><br/>(Now let me go fix the missing - in the pod2man docs....)<br/><br/>-- <br/>#!/usr/bin/perl -- Russ Allbery, Just Another Perl Hacker<br/>$^=q;@!&gt;~|{&gt;krw&gt;yn{u&lt;$$&lt;[~||&lt;Juukn{=,&lt;S~|}&lt;Jwx}qn{&lt;Yn{u&lt;Qjltn{ &gt; 0gFzD gD,<br/> 00Fz, 0,,( 0hF 0g)F/=, 0&gt; &quot;L$/GEIFewe{,$/ 0C$~&gt; &quot;@=,m,|,(e 0.), 01,pnn,y{<br/>rw} &gt;;,$0=q,$,,($_=$^)=~y,$/ C-~&gt;&lt;@=\n\r,-~$:-u/ #y,d,s,(\$.),$1,gee,print<br/> http://www.nntp.perl.org/group/perl.pod-people/2016/04/msg2046.html Sat, 30 Apr 2016 06:15:08 +0000 Re: Pod::Simple issues by Karl Williamson On 04/29/2016 04:33 PM, Russ Allbery wrote:<br/>&gt; Karl Williamson &lt;public@khwilliamson.com&gt; writes:<br/>&gt;<br/>&gt;&gt; Rather than aborting parsing at the point where this occurs, I think it<br/>&gt;&gt; should continue on, but generate an errors section, like it does for most<br/>&gt;&gt; other errors.<br/>&gt;<br/>&gt; This will cause a hard failure in pod2man and pod2text by default, since<br/>&gt; they do not generate ERRORS sections by default (you have to request that<br/>&gt; behavior with a flag). They used to generate ERRORS sections, which made<br/>&gt; people very unhappy because they didn&#39;t want their documents published<br/>&gt; with sections saying the documents were bad, and after a lot of previous<br/>&gt; discussion I changed the default to fail on generation. (I&#39;d really<br/>&gt; rather not reverse that decision at this point.)<br/>&gt;<br/><br/>I&#39;m not sure I understand what &quot;fail on generation&quot; means. I think it <br/>might mean just not generate a pod, rather than generate one with an <br/>error section. What I was intending was to add a scream() call. The <br/>only failure that I saw in Pod::Simple that stopped parsing was when it <br/>was clear the encoding of the pod was not understandable, so there was <br/>no point in continuing. So I don&#39;t understand what you do, unless it is <br/>to die on pod errors, or some such.<br/><br/>I tend to agree about not reversing your earlier decision.<br/> http://www.nntp.perl.org/group/perl.pod-people/2016/04/msg2045.html Sat, 30 Apr 2016 04:48:25 +0000 Re: Pod::Simple issues by Russ Allbery Karl Williamson &lt;public@khwilliamson.com&gt; writes:<br/><br/>&gt; Rather than aborting parsing at the point where this occurs, I think it<br/>&gt; should continue on, but generate an errors section, like it does for most<br/>&gt; other errors.<br/><br/>This will cause a hard failure in pod2man and pod2text by default, since<br/>they do not generate ERRORS sections by default (you have to request that<br/>behavior with a flag). They used to generate ERRORS sections, which made<br/>people very unhappy because they didn&#39;t want their documents published<br/>with sections saying the documents were bad, and after a lot of previous<br/>discussion I changed the default to fail on generation. (I&#39;d really<br/>rather not reverse that decision at this point.)<br/><br/>-- <br/>#!/usr/bin/perl -- Russ Allbery, Just Another Perl Hacker<br/>$^=q;@!&gt;~|{&gt;krw&gt;yn{u&lt;$$&lt;[~||&lt;Juukn{=,&lt;S~|}&lt;Jwx}qn{&lt;Yn{u&lt;Qjltn{ &gt; 0gFzD gD,<br/> 00Fz, 0,,( 0hF 0g)F/=, 0&gt; &quot;L$/GEIFewe{,$/ 0C$~&gt; &quot;@=,m,|,(e 0.), 01,pnn,y{<br/>rw} &gt;;,$0=q,$,,($_=$^)=~y,$/ C-~&gt;&lt;@=\n\r,-~$:-u/ #y,d,s,(\$.),$1,gee,print<br/> http://www.nntp.perl.org/group/perl.pod-people/2016/04/msg2044.html Fri, 29 Apr 2016 22:33:19 +0000 Re: Working on CPAN Testers fails for Pod::Simple::Search by Marc Green On Fri, Apr 29, 2016 at 1:54 PM, Ricardo Signes &lt;perl.pod@rjbs.manxome.org&gt; <br/>wrote: <br/> <br/>&gt; * &quot;David E. Wheeler&quot; &lt;dwheeler@cpan.org&gt; [2016-04-29T16:43:03] <br/>&gt; &gt; Anyone object to making Neil a committer and co-maint on Pod-Simple? (I&rsquo;m <br/>&gt; &gt; hoping Neil doesn&rsquo;t object.) The canonical repository is here: <br/>&gt; <br/>&gt; No objection, and I preemptively overrule Neil&#39;s potential objection. <br/>&gt; <br/> <br/> <br/>I very much welcome it! http://www.nntp.perl.org/group/perl.pod-people/2016/04/msg2043.html Fri, 29 Apr 2016 21:32:35 +0000 Re: Working on CPAN Testers fails for Pod::Simple::Search by Ricardo Signes * &quot;David E. Wheeler&quot; &lt;dwheeler@cpan.org&gt; [2016-04-29T16:43:03] <br/>&gt; Anyone object to making Neil a committer and co-maint on Pod-Simple? (I&rsquo;m <br/>&gt; hoping Neil doesn&rsquo;t object.) The canonical repository is here: <br/> <br/>No objection, and I preemptively overrule Neil&#39;s potential objection. <br/> <br/>-- <br/>rjbs http://www.nntp.perl.org/group/perl.pod-people/2016/04/msg2042.html Fri, 29 Apr 2016 20:54:30 +0000 Re: Working on CPAN Testers fails for Pod::Simple::Search by David E. Wheeler On Apr 29, 2016, at 11:41 AM, Karl Williamson &lt;public@khwilliamson.com&gt; wrote: <br/> <br/>&gt; Looking at the man page, it looks like Pod::Simple::Search does a similar function as Pod::Find does <br/> <br/>Yes, and it has been there since forever. <br/> <br/>Best, <br/> <br/>David <br/> <br/> http://www.nntp.perl.org/group/perl.pod-people/2016/04/msg2041.html Fri, 29 Apr 2016 20:43:33 +0000 Re: Working on CPAN Testers fails for Pod::Simple::Search by David E. Wheeler On Apr 23, 2016, at 9:45 AM, Neil Bowers &lt;neil.bowers@cogendo.com&gt; wrote: <br/> <br/>&gt; I talked this through with RJBS, who suggested the order should instead be: <br/>&gt; <br/>&gt; .pod &lt;none&gt; .pm .pl .plx <br/>&gt; <br/>&gt; David, you added the comment to the code that&rsquo;s mentioned above. Was there a reason you added that comment, or were you just commenting on what the code was doing? (like much of this module, it&rsquo;s somewhat opaque :-) <br/> <br/>I suspect I was just trying to get both functions to prefer things in the same order. I agree with Rik&rsquo;s suggested ordering, however, especially if it makes the bloody tests pass. <br/> <br/>Anyone object to making Neil a committer and co-maint on Pod-Simple? (I&rsquo;m hoping Neil doesn&rsquo;t object.) The canonical repository is here: <br/> <br/> https://github.com/perl-pod/pod-simple/ <br/> <br/>Best, <br/> <br/>David <br/> <br/> <br/> http://www.nntp.perl.org/group/perl.pod-people/2016/04/msg2040.html Fri, 29 Apr 2016 20:43:21 +0000 Re: Pod::Simple issues by Karl Williamson On 04/29/2016 01:58 PM, Shawn H Corey wrote:<br/>&gt; On Fri, 29 Apr 2016 13:34:21 -0600<br/>&gt; Karl Williamson &lt;public@khwilliamson.com&gt; wrote:<br/>&gt;<br/>&gt;&gt; Nested L&lt;&gt; are illegal. Pretending inner one is X&lt;&gt; so can<br/>&gt;&gt; continue looking for other errors.<br/>&gt;<br/>&gt; That would be Z&lt;&gt;<br/>&gt;<br/>&gt;<br/><br/>That would generate an additional warning that it wasn&#39;t empty. The <br/>mechanism is to divert the incoming text into the X&lt;&gt; so it doesn&#39;t do <br/>anything bad. I suppose we could set a flag for the Z&lt;&gt; to suppress the <br/>warning.<br/> http://www.nntp.perl.org/group/perl.pod-people/2016/04/msg2039.html Fri, 29 Apr 2016 20:33:08 +0000 Re: Pod::Simple issues by Shawn H Corey On Fri, 29 Apr 2016 13:34:21 -0600<br/>Karl Williamson &lt;public@khwilliamson.com&gt; wrote:<br/><br/>&gt; Nested L&lt;&gt; are illegal. Pretending inner one is X&lt;&gt; so can<br/>&gt; continue looking for other errors.<br/><br/>That would be Z&lt;&gt;<br/><br/><br/>-- <br/>Don&#39;t stop where the ink does.<br/> Shawn<br/> http://www.nntp.perl.org/group/perl.pod-people/2016/04/msg2038.html Fri, 29 Apr 2016 19:58:39 +0000 Pod::Simple issues by Karl Williamson I stumbled across a bug in Pod::Simple the other day: It does not create <br/>the promised {&#39;raw&#39;} structure element usable by parsers for L&lt;&gt; <br/>constructs if they occur within another formatting code, such as the <br/>fairly common C&lt;L&lt;foo::bar&gt;&gt;.<br/><br/>I figured out a way to fix this, but in doing so I realized that <br/>Pod::Simple does not catch nested L&lt;... L&lt;...&gt;...&gt;, contrary to the <br/>specification:<br/><br/> Authors must not nest L&lt;...&gt; codes. For example, &quot;L&lt;The L&lt;Foo::Bar&gt;<br/> man page&gt;&quot; should be treated as an error.<br/><br/>Pod::Simple does not treat this as an error. I think it should. Is <br/>there any disagreement?<br/><br/>Rather than aborting parsing at the point where this occurs, I think it <br/>should continue on, but generate an errors section, like it does for <br/>most other errors. Properly handling nested L&lt;&gt; is tricky. Currently, <br/>it sort of works, but the generated output for html doesn&#39;t link <br/>properly, as one can&#39;t nest links in html. I came up with this <br/>tentative message, which perhaps explains too much of how I was able to <br/>easily keep parsing with this error, and still fix the original {&#39;raw&#39;} <br/>bug; improved wording welcome:<br/><br/> Nested L&lt;&gt; are illegal. Pretending inner one is X&lt;&gt; so can continue <br/>looking for other errors.<br/><br/> http://www.nntp.perl.org/group/perl.pod-people/2016/04/msg2037.html Fri, 29 Apr 2016 19:34:29 +0000 Re: AW: Working on CPAN Testers fails for Pod::Simple::Search by Karl Williamson On 04/24/2016 11:34 PM, Marek Rouchal wrote:<br/>&gt; Does this mean that there is a &quot;find&quot;-like function in Pod::Simple that<br/>&gt; replaces Pod::Find? That would be an opportunity to discontinue<br/>&gt; Pod::Find along with Pod::Parser...<br/>&gt;<br/>&gt; -Marek<br/>&gt;<br/>&gt;<br/>&gt;<br/><br/>Looking at the man page, it looks like Pod::Simple::Search does a <br/>similar function as Pod::Find does<br/><br/> http://www.nntp.perl.org/group/perl.pod-people/2016/04/msg2036.html Fri, 29 Apr 2016 18:42:10 +0000 GitHub markup and POD by Zakariyya Mughal Hello all,<br/><br/>I wanted to bring to your attention several issues on GitHub having to<br/>deal with POD. Some of them have been there for years, but nobody from<br/>GitHub has responded.<br/><br/>Given how it took lots of publicity (e.g., &lt;https://github.com/dear-github/dear-github&gt;)<br/>to get GitHub to prioritise certain changes such as voting on issues,<br/>perhaps we can be squeaky wheels and get these merged?<br/><br/>- #241 Switch to Pod::Simple::XHTML &lt;https://github.com/github/markup/pull/241&gt;<br/><br/>- #421 POD CPAN Links (point from s.c.o. to metacpan.org) &lt;https://github.com/github/markup/issues/421&gt;<br/><br/>- #874 Fix POD markup in test &lt;https://github.com/github/markup/pull/874&gt;<br/><br/>Regards,<br/>- Zaki Mughal<br/><br/>P.S. Somewhat related is &lt;https://github.com/perl-pod/pod-simple/issues/61&gt;<br/>which proposes to change `$Pod::Simple::HTML::Perldoc_URL_Prefix` to switch to MetaCPAN.<br/>I don&#39;t want to get into that here, but if someone would like to start<br/>another thread for that, go ahead.<br/> http://www.nntp.perl.org/group/perl.pod-people/2016/04/msg2035.html Tue, 26 Apr 2016 21:41:26 +0000 GitHub markup and POD by Zakariyya Mughal Hello all,<br/><br/>I wanted to bring to your attention several issues on GitHub having to<br/>deal with POD. Some of them have been there for years, but nobody from<br/>GitHub has responded.<br/><br/>Given how it took lots of publicity (e.g., &lt;https://github.com/dear-github/dear-github&gt;)<br/>to get GitHub to prioritise certain changes such as voting on issues,<br/>perhaps we can be squeaky wheels and get these merged?<br/><br/>- #241 Switch to Pod::Simple::XHTML &lt;https://github.com/github/markup/pull/241&gt;<br/><br/>- #421 POD CPAN Links (point from s.c.o. to metacpan.org) &lt;https://github.com/github/markup/issues/421&gt;<br/><br/>- #874 Fix POD markup in test &lt;https://github.com/github/markup/pull/874&gt;<br/><br/>Regards,<br/>- Zaki Mughal<br/><br/>P.S. Somewhat related is &lt;https://github.com/perl-pod/pod-simple/issues/61&gt;<br/>which proposes to change `$Pod::Simple::HTML::Perldoc_URL_Prefix` to switch to MetaCPAN.<br/>I don&#39;t want to get into that here, but if someone would like to start<br/>another thread for that, go ahead.<br/> http://www.nntp.perl.org/group/perl.pod-people/2016/04/msg2034.html Tue, 26 Apr 2016 21:03:59 +0000 GitHub markup and POD by Zakariyya Mughal Hello all,<br/><br/>I wanted to bring to your attention several issues on GitHub having to<br/>deal with POD. Some of them have been there for years, but nobody from<br/>GitHub has responded.<br/><br/>Given how it took lots of publicity (e.g., &lt;https://github.com/dear-github/dear-github&gt;)<br/>to get GitHub to prioritise certain changes such as voting on issues,<br/>perhaps we can be squeaky wheels and get these merged?<br/><br/>- #241 Switch to Pod::Simple::XHTML &lt;https://github.com/github/markup/pull/241&gt;<br/><br/>- #421 POD CPAN Links (point from s.c.o. to metacpan.org) &lt;https://github.com/github/markup/issues/421&gt;<br/><br/>- #874 Fix POD markup in test &lt;https://github.com/github/markup/pull/874&gt;<br/><br/>Regards,<br/>- Zaki Mughal<br/><br/>P.S. Somewhat related is &lt;https://github.com/perl-pod/pod-simple/issues/61&gt;<br/>which proposes to change `$Pod::Simple::HTML::Perldoc_URL_Prefix` to switch to MetaCPAN.<br/>I don&#39;t want to get into that here, but if someone would like to start<br/>another thread for that, go ahead.<br/> http://www.nntp.perl.org/group/perl.pod-people/2016/04/msg2033.html Tue, 26 Apr 2016 20:45:10 +0000 Re: AW: pod2usage and Pod::Find, Pod::PlainText by Karl Williamson On 04/23/2016 03:26 PM, Marek Rouchal wrote: <br/>&gt; Thanks for the hint... two thoughts, feedback welcome: <br/>&gt; 1. Pod::PlainText used to be part of the core... but since now Pod::Usage depends on Pod::Simple, I think the tests should be restructured to use that, or as a last resort, Pod::Text <br/>Is there any real difference between PlainText and Pod::Simple::Text ? <br/> <br/>&gt; 2. Pod::Find might deserve a separate distribution, but again the test of Pod::Usage should not depend on it. <br/>&gt; Hope to find some time to get that done in the next days... <br/>&gt; <br/>&gt; -Marek <br/>&gt; <br/>&gt; -----Urspr&uuml;ngliche Nachricht----- <br/>&gt; It has been a goal to remove Pod::Parser from the core perl distribution. <br/>&gt; <br/>&gt; It turns out there is a dependency in 2 test files for pod2uage upon Pod::Find and Pod::PlainText, which are parts of Pod::Parser. <br/>&gt; <br/>&gt; The test files are Pod-Usage/t/pod/pod2usage.t <br/>&gt; and Pod-Usage/t/pod/pod2usage2.t <br/>&gt; <br/>&gt; Note that Pod::Usage itself doesn&#39;t depend on Pod::Parser, just two test files do. I don&#39;t understand this part of perl at all. So I&#39;m wondering what to do about this. Could the tests just be deleted? Is there a current alternative to the functionality of these modules? <br/>&gt; <br/>&gt; <br/>&gt; <br/>&gt; <br/> <br/> http://www.nntp.perl.org/group/perl.pod-people/2016/04/msg2032.html Tue, 26 Apr 2016 00:02:04 +0000 AW: Working on CPAN Testers fails for Pod::Simple::Search by Marek Rouchal <br/> <br/>Does this mean that there is a &quot;find&quot;-like function in Pod::Simple that replaces Pod::Find? That would be an opportunity to discontinue Pod::Find along with Pod::Parser...<br/>-Marek<br/><br/><br/>Von meinem Samsung Ger&auml;t gesendet. http://www.nntp.perl.org/group/perl.pod-people/2016/04/msg2031.html Mon, 25 Apr 2016 05:34:40 +0000