keiron      01/12/13 23:38:28

  Modified:    docs/xml-docs fop.xml
               docs/xml-docs/fop embedding.xml involved.xml readme.xml
  Added:       docs/xml-docs/fop output.xml
  Removed:     docs/xml-docs/fop architecture.xml properties.xml
  updated information, trying to make things a bit clearer
  Revision  Changes    Path
  1.11      +10 -9     xml-fop/docs/xml-docs/fop.xml
  Index: fop.xml
  RCS file: /home/cvs/xml-fop/docs/xml-docs/fop.xml,v
  retrieving revision 1.10
  retrieving revision 1.11
  diff -u -r1.10 -r1.11
  --- fop.xml   2001/11/01 11:33:52     1.10
  +++ fop.xml   2001/12/14 07:38:28     1.11
  @@ -3,26 +3,27 @@
   <book title="FOP XSL-FO documentation" copyright="1999-2001 The Apache Software 
     <external href="";  label="Home"/>
  -  <page id="index"          label="Readme"      source="fop/readme.xml"/>
  -  <page id="todo"           label="TODO"    source="fop/todo.xml"    />
  +  <page id="index"          label="About FOP"      source="fop/readme.xml"/>
     <page id="download"       label="Download"    source="fop/download.xml"    />
     <page id="running"        label="Running FOP"     source="fop/running.xml"    />
  +  <page id="embedding"      label="Embedding" source="fop/embedding.xml"    />
  +  <page id="output"      label="Ouput Formats" source="fop/output.xml"    />
     <page id="implemented"    label="Features" source="fop/implemented.xml"    />
  +  <page id="todo"           label="TODO"    source="fop/todo.xml"    />
     <page id="limitations"    label="Limitations" source="fop/limitations.xml"    />
     <page id="examples"       label="Examples" source="fop/examples.xml"    />
  -  <page id="config"         label="Configuration" source="fop/configuration.xml"    
  -  <page id="fonts"          label="Fonts" source="fop/fonts.xml"    />
  -  <page id="extensions"     label="Extensions" source="fop/extensions.xml"    />
  +  <separator/>
     <page id="svg"            label="SVG" source="fop/svg.xml"    />
  +  <page id="extensions"     label="Extensions" source="fop/extensions.xml"    />  
<page id="fonts"          label="Fonts" source="fop/fonts.xml"    />
  +  <page id="config"         label="Configuration" source="fop/configuration.xml"    
  +  <external href="design/index.html"      label="NEW DESIGN" />
  +  <page id="involved"       label="Getting involved" source="fop/involved.xml"    />
     <page id="compiling"      label="Compiling" source="fop/compiling.xml"    />
  -  <page id="embedding"      label="Embedding" source="fop/embedding.xml"    />
     <page id="testing"        label="Testing" source="fop/testing.xml"    />
  -  <page id="involved"       label="Getting involved" source="fop/involved.xml"    />
  -  <page id="architecture"   label="Architecture" source="fop/architecture.xml"/>
  +  <faqs id="faq"            label="FAQ" source="fop/faq.xml"/>
     <page id="bugs"           label="Bugs" source="fop/bugs.xml"    />
  -  <faqs id="faq"           label="FAQ" source="fop/faq.xml"/>
     <page id="resources"      label="Resources" source="fop/resources.xml"    />
     <page id="license"        label="License"     source="fop/license.xml"   />
  1.13      +4 -2      xml-fop/docs/xml-docs/fop/embedding.xml
  Index: embedding.xml
  RCS file: /home/cvs/xml-fop/docs/xml-docs/fop/embedding.xml,v
  retrieving revision 1.12
  retrieving revision 1.13
  diff -u -r1.12 -r1.13
  --- embedding.xml     2001/12/03 09:53:04     1.12
  +++ embedding.xml     2001/12/14 07:38:28     1.13
  @@ -57,8 +57,10 @@
        invocation of the method is either render(Document) or
        render(Parser, InputSource) respectively.
  -  <p>A third possibility may be used to build the FO Tree, namely
  -     calling getContentHandler() and firing the SAX events yourself.
  +  <p>
  +     <strong>Another possibility may be used to build the FO Tree. You can
  +     call getContentHandler() and fire the SAX events yourself.
  +     </strong>
     <p>Once the FO Tree is built, the format() and render() methods may be
        called in that order.
  1.9       +1 -1      xml-fop/docs/xml-docs/fop/involved.xml
  Index: involved.xml
  RCS file: /home/cvs/xml-fop/docs/xml-docs/fop/involved.xml,v
  retrieving revision 1.8
  retrieving revision 1.9
  diff -u -r1.8 -r1.9
  --- involved.xml      2001/12/13 08:06:41     1.8
  +++ involved.xml      2001/12/14 07:38:28     1.9
  @@ -26,7 +26,7 @@
        Fop source repository can be found at <jump 
        An introduction into cvs and the cvs manual can be found in the 
        <jump href="";>reference library</jump>.</p>
  -  <p>All changes to the code repository are annonced in a special discussion group. 
You can subscribe 
  +  <p>All changes to the code repository are sent to a special mailing list. After a 
cvs commit the diffs are automatically sent to this list. You can subscribe 
        to [EMAIL PROTECTED] by sending an email to <jump 
href="mailto:[EMAIL PROTECTED]";>
        [EMAIL PROTECTED]</jump>. If you want to contribute to the 
development of Fop you should subscribe, 
        because it is important that you follow changes being made. </p>
  1.16      +6 -2      xml-fop/docs/xml-docs/fop/readme.xml
  Index: readme.xml
  RCS file: /home/cvs/xml-fop/docs/xml-docs/fop/readme.xml,v
  retrieving revision 1.15
  retrieving revision 1.16
  diff -u -r1.15 -r1.16
  --- readme.xml        2001/12/13 08:06:41     1.15
  +++ readme.xml        2001/12/14 07:38:28     1.16
  @@ -18,8 +18,8 @@
       <p>FOP is the world's first print formatter driven by XSL formatting
          objects and the world's first output independent formatter. It is a
          Java application that reads a formatting object tree and then
  -       renders the resulting pages to a specified output. Output formats
  -       currently supported are PDF, PCL, SVG, XML (area tree representation),
  +       renders the resulting pages to a specified output. <jump 
href="output.html">Output formats</jump>
  +       currently supported are PDF, PCL, PS, SVG, XML (area tree representation),
          Print, AWT, MIF and TXT.
          The primary output target is PDF.
  @@ -43,6 +43,10 @@
          <jump href="";></jump>.
          Here you can find information about using and developing with FOP.
  +    <p>Users can subscribe to [EMAIL PROTECTED] by sending an email
  +        to <jump 
href="mailto:[EMAIL PROTECTED]";>[EMAIL PROTECTED]</jump>
  +        this is where user specific topics are discussed.
  +     </p>
     <s1 title="Formatting">
  1.1                  xml-fop/docs/xml-docs/fop/output.xml
  Index: output.xml
  <?xml version="1.0" standalone="no"?>
  <!-- Output Formats: Renderers -->
          <subtitle>Notes about Output Formats: Renderers</subtitle>
  <s1 title="Output Formats">
  FOP supports a number of different output formats. This is achieved by
  using different renderers that create the output.
  Here we will explain some information for uses to be able to understand
  what the renderers are doing and what difference there may be between
  different renderers.
  <s2 title="Common Information">
  Each renderer is given an area tree to render to its output format.
  The area tree is simply a representation of the pages and the placement
  of text and graphical objects on those pages.
  The renderer will be given each page as it is ready and an output stream
  to write the data out. The renderer is responsible for managing the
  output format and associated data and flow.
  Fonts and Layout - some formats (eg. PDF and AWT) rely on different
  font information. THe fonts for these outputs have different sizes
  for the same point size. This means that the layout can be quite
  different for the same fo document.
  DPI - This is an important issue when creating output for printing.
  The dpi is used to convert measurements into points. For example 1in
  = 2.54cm = 72 points. It is also used when determining the size of
  images and the rendering of certain graphics in the output. Currently
  FOP uses a value of 72dpi.
  You may want to send your output directly to a printer. The Print
  renderer uses the java api to print the document or you might be
  able to send the output stream directly to a printer. If your printer
  supports postscript you could send the postscript to the printer. If
  you have a printer that supports PCL you could stream the PCL document
  to your printer.
  <s2 title="PDF">
  PDF is the best supported output format. It is also the most accurate
  with text and layout. This creates a PDF document that is streamed out
  as each page is rendered. This means that the internal page index
  information is stored near the end of the document.
  The PDF version supported is 1.3 which is currently the most popular
  version for Acrobat Reader (4.0), PDF versions are forwards/backwards
  <s2 title="PCL">
  This format is for the Hewlett-Packard PCL printers.
  <s2 title="PS">
  The postscript format can be used to send to a printer or any other
  puspose you may have. It has good support for most text and
  layout. images and SVG are not fully supported due to some ps
  <s2 title="RTF">
  This is currently not integrated with FOP but it will soon.
  This will create an rtf (rich text format) document that will
  attempt to contatin as much information from the fo document as
  <s2 title="SVG">
  This format creates an SVG document that has links between the pages.
  This is primarily for slides and creating svg images of pages.
  Large documents will create SVG files that are far too large for
  and SVG viewer to handle. Since fo documents usually have text the
  SVG document will have a large number of text elements.
  <s2 title="XML">
  This is for testing and verification. The XML created is simply
  a representation of the internal area tree put into XML. It does
  not perform any other purpose.
  <s2 title="Print">
  It is possible to directly print the document from the command line.
  This is done with the same code that renders to the AWT renderer.
  <s2 title="AWT">
  The AWT viewer shows a window with the pages displayed inside a
  java graphic. It displays one page at a time.
  The fonts used for the formatting and viewing depend on the fonts
  available to your JRE.
  <s2 title="MIF">
  This format is the Maker Interchange Format which is used by
  Adobe Framemaker. This is currently not fully implemented.
  <s2 title="TXT">
  Text as you could imagine does not work very well. It is an output format
  that you should expect bad results. The main purpose of this is to get
  a quick and dirty view of the document and the text inside it.

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to