From 77aa00905f20f2bbb7db771b4bba7e1e76740630 Mon Sep 17 00:00:00 2001 From: Jeremias Maerki Date: Tue, 15 Nov 2005 20:49:37 +0000 Subject: [PATCH] Updates on the output formats. git-svn-id: https://svn.apache.org/repos/asf/xmlgraphics/fop/trunk@344439 13f79535-47bb-0310-9956-ffa450edef68 --- .../content/xdocs/trunk/output.xml | 156 ++++++++++-------- 1 file changed, 83 insertions(+), 73 deletions(-) diff --git a/src/documentation/content/xdocs/trunk/output.xml b/src/documentation/content/xdocs/trunk/output.xml index ec5274ee4..500d31f3d 100644 --- a/src/documentation/content/xdocs/trunk/output.xml +++ b/src/documentation/content/xdocs/trunk/output.xml @@ -184,57 +184,6 @@ out = proc.getOutputStream();]]> - - -
PostScript

@@ -266,19 +215,6 @@ out = proc.getOutputStream();]]> and produces best results on Microsoft Word.

-
- 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. - The font information for the text is obtained from the JVM in the - same way as the AWT viewer, if the SVG is view where the fonts are - different, such as another platform, then the page may appear wrong. -

-
XML (Area Tree XML)

@@ -289,6 +225,7 @@ out = proc.getOutputStream();]]>

Java2D/AWT + The Java2D/AWT, Print and Bitmap renderers may not yet fully work as expected. There are some known bugs and missing features.

The AWT viewer shows a window with the pages displayed inside a Java graphic. It displays one page at a time. @@ -317,17 +254,8 @@ out = proc.getOutputStream();]]> FOUserAgent.

-
- MIF - The MIF handler is not yet functional in FOP Trunk!!! -

- This format is the Maker Interchange Format which is used by - Adobe Framemaker. -

-
TXT - The TXT renderer is not yet functional in FOP Trunk!!!

The text renderer produces plain ASCII text output that attempts to match the output of the PDFRenderer as closely as @@ -358,6 +286,88 @@ out = proc.getOutputStream();]]>

  • line-height="10.5pt"
  • +
    + Output Formats in the Sandbox +

    + 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. +

    +
    + PCL + The PCL Renderer is in the sandbox and not yet functional in FOP Trunk!!! Please help us ressurrect this feature. +

    + This format is for the Hewlett-Packard PCL printers. + It should produce output as close to identical as possible to the + printed output of the PDFRenderer within the limitations of the + renderer, and output device. +

    + + + +
    +
    + MIF + The MIF handler is in the sandbox and not yet functional in FOP Trunk!!! Please help us ressurrect this feature. +

    + This format is the Maker Interchange Format which is used by + Adobe Framemaker. +

    +
    +
    + SVG + The SVG renderer is in the sandbox and may not work as expected in FOP Trunk!!! Please help us improve this feature. +

    + 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. + The font information for the text is obtained from the JVM in the + same way as the AWT viewer, if the SVG is view where the fonts are + different, such as another platform, then the page may appear wrong. +

    +
    +
    -- 2.39.5