forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject cvs commit: xml-forrest/src/documentation/content/xdocs faq.xml
Date Fri, 07 Nov 2003 03:24:08 GMT
crossley    2003/11/06 19:24:07

  Modified:    src/documentation/content/xdocs faq.xml
  Log:
  Revert last change, due to resurgence of discussion.
  
  Revision  Changes    Path
  1.51      +12 -1     xml-forrest/src/documentation/content/xdocs/faq.xml
  
  Index: faq.xml
  ===================================================================
  RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/faq.xml,v
  retrieving revision 1.50
  retrieving revision 1.51
  diff -u -r1.50 -r1.51
  --- faq.xml	6 Nov 2003 04:12:58 -0000	1.50
  +++ faq.xml	7 Nov 2003 03:24:07 -0000	1.51
  @@ -389,7 +389,13 @@
         </question>
         <answer>
           <p>
  -         Use the DocBook stylesheets directly. The DocBook
  +         There are two ways. Forrest can transform the DocBook format into the
  +         Forrest "document" DTD on-the-fly and then render that as normal.
  +         The stylesheet that does this transformation still needs a little
  +         work but it handles most things.
  +        </p>
  +        <p>
  +         The other way is to use the DocBook stylesheets directly. The DocBook
            DTDs are shipped with Forrest and automatically handled. However, you
            will need to have the DocBook stylesheets on your system (they are
            too massive to ship with Forrest) and configure Forrest accordingly.
  @@ -408,6 +414,11 @@
   ...
   ]]>
           </source>
  +        <p>
  +         You can also use a mixture of the two methods, some handled
  +         automatically by Forrest and some directly using DocBook stylesheets.
  +         You can also have a mixture of "document-v*" DTD and DocBook.
  +        </p>
           <p>
            Ensure that the document type declaration in your xml instance is
            well specified. Use a public identifier. The DTD will then be properly
  
  
  

Mime
View raw message