Tim Jenness <[EMAIL PROTECTED]> writes:
> This would also be the case for pod2html I imagine. pod2latex and
> pod2html do everything themselves (although pod2html simply uses
> Pod::Html). Both would have to be changed. The others (pod2text and
> pod2man) use Pod::Parser which is being updated to support C<<...>> The
> simplest solution is simply to rewrite pod2latex and pod2html so that
> they use Pod::Parser. To put my money where my mouth is I have two
> modules, Pod::LaTex and a Pod::Html replacement, that do use Pod::Parser
> and would therefore support this once Pod::Parser supports it.
Excellent! You've saved me some work; I was going to go off and write
Pod::LaTeX myself (I need it for some other things).
> I am new to p5p so I am not sure what the feeling is about updating
> these two commands -- I assume replacing these is not going to happen
> before the release of perl5.6 (time is too short to test changes such as
> these adequately before that release)
True for Pod::HTML, since it's widely used. pod2latex was never really
documented, hasn't been updated in quite some time, and really isn't that
usable unless you read the comments in the source to figure out what
you're doing; I therefore don't feel the need to be all that worried about
it. But of course that's not my call.
> but I would be happy to either put them on CPAN (named as Pod::LaTex and
> Pod::Html??) or submit them to the PodParser package so that people can
> test them (or hold back and submit them to the perl5.7 development) if
> there is a demand for that.
At the least, please do put Pod::LaTeX on CPAN. That would be great. For
the Pod::Html converter, I don't know if you want to try to fight through
the morass of competing translators; I know of at least three completely
different ones that use different mechanisms.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
