On Sun, Jul 31, 2011 at 05:34:22PM -0400, Rocco Caputo wrote:
Cc: pod-people@perl.org ... trying to segue the discussion into that list.
To that same end, I've removed p5p from this reply.
It's legal and encouraged for the same index term to reference multiple
points in the broader text.
On Aug 4, 2011, at 20:51, Ronald J Kimball wrote:
On Sun, Jul 31, 2011 at 05:34:22PM -0400, Rocco Caputo wrote:
The obvious solution to ambiguous Lfoo is to emulate books. If we know
Lfoo is ambiguous, then we already have a list of link targets. Send the
reader to that list, and let
On 11-08-04 09:55 PM, Rocco Caputo wrote:
For example, this looks great in the HTML TOC outline. It's reminiscent of
traditional man pages where usage summaries are listed at the top. But it's
terrible to link to this section:
=head3 select_read FILE_HANDLE [, EVENT_NAME [,
I thought the Z code was being use for named anchors:
=head3 select_read FILE_HANDLE [, EVENT_NAME [, ADDITIONAL_PARAMETERS] ]
Zselect_read_main
and later:
Lselect read|select_read_main
I think the Pod::Simple https://metacpan.org/module/Pod::Simple does this.
I believe Z is the null
