On Tue, Aug 11, 2009 at 01:29:11PM -0500, Karl Berry wrote: > another > easy way out would be to have nodes as stand-alone elements, but not > first childs of sections, they should just be output where they appear. > Karl, does it look good to you? > > Yes, sounds fine. Nodes and sections are theoretically independent.
So currently, the output for something along @chapter Chap1 @node chap2 @chapter Chap2 Is: <chapter> <title>Chap1</title> <node> <nodename>chap2</nodename> </node> </chapter> <chapter> <title>Chap2</title> </chapter> Which mleans that the node `chap2' is within the <chapter> with title `Chap1' element. Is it right? > For example, we could make yet another reference command, but it's not > an easy thing to do. We already have @ref, which seems about as minimal > as it can be. Anything related only to page numbers can't be used in > Info output. I don't know if this is the right thing to do, but if we want to simplify things, we can drop @xref and @pxref from the documentation and say that there are 3 ways to call @ref: * with one argument it is a reference to a node or an anchor within the document, * with argument 1 and 4 it is a reference to an info manual, * with argument 3 and 5 it is areference to a book, and it is possible to combine reference to a book and to an info manual. Not saying that it is the right thing to do, just how it could be simplified. -- Pat
