Have you looked at http://pugs.kwiki.org/?KwidSynopsis, which is what the Pugs project is using? Otherwise, yes, sure you can, invent/improve one, then go suggest it on p5p, then work to help implement it (after convincing everyone) ..

IMO, btw. XML sucks for this kind of thing, its much too easy to typo, and thus isnt good for handtyped docs at all. POD is nice and simple to use, if it makes the parsing harder, thats just tough, internals generally are more complex than externals, to support those simple externals.

C.

In reply to Re: Please for the love of god, can I get a documentation format that doesn't suck? by castaway
in thread Please for the love of god, can I get a documentation format that doesn't suck? by BUU

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.