<?xml version="1.0" encoding="ISO-8859-1"?>

<sect1>
<sect1info>

<!-- Please, do NOT edit the following revision history by hand. Use the
"make <module_name>.revision" target instead.  -->

<revhistory>
  <revision>
    <revnumber>1.en.lproof</revnumber>
    <date>YYYY-MM-DD</date>
    <authorinitials>tbn</authorinitials>
  </revision>
  <revision>
    <revnumber>1.en.ispell</revnumber>
    <date>YYYY-MM-DD</date>
    <authorinitials>tbn</authorinitials>
  </revision>
  <revision>
    <revnumber>1.en.pproof</revnumber>
    <date>YYYY-MM-DD</date>
    <authorinitials>tbn</authorinitials>
  </revision>
  <revision>
    <revnumber>1.en.tproof</revnumber>
    <date>YYYY-MM-DD</date>
    <authorinitials>tbn</authorinitials>
  </revision>
  <revision>
    <revnumber>1.en.translate</revnumber>
    <date>YYYY-MM-DD</date>
    <authorinitials>tbn</authorinitials>
  </revision>
  <revision>
    <revnumber>1.en.write</revnumber>
    <date>YYYY-MM-DD</date>
    <authorinitials>tbn</authorinitials>
  </revision>
</revhistory></sect1info>

  <sect1info>
<sect1info>

<!-- Please, do NOT edit the following revision history by hand. Use the
"make <module_name>.revision" target instead.  -->

<revhistory>
  <revision>
    <revnumber>1.en.lproof</revnumber>
    <date>YYYY-MM-DD</date>
    <authorinitials>tbn</authorinitials>
  </revision>
  <revision>
    <revnumber>1.en.ispell</revnumber>
    <date>YYYY-MM-DD</date>
    <authorinitials>tbn</authorinitials>
  </revision>
  <revision>
    <revnumber>1.en.pproof</revnumber>
    <date>YYYY-MM-DD</date>
    <authorinitials>tbn</authorinitials>
  </revision>
  <revision>
    <revnumber>1.en.tproof</revnumber>
    <date>YYYY-MM-DD</date>
    <authorinitials>tbn</authorinitials>
  </revision>
  <revision>
    <revnumber>1.en.translate</revnumber>
    <date>YYYY-MM-DD</date>
    <authorinitials>tbn</authorinitials>
  </revision>
  <revision>
    <revnumber>1.en.write</revnumber>
    <date>YYYY-MM-DD</date>
    <authorinitials>tbn</authorinitials>
  </revision>
</revhistory></sect1info>


<!-- Please, do NOT edit the following revision history by hand. Use the
"make <module_name>.revision" target instead.  -->

<revhistory>
      <revision>
        <revnumber>1.en.lproof</revnumber>
        <date>YYYY-MM-DD</date>
        <authorinitials>tbn</authorinitials>
      </revision>
      <revision>
        <revnumber>1.en.ispell</revnumber>
        <date>YYYY-MM-DD</date>
        <authorinitials>tbn</authorinitials>
      </revision>
      <revision>
        <revnumber>1.en.pproof</revnumber>
        <date>YYYY-MM-DD</date>
        <authorinitials>tbn</authorinitials>
      </revision>
      <revision>
        <revnumber>1.en.tproof</revnumber>
        <date>YYYY-MM-DD</date>
        <authorinitials>fm</authorinitials>
      </revision>
      <revision>
        <revnumber>1.en.write</revnumber>
        <date>2002-10-11</date>
        <authorinitials>cb</authorinitials>
      </revision>
    </revhistory></sect1info>
  <title>For next versions</title>

  <sect2 id="f107">
    <title>f107: Allow to have modules sorted in different
    dirs</title> <para>When there are many many modules it becomes
    difficult to navigate through them.</para> <para>Allow to create
    arbitrary directories under <filename>modules/xx/</filename> and
    sort modules in it.</para>
  </sect2>
 
  <sect2 id="sf567427">
    <title>567427: Replace initials for To Be Named author</title>
    <para>When an author is not defined, "tbn" should be replaced by
    something like <literal>NotKnown</literal> or other
    <quote>strange</quote> set of initials to avoid possible conflict
    with authors whose initials are <acronym>TBN</acronym>.</para>
  </sect2>
 
  <sect2 id="f101">
    <title>f101: Use a default image in output when it's
    missing</title> <para>Use a big red X so that it shows on
    output.</para>
  </sect2>
 
  <sect2 id="f102">
    <title>f102: Generate per document/module bugreport</title>
    <para>This report would include the following:<itemizedlist>
	<listitem>
	  <para>DocBook validity;</para>
	</listitem>
	<listitem>
	  <para>Missing images (this is related to <xref
	  linkend="f101"/>);</para>
	</listitem>
	<listitem>
	  <para>Spelling: by using <ulink
	  url="http://www.ca.postgresql.org/~petere/spellcheck.html"><application>sgml-spell-checker</application></ulink>. This
	  will require to maintain a list of acceptable words.</para>
	</listitem>
      </itemizedlist>This should be cistomizable: get only the report
      type desired.</para>
  </sect2>
 
  <sect2 id="f110">
    <title>f110: Use a default image in output when it's
    missing</title> <para></para>
  </sect2>
 
  <sect2 id="sf608447">
    <title>608447: Consider (some) attributes for reports</title>
    <para> Borges reports should take into account element attributes
    too in order to properly signal differences between two
    languages.</para> <para>At least the
    <literal>condition=""</literal> attribute should be taken into
    account because it has an impact on the output document.</para>
  </sect2>
 
  <sect2 id="f103">
    <title>f103: Allow custom tasks list</title> <para>Get rid of the
    fixed tasks set and allow a user to customize needed tasks. Two
    tasks are probably necessary anymey:
    <literal>write</literal> and <literal>translate</literal>.</para>
  </sect2>
 
  <sect2 id="f104">
    <title>f104: XRefs across manuals</title> <para>Moving a module
    from one manual to another may prove a real headache wrt cross
    references. If other modules were refering to that moved module,
    references are invalid.</para> <para>We must find a solution to
    automate this, by adding the name of the manual to the generated
    xref text when the referred module is in another manual. This
    should be done in conjunction to DocBook community.</para>
  </sect2>
 
  <sect2 id="f105">
    <title>f105: Use "borges:" namespace</title> <para>Currently,
    Borges management information is stored in DocBook own elements
    (notably revhistory). This requires then to ignore those elements
    in actual output if we don't want them to appear.</para>
    <para>This require to identify which are the elements concerned,
    write a Borges management DTD, and modify the system to use those
    new Borges management elements in source files through the use of
    namespaces.</para>
  </sect2>
 
  <sect2 id="f106">
    <title>f106: Allow specific lang per document</title> <para>Some
    documents may not need to be translated in all the languages
    supported by the whole project (in
    <filename>conf/repository.xml</filename>).</para> <para>Allow to
    specify in <filename>conf/manual-default.xml</filename> (and
    therefore in <filename>manuals/Manual/conf.xml</filename>) the
    subset of languages needed for that document.</para>
  </sect2>
 
</sect1>

<!-- Keep this comment at the end of the file
Local variables:
mode: xml
sgml-parent-document: ("../../manuals/Borges-Roadmap/master.xml" "sect1")
End:
-->