<sect1 id="todo">

<sect1info>

<abstract role="texinfo-node">

  <para>Ideas for future improvements</para>

</abstract>

</sect1info>

<title>To-do list</title>

<indexterm><primary>to-do</primary></indexterm>

<indexterm><primary>future</primary></indexterm>

<indexterm><primary>bugs</primary></indexterm>

<indexterm><primary>wishlist</primary></indexterm>

<indexterm><primary>DocBook</primary></indexterm>

<para>

  With regards to DocBook support:

  <itemizedlist>

    <listitem>

      <para>

        <sgmltag class="element">qandaset</sgmltag> table of contents

        Perhaps allow <sgmltag class="element">qandadiv</sgmltag>

        elements to be nodes in Texinfo.

      </para>

    </listitem>

    <listitem>

      <para>

        <sgmltag class="element">olink</sgmltag>

	(do it like what the DocBook XSL stylesheets do)

      </para>

    </listitem>

    <listitem>

      <para>

        <sgmltag class="element">synopfragmentref</sgmltag>

      </para>

    </listitem>

    <listitem>

      <para>

        Man pages should support 

        class="element">qandaset</sgmltag>, 

        class="element">footnote</sgmltag>, 

        class="element">mediaobject</sgmltag>, 

        class="element">bridgehead</sgmltag>, 

        <sgmltag class="element">synopfragmentref</sgmltag>

        <sgmltag class="element">sidebar</sgmltag>,

        <sgmltag class="element">msgset</sgmltag>,

        <sgmltag class="element">procedure</sgmltag>

        (and there's more).

      </para>

    </listitem>

    <listitem>

      <para>

        Some DocBook 4.0 stuff:

        e.g. <sgmltag class="element">methodsynopsis</sgmltag>.

        On the other hand adding the DocBook 4.2 stuff shouldn't be that hard.

      </para>

    </listitem>

    <listitem>

      <para>

        <sgmltag class="element">programlisting</sgmltag>

        line numbering, and call-out bugs specified

        using <sgmltag class="element">area</sgmltag>.

        Seems to need XSLT extensions though.

      </para>

    </listitem>

    <listitem>

      <para>

        A template-based system for title pages, and 

        class="element">biblioentry</sgmltag>.

      </para>

    </listitem>

    <listitem>

      <para>

        Setting column widths in tables are not yet supported in man

        pages, but they should be.

      </para>

    </listitem>

    <listitem>

      <para>

        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.

      </para>

    </listitem>

  </itemizedlist>

</para>

<para>

For other work items, see the <quote>limitations</quote> or

<quote>bugs</quote> section in the individual tools’ reference pages.

</para>

<para>

  Other work items:

  <itemizedlist>

    <listitem>

      <para>

        Implement tables in pure XSLT.  Probably swipe the code

        that is in the DocBook XSL stylesheets to do so.

      </para>

    </listitem>

    <listitem>

      <para>

        Many stylesheet templates are still undocumented.

      </para>

    </listitem>

    <listitem>

      <para>

        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.

      </para>

    </listitem>

    <listitem>

      <para>

        Need to go through the stylesheets and check/fill in

        any missing DocBook functionality.  Make a table

        outlining what part of DocBook we support.

      </para>

      <para>

        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.

      </para>

      <para>

        Also some of the DocBook elements are not rendered

        very nicely even when they are supported.

      </para>

    </listitem>

    <listitem>

      <para>Fault-tolerant, complete error handling.</para>

    </listitem>

    <listitem>

      <para>

        Full localization for the output, as well as the messages

        from docbook2X programs.  (Note that 

        we already have internationalization for the output.)

      </para>

    </listitem>

  </itemizedlist>

</para>

</sect1>