Well guys, if this is the case, then it will be up to me again to remove this error detection from Pod::Parser and release a 1.51. Would be nice if this was the final verdict on this matter...
Stay tuned... -Marek -------- Original-Nachricht -------- > Datum: Mon, 23 Jan 2012 11:27:54 -0700 > Von: Karl Williamson <[email protected]> > An: "David E. Wheeler" <[email protected]> > CC: [email protected], Perl5 Porters <[email protected]>, > [email protected] > Betreff: Re: Deprecation of alternate text in hyperlinks > On 01/23/2012 11:03 AM, David E. Wheeler wrote: > > On Jan 23, 2012, at 9:26 AM, Karl Williamson wrote: > > > >> 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? > > > > I can’t parse that sentence, but if you’re asking if this bit should > be removed: > > > >> "Authors wanting to link to a particular (absolute) URL, must do so > >> only with "LE<lt>scheme:...>" codes (like > >> LE<lt>http://www.perl.org>), and must not attempt "LE<lt>Some Site > >> Name|scheme:...>" codes. This restriction avoids many problems > >> in parsing and rendering LE<lt>...> codes." > > > > Then the answer is “yes.” And Pod::Parser should be modified to > allow or support L<text|scheme:>. > > > > Best, > > > > David > > > > > > > > Sorry for the confusing text. You did parse it correctly, and blead now > has the text from perlpodspec removed. -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de
