xml-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From fo...@locus.apache.org
Subject cvs commit: xml-site/sources/fop examples.xml bugs.xml download.xml involved.xml running.xml
Date Fri, 18 Feb 2000 10:05:58 GMT
fotis       00/02/18 02:05:58

  Modified:    sources/fop bugs.xml download.xml involved.xml running.xml
  Added:       sources/fop examples.xml
  Log:
  updated documentation for release 0.12.1
  
  Revision  Changes    Path
  1.3       +17 -10    xml-site/sources/fop/bugs.xml
  
  Index: bugs.xml
  ===================================================================
  RCS file: /home/cvs/xml-site/sources/fop/bugs.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- bugs.xml	2000/01/27 10:45:47	1.2
  +++ bugs.xml	2000/02/18 10:05:57	1.3
  @@ -5,14 +5,21 @@
   <!-- Bugs -->
   
   <s1 title="Bugs">
  -  <p>In release version 0.12.0 you cannot use FOP with the commandline XTCommandLine.

  -     This results always in the fatal error "Root element must be root". If you need 
  -     XTCommandLine please use the cvs version, where the bug is fixed.  
  -  </p>
  -  <p>The page count (/Count tag) in the Pages dictionary is 0 in PDF files produced
by 
  -     FOP. Most of the time this doesn't do any harm, but it has been reported to be a 
  -     problem with xpdf. 
  -  </p>
  -  <p>Colour not continued onto subsequent pages if coloured block goes over page.
  -  </p>
  +  <s2 title="How to report bugs">
  +    <p>Please use the bug reporting system <jump href="http://xml.apache.org/bugs/">bugzilla
  +    </jump>, which is part of xml.apache.org.</p>
  +  </s2>
  +  <s2 title="Some bugs">
  +    <p>In release version 0.12.0 you cannot use FOP with the commandline XTCommandLine.

  +       This results always in the fatal error "Root element must be root". If you need

  +       XTCommandLine please use the cvs version, where the bug is fixed, or a newer version
  +       of FOP.
  +    </p>
  +    <p>The page count (/Count tag) in the Pages dictionary is 0 in PDF files produced
by 
  +       FOP. Most of the time this doesn't do any harm, but it has been reported to be a

  +       problem with xpdf. 
  +    </p>
  +    <p>Colour not continued onto subsequent pages, if coloured block goes over page.
  +    </p>
  +  </s2>
   </s1>
  
  
  
  1.3       +4 -15     xml-site/sources/fop/download.xml
  
  Index: download.xml
  ===================================================================
  RCS file: /home/cvs/xml-site/sources/fop/download.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- download.xml	1999/12/14 12:53:08	1.2
  +++ download.xml	2000/02/18 10:05:57	1.3
  @@ -4,25 +4,14 @@
   <!-- Download FOP -->
   
   <s1 title="Downloading FOP">
  -  <s2 title="Downloading binaries">
  +  <s2 title="">
       <p>You can download the latest release version <jump 
  -       href="http://xml.apache.org/dist/fop_bin_0_12_0.jar">FOP 0.12.0</jump>.
</p>
  -    <p>NOTE: you do not have to unjar or unzip this jar file.</p>
  +       href="http://xml.apache.org/dist/fop-0_12_1.jar">FOP 0.12.1</jump>. </p>
  +    <p>Note: This jar file must be unpacked. It contains the binary fop_bin_0_12_1.jar,
  +       the documentation (including some example fo files) and the source.  </p>
       <p>To run FOP from the command line, see <jump href="running.html">Running
FOP</jump>. If you are 
          interested in embedding FOP in a Java application of your own, see 
          <jump href="embedding.html">Embedding FOP</jump>.
  -    </p>
  -  </s2>
  -<!--    <s2 title="">
  -    <p>Documentation can be downloaded here as <jump href="">HMTL file</jump>
or 
  -       as <jump href="">PDF file</jump>.
  -    </p> 
  -  </s2>
  --->
  -
  -  <s2 title="Downloading source code">
  -    <p>You can also download the <jump href="http://xml.apache.org/dist/fop_src_0_12_0.jar">source
code 
  -       v. 0.12.0</jump> as a jar file
       </p>
     </s2>
   </s1>
  
  
  
  1.3       +2 -0      xml-site/sources/fop/involved.xml
  
  Index: involved.xml
  ===================================================================
  RCS file: /home/cvs/xml-site/sources/fop/involved.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- involved.xml	1999/12/20 15:35:55	1.2
  +++ involved.xml	2000/02/18 10:05:57	1.3
  @@ -19,6 +19,8 @@
     <p>7. When you feel comfortable modifying the code, send diffs to 
           fop-dev with your contributions. </p>
     <p>8. Have fun!</p>
  +  <p><jump href="http://xml.apache.org/overview.html">xml.apache.org</jump>

  +     has a more explicit description how to get involved. </p>
     </s2>
     <s2 title="The Ways of FOP">
       <p>The following shows an example use of FOP from org.apache.fop.apps.CommandLine.java:</p>
  
  
  
  1.4       +15 -20    xml-site/sources/fop/running.xml
  
  Index: running.xml
  ===================================================================
  RCS file: /home/cvs/xml-site/sources/fop/running.xml,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- running.xml	1999/12/14 12:53:08	1.3
  +++ running.xml	2000/02/18 10:05:57	1.4
  @@ -8,7 +8,8 @@
       <p>Following software must be installed:</p>
       <p>a) Java 1.1.x or later</p>
       <p>b) An XML parser which supports SAX and DOM like 
  -          <jump href="http://xml.apache.org/xerces-j/index.html">Xerces-J</jump>.</p>
  +          <jump href="http://xml.apache.org/xerces-j/index.html">Xerces-J</jump>.

  +          (Xerces is the default xml parser)</p>
       <p>c) If you have to produce the flow objects files, which are the input for
FOP, 
          you need a transformation utility to create this files from your xml files. 
          Normally this is an XSLT stylesheet processor like 
  @@ -21,7 +22,7 @@
       <p>a) Batch processing formatting objects (fo) files: </p>
       <p><code>java org.apache.fop.apps.CommandLine fo-file pdf-file</code></p>
       <p>b) Batch processing xml files (includes production of the fo-files):</p>
  -    <p><code>java org.apache.fop.apps.CommandLine xml-file xsl-file pdf-file</code></p>
  +    <p><code>java org.apache.fop.apps.XTCommandLine xml-file xsl-file pdf-file</code></p>
       <p>c) Previewing the fo-file:</p>
       <p><code>java org.apache.fop.apps.AWTCommandLine fo-file</code></p>
       <p>Each method uses next to the fop classes other packages. The following describes

  @@ -33,31 +34,29 @@
            and set the used sax parser according to your enviroment
         </p>
         <p>Classpath settings: You will need to include FOP and your XML Parser 
  -         in your classpath and so you might invoke FOP, if XP is your sax parser 
  -         and Xerces-J your DOM parser: 
  +         in your classpath and so you might invoke FOP, if Xerces-J is your xml parser:

         </p>
  -      <p><code>java -cp fop_bin_0_12_0.jar;xp.jar;xerces.jar </code></p>
  +      <p><code>java -cp fop_bin_0_12_1.jar;xerces.jar </code></p>
         <p><code>org.apache.fop.apps.CommandLine fo-file pdf-file</code></p>
  -      <p>For historical reasons the standard sax parser for FOP is XP from James
Clark. 
  -         This will change in the future to Xerces-J, but at the moment you will need to
set the property 
  +      <p>If you want to use another sax parser, you will need to set the property

            org.xml.sax.parser to any other SAX Parser class to use. The following example
shows 
  -         the command line, if you use Xerces-J: 
  +         the command line, if you use XP from James Clark: 
         </p>
  -      <p><code>java -Dorg.xml.sax.parser=org.apache.xerces.parsers.SAXParser</code></p>
  -      <p><code>-cp fop_bin_0_12_0.jar;xerces.jar</code></p>
  +      <p><code>java -Dorg.xml.sax.parser=com.jclark.xml.sax.Driver</code></p>
  +      <p><code>-cp fop_bin_0_12_1.jar;xerces.jar;xp.jar</code></p>
         <p><code>org.apache.fop.apps.CommandLine fo-file pdf-file</code></p>
  +      <p>Note: The xerces jar file must be included, because xp has no dom support.</p>
       </s3>
       <s3 title="Method Two">
         <p>Rather than performing transformation with an XSLT before invoking FOP,
it is 
            possible, if you use XT as your XSLT engine, to just call FOP and have it call

            XT for you. To do this, run the class org.apache.fop.apps.CommandLine with the

            source XML file name, XSL file name and PDF file name as arguments. You will 
  -         need to include FOP, SAX, your SAX Parser and XT in your classpath and so you
might 
  -         invoke 
  +         need to include XT in your classpath and so you might invoke 
         </p>
  -      <p><code>java -cp fop_bin_0_12_0.jar;xt.jar;xp.jar;xerces.jar</code></p>
  -      <p><code>org.apache.fop.apps.CommandLine xml-file xsl-file pdf-file</code></p>
  -      <p>Again, if your SAX Parser is other than XP, you will need to set the property
  +      <p><code>java -cp fop_bin_0_12_1.jar;xt.jar;xerces.jar</code></p>
  +      <p><code>org.apache.fop.apps.XTCommandLine xml-file xsl-file pdf-file</code></p>
  +      <p>Again, if your SAX Parser is other than Xerces, you will need to set the
property
            org.xml.sax.parser to the SAX Parser class to use.
         </p>
       </s3>
  @@ -66,7 +65,7 @@
            transformation without using any pdf viewer by invoking FOP with the viewer 
            application. You will need to include FOP and your XML Parser in your classpath

         </p>
  -      <p><code>java -cp fop_bin_0_12_0.jar;xp.jar;xerces.jar</code></p>
  +      <p><code>java -cp fop_bin_0_12_1.jar;xerces.jar</code></p>
         <p><code>org.apache.fop.apps.AWTCommandLine fo-file </code></p>
         <p>The viewer uses the swing classes.</p> 
         <p>Note: If you are using java 2 or later (i.e. jdk 1.2. or later) you can
put all 
  @@ -104,7 +103,3 @@
     </s2>
   </s1>
   
  -<!-- Examples 
  -<s1 title="Examples">
  -  <p></p>
  --->
  
  
  
  1.1                  xml-site/sources/fop/examples.xml
  
  Index: examples.xml
  ===================================================================
  <?xml version="1.0" standalone="no"?>
  <!DOCTYPE s1 SYSTEM "sbk:/style/dtd/document.dtd">
  
  <!-- Examples -->
  
  <s1 title="Examples">
    <s2 title="Warning">
      <p>The following files show some simple examples, how formatting object files
conforming to the xsl working
         draft could look like to work with FOP. Please be warned: At the moment FOP only
supports the 
         XSL Working Draft 21 April 1999 and the examples are also following this version.

      </p>
  
    </s2>
    <s2 title="Normal text">
      <ul>
        <li><jump href="examples/normal.fo">xsl-fo-file</jump></li>
        <li><jump href="examples/normal.pdf">pdf-file</jump></li>
      </ul>
    </s2>
    <s2 title="Simple table">
      <ul>
        <li><jump href="examples/table.fo">xsl-fo-file</jump></li>
        <li><jump href="examples/table.pdf">pdf-file</jump></li>
      </ul>
    </s2>
    <s2 title="Simple list">
      <ul>
        <li><jump href="examples/list.fo">xsl-fo-file</jump></li>
        <li><jump href="examples/list.pdf">pdf-file</jump></li>
      </ul>
    </s2>
    <s2 title="All examples">
      <ul>
        <li><jump href="examples/fop-examples.jar">jar file</jump></li>
      </ul>
      <p>You can unpack this jar file by using the java command line tool jar</p>
      <p>jar xf fop-examples.jar</p>
      <p>The jar file format is identical with the zip file format, so you can
         can also use your normal unzip tools instead of jar
      </p>
    </s2>
  
  </s1>
  
  
  
  

Mime
View raw message