Re: Which Pod module should be used / subclassed?
[email protected] ("LNATION .") Sat, 11 May 2019 06:20:52 +0800
| Newsgroups | perl.pod-people |
|---|---|
| Message-ID | <CAPJW-Giaavdke2FsqjQzy7TeEj74v39ZO3fyBy_KunFO__Z_Wg@mail.gmail.com> |
--000000000000bd6d1805888ffbfe Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable May or may not help: https://metacpan.org/pod/Pod::Simpler::Aoh https://github.com/ThisUsedToBeAnEmail/podsearch Its simple On Sat, 11 May 2019, 03:52 Harald J=C3=B6rg, <[email protected]> wrote: > Karl Williamson <[email protected]> writes: > > > [...] > > I seem to be the one mostly maintaining Pod:Simple these days. I > > think the design of Pod::Simple is basically sound. If you came up > > with reasonable pull requests for either of those modules, I would > > apply them. > > > > All those TODOs in the code are from the original author, I believe, > > and they would be nice to have, but the code basically works and no > > one has felt the need to spend the effort to implement them. > > Indeed, the parser in Pod::Simple is pretty easy to use. I guess that > the formatting part can turn into a can of worms with regard to > different tastes how things should look like or behave. It seems that > the Pods I'm dealing with are somewhat non-standard, so I don't think > that changing the behaviour of the existing formatters is justified. > > For now, I've submitted a pull request for a few of those documentation > TODOs where I had to open the source to see what's available. > > Maybe I'll get to that problem of nested 'a' elements later, but since > browsers don't really choke on that, it isn't too high on my list. > -- > Cheers, > haj > --000000000000bd6d1805888ffbfe Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"auto">May or may not help:<div dir=3D"auto"><br></div><div dir= =3D"auto"><a href=3D"https://metacpan.org/pod/Pod::Simpler::Aoh" target=3D"= _blank" rel=3D"noreferrer">https://metacpan.org/pod/Pod::Simpler::Aoh</a><b= r></div><div dir=3D"auto"><br></div><div dir=3D"auto"><a href=3D"https://gi= thub.com/ThisUsedToBeAnEmail/podsearch">https://github.com/ThisUsedToBeAnEm= ail/podsearch</a><br></div><div dir=3D"auto"><br></div><div dir=3D"auto">It= s simple</div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class= =3D"gmail_attr">On Sat, 11 May 2019, 03:52 Harald J=C3=B6rg, <<a href=3D= "mailto:[email protected]" target=3D"_blank" rel=3D"noreferrer">[email protected]</= a>> wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 = 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Karl Williamson <<= a href=3D"mailto:[email protected]" rel=3D"noreferrer noreferrer" tar= get=3D"_blank">[email protected]</a>> writes:<br> <br> > [...]<br> > I seem to be the one mostly maintaining Pod:Simple these days.=C2=A0 I= <br> > think the design of Pod::Simple is basically sound.=C2=A0 If you came = up<br> > with reasonable pull requests for either of those modules, I would<br> > apply them.<br> ><br> > All those TODOs in the code are from the original author, I believe,<b= r> > and they would be nice to have, but the code basically works and no<br= > > one has felt the need to spend the effort to implement them.<br> <br> Indeed, the parser in Pod::Simple is pretty easy to use.=C2=A0 I guess that= <br> the formatting part can turn into a can of worms with regard to<br> different tastes how things should look like or behave.=C2=A0 It seems that= <br> the Pods I'm dealing with are somewhat non-standard, so I don't thi= nk<br> that changing the behaviour of the existing formatters is justified.<br> <br> For now, I've submitted a pull request for a few of those documentation= <br> TODOs where I had to open the source to see what's available.<br> <br> Maybe I'll get to that problem of nested 'a' elements later, bu= t since<br> browsers don't really choke on that, it isn't too high on my list.<= br> -- <br> Cheers,<br> haj<br> </blockquote></div> --000000000000bd6d1805888ffbfe--