The handling of =over, =back and =item is different in pod2html than
it is in either pod2man or pod2latex. In the former, they nest. In the
latter they do not (almost).
In fact, on the following pod:
=over 1
=item 1
=over 1
=item a
=back
=item 2
=back
pod2man will output:
1
a
2
pod2 latex will complain:
Illegal '=item' command without preceding 'over': at /usr/new/bin/pod2latex line 361, <POD> chunk 6.
and output the correctly nested enumerate and description blocks but
the wrong \item for "2" (eg. it spits out \item[2] when it should spit
out \item).
pod2html will output currectly nested
1
a
.
2
.
but with the "."'s in the places noted.
*******************WARNING: Dream-functionality idea ahead!*******************
Given all of this flakiness, wouldn't it be esier to have a Pod module
that reads in pod files, and represents them as perl datastructures
and THEN write modules to convert that internal representation to
another format? This would lend itself to more consistency and would
even allow for silly things like "suggesting" a common set of
command-line options and i/o conventions (what DOES "pod2x file.pod"
do?)
pod2foo could just be:
use Pod;
use Pod::Foo;
$pod = Pod->new(@ARGV);
$pod->convert('Foo');
exit 0;
-AJS
--
Aaron Sherman <ajs@ajs.com> B4 f w+ c kv s+(--)v r p
I-Kinetics, Inc. Pager: (508)545-0584
1 NE Executive Park Fax: (617)270-4979
Burlington, MA 01803-5005 WWW: http://ajs.com/~ajs/
ajs@ajs.com or ajs@openmarket.com
"I speak for no one."
it is in either pod2man or pod2latex. In the former, they nest. In the
latter they do not (almost).
In fact, on the following pod:
=over 1
=item 1
=over 1
=item a
=back
=item 2
=back
pod2man will output:
1
a
2
pod2 latex will complain:
Illegal '=item' command without preceding 'over': at /usr/new/bin/pod2latex line 361, <POD> chunk 6.
and output the correctly nested enumerate and description blocks but
the wrong \item for "2" (eg. it spits out \item[2] when it should spit
out \item).
pod2html will output currectly nested
1
a
.
2
.
but with the "."'s in the places noted.
*******************WARNING: Dream-functionality idea ahead!*******************
Given all of this flakiness, wouldn't it be esier to have a Pod module
that reads in pod files, and represents them as perl datastructures
and THEN write modules to convert that internal representation to
another format? This would lend itself to more consistency and would
even allow for silly things like "suggesting" a common set of
command-line options and i/o conventions (what DOES "pod2x file.pod"
do?)
pod2foo could just be:
use Pod;
use Pod::Foo;
$pod = Pod->new(@ARGV);
$pod->convert('Foo');
exit 0;
-AJS
--
Aaron Sherman <ajs@ajs.com> B4 f w+ c kv s+(--)v r p
I-Kinetics, Inc. Pager: (508)545-0584
1 NE Executive Park Fax: (617)270-4979
Burlington, MA 01803-5005 WWW: http://ajs.com/~ajs/
ajs@ajs.com or ajs@openmarket.com
"I speak for no one."