You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-commits@xmlgraphics.apache.org by je...@apache.org on 2006/07/24 15:24:10 UTC
svn commit: r425045 -
/xmlgraphics/fop/trunk/src/documentation/content/xdocs/trunk/output.xml
Author: jeremias
Date: Mon Jul 24 06:24:10 2006
New Revision: 425045
URL: http://svn.apache.org/viewvc?rev=425045&view=rev
Log:
Promote AFP and PCL renderers from sandbox to main source tree.
Modified:
xmlgraphics/fop/trunk/src/documentation/content/xdocs/trunk/output.xml
Modified: xmlgraphics/fop/trunk/src/documentation/content/xdocs/trunk/output.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/src/documentation/content/xdocs/trunk/output.xml?rev=425045&r1=425044&r2=425045&view=diff
==============================================================================
--- xmlgraphics/fop/trunk/src/documentation/content/xdocs/trunk/output.xml (original)
+++ xmlgraphics/fop/trunk/src/documentation/content/xdocs/trunk/output.xml Mon Jul 24 06:24:10 2006
@@ -209,102 +209,6 @@
</ul>
</section>
</section>
-<section id="rtf">
- <title>RTF</title>
- <p>
- JFOR, an open source XSL-FO to RTF converter has been integrated into Apache FOP.
- This will create an RTF (rich text format) document that will
- attempt to contain as much information from the fo document as
- possible. The RTF output follows Microsoft's RTF specifications
- and produces best results on Microsoft Word.
- </p>
-</section>
-<section id="xml">
- <title>XML (Area Tree XML)</title>
- <p>
- This is primarily for testing and verification. The XML created is simply
- a representation of the internal area tree put into XML. We use that to verify
- the functionality of FOP's layout engine.
- </p>
- <p>
- The other use case of the Area Tree XML is as FOP's "intermediate format". More information
- on that can be found on the page dedicated to the <a href="intermediate.html">Intermediate Format</a>.
- </p>
-</section>
-<section id="awt">
- <title>Java2D/AWT</title>
- <p>
- The Java2DRenderer provides the basic functionality for all
- Java2D-based output formats (AWT viewer, direct print, PNG, TIFF).
- </p>
- <p>
- 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.
- </p>
-</section>
-<section id="print">
- <title>Print</title>
- <p>
- It is possible to directly print the document from the command line.
- This is done with the same code that renders to the Java2D/AWT renderer.
- </p>
-</section>
-<section id="bitmap">
- <title>Bitmap (TIFF/PNG)</title>
- <p>
- It is possible to directly create bitmap images from the individual
- pages generated by the layout engine.
- This is done with the same code that renders to the Java2D/AWT renderer.
- </p>
- <p>
- Currently, two output formats are supported: PNG and TIFF. TIFF produces
- one file with multiple pages, while PNG output produces one file per
- page. The quality of the bitmap depends on the target resolution setting
- on the FOUserAgent.
- </p>
-</section>
-<section id="txt">
- <title>TXT</title>
- <p>
- The text renderer produces plain ASCII text output
- that attempts to match the output of the PDFRenderer as closely as
- possible. This was originally developed to accommodate an archive system
- that could only accept plain text files, and is primarily useful for getting
- a quick-and-dirty view of the document text. The renderer is very limited,
- so do not be surprised if it gives unsatisfactory results.
- </p>
- <p>
- The Text renderer works with a fixed size page buffer. The size of this
- buffer is controlled with the textCPI and textLPI public variables.
- The textCPI is the effective horizontal characters per inch to use.
- The textLPI is the vertical lines per inch to use. From these values
- and the page width and height the size of the buffer is calculated.
- The formatting objects to be rendered are then mapped to this grid.
- Graphic elements (lines, borders, etc) are assigned a lower priority
- than text, so text will overwrite any graphic element representations.
- </p>
- <p>
- Because FOP lays the text onto a grid during layout, there are frequently
- extra or missing spaces between characters and lines, which is generally
- unsatisfactory.
- Users have reported that the optimal settings to avoid such spacing problems are:
- </p>
- <ul>
- <li>font-family="Courier"</li>
- <li>font-size="7.3pt"</li>
- <li>line-height="10.5pt"</li>
- </ul>
-</section>
-<section id="sandbox">
- <title>Output Formats in the Sandbox</title>
- <p>
- Due to the state of certain renderers we moved some of them to a "sandbox" area until
- they are ready for more serious use. The renderers and FOEventHandlers in the sandbox
- can be found under src/sandbox and are compiled into build/fop-sandbox.jar during the
- main build. The output formats in the sandbox are marked as such below.
- </p>
<section id="pcl">
<title>PCL</title>
<p>
@@ -673,6 +577,102 @@
</section>
</section>
</section>
+<section id="rtf">
+ <title>RTF</title>
+ <p>
+ JFOR, an open source XSL-FO to RTF converter has been integrated into Apache FOP.
+ This will create an RTF (rich text format) document that will
+ attempt to contain as much information from the fo document as
+ possible. The RTF output follows Microsoft's RTF specifications
+ and produces best results on Microsoft Word.
+ </p>
+</section>
+<section id="xml">
+ <title>XML (Area Tree XML)</title>
+ <p>
+ This is primarily for testing and verification. The XML created is simply
+ a representation of the internal area tree put into XML. We use that to verify
+ the functionality of FOP's layout engine.
+ </p>
+ <p>
+ The other use case of the Area Tree XML is as FOP's "intermediate format". More information
+ on that can be found on the page dedicated to the <a href="intermediate.html">Intermediate Format</a>.
+ </p>
+</section>
+<section id="awt">
+ <title>Java2D/AWT</title>
+ <p>
+ The Java2DRenderer provides the basic functionality for all
+ Java2D-based output formats (AWT viewer, direct print, PNG, TIFF).
+ </p>
+ <p>
+ 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.
+ </p>
+</section>
+<section id="print">
+ <title>Print</title>
+ <p>
+ It is possible to directly print the document from the command line.
+ This is done with the same code that renders to the Java2D/AWT renderer.
+ </p>
+</section>
+<section id="bitmap">
+ <title>Bitmap (TIFF/PNG)</title>
+ <p>
+ It is possible to directly create bitmap images from the individual
+ pages generated by the layout engine.
+ This is done with the same code that renders to the Java2D/AWT renderer.
+ </p>
+ <p>
+ Currently, two output formats are supported: PNG and TIFF. TIFF produces
+ one file with multiple pages, while PNG output produces one file per
+ page. The quality of the bitmap depends on the target resolution setting
+ on the FOUserAgent.
+ </p>
+</section>
+<section id="txt">
+ <title>TXT</title>
+ <p>
+ The text renderer produces plain ASCII text output
+ that attempts to match the output of the PDFRenderer as closely as
+ possible. This was originally developed to accommodate an archive system
+ that could only accept plain text files, and is primarily useful for getting
+ a quick-and-dirty view of the document text. The renderer is very limited,
+ so do not be surprised if it gives unsatisfactory results.
+ </p>
+ <p>
+ The Text renderer works with a fixed size page buffer. The size of this
+ buffer is controlled with the textCPI and textLPI public variables.
+ The textCPI is the effective horizontal characters per inch to use.
+ The textLPI is the vertical lines per inch to use. From these values
+ and the page width and height the size of the buffer is calculated.
+ The formatting objects to be rendered are then mapped to this grid.
+ Graphic elements (lines, borders, etc) are assigned a lower priority
+ than text, so text will overwrite any graphic element representations.
+ </p>
+ <p>
+ Because FOP lays the text onto a grid during layout, there are frequently
+ extra or missing spaces between characters and lines, which is generally
+ unsatisfactory.
+ Users have reported that the optimal settings to avoid such spacing problems are:
+ </p>
+ <ul>
+ <li>font-family="Courier"</li>
+ <li>font-size="7.3pt"</li>
+ <li>line-height="10.5pt"</li>
+ </ul>
+</section>
+<section id="sandbox">
+ <title>Output Formats in the Sandbox</title>
+ <p>
+ Due to the state of certain renderers we moved some of them to a "sandbox" area until
+ they are ready for more serious use. The renderers and FOEventHandlers in the sandbox
+ can be found under src/sandbox and are compiled into build/fop-sandbox.jar during the
+ main build. The output formats in the sandbox are marked as such below.
+ </p>
<section id="mif">
<title>MIF</title>
<warning>The MIF handler is in the sandbox and not yet functional in FOP Trunk!!! Please help us ressurrect this feature.</warning>
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-commits-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-commits-help@xmlgraphics.apache.org