Summary: | let the HTML documentation support sync-ToC | ||
---|---|---|---|
Product: | xorg | Reporter: | Christopher Yeleighton <giecrilj> |
Component: | Documentation | Assignee: | Xorg Project Team <xorg-team> |
Status: | RESOLVED INVALID | QA Contact: | Xorg Project Team <xorg-team> |
Severity: | enhancement | ||
Priority: | medium | CC: | marcoz, memsize |
Version: | 7.6 (2010.12) | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | 2011BRB_Reviewed | ||
i915 platform: | i915 features: |
Description
Christopher Yeleighton
2011-05-19 05:39:39 UTC
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.