Front page | perl.perl5.porters |
Postings from November 2021
* Ricardo Signes <perl.p5p@rjbs.manxome.org> [2021-11-27 14:30:13 -0500]: > On Mon, Nov 22, 2021, at 3:12 PM, Ovid via perl5-porters wrote: > > What if we punted on much of this and allow: > > > > =poddown > > I mostly want to stay out of this, personally ? but here I am posting. > > There's a lot to do in "extend Pod with Markdown," and I'm not sure it's really practical. Of course, I'm not proposing to do it or forbid it, so this isn't my thing to worry about so much. > > But I will say that I think that by far the most tedious thing in Pod is lists, for which I provided myself with a solution in Pod::Elemental::Transformer::List <https://metacpan.org/pod/Pod::Elemental::Transformer::List>, which creates a "=begin :list" region or "=for :list" paragraph, which allows very compact notation for bulleted, definition, or ordered lists that uses Pod sequences instead of Markdown, and so remains very much like all other Pod. Adding support to that to Pod::Simple might be a fair bit simpler than Markdown... but I won't be the one to do it! ????? What's your workflow for rendering this to POD, is it transformed in the source after you've written once (e.g., via an external tool or vim plugin), or does it remain in the source for downstream consumption? My personal take is that beyond affecting the POD syntax itself, the next most convenient solutions a tool-based one. Brett > > -- > rjbs -- -- oodler@cpan.org oodler577@sdf-eu.org SDF-EU Public Access UNIX System - http://sdfeu.org irc.perl.org #openmp #pdl #nativeThread Previous | Thread Next