comment on

FYI, this is how your failing pod is parsed

$ perl -MPod::Simple::DumpAsXML -e  " Pod::Simple::DumpAsXML->filter(s
+hift)->any_errata_seen" udge
<Document start_line="5">
  <head1 start_line="5">
    SYNOPSIS here&#39;s the main usage stuff
  </head1>
  <head1 start_line="8">
    SPECIAL special usage stuff here...
  </head1>
</Document>
[download]

Corrected pod, like toolic wrote, with the head sections being one word strings :)

$ perl -MPod::Simple::DumpAsXML -e  " Pod::Simple::DumpAsXML->filter(s
+hift)->any_errata_seen" udge
<Document start_line="5">
  <head1 start_line="5">
    SYNOPSIS
  </head1>
  <VerbatimFormatted start_line="7" xml:space="preserve">
         here&#39;s the main usage stuff
  </VerbatimFormatted>
  <head1 start_line="9">
    SPECIAL
  </head1>
  <VerbatimFormatted start_line="11" xml:space="preserve">
        special usage stuff here...
  </VerbatimFormatted>
</Document>
[download]

In pod, empty line is paragraph separator, perlpod, perlpodspec

In reply to Re: pod::usage "-sections" not working by Anonymous Monk
in thread pod::usage "-sections" not working by johnguillory

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


There's more than one way to do things
	PerlMonks