John Siracusa wrote: > > Tables are my personal peeve, but I'm sure you can think of many more common > documentation features that POD should support natively. Hypertext is > another example, off the top of my head. I agree that pod could support these thing better. I believe it will, and it won't be difficult -- nothing that would make XML seem like an attractive alternative. -- John Porter By pressing down a special key It plays a little melody
- Re: RFC 357 (v1) Perl should use XML for documenta... Nicholas Clark
- Re: RFC 357 (v1) Perl should use XML for docum... John Porter
- Re: RFC 357 (v1) Perl should use XML for d... John Barnette
- Re: RFC 357 (v1) Perl should use XML for documenta... John Siracusa
- Re: RFC 357 (v1) Perl should use XML for docum... John Porter
- Re: RFC 357 (v1) Perl should use XML for d... Robin Berjon
- Re: RFC 357 (v1) Perl should use XML ... John Porter
- Re: RFC 357 (v1) Perl should use XML for d... John Siracusa
- Re: RFC 357 (v1) Perl should use XML ... John Porter
- Re: RFC 357 (v1) Perl should use ... John Siracusa
- Re: RFC 357 (v1) Perl should use ... John Porter
- Re: RFC 357 (v1) Perl should use ... Peter Scott
- Re: RFC 357 (v1) Perl should use XML for documentation... Adam Turoff
- Re: RFC 357 (v1) Perl should use XML for documenta... Philip Newton
- RE: RFC 357 (v1) Perl should use XML for documentation inst... Myers, Dirk
- RE: RFC 357 (v1) Perl should use XML for documentation inst... Garrett Goebel
- RE: RFC 357 (v1) Perl should use XML for documentation inst... Garrett Goebel
- RE: RFC 357 (v1) Perl should use XML for documentation inst... David Grove