Deprecation of alternate text in hyperlinks

2012-01-23 Thread Karl Williamson
Version 1.50 of Pod::Parser adds a check and message indicating that 
Ltext|hyperlink is deprecated.  This is based on the following 
sentences in perlpodspec, which has been there since its inception in 2001:


Authors wanting to link to a particular (absolute) URL, must do so
only with LEltscheme:... codes (like
LElthttp://www.perl.org), and must not attempt LEltSome Site
Name|scheme:... codes.  This restriction avoids many problems
in parsing and rendering LElt... codes.

Elsewhere in the document, it says that the handler should handle these, 
as in the example


 LPerl.org|http://www.perl.org/

The new Pod:Parser has just been installed in blead, and about 10 pods 
run afoul of this new check, including things like


Lperl...@perl.org|mailto:perl...@perl.org

My question is should there really be a message for this kind of use, 
and if so, should it extend to mailto: links?


Re: Deprecation of alternate text in hyperlinks

2012-01-23 Thread Karl Williamson

On 01/23/2012 10:05 AM, David E. Wheeler wrote:

On Jan 23, 2012, at 8:06 AM, Karl Williamson wrote:


The new Pod:Parser has just been installed in blead, and about 10 pods run 
afoul of this new check, including things like

Lperl...@perl.org|mailto:perl...@perl.org

My question is should there really be a message for this kind of use, and if 
so, should it extend to mailto: links?


No. Suport for Lname|scheme:...  was added to perlpodspec in 2009. 
Pod::Simple has supported it for years; Test::Pod started officially allowing it in 
v1.41, IIRC.

Relevant changes:

   
https://github.com/theory/pod-simple/commit/1e61e819debf9c7c23907d7bb9e37855665fd595
   
http://perl5.git.perl.org/perl.git/commit/f6e963e4dd62b8e3c01b31f4a4dd57e47e104997
   
https://github.com/theory/test-pod/commit/ae6a44894eda4fd09fb412d837efe543628cd7d6

Discussion:

   http://code.activestate.com/lists/perl-pod-people/1393/

Best,

David




So, you're saying I believe the text in perlpodspec that was the 
motivation for these changes should be removed, and that Pod::Parser 
should revert to its old behavior of not checking for this.


Is that so?



Re: Deprecation of alternate text in hyperlinks

2012-01-23 Thread Ricardo Signes
* Karl Williamson pub...@khwilliamson.com [2012-01-23T12:26:27]
 So, you're saying I believe the text in perlpodspec that was the
 motivation for these changes should be removed, and that Pod::Parser
 should revert to its old behavior of not checking for this.

After all the care taken to be sure that the original fears about
L...|http:/// were unfounded, I think we should stick to it and allow it.
Pod::Parser should probably not be warning on these, unless it somehow can't
handle them, in which case the better fix is to handling them, not warning.

-- 
rjbs


signature.asc
Description: Digital signature


Re: Deprecation of alternate text in hyperlinks

2012-01-23 Thread Russ Allbery
Karl Williamson pub...@khwilliamson.com writes:

 Version 1.50 of Pod::Parser adds a check and message indicating that
 Ltext|hyperlink is deprecated.  This is based on the following
 sentences in perlpodspec, which has been there since its inception in
 2001:

 Authors wanting to link to a particular (absolute) URL, must do so
 only with LEltscheme:... codes (like
 LElthttp://www.perl.org), and must not attempt LEltSome Site
 Name|scheme:... codes.  This restriction avoids many problems
 in parsing and rendering LElt... codes.

 Elsewhere in the document, it says that the handler should handle these,
 as in the example

  LPerl.org|http://www.perl.org/

 The new Pod:Parser has just been installed in blead, and about 10 pods
 run afoul of this new check, including things like

 Lperl...@perl.org|mailto:perl...@perl.org

 My question is should there really be a message for this kind of use,
 and if so, should it extend to mailto: links?

I disagree with this change, and disagreed with the statement in
perlpodspec in 2001 as well.  There's really no good reason to disallow
anchor text for hyperlinks in L codes.  The parsing issues are not that
serious.

I think this syntax should be undeprecated and declared officially
blessed.

-- 
Russ Allbery (r...@stanford.edu) http://www.eyrie.org/~eagle/