To-do list
<< Previous |  | Next >>

## To-do list

With regards to DocBook support:

- `qandaset` table of contents Perhaps allow `qandadiv` elements to be nodes in Texinfo.

- `olink` (do it like what the DocBook XSL stylesheets do)

- `synopfragmentref`

- Man pages should support `qandaset`, `footnote`, `mediaobject`, `bridgehead`, `synopfragmentref` `sidebar`, `msgset`, `procedure` (and there's more).

- Some DocBook 4.0 stuff: e.g. `methodsynopsis`. On the other hand adding the DocBook 4.2 stuff shouldn't be that hard.

- `programlisting` line numbering, and call-out bugs specified using `area`. Seems to need XSLT extensions though.

- A template-based system for title pages, and `biblioentry`.

- Setting column widths in tables are not yet supported in man pages, but they should be.

- Support for typesetting mathematics. However, I have never seen any man pages or Texinfo manuals that require this, obviously because math looks horrible in ASCII text.

For other work items, see the “limitations” or “bugs” section in the individual tools’ reference pages.

Other work items:

- Implement tables in pure XSLT. Probably swipe the code that is in the DocBook XSL stylesheets to do so.

- Many stylesheet templates are still undocumented.

- Write documentation for Man-XML and Texi-XML. Write a smaller application (smaller than DocBook, that is!) of Man-XML and/or Texi-XML (e.g. for W3C specs). A side benefit is that we can identify any bugs or design misfeatures that are not noticed in the DocBook application.

- Need to go through the stylesheets and check/fill in any missing DocBook functionality. Make a table outlining what part of DocBook we support.

  For example, we have to check that each attribute is actually supported for an element that we claim to support, or else at least raise a warning to the user when that attribute is used.

  Also some of the DocBook elements are not rendered very nicely even when they are supported.

- Fault-tolerant, complete error handling.

- Full localization for the output, as well as the messages from docbook2X programs. (Note that we already have internationalization for the output.)

<< Previous |  | Next >>
How docbook2X is tested | Table of Contents | Release history