OOO v1.1 Forrest Transformation Examples
by AD Marshall (who's just filling in the XML blanks...)

Table Of Contents
=================
Forrest-generated Sub-directories
OOWriter v1.1 SXW Test Transformations

Forrest-generated Sub-directories
=================================

  This is an example of a sub-menu generated from an "xdocs" 
  sub-directory.


  :: A note from Forrest that was part of the original page this one is based 
     on:
     When creating new subdirectories, remember that these must be declared in 
     site.xml or each directory must have a book.xml file.

OOWriter v1.1 SXW Test Transformations
======================================

  The menu on the left lists the examples of OpenOffice.org Writer test 
  transformations under the sub-menu OpenOffice.org v1.1. Other 
  transformation examples are listed as entries of the main menu.

  The lpi-manuals project participants might note:

  * the OOW v1.1 examples, but especially LPI-101 v0.2;
  * Apache doc v1.3 & v2.0 — sample pages demonstrating the use of the Apache 
    Document v1.3 & v2.0 XML DTDs, from which all the pages of this project 
    site were generated;
  * ascii-art page — demonstrates using ascii-art to generate SVG graphics 
    via Forrest.

                                  ** Note **
  While the LPI-101 v0.02 [Link: 
  Sernet-LATM-LPI-101-v-0.2-20050712-1243-noXSO.html] sample, in the menu 
  panel to the left, includes an icon linked to a PDF version of the 
  original file [Link: 
  Sernet-LATM-LPI-101-v-0.2-20050712-1243-noXSO.sxw], that PDF was 
  produced by OOWriter 2.0-pre (Novell Edition), not Forrest. (Simply 
  placing the finished PDF file appropriately under the project's 
  completed "build/site" directory prevented Forrest from building it 
  again while it's configured to produce PDF output.) 
  --------------------------------------------------------------------------

  The 256MB of RAM in the ThinkPad 600x PIII used to run Forrest to build 
  this project site is insufficient to convert the LPI-101 document to 
  PDF and a Java Out-of-Memory exception occurs (after 20+ minutes of 
  Forrest running with no warning or other messages being displayed).

  The Forrest 0.70 FAQ [Link: ../../samples/faq.html], however, may offer 
  a solution issue under the question "1.7. How can I specify the amount 
  of memory to be used by Java?. That solution is as yet untested.

  Another potential solution might be to individually tranform large, 
  complex documents. So far, only complete site generations were tried.

                                ** Warning **
  Forrest produces variously Apache doc "v1.2" or "v1.3" XML from the 
  original LPI-101 v0.2 (sxw) file. (See the "DOCTYPE" of source the XML 
  linked to the XML icon on the LPI-101 v0.2 example.) That XML, however, 
  could not be loaded into either Forrest, as a replacement for the 
  original SXW file, without hundreds of validation errors resulting, nor 
  into OOWriter (2.0-pre Novell Edition) as anything but plain, 
  unformatted text. Since neither OOWriter nor any other conversion tool 
  know can yet be used to generate any valid Docbook XML from OOO v1.1 
  SXW documents, this remains a key issue for lpi-manuals.
  --------------------------------------------------------------------------

  In the end, it is worth noting that, so far, no tool known to date has 
  been able to produce largely valid Docbook from any version of the 
  LPI-101 document, while the ooo2sdbk [Link: 
  http://www.chez.com/ebellot/ooo2sdbk/] tool was able to produce largely 
  valid Simplified Docbook XML from the LPI-102 SXW file. It may well be 
  that this document's structure and formatting need to be made more 
  simple or consistent before any such conversion utility can be 
  effectively applied.