From 1b703845a6f4919d1e09c5976d22df6c8f15ba39 Mon Sep 17 00:00:00 2001 From: Vincent Hennebert Date: Sun, 5 Aug 2007 15:22:15 +0000 Subject: [PATCH] Merge changes on the Trunk tab from revision 562881 git-svn-id: https://svn.apache.org/repos/asf/xmlgraphics/fop/branches/fop-0_94@562887 13f79535-47bb-0310-9956-ffa450edef68 --- src/documentation/content/xdocs/0.94/compiling.xml | 5 +++-- .../content/xdocs/0.94/configuration.xml | 2 +- src/documentation/content/xdocs/0.94/extensions.xml | 6 +----- src/documentation/content/xdocs/0.94/fonts.xml | 12 +++--------- src/documentation/content/xdocs/0.94/graphics.xml | 1 - src/documentation/content/xdocs/0.94/output.xml | 3 +++ .../content/xdocs/0.94/pdfencryption.xml | 4 ---- src/documentation/content/xdocs/0.94/running.xml | 7 +------ src/documentation/content/xdocs/0.94/upgrading.xml | 9 ++------- 9 files changed, 14 insertions(+), 35 deletions(-) diff --git a/src/documentation/content/xdocs/0.94/compiling.xml b/src/documentation/content/xdocs/0.94/compiling.xml index 76d7b214f..c6c17a3c0 100644 --- a/src/documentation/content/xdocs/0.94/compiling.xml +++ b/src/documentation/content/xdocs/0.94/compiling.xml @@ -59,7 +59,7 @@

The build script uses Apache Ant, a popular Java-based build tool, which usually requires that the environment variable JAVA_HOME point to - your local JDK root directory. This is true even if you use JDK 1.2 or above, which normally + your local JDK root directory. This is true even if you use JDK 1.3 or above, which normally does not need this setting.

@@ -103,7 +103,8 @@ needed, but may be helpful if you are having problems with the build process itself.
  • - javadocs: Generates javadocs. This creates the FOP API documentation. + javadocs: Creates the FOP API documentation. + A minimum JDK version of 1.4.2 is required for generating the javadocs.

    • To run the build:

    diff --git a/src/documentation/content/xdocs/0.94/configuration.xml b/src/documentation/content/xdocs/0.94/configuration.xml index f030b1740..8b9e7e288 100644 --- a/src/documentation/content/xdocs/0.94/configuration.xml +++ b/src/documentation/content/xdocs/0.94/configuration.xml @@ -311,7 +311,7 @@ offered by Java.

    - Additionally, there are certain settings that control who the renderer handles various elements. + Additionally, there are certain settings that control how the renderer handles various elements.

    quality diff --git a/src/documentation/content/xdocs/0.94/extensions.xml b/src/documentation/content/xdocs/0.94/extensions.xml index 0c22ca123..dd4a79535 100644 --- a/src/documentation/content/xdocs/0.94/extensions.xml +++ b/src/documentation/content/xdocs/0.94/extensions.xml @@ -34,7 +34,7 @@ to you. If you wish to add an extension of your own to FOP, please see the Developers' Extension Page.

    - All extensions required the correct use of an appropriate namespace in your input document. + All extensions require the correct use of an appropriate namespace in your input document.
    SVG

    @@ -52,10 +52,6 @@

    ]]> - - Currently, no extension elements are implemented in FOP Trunk which use the - FOP extension namespace. -
    PDF Bookmarks diff --git a/src/documentation/content/xdocs/0.94/fonts.xml b/src/documentation/content/xdocs/0.94/fonts.xml index e6424dff6..f6e00250c 100644 --- a/src/documentation/content/xdocs/0.94/fonts.xml +++ b/src/documentation/content/xdocs/0.94/fonts.xml @@ -273,7 +273,7 @@ It will display all of the font names and exit with an Exception.

    See FOP: Configuration for more information.
  • Either an "embed-url" or a "metrics-url" must be specified for font tag configurations.
    • -
  • The font "kerning" attribute is optional. Kerning is currently not used at all.
    • +
  • The font "kerning" attribute is optional.
  • If embedding is off, the output will position the text correctly (from the metrics file), but it will not be displayed or printed correctly unless the viewer has the applicable font available to their local system.
  • When setting the "embed-url" attribute for Type 1 fonts, be sure to specify the PFB (actual font data), not PFM (font metrics) file that you used to generate the XML font metrics file.
  • The fonts "directory" tag can be used to register fonts contained within a single or list of directory paths. The "recursive" attribute can be specified to recursively add fonts from all sub directories.
    • @@ -302,14 +302,8 @@ If you don't specify the embed-url attribute the font will not be embedded, but

    When FOP embeds a font, it adds a prefix to the fontname to ensure that the name will not match the fontname of an installed font. This is helpful with older versions of Acrobat Reader that preferred installed fonts over embedded fonts.

    When embedding PostScript fonts, the entire font is always embedded.

    -

    When embedding TrueType fonts (ttf) or TrueType Collections (ttc), a subset of the original font, containing only the glyphs used, is embedded in the output document. -Currently, this embedded font contains only the minimum data needed to be embedded in a pdf document, and does not contain any codepage information. -The PDF document contains indexes to the glyphs in the font instead of to encoded characters. -While the document will be displayed correctly, the net effect of this is that searching, indexing, and cut-and-paste will not work properly.

    -

    One workaround for this behavior is to use the "-enc ansi" option when generating metrics with TTFReader. -This will cause the whole font to be embedded in the pdf document. -Characters will be WinAnsi encoded (as specified in the PDF spec), so you lose the ability to use characters from other character sets. -See Table of TTF Encoding Options for more details.

    +

    When embedding TrueType fonts (ttf) or TrueType Collections (ttc), a subset of the + original font, containing only the glyphs used, is embedded in the output document.

    Explicitly embedding the base 14 fonts diff --git a/src/documentation/content/xdocs/0.94/graphics.xml b/src/documentation/content/xdocs/0.94/graphics.xml index fb0a393f3..164069733 100644 --- a/src/documentation/content/xdocs/0.94/graphics.xml +++ b/src/documentation/content/xdocs/0.94/graphics.xml @@ -155,7 +155,6 @@ Then, copy the file "JimiProClasses.zip" from the archive to {fop-install-dir}/l
    JAI (Java Advanced Imaging API) - JAI support is available for Release 0.20.5 and later. The comments in this section do not apply to releases earlier than 0.20.5.

    FOP has been compiled with JAI support, but JAI is not included in the FOP distribution. To use it, install JAI, then copy the jai_core.jar and the jai_codec.jar files to {fop-install-dir}/lib. diff --git a/src/documentation/content/xdocs/0.94/output.xml b/src/documentation/content/xdocs/0.94/output.xml index 96f7000a2..998a5e1ce 100644 --- a/src/documentation/content/xdocs/0.94/output.xml +++ b/src/documentation/content/xdocs/0.94/output.xml @@ -618,6 +618,9 @@ out = proc.getOutputStream();]]> possible. The RTF output follows Microsoft's RTF specifications and produces best results on Microsoft Word.

    + RTF output is currently unmaintained and lacks many features compared to other output + formats. Using other editable formats like Open Document Format, instead of producing XSL-FO + then RTF through FOP, might give better results.
    XML (Area Tree XML) diff --git a/src/documentation/content/xdocs/0.94/pdfencryption.xml b/src/documentation/content/xdocs/0.94/pdfencryption.xml index f68eae437..c8cdbb29c 100644 --- a/src/documentation/content/xdocs/0.94/pdfencryption.xml +++ b/src/documentation/content/xdocs/0.94/pdfencryption.xml @@ -29,10 +29,6 @@
    Overview - - PDF Encryption is available in Release 0.20.5 and later. The comments on this page do - not apply to releases earlier than 0.20.5. -

    FOP supports encryption of PDF output, thanks to Patrick C. Lankswert. This feature is commonly used to prevent diff --git a/src/documentation/content/xdocs/0.94/running.xml b/src/documentation/content/xdocs/0.94/running.xml index 74284d6d0..dc173d7a1 100644 --- a/src/documentation/content/xdocs/0.94/running.xml +++ b/src/documentation/content/xdocs/0.94/running.xml @@ -180,7 +180,7 @@ Fop [options] [-fo|-xml] infile [-xsl file] [-awt|-pdf|-mif|-rtf|-tiff|-png|-pcl Fop foo.fo -awt]]>

    PDF encryption is only available if FOP was compiled with encryption support - and if compatible encryption support is availabe at run time. + and if compatible encryption support is available at run time. Currently, only the JCE is supported. Check the Details.

    @@ -339,11 +339,6 @@ Fop [options] [-fo|-xml] infile [-xsl file] [-awt|-pdf|-mif|-rtf|-tiff|-png|-pcl This can be substantial if the page sequence contains lots of FO elements. -

    - One of FOP's stated design goals is to be able to process input of arbitrary size. - Addressing this goal is one of the prime motivations behind the - FOP Redesign. -

    Problems diff --git a/src/documentation/content/xdocs/0.94/upgrading.xml b/src/documentation/content/xdocs/0.94/upgrading.xml index f99cdc93a..6a0d05454 100644 --- a/src/documentation/content/xdocs/0.94/upgrading.xml +++ b/src/documentation/content/xdocs/0.94/upgrading.xml @@ -77,18 +77,13 @@
  • Extensions and Renderers written for version 0.20.5 will not work with the new code! The new FOP - extension for Barcode4J will be available in + extension for Barcode4J is available since January 2007.
  • - The PCL Renderer and the MIF Handler have not been resurrected, yet! They are currently non-functional + The SVG Renderer and the MIF Handler have not been resurrected, yet! They are currently non-functional and hope for someone to step up and reimplement them.
    • -
  • - By looking at the Compliance page you might get the impression - that the new code is much more advanced than version 0.20.5. That's true but there may still - be a few things that may not be handled as gracefully by the new code as by version 0.20.5. -
    • -- 2.39.5