Re: allowing L<text|href>
[email protected] (John McNamara)
| Newsgroups | perl.pod-people |
|---|---|
| Message-ID | <[email protected]> |
On Tue, Dec 1, 2009 at 5:16 AM, David E. Wheeler <[email protected]>wrote: > On Nov 30, 2009, at 7:28 PM, David E. Wheeler wrote: > > > And I'd be happy to test Pod::Simple's existing implementation of this > feature, and make sure it works properly for man pages and plain text. I can > probably squeeze some time to do that this week. > > FWIW, Pod::Simple already parses things as you expect. Here's the relevant > comment: > Hi, This should be implemented without a doubt. Just to note however that Pod::Simple::HTML and (and by extension search.cpan.org) currently convert this link: =pod This is a link to L<Perl|http://perl.org>. =cut To this: <p>This is a link to <a href=" http://search.cpan.org/perldoc?http%3A#%2Fperl.org" class="podlinkpod">Perl</a>.</p> Which isn't really what you would want since it adds in a perldoc search prefix. The $perldoc_url_prefix variable is configurable but resolve_pod_page_link() will probably have to be extended to avoid adding it to urls. This probably applies to Pod::Simple::XHTML as well. As a further aside, the kobesearch.cpan.org site doesn't do what you want either with the above pod. It creates a link within the page: <p><a href="#http://perl.org">Perl</a></p> And finally, the only installed module on my current machine that uses L<Text|url> is URI::ldap: ack "L<.+\|.+htm" /Library/Perl/ So we will probably have to get the word out that it is okay to use that syntax after it has been implemented. John. --