Return-Path: Delivered-To: apmail-xmlgraphics-commits-archive@www.apache.org Received: (qmail 12328 invoked from network); 16 Dec 2009 11:49:30 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 16 Dec 2009 11:49:30 -0000 Received: (qmail 43090 invoked by uid 500); 16 Dec 2009 11:49:30 -0000 Mailing-List: contact commits-help@xmlgraphics.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: general@xmlgraphics.apache.org Delivered-To: mailing list commits@xmlgraphics.apache.org Received: (qmail 43081 invoked by uid 500); 16 Dec 2009 11:49:30 -0000 Delivered-To: apmail-xmlgraphics-site-commits@xmlgraphics.apache.org Received: (qmail 43078 invoked by uid 99); 16 Dec 2009 11:49:30 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Dec 2009 11:49:30 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO eris.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Dec 2009 11:49:17 +0000 Received: by eris.apache.org (Postfix, from userid 65534) id AB3C22388AA7; Wed, 16 Dec 2009 11:48:26 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: svn commit: r891203 [8/9] - in /xmlgraphics/site/deploy/fop: ./ 0.94/ 0.95/ dev/ dev/design/ dev/fo/ dev/svg/ fo/ skin/ trunk/ Date: Wed, 16 Dec 2009 11:48:18 -0000 To: site-commits@xmlgraphics.apache.org From: vhennebert@apache.org X-Mailer: svnmailer-1.0.8 Message-Id: <20091216114826.AB3C22388AA7@eris.apache.org> X-Virus-Checked: Checked by ClamAV on apache.org Modified: xmlgraphics/site/deploy/fop/trunk/extensions.html URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/extensions.html?rev=891203&r1=891202&r2=891203&view=diff ============================================================================== --- xmlgraphics/site/deploy/fop/trunk/extensions.html (original) +++ xmlgraphics/site/deploy/fop/trunk/extensions.html Wed Dec 16 11:48:08 2009 @@ -165,6 +165,9 @@ +
@@ -285,7 +288,7 @@
All extensions require the correct use of an appropriate namespace in your input document.
- +

SVG

@@ -293,10 +296,10 @@

- +

FO Extensions

- +

Namespace

By convention, FO extensions in FOP use the "fox" namespace prefix. @@ -305,14 +308,14 @@

<fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format"
                xmlns:fox="http://xmlgraphics.apache.org/fop/extensions">
- +

PDF Bookmarks

In previous versions of Apache FOP there was a fox:outline element which was used to create outlines in PDF files. The redesigned code makes use of the new bookmark feature defined in the latest XSL 1.1 working draft.

- +

Anchors or Named Destinations

Use the fox:destination element to define "named destinations" inside a PDF document. These are useful as fragment identifiers, e.g. "http://server/document.pdf#anchor-name". @@ -331,10 +334,10 @@ "id" attributes will generate named-destinations, which will eliminate the need for fox:destination.

- +

Table Continuation Label

This extension element hasn't been reimplemented for the redesigned code, yet.

- +

fox:orphan-content-limit and fox:widow-content-limit

The two proprietary extension properties, fox:orphan-content-limit and @@ -348,7 +351,7 @@ the you'll have at least three lines (assuming line-height="1.2") together on a table or list-block.

- +

fox:external-document

Note
@@ -377,7 +380,7 @@

- +

Specification

The fox:external-document extension formatting object is used to specify @@ -447,7 +450,7 @@ For this, XInclude is recommended.

- +

Free-form Transformation for fo:block-container

For fo:block-container elements whose absolute-position set to @@ -472,14 +475,14 @@ supported for PDF, PS and Java2D-based renderers. - +

Color functions

XSL-FO supports specifying color using the rgb(), rgb-icc() and system-color() functions. Apache FOP provides additional color functions for special use cases. Please note that using these functions compromises the interoperability of an FO document.

- +

cmyk()

color cmyk(numeric, numeric, numeric, numeric) @@ -489,7 +492,7 @@ must be between 0.0 and 1.0. For output formats that don't support device-specific color space the CMYK value is converted to an sRGB value.

- +

#CMYK pseudo-profile

color rgb-icc(numeric, numeric, numeric, #CMYK, numeric, numeric, numeric, numeric) @@ -514,7 +517,7 @@ - +

Prepress Support

This section defines a number of extensions related to @@ -532,7 +535,7 @@ Those extensions have been implemented in the PDF and Java2D renderers only. - +

fox:scale

Value: <number>{1,2}

Initial: 1

@@ -542,7 +545,7 @@ is provided it is used for both the x and y scales. A scale factor smaller than 1 shrinks the page. A scale factor greater than 1 enlarges the page.

- +

fox:bleed

Value: <length>{1,4} @@ -564,7 +567,7 @@ This extension indirectly defines the BleedBox and is calculated by expanding the TrimBox by the bleed widths. The lengths must be non-negative.

- +

fox:crop-offset

Value: <length>{1,4} @@ -581,7 +584,7 @@ This extension indirectly defines the MediaBox and is calculated by expanding the TrimBox by the crop offsets. The lengths must be non-negative.

- +

fox:crop-box

Value: [trim-box | bleed-box | media-box] Modified: xmlgraphics/site/deploy/fop/trunk/extensions.pdf URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/extensions.pdf?rev=891203&r1=891202&r2=891203&view=diff ============================================================================== Files xmlgraphics/site/deploy/fop/trunk/extensions.pdf (original) and xmlgraphics/site/deploy/fop/trunk/extensions.pdf Wed Dec 16 11:48:08 2009 differ Modified: xmlgraphics/site/deploy/fop/trunk/extensions.xml URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/extensions.xml?rev=891203&r1=891202&r2=891203&view=diff ============================================================================== --- xmlgraphics/site/deploy/fop/trunk/extensions.xml (original) +++ xmlgraphics/site/deploy/fop/trunk/extensions.xml Wed Dec 16 11:48:08 2009 @@ -14,7 +14,7 @@ See the License for the specific language governing permissions and limitations under the License. --> - +

Standard FOP Extensions $Revision: 815938 $ @@ -333,4 +333,4 @@ - + \ No newline at end of file Modified: xmlgraphics/site/deploy/fop/trunk/fonts.html URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/fonts.html?rev=891203&r1=891202&r2=891203&view=diff ============================================================================== --- xmlgraphics/site/deploy/fop/trunk/fonts.html (original) +++ xmlgraphics/site/deploy/fop/trunk/fonts.html Wed Dec 16 11:48:08 2009 @@ -165,6 +165,9 @@ +
@@ -258,7 +261,7 @@ - +

Summary

The following table summarizes the font capabilities of the various FOP renderers:

@@ -381,7 +384,7 @@
- +

Base-14 Fonts

@@ -451,7 +454,7 @@

- +

Missing Fonts

@@ -462,7 +465,7 @@

- +

Missing Glyphs

@@ -478,7 +481,7 @@

- +

Java2D/AWT/Operating System Fonts

@@ -495,7 +498,7 @@

- +

Custom Fonts

@@ -532,7 +535,7 @@

- +

Basic font configuration

@@ -568,7 +571,7 @@

- +

Advanced font configuration

@@ -576,7 +579,7 @@ additional instructions in case the basic font configuration doesn't lead to the desired results.

- +

Type 1 Font Metrics

FOP includes PFMReader, which reads the PFM file that normally comes with a Type 1 font, and generates an appropriate font metrics file for it. To use it, run the class org.apache.fop.fonts.apps.PFMReader:

@@ -610,7 +613,7 @@ The PFMReader tool does not yet interpret PFB or AFM files, so if you want to be correct, you may have to adjust the values in the XML file manually. The constructed values however appear to have no visible influence.
- +

TrueType Font Metrics

FOP includes TTFReader, which reads the TTF file and generates an appropriate font metrics file for it. Use it in a similar manner to PFMReader. @@ -677,7 +680,7 @@ the so-called Unicode "cmap" table. TTFReader can currently not deal with font like this. - +

TrueType Collections

TrueType collections (.ttc files) contain more than one font. To create metrics files for these fonts, you must specify which font in the collection should be generated, by using the "-ttcname" option with the TTFReader.

@@ -695,7 +698,7 @@
<font embed-url="gulim.ttc" sub-font="GulimChe">
   <font-triplet name="GulimChe" style="normal" weight="normal"/>
 </font>
- +

Register Fonts with FOP

You must tell FOP how to find and use the font metrics files by registering them in the FOP Configuration. Add entries for your custom fonts, regardless of font type, to the configuration file in a manner similar to the following:

@@ -766,7 +769,7 @@
           
         
 
-
+
 

Auto-Detect and auto-embed feature

When the "auto-detect" flag is set in the configuration, FOP will automatically search for fonts in the default paths for your operating system.

FOP will also auto-detect fonts which are available in the classpath, if they are described as "application/x-font" in the MANIFEST.MF file. For example, if your .jar file contains font/myfont.ttf:

@@ -775,7 +778,7 @@ Name: font/myfont.ttf Content-Type: application/x-font

This feature allows you to create JAR files containing fonts. The JAR files can be added to fop by providem them in the classpath, e.g. copying them into the lib/ directory.

- +

Embedding

By default, all fonts are embedded if an output format supports font embedding. In some @@ -819,6 +822,13 @@ referenced. If you want to reference all fonts, just specify font-family=".*".

+ The referenced-fonts element can be placed either inside the general + fonts element (right under the root) or in the fonts element + under the renderer configuration. In the first case, matches apply to all renderers. + In the second case, matches only apply to the renderer where the element was specified. + Both cases can be used at the same time. +

+

Various notes related to embedded fonts:

    @@ -838,7 +848,7 @@ complete font is embedded.
- +

Substitution

When a <substitutions/> section is defined in the configuration, FOP will re-map any font-family references found in your FO input to a given substitution font.

    @@ -866,7 +876,7 @@ </fop> - +

    Font Selection Strategies

    @@ -886,7 +896,7 @@

    Character-by-Character is NOT yet supported!

    - +

    Font List Command-Line Tool

    @@ -900,7 +910,7 @@ by Jeremias Märki, Tore Engvig, Adrian Cumiskey, Max Berger

    - version 757172 + version 821058
    - +
    Apache FOP: Fonts - $Revision: 757172 $ + $Revision: 821058 $ @@ -465,6 +465,13 @@ referenced. If you want to reference all fonts, just specify font-family=".*".

    + The referenced-fonts element can be placed either inside the general + fonts element (right under the root) or in the fonts element + under the renderer configuration. In the first case, matches apply to all renderers. + In the second case, matches only apply to the renderer where the element was specified. + Both cases can be used at the same time. +

    +

    Various notes related to embedded fonts:

      @@ -551,4 +558,4 @@

      - + \ No newline at end of file Modified: xmlgraphics/site/deploy/fop/trunk/graphics.html URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/graphics.html?rev=891203&r1=891202&r2=891203&view=diff ============================================================================== --- xmlgraphics/site/deploy/fop/trunk/graphics.html (original) +++ xmlgraphics/site/deploy/fop/trunk/graphics.html Wed Dec 16 11:48:08 2009 @@ -165,6 +165,9 @@ +
      @@ -294,7 +297,7 @@ - +

      Introduction

      @@ -329,7 +332,7 @@

      - +

      Overview of Graphics Support

      @@ -475,7 +478,7 @@ the image manipulation functionality.

      - +

      Map of supported image formats by output format

      Not all image formats are supported for all output formats! For example, while you can @@ -622,10 +625,10 @@

    - +

    Graphics Packages

    - +

    XML Graphics Commons Native

    @@ -633,14 +636,14 @@ of graphic file formats natively as basic functionality: all bitmap formats for which there are Image I/O codecs available (JPEG, PNG, GIF, TIFF, etc.), EPS and EMF.

    - +

    FOP Native

    FOP has no native image plug-ins for the image loading framework of its own but currently hosts the Batik-dependent SVG and WMF plug-ins until they can be moved to Apache Batik.

    - +

    Apache Batik

    @@ -684,7 +687,7 @@

- +

Image I/O

The image loading framework in XML Graphics Commons @@ -697,22 +700,22 @@

- +

Details on image formats

- +

BMP

BMP images are supported through an Image I/O codec. There may be limitations of the codec which are outside the control of Apache FOP.

- +

EMF

Windows Enhanced Metafiles (EMF) are only supported in RTF output where they are embedded without decoding.

- +

EPS

Apache FOP allows to use EPS files when generating PostScript output only.

@@ -720,13 +723,13 @@ FOP lacks a PostScript interpreter. Furthermore, FOP is currently not able to parse the preview bitmaps sometimes contained in EPS files.

- +

GIF

GIF images are supported through an Image I/O codec. Transparency is supported but not guaranteed to work with every output format.

- +

JPEG

FOP native support (i.e. the handling of undecoded images) of JPEG does not include all @@ -740,15 +743,15 @@ in some Image I/O codecs concerning images in the CMYK color space. Work-arounds are in place but may not always work as expected.

- +

PNG

PNG images are supported through an Image I/O codec. Transparency is supported but not guaranteed to work with every output format.

- +

SVG

- +

Introduction

FOP uses Apache Batik for SVG support. This format can be handled as an fo:instream-foreign-object or in a separate @@ -762,7 +765,7 @@ on the Batik site.

- +

Placing SVG Graphics into PDF

The SVG is rendered into PDF by using PDF commands to draw and fill @@ -782,7 +785,7 @@ contain effects or graphics with transparent areas may not be displayed correctly.

- +

Placing SVG Text into PDF and PostScript

If possible, Batik will use normal PDF or PostScript text when inserting text. It does this by checking if the text can be drawn normally and the font is @@ -813,7 +816,7 @@ This setting will not affect the printing of your document, which should be OK in any case, but will only affect the quality of the screen display.

- +

Font selection notes

Apache Batik uses the AWT/Java2D subsystem as font source while FOP has its own font @@ -834,7 +837,7 @@ if a particular font could not be found and had to be substituted, or if a particular glyph is missing in a font.

- +

Scaling

Currently, SVG images are rendered with the dimensions specified in the SVG @@ -849,7 +852,7 @@ size of a pixel. The use of pixels to specify sizes is discouraged as they may be interpreted differently in different environments.

- +

Known Problems

    @@ -875,7 +878,7 @@
- +

TIFF

FOP can embed TIFF images without decompression into PDF, PostScript and AFP if they @@ -885,7 +888,7 @@

There may be some limitation concerning images in the CMYK color space.

- +

WMF

Windows Metafiles (WMF) are supported through classes in @@ -894,7 +897,7 @@

- +

Graphics Resolution

@@ -919,7 +922,7 @@

- +

Page selection for multi-page formats

@@ -930,7 +933,7 @@

- +

Image caching

Modified: xmlgraphics/site/deploy/fop/trunk/graphics.pdf URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/graphics.pdf?rev=891203&r1=891202&r2=891203&view=diff ============================================================================== Files xmlgraphics/site/deploy/fop/trunk/graphics.pdf (original) and xmlgraphics/site/deploy/fop/trunk/graphics.pdf Wed Dec 16 11:48:08 2009 differ Modified: xmlgraphics/site/deploy/fop/trunk/graphics.xml URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/graphics.xml?rev=891203&r1=891202&r2=891203&view=diff ============================================================================== --- xmlgraphics/site/deploy/fop/trunk/graphics.xml (original) +++ xmlgraphics/site/deploy/fop/trunk/graphics.xml Wed Dec 16 11:48:08 2009 @@ -14,7 +14,7 @@ See the License for the specific language governing permissions and limitations under the License. --> - +

Apache FOP: Graphics Formats $Revision: 732299 $ @@ -588,4 +588,4 @@

- + \ No newline at end of file Modified: xmlgraphics/site/deploy/fop/trunk/hyphenation.html URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/hyphenation.html?rev=891203&r1=891202&r2=891203&view=diff ============================================================================== --- xmlgraphics/site/deploy/fop/trunk/hyphenation.html (original) +++ xmlgraphics/site/deploy/fop/trunk/hyphenation.html Wed Dec 16 11:48:08 2009 @@ -165,6 +165,9 @@ +
@@ -225,10 +228,10 @@ - +

Hyphenation Support

- +

Introduction

FOP uses Liang's hyphenation algorithm, well known from TeX. It needs language specific pattern and other data for operation.

@@ -244,7 +247,7 @@ Please inquire on the FOP User mailing list.
- +

License Issues

Many of the hyphenation files distributed with TeX and its offspring are licenced under the LaTeX @@ -263,12 +266,12 @@

- +

Sources of Custom Hyphenation Pattern Files

The most important source of hyphenation pattern files is the CTAN TeX Archive.

- +

Installing Custom Hyphenation Patterns

To install a custom hyphenation pattern for use with FOP:

    @@ -354,7 +357,7 @@ - +

    Hyphenation Patterns

    If you would like to build your own hyphenation pattern files, or modify Modified: xmlgraphics/site/deploy/fop/trunk/hyphenation.pdf URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/hyphenation.pdf?rev=891203&r1=891202&r2=891203&view=diff ============================================================================== Files xmlgraphics/site/deploy/fop/trunk/hyphenation.pdf (original) and xmlgraphics/site/deploy/fop/trunk/hyphenation.pdf Wed Dec 16 11:48:08 2009 differ Modified: xmlgraphics/site/deploy/fop/trunk/hyphenation.xml URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/hyphenation.xml?rev=891203&r1=891202&r2=891203&view=diff ============================================================================== --- xmlgraphics/site/deploy/fop/trunk/hyphenation.xml (original) +++ xmlgraphics/site/deploy/fop/trunk/hyphenation.xml Wed Dec 16 11:48:08 2009 @@ -14,7 +14,7 @@ See the License for the specific language governing permissions and limitations under the License. --> - +

    Apache FOP: Hyphenation $Revision: 627324 $ @@ -231,4 +231,4 @@ hyphenation.

    - + \ No newline at end of file Modified: xmlgraphics/site/deploy/fop/trunk/index.html URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/index.html?rev=891203&r1=891202&r2=891203&view=diff ============================================================================== --- xmlgraphics/site/deploy/fop/trunk/index.html (original) +++ xmlgraphics/site/deploy/fop/trunk/index.html Wed Dec 16 11:48:08 2009 @@ -165,6 +165,9 @@ +
    @@ -214,7 +217,7 @@
    - +

    Introduction

    @@ -232,7 +235,7 @@

    - +

    Upgrading from an earlier version

    Modified: xmlgraphics/site/deploy/fop/trunk/index.pdf URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/index.pdf?rev=891203&r1=891202&r2=891203&view=diff ============================================================================== Files xmlgraphics/site/deploy/fop/trunk/index.pdf (original) and xmlgraphics/site/deploy/fop/trunk/index.pdf Wed Dec 16 11:48:08 2009 differ Modified: xmlgraphics/site/deploy/fop/trunk/index.xml URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/index.xml?rev=891203&r1=891202&r2=891203&view=diff ============================================================================== --- xmlgraphics/site/deploy/fop/trunk/index.xml (original) +++ xmlgraphics/site/deploy/fop/trunk/index.xml Wed Dec 16 11:48:08 2009 @@ -14,7 +14,7 @@ See the License for the specific language governing permissions and limitations under the License. --> - +

    Apache FOP Trunk (Development code) $Revision: 627324 $ @@ -43,4 +43,4 @@

    - + \ No newline at end of file Modified: xmlgraphics/site/deploy/fop/trunk/intermediate.html URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/intermediate.html?rev=891203&r1=891202&r2=891203&view=diff ============================================================================== --- xmlgraphics/site/deploy/fop/trunk/intermediate.html (original) +++ xmlgraphics/site/deploy/fop/trunk/intermediate.html Wed Dec 16 11:48:08 2009 @@ -165,6 +165,9 @@ +
    @@ -258,7 +261,7 @@ - +

    Introduction

    @@ -285,14 +288,14 @@

    - +

    Which Intermediate Format to choose?

    Both formats have their use cases, so the choice you will make will depend on your particular situation. Here is a list of strengths and use cases for both formats:

    - +

    Area Tree XML (AT XML)

      @@ -303,7 +306,7 @@
    • Used in FOP's layout engine test suite for regression testing.
    - +

    Intermediate Format (IF)

      @@ -327,14 +330,14 @@

    - +

    Architectural Overview

    Diagram with an architectural overview over the intermediate formats
    - +

    Usage of the Area Tree XML format (AT XML)

    @@ -407,7 +410,7 @@ by using the "-atin" parameter for specifying the area tree XML as input file. You can also specify a "mimic renderer" by inserting a MIME type between "-at" and the output file.

    - +

    Concatenating Documents

    This initial example is obviously not very useful. It would be faster to create the PDF file @@ -416,7 +419,7 @@ same AreaTreeModel instance which essentially concatenates all the input document to one single output document.

    - +

    Modifying Documents

    One of the most important use cases for this format is obviously modifying the area @@ -433,7 +436,7 @@ the modified file may not render correctly.

    - +

    Advanced Use

    The generation of the area tree format as well as it parsing process has been designed to allow @@ -445,7 +448,7 @@

    - +

    Usage of the Intermediate Format (IF)

    @@ -535,7 +538,7 @@ IFParser.parse() is used, but you can also just get a SAX ContentHandler by using the IFParser.getContentHandler() method.

    - +

    Concatenating Documents

    This initial example is obviously not very useful. It would be faster to create the PDF file @@ -547,7 +550,7 @@ IFDocumentHandler interface. You could also do this in XSLT or using SAX on the XML level. Whatever suits your process best.

    - +

    Modifying Documents

    One of the most important use cases for this format is obviously modifying the @@ -564,7 +567,7 @@ arbitrary transformations on the IF's "viewport" and "g" elements. Possible are only rotations in 90 degree steps and translations.

    - +

    Advanced Use

    The generation of the intermediate format as well as it parsing process has been Modified: xmlgraphics/site/deploy/fop/trunk/intermediate.pdf URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/intermediate.pdf?rev=891203&r1=891202&r2=891203&view=diff ============================================================================== Files xmlgraphics/site/deploy/fop/trunk/intermediate.pdf (original) and xmlgraphics/site/deploy/fop/trunk/intermediate.pdf Wed Dec 16 11:48:08 2009 differ Modified: xmlgraphics/site/deploy/fop/trunk/intermediate.xml URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/intermediate.xml?rev=891203&r1=891202&r2=891203&view=diff ============================================================================== --- xmlgraphics/site/deploy/fop/trunk/intermediate.xml (original) +++ xmlgraphics/site/deploy/fop/trunk/intermediate.xml Wed Dec 16 11:48:08 2009 @@ -14,7 +14,7 @@ See the License for the specific language governing permissions and limitations under the License. --> - +

    Intermediate Format $Revision: 746664 $ @@ -324,4 +324,4 @@ - + \ No newline at end of file Modified: xmlgraphics/site/deploy/fop/trunk/metadata.html URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/metadata.html?rev=891203&r1=891202&r2=891203&view=diff ============================================================================== --- xmlgraphics/site/deploy/fop/trunk/metadata.html (original) +++ xmlgraphics/site/deploy/fop/trunk/metadata.html Wed Dec 16 11:48:08 2009 @@ -165,6 +165,9 @@ +
    @@ -227,7 +230,7 @@ - +

    Overview

    @@ -245,7 +248,7 @@

    - +

    Embedding XMP in an XSL-FO document

    @@ -261,7 +264,7 @@ x:xmpmeta and rdf:RDF elements are recognized as the top-level element introducing an XMP fragment (as per the XMP specification).

    - +

    Example

    [..]
     </fo:layout-master-set>
    @@ -295,7 +298,7 @@
     
    - +

    Implementation in Apache FOP

    @@ -438,7 +441,7 @@ this was changed to map to dc:description["x-default"].

    - +

    Namespaces

    Metadata is made of property sets where each property set uses a different namespace URI. @@ -493,7 +496,7 @@

    - +

    Links

      Modified: xmlgraphics/site/deploy/fop/trunk/metadata.pdf URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/metadata.pdf?rev=891203&r1=891202&r2=891203&view=diff ============================================================================== Binary files - no diff available. Modified: xmlgraphics/site/deploy/fop/trunk/metadata.xml URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/metadata.xml?rev=891203&r1=891202&r2=891203&view=diff ============================================================================== --- xmlgraphics/site/deploy/fop/trunk/metadata.xml (original) +++ xmlgraphics/site/deploy/fop/trunk/metadata.xml Wed Dec 16 11:48:08 2009 @@ -14,7 +14,7 @@ See the License for the specific language governing permissions and limitations under the License. --> - +
      Metadata
      @@ -237,4 +237,4 @@
    - + \ No newline at end of file Modified: xmlgraphics/site/deploy/fop/trunk/output.html URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/output.html?rev=891203&r1=891202&r2=891203&view=diff ============================================================================== --- xmlgraphics/site/deploy/fop/trunk/output.html (original) +++ xmlgraphics/site/deploy/fop/trunk/output.html Wed Dec 16 11:48:08 2009 @@ -165,6 +165,9 @@ +
    @@ -392,10 +395,10 @@ attention than others.

    - +

    General Information

    - +

    Fonts

    Most FOP renderers use a FOP-specific system for font registration. @@ -452,7 +455,7 @@

- +

Output to a Printer or Other Device

The most obvious way to print your document is to use the FOP @@ -476,7 +479,7 @@

- +

PDF

@@ -491,7 +494,7 @@ Note that FOP does not currently support "tagged PDF" or PDF/A-1a. Support for PDF/A-1b and PDF/X has recently been added, however.

- +

Fonts

PDF has a set of fonts that are always available to all PDF viewers; @@ -505,7 +508,7 @@ guaranteed to be available in all PDF viewer applications."

- +

Post-processing

FOP does not currently support several desirable PDF features: watermarks and signatures. @@ -575,7 +578,7 @@ Check the iText tutorial and documentation for setting access flags, password, encryption strength and other parameters.

- +

Watermarks

In addition to the PDF Post-processing options, consider the following workarounds: @@ -599,7 +602,7 @@

- +

PostScript

@@ -612,7 +615,7 @@ filter (the latter is used for 1:1 embedding of JPEG images), everything else is Level 2.

- +

Configuration

The PostScript renderer configuration currently allows the following settings: @@ -655,7 +658,7 @@ the particular postscript implementation issuing unwanted postscript subsystem initgraphics/erasepage calls on each setpagedevice call.

- +

Limitations

    @@ -670,7 +673,7 @@
- +

PCL

@@ -688,7 +691,7 @@ painting operations. Certain painting operations are done off-screen and rendered to PCL as bitmaps because of limitations in PCL 5.

- +

References

    @@ -701,7 +704,7 @@
- +

Limitations

    @@ -749,7 +752,7 @@
- +

Configuration

The PCL renderer configuration currently allows the following settings: @@ -785,7 +788,7 @@ should be enough for most use cases. Note that this setting directly affects the size of the output file and the print quality.

- +

Extensions

The PCL Renderer supports some PCL specific extensions which can be embedded into the input FO document. To use the extensions the appropriate namespace must @@ -794,7 +797,7 @@ <fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format" xmlns:pcl="http://xmlgraphics.apache.org/fop/extensions/pcl"> - +

Page Source (Tray selection)

The page-source extension attribute on fo:simple-page-master allows to @@ -819,7 +822,7 @@ "7" is "auto-select". Consult the technical reference for your printer for all available values.

- +

Output Bin

The output-bin extension attribute on fo:simple-page-master allows to @@ -840,7 +843,7 @@ "2" is the lower (rear) output bin. Consult the technical reference for your printer for all available values.

- +

Page Duplex Mode

The duplex-mode extension attribute on fo:simple-page-master allows to @@ -866,7 +869,7 @@

- +

AFP

@@ -911,7 +914,7 @@ FOP creates exactly one Document per Printfile with an optional Resource Group at the beginning. FOP does not create document indices.

- +

References

    @@ -928,7 +931,7 @@
- +

Limitations

This list is most likely badly incomplete.

    @@ -943,7 +946,7 @@
- +

Deployment in older environments

There are still a big number of older (or limited) MO:DCA/IPDS environments in production @@ -955,9 +958,9 @@ bits per pixel is configured, FOP has to switch to at least FS11 which may not work everywhere.

- +

Configuration

- +

Fonts

The AFP Renderer requires special configuration particularly related to fonts. AFP Render configuration is done through the normal FOP configuration file. The MIME type @@ -1104,13 +1107,13 @@ referenced-fonts section of the configuration file. However, the default fonts shown above will not be embedded.

- +

Output Resolution

By default the AFP Renderer creates output with a resolution of 240 dpi. This can be overridden by the <renderer-resolution/> configuration element. Example:

       <renderer-resolution>240</renderer-resolution>
- +

Images

By default the AFP Renderer converts all images to 8 bit grey level. This can be overridden by the <images/> configuration element. Example:

@@ -1128,9 +1131,16 @@

When the native attribute is specified and set to "true", all image resources will be natively injected into the datastream using an object container rather than being converted into an IOCA FS45 image. - Support for native image formats (e.g. JPEG, GIF) is not always available on printer implementations + Support for native image formats (e.g. JPEG, TIFF, GIF) is not always available on printer implementations so by default this configuration option is set to "false".

- +

+ Setting cmyk="true" on the images element will enable CMYK + colors. This will only have an effect if the color mode is set to "color". Example: +

+
+      <images mode="color" cmyk="true"/>
+
+

Shading

By default, filled rectangles are painted using their given color using a PTOCA I-axis rule @@ -1143,7 +1153,7 @@

       <shading>dithered</shading>
 
- +

Resource Group File

By default the AFP Renderer will place all data resource objects such as images within the document of the main output datastream. An external resource group file where document resources @@ -1155,7 +1165,7 @@

Note
Be careful when using this option not to overwrite existing resource files from previous rendering runs.
- +

Resource Level Defaults

By default, bitmap image objects (or page segments derived from them) are put in the @@ -1174,7 +1184,7 @@ for the attributes are "inline" and "print-file". In the future, additional possibilities may be added.

- +

Extensions

The AFP Renderer supports some AFP specific extensions which can be embedded into the input fo document. To use the extensions the appropriate namespace must be declared in the fo:root element like this:

@@ -1182,20 +1192,21 @@ <fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format" xmlns:afp="http://xmlgraphics.apache.org/fop/extensions/afp"> - +

Page Overlay (IPO) Extension

The include-page-overlay extension element allows to define on a per simple-page-master basis a page overlay resource. Example:

       <fo:layout-master-set>
         <fo:simple-page-master master-name="simple">
-          <afp:include-page-overlay name="O1SAMP1 " />
+          <afp:include-page-overlay name="O1SAMP1 " x="20mm" y="30mm" />
           ...
         </fo:simple-page-master>
       </fo:layout-master-set>
 

The mandatory name attribute must refer to an 8 character (space padded) resource name that - must be known in the AFP processing environment.

- + must be known in the AFP processing environment. Optional x and y attributes can be specified + to place the Overlay at an offset from the top left of the page.

+

Page Segment (IPS) Extension

The include-page-segment extension element allows to define resource substitution for fo:external-graphics elements. Example:

@@ -1228,7 +1239,7 @@ segment in the generated file. Please also note that page segments cannot be scaled. They are always rendered in their intrinsic size.

- +

Tag Logical Element (TLE) Extension

The tag-logical-element extension element allows to injects TLEs into the AFP output stream. Example:

@@ -1252,7 +1263,7 @@
           Multiple tag-logical-element extension elements within a simple-page-master or
           page-sequence are allowed. The name and value attributes are mandatory.
         

- +

No Operation (NOP) Extension

The no-operation extension provides the ability to carry up to 32K of comments or any other type of unarchitected data into the AFP output stream. Example:

@@ -1269,7 +1280,7 @@ Multiple no-operation extension elements within a simple-page-master are allowed. The name attribute is mandatory.

- +

Invoke Medium Map (IMM) Extension

The invoke-medium-map extension allows to generate IMM fields (Invoke Medium Map) in the @@ -1291,7 +1302,7 @@ only reference an existing medium map by name. The medium map has to be constructed through different means and available on the target platform.

- +

Form Maps/Defs

Apache FOP supports embedding an external form map resource in the @@ -1322,9 +1333,9 @@ tool. - +

Foreign Attributes

- +

Resource

The resource foreign attributes provides the ability to name and control where data object resources (e.g. images/scalable vector graphics) will reside in the AFP output. @@ -1361,7 +1372,7 @@

- +

RTF

@@ -1415,7 +1426,7 @@

- +

XML (Area Tree XML)

@@ -1429,7 +1440,7 @@

- +

Java2D/AWT

@@ -1444,14 +1455,14 @@

- +

Print

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.

- +

Known issues

If you run into the problem that the printed output is incomplete on Windows: @@ -1462,7 +1473,7 @@

- +

Bitmap (TIFF/PNG)

@@ -1481,7 +1492,7 @@ The quality of the bitmap depends on the target resolution setting on the FOUserAgent and on further settings described below.

- +

Configuration

The TIFF and PNG renderer configuration currently allows the following settings: @@ -1542,7 +1553,7 @@ at the loss of some image quality. If this setting has an actual effect depends on the JVM's Java2D backend.

- +

TIFF-specific Configuration

In addition to the above values the TIFF renderer configuration allows some additional @@ -1608,7 +1619,7 @@ Deflate and JPEG compression for writing.

- +

Runtime Rendering Options

The IF-based bitmap output implementations support a rendering option with the key @@ -1620,7 +1631,7 @@ "target-bitmap-size", new Dimension(320, 200));

- +

TXT

@@ -1658,7 +1669,7 @@

- +

Output Formats in the Sandbox

@@ -1667,7 +1678,7 @@ 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.

- +

MIF

Warning
@@ -1677,7 +1688,7 @@ This format is the Maker Interchange Format which is used by Adobe Framemaker.

- +

SVG

Warning
@@ -1696,7 +1707,7 @@

- +

Wish list

@@ -1719,7 +1730,7 @@ by Keiron Liddle, Art Welch

- version 820939 + version 829347
- +
Apache FOP Output Formats - $Revision: 820939 $ + $Revision: 829347 $ @@ -699,8 +699,15 @@ ]]>

When the native attribute is specified and set to "true", all image resources will be natively injected into the datastream using an object container rather than being converted into an IOCA FS45 image. - Support for native image formats (e.g. JPEG, GIF) is not always available on printer implementations + Support for native image formats (e.g. JPEG, TIFF, GIF) is not always available on printer implementations so by default this configuration option is set to "false".

+

+ Setting cmyk="true" on the images element will enable CMYK + colors. This will only have an effect if the color mode is set to "color". Example: +

+ +]]>
Shading @@ -761,13 +768,14 @@ - + ... ]]>

The mandatory name attribute must refer to an 8 character (space padded) resource name that - must be known in the AFP processing environment.

+ must be known in the AFP processing environment. Optional x and y attributes can be specified + to place the Overlay at an offset from the top left of the page.

Page Segment (IPS) Extension @@ -1223,4 +1231,4 @@
- + \ No newline at end of file Modified: xmlgraphics/site/deploy/fop/trunk/pdfa.html URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/pdfa.html?rev=891203&r1=891202&r2=891203&view=diff ============================================================================== --- xmlgraphics/site/deploy/fop/trunk/pdfa.html (original) +++ xmlgraphics/site/deploy/fop/trunk/pdfa.html Wed Dec 16 11:48:08 2009 @@ -165,6 +165,9 @@ +
@@ -226,14 +229,14 @@ - +

Overview

PDF/A is a standard which turns PDF into an "electronic document file format for long-term preservation". PDF/A-1 is the first part of the standard and is documented in - ISO 19005-1:2005(E). + ISO 19005-1:2005(E). Work on PDF/A-2 is in progress at AIIM.

@@ -243,7 +246,7 @@

- +

Implementation Status

@@ -258,12 +261,13 @@

-PDF/A-1a is not implemented, yet. This is mostly because of the requirement - for tagged PDF which is not available in FOP, yet. +PDF/A-1a is based on PDF-A-1b and adds accessibility features + (such as Tagged PDF). This format is available within the limitation described on + the Accessibility page.

- +

Usage (command line)

@@ -271,9 +275,12 @@ as a parameter. If there is a violation of one of the validation rules for PDF/A, an error message is presented and the processing stops.

+

+ PDF/A-1a is enabled by specifying "-pdfprofile PDF/A-1a". +

- +

Usage (embedded)

@@ -289,9 +296,12 @@ If one of the validation rules of PDF/A is violated, an PDFConformanceException (descendant of RuntimeException) is thrown.

+

+ For PDF/A-1a, just use the string "PDF/A-1a" instead of "PDF/A-1b". +

- +

PDF/A in Action

@@ -337,18 +347,26 @@ +

+
Note
+
+ There are additional requirements if you want to enabled PDF/A-1a (Tagged PDF). This is + particularly the specification of the natural language and alternative descriptions for + images. Please refer to the Accessibility page for details. +
+
- +

PDF profile compatibility

- The PDF profiles "PDF/X-3:2003" and "PDF/A-1b" are compatible and can both be - activated at the same time. + The PDF profiles "PDF/X-3:2003" and "PDF/A-1b" (or "PDF/A-1a") are compatible and can + both be activated at the same time.

- +

Interoperability

@@ -390,7 +408,7 @@ by Jeremias Märki

- version 688653 + version 830293
- +
PDF/A (ISO 19005) - $Revision: 688653 $ + $Revision: 830293 $ @@ -50,8 +50,9 @@ lack of a full license to get a detailed error protocol.

- PDF/A-1a is not implemented, yet. This is mostly because of the requirement - for tagged PDF which is not available in FOP, yet. + PDF/A-1a is based on PDF-A-1b and adds accessibility features + (such as Tagged PDF). This format is available within the limitation described on + the Accessibility page.

@@ -61,6 +62,9 @@ as a parameter. If there is a violation of one of the validation rules for PDF/A, an error message is presented and the processing stops.

+

+ PDF/A-1a is enabled by specifying "-pdfprofile PDF/A-1a". +

Usage (embedded) @@ -77,6 +81,9 @@ If one of the validation rules of PDF/A is violated, an PDFConformanceException (descendant of RuntimeException) is thrown.

+

+ For PDF/A-1a, just use the string "PDF/A-1a" instead of "PDF/A-1b". +

PDF/A in Action @@ -115,12 +122,17 @@ embedded in clear text so non-PDF-aware applications can extract the XMP metadata. + + There are additional requirements if you want to enabled PDF/A-1a (Tagged PDF). This is + particularly the specification of the natural language and alternative descriptions for + images. Please refer to the Accessibility page for details. +
PDF profile compatibility

- The PDF profiles "PDF/X-3:2003" and "PDF/A-1b" are compatible and can both be - activated at the same time. + The PDF profiles "PDF/X-3:2003" and "PDF/A-1b" (or "PDF/A-1a") are compatible and can + both be activated at the same time.

@@ -150,4 +162,4 @@

- + \ No newline at end of file Modified: xmlgraphics/site/deploy/fop/trunk/pdfencryption.html URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/pdfencryption.html?rev=891203&r1=891202&r2=891203&view=diff ============================================================================== --- xmlgraphics/site/deploy/fop/trunk/pdfencryption.html (original) +++ xmlgraphics/site/deploy/fop/trunk/pdfencryption.html Wed Dec 16 11:48:08 2009 @@ -165,6 +165,9 @@ +
@@ -220,7 +223,7 @@ - +

Overview

@@ -240,7 +243,7 @@

- +

Usage (command line)

@@ -272,7 +275,7 @@

- +

Usage (embedded)

@@ -403,7 +406,7 @@

- +

Environment

@@ -432,7 +435,7 @@

- +

Installing a crypto provider

Modified: xmlgraphics/site/deploy/fop/trunk/pdfencryption.pdf URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/pdfencryption.pdf?rev=891203&r1=891202&r2=891203&view=diff ============================================================================== Files xmlgraphics/site/deploy/fop/trunk/pdfencryption.pdf (original) and xmlgraphics/site/deploy/fop/trunk/pdfencryption.pdf Wed Dec 16 11:48:08 2009 differ Modified: xmlgraphics/site/deploy/fop/trunk/pdfencryption.xml URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/pdfencryption.xml?rev=891203&r1=891202&r2=891203&view=diff ============================================================================== --- xmlgraphics/site/deploy/fop/trunk/pdfencryption.xml (original) +++ xmlgraphics/site/deploy/fop/trunk/pdfencryption.xml Wed Dec 16 11:48:08 2009 @@ -14,7 +14,7 @@ See the License for the specific language governing permissions and limitations under the License. --> - +

PDF encryption. $Revision: 638396 $ @@ -218,4 +218,4 @@

- + \ No newline at end of file Modified: xmlgraphics/site/deploy/fop/trunk/pdfx.html URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/pdfx.html?rev=891203&r1=891202&r2=891203&view=diff ============================================================================== --- xmlgraphics/site/deploy/fop/trunk/pdfx.html (original) +++ xmlgraphics/site/deploy/fop/trunk/pdfx.html Wed Dec 16 11:48:08 2009 @@ -165,6 +165,9 @@ +
@@ -223,7 +226,7 @@ - +

Overview

@@ -237,13 +240,13 @@ PDF/X is a standard which faciliates prepress digital data exchange using PDF. Currently, only PDF/X-3:2003 is implemented out of the many different flavours of PDF/X profiles. PDF/X-3:2003 is documented in - ISO 15930-6:2003(E). + ISO 15930-6:2003(E). More info on PDF/X can be found on the PDF/X info site.

- +

Implementation Status

@@ -271,7 +274,7 @@

- +

Usage (command line)

@@ -281,7 +284,7 @@

- +

Usage (embedded)

@@ -300,7 +303,7 @@

- +

PDF/X in Action

@@ -344,7 +347,7 @@

- +

PDF profile compatibility

Modified: xmlgraphics/site/deploy/fop/trunk/pdfx.pdf URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/pdfx.pdf?rev=891203&r1=891202&r2=891203&view=diff ============================================================================== Files xmlgraphics/site/deploy/fop/trunk/pdfx.pdf (original) and xmlgraphics/site/deploy/fop/trunk/pdfx.pdf Wed Dec 16 11:48:08 2009 differ Modified: xmlgraphics/site/deploy/fop/trunk/pdfx.xml URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/pdfx.xml?rev=891203&r1=891202&r2=891203&view=diff ============================================================================== --- xmlgraphics/site/deploy/fop/trunk/pdfx.xml (original) +++ xmlgraphics/site/deploy/fop/trunk/pdfx.xml Wed Dec 16 11:48:08 2009 @@ -13,7 +13,7 @@ See the License for the specific language governing permissions and limitations under the License. --> - +

PDF/X (ISO 15930) $Revision: 627324 $ @@ -130,4 +130,4 @@

- + \ No newline at end of file Modified: xmlgraphics/site/deploy/fop/trunk/running.html URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/running.html?rev=891203&r1=891202&r2=891203&view=diff ============================================================================== --- xmlgraphics/site/deploy/fop/trunk/running.html (original) +++ xmlgraphics/site/deploy/fop/trunk/running.html Wed Dec 16 11:48:08 2009 @@ -165,6 +165,9 @@ +
@@ -245,7 +248,7 @@ - +

System Requirements

The following software must be installed:

@@ -315,10 +318,10 @@
- +

Installation

- +

Instructions

Basic FOP installation consists of first unzipping the .gz file that is the @@ -327,7 +330,7 @@ documentation or Zip application software documentation for instructions specific to your site.

- +

Problems

Some Mac OSX users have experienced filename truncation problems using Stuffit to unzip @@ -337,10 +340,10 @@

- +

Starting FOP as a Standalone Application

- +

Using the fop script or batch file

The usual and recommended practice for starting FOP from the command line is to run the @@ -432,7 +435,7 @@ and if compatible encryption support is available at run time. Currently, only the JCE is supported. Check the Details.

- +

Writing your own script

FOP's entry point for your own scripts is the class org.apache.fop.cli.Main. The general pattern for the @@ -443,7 +446,7 @@ the standard scripts to make sure that you get your environment properly configured.

- +

Running with java's -jar option

As an alternative to the start scripts you can run java @@ -461,7 +464,7 @@

In both cases the arguments consist of the options and infile and outfile specifications as shown above for the standard scripts.

- +

FOP's dynamical classpath construction

If FOP is started without a proper classpath, it tries to add its dependencies dynamically. If the system property @@ -485,7 +488,7 @@ org.apache.fop.cli.Main.

- +

Using Xalan to Check XSL-FO Input

@@ -539,7 +542,7 @@

- +

Memory Usage

@@ -600,7 +603,7 @@

- +

Problems

If you have problems running FOP, please see the "How to get Help" page.

Modified: xmlgraphics/site/deploy/fop/trunk/running.pdf URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/running.pdf?rev=891203&r1=891202&r2=891203&view=diff ============================================================================== Files xmlgraphics/site/deploy/fop/trunk/running.pdf (original) and xmlgraphics/site/deploy/fop/trunk/running.pdf Wed Dec 16 11:48:08 2009 differ Modified: xmlgraphics/site/deploy/fop/trunk/running.xml URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/running.xml?rev=891203&r1=891202&r2=891203&view=diff ============================================================================== --- xmlgraphics/site/deploy/fop/trunk/running.xml (original) +++ xmlgraphics/site/deploy/fop/trunk/running.xml Wed Dec 16 11:48:08 2009 @@ -14,7 +14,7 @@ See the License for the specific language governing permissions and limitations under the License. --> - +
Running Apache FOP $Revision: 638396 $ @@ -343,4 +343,4 @@

If you have problems running FOP, please see the "How to get Help" page.

- + \ No newline at end of file --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscribe@xmlgraphics.apache.org For additional commands, e-mail: commits-help@xmlgraphics.apache.org