Re^2: Avoid inconsistent POD =over =item indentation

I agree that the ultimate appearance depends on the renderer. I think I just stumbled upon further proof of this. I happened to be looking at the xml_merge script on CPAN, and the OPTIONS section in my web browser looks quite different from what I see at my linux command prompt when I use:

perldoc xml_merge
[download]

which resolves to:

pod2man --lax xml_merge | nroff -man
[download]

Here is a snippet of the xml_merge POD:

=head1 OPTIONS

=over 4

=item -o <output_file>

unless this option is used the program output goes to STDOUT

=item -i

the files use XInclude instead of processing instructions (they
were created using the C<-i> option in C<xml_split>)

=item -v

verbose output

=item -V

outputs version and exit

=item -h

short help

=item -m

man (requires pod2text to be in the path)

=back
[download]

Here's how the CPAN page renders for me in Firefox:

OPTIONS

-o <output_file>

    unless this option is used the program output goes to STDOUT
-i

    the files use XInclude instead of processing instructions (they we
+re
    created using the -i option in xml_split)
-v

    verbose output
-V

    outputs version and exit
-h

    short help
-m

    man (requires pod2text to be in the path)
[download]

And here's how it looks at my linux command prompt:

OPTIONS
       -o <output_file>
           unless this option is used the program output goes to STDOU
+T

       -i  the files use XInclude instead of processing instructions (
+they
           were created using the "-i" option in "xml_split")

       -v  verbose output

       -V  outputs version and exit

       -h  short help

       -m  man (requires pod2text to be in the path)
[download]

And, yes, I am tossing the term 'POD' around rather loosely.

Comment on Re^2: Avoid inconsistent POD =over =item indentation Select or Download Code