The documentation books like [1] available on line have a table of contents. However, the documentation nodes do not have any navigation facilities. At least up-links should be supported (by attaching a jumper to the node H3 or just converting the node H3 to a link to the corresponding entry in the table of contents). ___ [1] <URL: http://www.x.org/releases/X11R7.6/doc/libX11/specs/libX11/libX11.html#Setting_and_Reading_the_WM_PROTOCOLS_Property >
How do we go about doing this in the xml? I'm all for making getting around in the documentation easier. I don't know how to do this in the xml. Ideas?
(In reply to comment #1) > How do we go about doing this in the xml? > > I'm all for making getting around in the documentation easier. I don't know > how to do this in the xml. > Ideas? A brief reading of DocBook manual indicates the toc is generated and not written in the source. The customization of the toc can be done in the xorg stylesheet following these options: http://docbook.sourceforge.net/release/xsl/current/doc/html/toc_index.html Nothing is obvious to me as for adding uplinks to the toc. This would have to be a feature of the toc generation function as the toc does not exist in the source.
Heck, the generated ToC elements do not even have identifiers to target. Seems a DocBook-XSL problem then.
(In reply to comment #1) > How do we go about doing this in the xml? > > I'm all for making getting around in the documentation easier. I don't know > how to do this in the xml. > Ideas? http://docbook.sourceforge.net/release/xsl/current/webhelp/docs/content/ch01.html
Mass closure: This bug has been untouched for more than six years, and is not obviously still valid. Please reopen this bug or file a new report if you continue to experience issues with current releases.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.