Re: RFC Suggest: Use of L<> to link RFCs; "CONFLICTS WITH", "REQUIRES", "STATUS" sections

--q6mBvMCt6oafMx9a
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

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

--q6mBvMCt6oafMx9a
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.2 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE5o4zM53XjJNtBs4cRAroxAJ0SYTQL2cAmvNfTNrECQXvXPcmCOgCcCdtW
d3WkbmNXiCxH0GPx5KAUZRM=
=7WUD
-----END PGP SIGNATURE-----

--q6mBvMCt6oafMx9a--