Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I had the same frustration, and wrote Pod::WikiDoc [cpan.org] so I could write in a Kwiki-like format and have it converted to Pod. Bullets are like this:

    * item 1
    * item 2

    I wrote up a lightning talk about it: http://dagolden.com/files/pod-wikidoc.pdf [dagolden.com]

    Unfortunately, it doesn't do DT/DD style lists yet, but mostly because I haven't gotten around to adding it. A request for it [cpan.org] has been in the RT queue for a while.

    If you're interested in patching in support and using WikiDoc instead of rolling your own system around Ma

    • Looking at the POD of your module, I can see you have the exact same beef with POD as I have.

      But, IMHO, there are already just too many similar yet slightly different markup languages out there. I don't feel like learning yet another dialect; I'd just end up getting confused. And they all have their own translators. For example, your Wikidoc format is very much like Markdown, with probably the largest differences between them in the format of the links.

      Do you think it would be feasible to unify those transl

      • I think generalizing the framework -- parsing POD in *.pm for a block of some style and "compiling" it to .pod -- is possible. (I'm currently working on an "inline" style that just appends the proper POD at the end of the *.pm). It would need to have the actual parsing/translating code extracted into either a plugin or a subclass.

        There are others thinking about this, too. See, for example, Pod-Weaver [cpan.org]. That's something new from RJBS, but it might prove a better platform for a general tool.

        But if you want to look at refactoring Pod::WikiDoc into a more general tool, please feel free.

        On DL/DT/DD markup, the RT ticket discusses this kind of markup, which I think other wiki-style engines use:

        ; foo : This is a description of foo

        I like your style visually, tough. I have to think about what it would be like to parse unambiguously in Parse::RecDescent. (What Pod::WikiDoc uses internally.)

        -- dagolden