On Thu, Aug 5, 2010 at 8:42 AM, Georg Brandl <ge...@python.org> wrote:
> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Am 23.07.2010 17:50, schrieb Jean Daniel: > > Hello, > > > > I am using the :rfc:`3501` role to express this url : > > http://tools.ietf.org/html/rfc3501 > > > > This works fine and I am looking for a way to link to a specific > > section of the rfc; I would like to link to > > http://tools.ietf.org/html/rfc3501#section-2.3.1.1 > > > > I have tried :rfc:`3501#section-2.3.1.1` but I get the following error: > > > > (ERROR/3) invalid RFC number 3501#section-2.3.1.1 > > > > question 1: Is there a better way than using the :ref: role? > > I've now implemented the above syntax, it is a good idea to allow that. > > > question 2: Is it possible to use literalinclude with an _url_ to a text > file? > > Not right now. I'd also be reluctant to add this, since it adds another > case where internet access is needed to build docs. > > Georg > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.16 (GNU/Linux) > > iEYEARECAAYFAkxav9oACgkQN9GcIYhpnLCrDACgq/3fqzQnM4du70Lgpi1WNfdS > /EkAnRy50G2wCTMQFmyn0Hd205DnUEag > =ulOd > -----END PGP SIGNATURE----- > > > Perhaps a separate directive is in order for urls? Something like "urlinclude"? Kevin Horn -- You received this message because you are subscribed to the Google Groups "sphinx-dev" group. To post to this group, send email to sphinx-...@googlegroups.com. To unsubscribe from this group, send email to sphinx-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sphinx-dev?hl=en.
