LMPX.COM |
Home | Linux | Mysql | PHP | XML | ||
|
|
|||
From: Bradley M. Kuhn Date: Wed Aug 23 02:35:24 2000 Subject: Re: RFC Suggest: Use of L<> to link RFCs; "CONFLICTS WITH", "REQUIRES", "STATUS" sections
Larry Wall wrote: > John Porter writes: > : Bradley M. Kuhn wrote: > : > Nathan Torkington wrote: > : > > Why not just L<RFC21> ? It's shorter. > : > > : > The main thing I have been struggling with is (to quote perlpod(1)): > : > L<name> manual page > : > whereas: > : > L<name/"sec"> section in other manual page > : > > : > Thus, I didn't think we'd want to pollute the man page space with our RFC's, > : > but I did think it might be possible that there would be a "perl6-RFCs" man > : > page, with sections for each RFC. > : > : I think we can safely presume that the pod-to-foo translators will have > : been locally hacked to account for the RFC-ish nature of the documents. > : IOW, that L<RFC1> will be correctly translated into > : <a href="/rfc/1.html">RFC1</a> or some such. Based on the discussion of this thread, I think L<RFCNN> is the right approach, instead of my convoluted system. :) I didn't do a new patch for rfc-format.pod and rfc-sample.pod. Ziggy, if you need one to make your life easier, let me know. -- Bradley M. Kuhn - http://www.ebb.org/bkuhn Attachment: [application/pgp-signature]
| Navigate in group perl.bootstrap at sever nntp.perl.org | |
| Previous | Next |
| © No Copyright You are free to use Anything |
Site Maintained by PHP Developer
Powered By PHP Consultants |