| Subject: | Don't use L<....(3)> in links in Pod |
The problem with L<...(3)> in Pod links is that some Pod viewers,
especially Pod::Simple-based like tkpod, use this style to recognize the
link as a manpage link, not as a link to another Pod page.
pod perlpodspec also mentions this problem:
ยท At time of writing, "L<name>" values are of two types: either
the name of a Pod page like "L<Foo::Bar>" (which might be a real Perl
module or program in an @INC / PATH directory, or a .pod file in those
places); or
the name of a UNIX man page, like "L<crontab(5)>". In
theory, "L<chmod>" in ambiguous between a Pod page called "chmod", or
the Unix man page "chmod" (in whatever man-section). However, the
presence of a string in
parens, as in "crontab(5)", is sufficient to signal that what
is being discussed is not a Pod page, and so is presumably a UNIX man
page. The distinction is of no importance to many Pod processors, but some
processors that render to hypertext formats may need to
distinguish them in order to know how to render a given "L<foo>" code.
So I would suggest to remove the chapter specification from the L<...>
content. Note that search.cpan.org does not have this problem, it
assumes everything to be a Pod (probably because it has no way to link
to manpages).
Regards,
Slaven