in reply to Anyone a wiz with Pod::HTML ?


I don't think that it is configurable. When I ran into this, and another problem, in the past I modified the Pod::Html code. The sub in question is process_puretext().

Of course, sublassing the module would be a better option. :-)

Update: The other problem, that I mention above, was the way that function descriptions in =head* are treated differently depending on the number of parameters that they have. For example here is some simple pod and the output from pod2html:

=head1 NAME Test - Some pod =head2 function1() Some text here. =head2 function2($foo) Some text "here". =head2 function3($foo, $bar) Some text here. =head2 function4($foo,$bar) Some text here. =cut


NAME

Test - Some pod

function1()

Some text here.

function2($foo)

Some text ``here''.

function3($foo, $bar)

Some text here.

function4($foo,$bar)

Some text here.


For some, possibly valid reason the third function isn't given code tags. This wasn't what I wanted however, so I modified the Pod::Html code to get the same behaviour in each of the above cases.

--
John.

Replies are listed 'Best First'.
Re: Re: Anyone a wiz with Pod::HTML ?
by John M. Dlugosz (Monsignor) on Jan 17, 2003 at 05:43 UTC
    I see, the code is not extensible at all, or even fully modular.

    Interesting about the function with 2 arguments! How strange.

    —John