cvs commit: LFS/newxml README TODO

matthew at linuxfromscratch.org matthew at linuxfromscratch.org
Thu Mar 11 14:33:32 PST 2004


matthew     04/03/11 15:33:32

  Modified:    newxml   README TODO
  Log:
  * Updated README noting dependency on FOP for PDF processing
  * Restructured TODO to hopefully make it clearer and easier to digest
  
  Revision  Changes    Path
  1.8       +3 -1      LFS/newxml/README
  
  Index: README
  ===================================================================
  RCS file: /home/cvsroot/LFS/newxml/README,v
  retrieving revision 1.7
  retrieving revision 1.8
  diff -u -r1.7 -r1.8
  --- README	11 Mar 2004 22:10:05 -0000	1.7
  +++ README	11 Mar 2004 22:33:32 -0000	1.8
  @@ -14,6 +14,9 @@
   libxml2-2.6.7 & libxslt-1.1.4 - these releases have a couple of XInclude related
                                   bugfixes in them
   
  +FOP-0.20.5 - required for PDF generation.  The easiest method of installation is
  +             to download the binary tarball, extract it to /opt/fop and set
  +             JAVA_HOME, FOP_HOME and PATH appropriately.
   
   Setting up the DTD
   ~~~~~~~~~~~~~~~~~~
  @@ -47,7 +50,6 @@
   be routed through the local /etc/xml/docbook file (which subsequently rewrites
   those URIs to our local copy of the DTD).  This step won't be required once the
   official 4.3 release is made.
  -
   
   Processing the sources
   ~~~~~~~~~~~~~~~~~~~~~~
  
  
  
  1.7       +41 -22    LFS/newxml/TODO
  
  Index: TODO
  ===================================================================
  RCS file: /home/cvsroot/LFS/newxml/TODO,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- TODO	9 Mar 2004 21:57:50 -0000	1.6
  +++ TODO	11 Mar 2004 22:33:32 -0000	1.7
  @@ -1,25 +1,44 @@
   TODO
   ~~~~
   
  -1. Decide on a validation method to use.  DTD's are not namespace aware
  -   which may cause us problems in the future.  RelaxNG looks promising but
  -   there's also the W3C's "XML Schema".  Docbook is available in both, and
  -   libxml2 supports both.
  -2. Provide a css file to provide nicer output than whatever the UA's default is.
  -   * Started - needs some comments regarding layout.
  -   * Binary/library names listed in "Short Description" sections should be in a
  -     fixed-width font.
  -   * URLs of "Official download locations" appear on the line below where they
  -     should do in chapter 6.
  -   * Header (naviagtion) areas, TOCs & "Titlepage" sections need font sizes &
  -     style fixing.
  -3. Decide whether we want to use the strict or transitional XHTML DTD.  Note in
  -   particular http://www.sagehill.net/docbookxsl/OtherOutputForms.html#d0e23340.
  -4. Do we want to use graphics in the navigation headers?
  -5. The legalinfo page:
  -     * It generates it's own hyperlink ("Legal Notice") but the current book has
  -       it linked to via the "Copyright" message above.  Does this matter?
  -6. Decide on what levels the TOCs should go down to.
  -   * Section elements now no longer have a TOC generated for them - the book TOC
  -     remains unchanged as do the part and appendix level TOCs.
  -7. Write some more stylesheets to produce alternative output formats.
  +1. General
  +~~~~~~~~~~
  +
  +1.1.  Decide on a validation method to use.  DTD's are not namespace aware
  +      which may cause us problems in the future.  RelaxNG looks promising but
  +      there's also the W3C's "XML Schema".  Docbook is available in both, and
  +      libxml2 supports both.
  +
  +2. HTML
  +~~~~~~~
  +
  +2.1. Provide a css file to provide nicer output than whatever the UA's default
  +     is.
  +       * Started - needs some comments regarding layout.
  +       * Binary/library names listed in "Short Description" sections should be
  +         in a fixed-width font.
  +       * URLs of "Official download locations" appear on the line below where
  +         they should do in chapter 6.
  +       * Header (naviagtion) areas, TOCs & "Titlepage" sections need font sizes
  +         & style fixing.
  +2.2. Decide whether we want to use the strict or transitional XHTML DTD. Note in
  +     particular http://www.sagehill.net/docbookxsl/OtherOutputForms.html#d0e23340.
  +2.3. The legalinfo page generates it's own hyperlink ("Legal Notice") but the
  +     current book has it linked to via the "Copyright" message above.  Does this
  +     matter?
  +2.4. Decide on what levels the TOCs should go down to.
  +       * Section elements now no longer have a TOC generated for them - the book         TOC remains unchanged as do the part and appendix level TOCs.
  +
  +3. PDF
  +~~~~~~
  +
  +  3.1. Obtain feedback on the current layout.
  +  3.2. Investigate the possibility of using PassiveTex in place of FOP.
  +
  +4. Other Formats
  +~~~~~~~~~~~~~~~~
  +
  +  4.1. LaTeX - confirm that the publisher does in fact *need* this.
  +  4.2. TXT & PS are possible using FOP, going via XSL:FO.
  +  4.3. RTF may be possible in future versions of FOP.
  +  4.4. nALFS profiles.
  
  
  



More information about the lfs-book mailing list