Return-Path:
By "extension", we mean any data that can be placed in the input XML document that
@@ -293,7 +295,7 @@ document.write("Last Published: " + docu
@@ -301,10 +303,10 @@ document.write("Last Published: " + docu
By convention, FO extensions in FOP use the "fox" namespace prefix.
@@ -313,14 +315,14 @@ document.write("Last Published: " + docu
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.
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".
@@ -339,10 +341,10 @@ PDF document. The fox:destination simply
"id" attributes will generate named-destinations, which will eliminate the need for
fox:destination. This extension element hasn't been reimplemented for the redesigned code, yet.
The two proprietary extension properties, fox:orphan-content-limit and
@@ -356,7 +358,7 @@ fox:destination.
the you'll have at least three lines (assuming line-height="1.2") together on a table
or list-block.
Standard FOP Extensions
+
SVG
FO Extensions
Namespace
<fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format"
xmlns:fox="http://xmlgraphics.apache.org/fop/extensions">
-
+
PDF Bookmarks
Anchors or Named Destinations
Table Continuation Label
fox:orphan-content-limit and fox:widow-content-limit
fox:external-document
The fox:external-document extension formatting object is used to specify @@ -455,7 +457,7 @@ fox:destination. For this, XInclude is recommended. - +
For fo:block-container elements whose absolute-position set to @@ -480,14 +482,14 @@ fox:destination. supported for PDF, PS and Java2D-based renderers. - +
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.
- +color cmyk(numeric, numeric, numeric, numeric) @@ -497,7 +499,7 @@ fox:destination. 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.
- +color rgb-icc(numeric, numeric, numeric, #CMYK, numeric, numeric, numeric, numeric) @@ -522,7 +524,7 @@ fox:destination. - +
This section defines a number of extensions related to @@ -540,7 +542,7 @@ fox:destination. Those extensions have been implemented in the PDF and Java2D renderers only. - +
Value: <number>{1,2}
Initial: 1
@@ -550,7 +552,7 @@ fox:destination. 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. - +Value: <length>{1,4} @@ -572,7 +574,7 @@ fox:destination. This extension indirectly defines the BleedBox and is calculated by expanding the TrimBox by the bleed widths. The lengths must be non-negative.
- +Value: <length>{1,4} @@ -589,7 +591,7 @@ fox:destination. This extension indirectly defines the MediaBox and is calculated by expanding the TrimBox by the crop offsets. The lengths must be non-negative.
- +
Value: [trim-box | bleed-box | media-box]
Modified: xmlgraphics/site/deploy/fop/1.0/extensions.pdf
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/1.0/extensions.pdf?rev=1032553&r1=1032552&r2=1032553&view=diff
==============================================================================
Files xmlgraphics/site/deploy/fop/1.0/extensions.pdf (original) and xmlgraphics/site/deploy/fop/1.0/extensions.pdf Mon Nov 8 11:59:27 2010 differ
Modified: xmlgraphics/site/deploy/fop/1.0/extensions.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/1.0/extensions.xml?rev=1032553&r1=1032552&r2=1032553&view=diff
==============================================================================
--- xmlgraphics/site/deploy/fop/1.0/extensions.xml (original)
+++ xmlgraphics/site/deploy/fop/1.0/extensions.xml Mon Nov 8 11:59:27 2010
@@ -14,7 +14,7 @@
See the License for the specific language governing permissions and
limitations under the License.
-->
-
The following table summarizes the font capabilities of the various FOP renderers:
@@ -389,7 +391,7 @@ document.write("Last Published: " + docu@@ -459,7 +461,7 @@ document.write("Last Published: " + docu
@@ -470,7 +472,7 @@ document.write("Last Published: " + docu
@@ -486,7 +488,7 @@ document.write("Last Published: " + docu
@@ -503,7 +505,7 @@ document.write("Last Published: " + docu
@@ -540,7 +542,7 @@ document.write("Last Published: " + docu
@@ -576,7 +578,7 @@ document.write("Last Published: " + docu
@@ -584,7 +586,7 @@ document.write("Last Published: " + docu additional instructions in case the basic font configuration doesn't lead to the desired results.
- +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:
@@ -618,7 +620,7 @@ document.write("Last Published: " + docu 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.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. @@ -685,7 +687,7 @@ document.write("Last Published: " + docu the so-called Unicode "cmap" table. TTFReader can currently not deal with font like this. - +
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.
@@ -703,7 +705,7 @@ document.write("Last Published: " + docu<font embed-url="gulim.ttc" sub-font="GulimChe"> <font-triplet name="GulimChe" style="normal" weight="normal"/> </font>- +
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:
@@ -774,7 +776,7 @@ document.write("Last Published: " + docu - +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:
@@ -783,7 +785,7 @@ document.write("Last Published: " + docu 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.
- +By default, all fonts are embedded if an output format supports font embedding. In some @@ -853,7 +855,7 @@ document.write("Last Published: " + docu complete font is embedded. - +
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.
@@ -901,7 +903,7 @@ document.write("Last Published: " + docu
Character-by-Character is NOT yet supported!
Modified: xmlgraphics/site/deploy/fop/1.0/fonts.pdf
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/1.0/fonts.pdf?rev=1032553&r1=1032552&r2=1032553&view=diff
==============================================================================
Files xmlgraphics/site/deploy/fop/1.0/fonts.pdf (original) and xmlgraphics/site/deploy/fop/1.0/fonts.pdf Mon Nov 8 11:59:27 2010 differ
Modified: xmlgraphics/site/deploy/fop/1.0/fonts.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/1.0/fonts.xml?rev=1032553&r1=1032552&r2=1032553&view=diff
==============================================================================
--- xmlgraphics/site/deploy/fop/1.0/fonts.xml (original)
+++ xmlgraphics/site/deploy/fop/1.0/fonts.xml Mon Nov 8 11:59:27 2010
@@ -14,7 +14,7 @@
See the License for the specific language governing permissions and
limitations under the License.
-->
-
@@ -333,7 +335,7 @@ document.write("Last Published: " + docu
@@ -479,7 +481,7 @@ document.write("Last Published: " + docu the image manipulation functionality.
Not all image formats are supported for all output formats! For example, while you can @@ -626,10 +628,10 @@ document.write("Last Published: " + docu
@@ -637,14 +639,14 @@ document.write("Last Published: " + docu 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 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.
- +@@ -688,7 +690,7 @@ document.write("Last Published: " + docu - +
The image loading framework in XML Graphics Commons @@ -701,22 +703,22 @@ document.write("Last Published: " + docu
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.
- +Windows Enhanced Metafiles (EMF) are only supported in RTF output where they are embedded without decoding.
- +Apache FOP allows to use EPS files when generating PostScript output only.
@@ -724,13 +726,13 @@ document.write("Last Published: " + docu FOP lacks a PostScript interpreter. Furthermore, FOP is currently not able to parse the preview bitmaps sometimes contained in EPS files.
- +GIF images are supported through an Image I/O codec. Transparency is supported but not guaranteed to work with every output format.
- +FOP native support (i.e. the handling of undecoded images) of JPEG does not include all @@ -744,15 +746,15 @@ document.write("Last Published: " + docu 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 images are supported through an Image I/O codec. Transparency is supported but not guaranteed to work with every output format.
- +FOP uses Apache Batik for SVG support. This format can be handled as an fo:instream-foreign-object or in a separate @@ -766,7 +768,7 @@ document.write("Last Published: " + docu on the Batik site.
The SVG is rendered into PDF by using PDF commands to draw and fill @@ -786,7 +788,7 @@ document.write("Last Published: " + docu contain effects or graphics with transparent areas may not be displayed correctly.
- +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 @@ -817,7 +819,7 @@ document.write("Last Published: " + docu 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.
- +Apache Batik uses the AWT/Java2D subsystem as font source while FOP has its own font @@ -838,7 +840,7 @@ document.write("Last Published: " + docu if a particular font could not be found and had to be substituted, or if a particular glyph is missing in a font.
- +Currently, SVG images are rendered with the dimensions specified in the SVG @@ -853,7 +855,7 @@ document.write("Last Published: " + docu size of a pixel. The use of pixels to specify sizes is discouraged as they may be interpreted differently in different environments.
- +FOP can embed TIFF images without decompression into PDF, PostScript and AFP if they @@ -889,7 +891,7 @@ document.write("Last Published: " + docu
There may be some limitation concerning images in the CMYK color space.
- +Windows Metafiles (WMF) are supported through classes in @@ -898,7 +900,7 @@ document.write("Last Published: " + docu
- +@@ -923,7 +925,7 @@ document.write("Last Published: " + docu
@@ -934,7 +936,7 @@ document.write("Last Published: " + docu
Modified: xmlgraphics/site/deploy/fop/1.0/graphics.pdf
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/1.0/graphics.pdf?rev=1032553&r1=1032552&r2=1032553&view=diff
==============================================================================
Files xmlgraphics/site/deploy/fop/1.0/graphics.pdf (original) and xmlgraphics/site/deploy/fop/1.0/graphics.pdf Mon Nov 8 11:59:27 2010 differ
Modified: xmlgraphics/site/deploy/fop/1.0/graphics.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/1.0/graphics.xml?rev=1032553&r1=1032552&r2=1032553&view=diff
==============================================================================
--- xmlgraphics/site/deploy/fop/1.0/graphics.xml (original)
+++ xmlgraphics/site/deploy/fop/1.0/graphics.xml Mon Nov 8 11:59:27 2010
@@ -14,7 +14,7 @@
See the License for the specific language governing permissions and
limitations under the License.
-->
-
FOP uses Liang's hyphenation algorithm, well known from TeX. It needs language specific pattern and other data for operation.
@@ -252,7 +254,7 @@ document.write("Last Published: " + docu Please inquire on the FOP User mailing list.Many of the hyphenation files distributed with TeX and its offspring are
licenced under the LaTeX
@@ -271,12 +273,12 @@ document.write("Last Published: " + docu
The most important source of hyphenation pattern files is the CTAN TeX Archive.
- +To install a custom hyphenation pattern for use with FOP:
If you would like to build your own hyphenation pattern files, or modify
Modified: xmlgraphics/site/deploy/fop/1.0/hyphenation.pdf
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/1.0/hyphenation.pdf?rev=1032553&r1=1032552&r2=1032553&view=diff
==============================================================================
Files xmlgraphics/site/deploy/fop/1.0/hyphenation.pdf (original) and xmlgraphics/site/deploy/fop/1.0/hyphenation.pdf Mon Nov 8 11:59:27 2010 differ
Modified: xmlgraphics/site/deploy/fop/1.0/hyphenation.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/1.0/hyphenation.xml?rev=1032553&r1=1032552&r2=1032553&view=diff
==============================================================================
--- xmlgraphics/site/deploy/fop/1.0/hyphenation.xml (original)
+++ xmlgraphics/site/deploy/fop/1.0/hyphenation.xml Mon Nov 8 11:59:27 2010
@@ -14,7 +14,7 @@
See the License for the specific language governing permissions and
limitations under the License.
-->
-
@@ -254,7 +256,7 @@ document.write("Last Published: " + docu
@@ -263,7 +265,7 @@ document.write("Last Published: " + docu
Modified: xmlgraphics/site/deploy/fop/1.0/index.pdf
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/1.0/index.pdf?rev=1032553&r1=1032552&r2=1032553&view=diff
==============================================================================
Files xmlgraphics/site/deploy/fop/1.0/index.pdf (original) and xmlgraphics/site/deploy/fop/1.0/index.pdf Mon Nov 8 11:59:27 2010 differ
Modified: xmlgraphics/site/deploy/fop/1.0/index.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/1.0/index.xml?rev=1032553&r1=1032552&r2=1032553&view=diff
==============================================================================
--- xmlgraphics/site/deploy/fop/1.0/index.xml (original)
+++ xmlgraphics/site/deploy/fop/1.0/index.xml Mon Nov 8 11:59:27 2010
@@ -14,7 +14,7 @@
See the License for the specific language governing permissions and
limitations under the License.
-->
-
@@ -293,14 +295,14 @@ document.write("Last Published: " + docu
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:
- +@@ -415,7 +417,7 @@ try { 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.
- +This initial example is obviously not very useful. It would be faster to create the PDF file @@ -424,7 +426,7 @@ try { same AreaTreeModel instance which essentially concatenates all the input document to one single output document.
- +One of the most important use cases for this format is obviously modifying the area @@ -441,7 +443,7 @@ try { the modified file may not render correctly.
The generation of the area tree format as well as it parsing process has been designed to allow @@ -453,7 +455,7 @@ try {
- +@@ -543,7 +545,7 @@ try { IFParser.parse() is used, but you can also just get a SAX ContentHandler by using the IFParser.getContentHandler() method.
- +This initial example is obviously not very useful. It would be faster to create the PDF file @@ -555,7 +557,7 @@ try { IFDocumentHandler interface. You could also do this in XSLT or using SAX on the XML level. Whatever suits your process best.
- +One of the most important use cases for this format is obviously modifying the @@ -572,7 +574,7 @@ try { arbitrary transformations on the IF's "viewport" and "g" elements. Possible are only rotations in 90 degree steps and translations.
- +
The generation of the intermediate format as well as it parsing process has been
Modified: xmlgraphics/site/deploy/fop/1.0/intermediate.pdf
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/1.0/intermediate.pdf?rev=1032553&r1=1032552&r2=1032553&view=diff
==============================================================================
Files xmlgraphics/site/deploy/fop/1.0/intermediate.pdf (original) and xmlgraphics/site/deploy/fop/1.0/intermediate.pdf Mon Nov 8 11:59:27 2010 differ
Modified: xmlgraphics/site/deploy/fop/1.0/intermediate.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/1.0/intermediate.xml?rev=1032553&r1=1032552&r2=1032553&view=diff
==============================================================================
--- xmlgraphics/site/deploy/fop/1.0/intermediate.xml (original)
+++ xmlgraphics/site/deploy/fop/1.0/intermediate.xml Mon Nov 8 11:59:27 2010
@@ -14,7 +14,7 @@
See the License for the specific language governing permissions and
limitations under the License.
-->
-
@@ -261,7 +263,7 @@ document.write("Last Published: " + docu tests during the normal build process. This indicates a problem in the current codebase. When a bug is fixed or a missing feature is added the entry for the relevant test case(s) are removed.
- +
This section lists disabled test cases in the test suite for the FO tree tests, at the time
@@ -420,7 +422,7 @@ document.write("Last Published: " + docu
keep_within-page_multi-column_overflow.xml (Page-keep not respected in multi-column layout):
The block should cause overflow in the
last column on the page, rather than be broken.
This section lists other known issues.
This section lists other known issues.
-@@ -253,7 +255,7 @@ document.write("Last Published: " + docu
@@ -269,7 +271,7 @@ document.write("Last Published: " + docu x:xmpmeta and rdf:RDF elements are recognized as the top-level element introducing an XMP fragment (as per the XMP specification).
- +[..] </fo:layout-master-set> @@ -303,7 +305,7 @@ document.write("Last Published: " + docu
@@ -446,7 +448,7 @@ document.write("Last Published: " + docu this was changed to map to dc:description["x-default"].
Metadata is made of property sets where each property set uses a different namespace URI. @@ -501,7 +503,7 @@ document.write("Last Published: " + docu
- +FOP supports multiple output formats by using a different renderer for each format. @@ -400,10 +402,10 @@ document.write("Last Published: " + docu attention than others.
- +Most FOP renderers use a FOP-specific system for font registration. @@ -460,7 +462,7 @@ document.write("Last Published: " + docu - +
The most obvious way to print your document is to use the FOP @@ -484,7 +486,7 @@ out = proc.getOutputStream();
@@ -500,7 +502,7 @@ out = proc.getOutputStream(); Support for Tagged PDF, PDF/A-1b and PDF/X has recently been added, however.
- +PDF has a set of fonts that are always available to all PDF viewers; @@ -514,7 +516,7 @@ out = proc.getOutputStream(); guaranteed to be available in all PDF viewer applications."
- +FOP does not currently support several desirable PDF features: watermarks and signatures. @@ -584,7 +586,7 @@ out = proc.getOutputStream(); Check the iText tutorial and documentation for setting access flags, password, encryption strength and other parameters.
- +In addition to the PDF Post-processing options, consider the following workarounds: @@ -608,7 +610,7 @@ out = proc.getOutputStream();
@@ -621,7 +623,7 @@ out = proc.getOutputStream(); filter (the latter is used for 1:1 embedding of JPEG images), everything else is Level 2.
- +The PostScript renderer configuration currently allows the following settings: @@ -664,7 +666,7 @@ out = proc.getOutputStream(); the particular postscript implementation issuing unwanted postscript subsystem initgraphics/erasepage calls on each setpagedevice call.
- +@@ -697,7 +699,7 @@ out = proc.getOutputStream(); painting operations. Certain painting operations are done off-screen and rendered to PCL as bitmaps because of limitations in PCL 5.
- +The PCL renderer configuration currently allows the following settings: @@ -794,7 +796,7 @@ out = proc.getOutputStream(); should be enough for most use cases. Note that this setting directly affects the size of the output file and the print quality.
- +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 @@ -803,7 +805,7 @@ out = proc.getOutputStream(); <fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format" xmlns:pcl="http://xmlgraphics.apache.org/fop/extensions/pcl"> - +
The page-source extension attribute on fo:simple-page-master allows to @@ -828,7 +830,7 @@ out = proc.getOutputStream(); "7" is "auto-select". Consult the technical reference for your printer for all available values.
- +The output-bin extension attribute on fo:simple-page-master allows to @@ -849,7 +851,7 @@ out = proc.getOutputStream(); "2" is the lower (rear) output bin. Consult the technical reference for your printer for all available values.
- +The duplex-mode extension attribute on fo:simple-page-master allows to @@ -875,7 +877,7 @@ out = proc.getOutputStream();
@@ -920,7 +922,7 @@ out = proc.getOutputStream(); FOP creates exactly one Document per Printfile with an optional Resource Group at the beginning. FOP does not create document indices.
- +This list is most likely badly incomplete.
There are still a big number of older (or limited) MO:DCA/IPDS environments in production @@ -965,9 +967,9 @@ out = proc.getOutputStream(); If a higher number of bits per pixel is configured, FOP has to switch to at least FS11 which may not work everywhere.
- +The AFP Renderer requires special configuration particularly related to fonts. AFP Render configuration is done through the normal FOP configuration file. The MIME type @@ -1128,13 +1130,13 @@ Note that the value of the encoding attr referenced-fonts section of the configuration file. However, the default fonts shown above will not be embedded.
- +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>- +
By default the AFP Renderer converts all images to 8 bit grey level. This can be overridden by the <images/> configuration element. Example:
@@ -1173,7 +1175,7 @@ Note that the value of the encoding attr<images mode="b+w" bits-per-pixel="1" dithering-quality="maximum"/>- +
By default, filled rectangles are painted using their given color using a PTOCA I-axis rule @@ -1186,7 +1188,7 @@ Note that the value of the encoding attr
<shading>dithered</shading>- +
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 @@ -1198,7 +1200,7 @@ Note that the value of the encoding attr
By default, bitmap image objects (or page segments derived from them) are put in the @@ -1217,7 +1219,7 @@ Note that the value of the encoding attr for the attributes are "inline" and "print-file". In the future, additional possibilities may be added.
- +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:
@@ -1225,7 +1227,7 @@ Note that the value of the encoding attr <fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format" xmlns:afp="http://xmlgraphics.apache.org/fop/extensions/afp"> - +The include-page-overlay extension element allows to define on a per simple-page-master basis a page overlay resource. Example:
@@ -1239,7 +1241,7 @@ Note that the value of the encoding attrThe mandatory name attribute must refer to an 8 character (space padded) resource name that 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:
@@ -1272,7 +1274,7 @@ Note that the value of the encoding attr 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:
@@ -1296,7 +1298,7 @@ Note that the value of the encoding attr 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:
@@ -1313,7 +1315,7 @@ Note that the value of the encoding attr 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 @@ -1335,7 +1337,7 @@ Note that the value of the encoding attr 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 @@ -1366,9 +1368,9 @@ Note that the value of the encoding attr 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. @@ -1405,7 +1407,7 @@ Note that the value of the encoding attr
- +RTF
- +@@ -1459,7 +1461,7 @@ Note that the value of the encoding attr
XML (Area Tree XML)
- +@@ -1473,7 +1475,7 @@ Note that the value of the encoding attr
Java2D/AWT
- +@@ -1488,14 +1490,14 @@ Note that the value of the encoding attr
- +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: @@ -1506,7 +1508,7 @@ Note that the value of the encoding attr
Bitmap (TIFF/PNG)
- +@@ -1525,7 +1527,7 @@ Note that the value of the encoding attr 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: @@ -1586,7 +1588,7 @@ Note that the value of the encoding attr 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 @@ -1652,7 +1654,7 @@ Note that the value of the encoding attr Deflate and JPEG compression for writing.
Runtime Rendering Options
The IF-based bitmap output implementations support a rendering option with the key @@ -1664,7 +1666,7 @@ Note that the value of the encoding attr "target-bitmap-size", new Dimension(320, 200));
TXT
- +@@ -1702,7 +1704,7 @@ Note that the value of the encoding attr
Output Formats in the Sandbox
@@ -1711,7 +1713,7 @@ Note that the value of the encoding attr 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@@ -1721,7 +1723,7 @@ Note that the value of the encoding attr This format is the Maker Interchange Format which is used by Adobe Framemaker. - +SVG
- +Warning@@ -1740,7 +1742,7 @@ Note that the value of the encoding attrWish list
Modified: xmlgraphics/site/deploy/fop/1.0/output.pdf URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/1.0/output.pdf?rev=1032553&r1=1032552&r2=1032553&view=diff ============================================================================== Files xmlgraphics/site/deploy/fop/1.0/output.pdf (original) and xmlgraphics/site/deploy/fop/1.0/output.pdf Mon Nov 8 11:59:27 2010 differ Modified: xmlgraphics/site/deploy/fop/1.0/output.xml URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/1.0/output.xml?rev=1032553&r1=1032552&r2=1032553&view=diff ============================================================================== --- xmlgraphics/site/deploy/fop/1.0/output.xml (original) +++ xmlgraphics/site/deploy/fop/1.0/output.xml Mon Nov 8 11:59:27 2010 @@ -14,7 +14,7 @@ See the License for the specific language governing permissions and limitations under the License. --> -
- ++ \ No newline at end of file Modified: xmlgraphics/site/deploy/fop/1.0/pdfa.html URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/1.0/pdfa.html?rev=1032553&r1=1032552&r2=1032553&view=diff ============================================================================== --- xmlgraphics/site/deploy/fop/1.0/pdfa.html (original) +++ xmlgraphics/site/deploy/fop/1.0/pdfa.html Mon Nov 8 11:59:27 2010 @@ -3,7 +3,7 @@+ Apache FOP Output Formats $Revision: 979214 $ @@ -1258,4 +1258,4 @@ Note that the value of the encoding attr -PDF/A (ISO 19005) @@ -208,6 +208,7 @@ document.write("Last Published: " + docuPDF/A (ISO 19005)
+- ++
- @@ -233,15 +234,16 @@ document.write("Last Published: " + docu
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.
@@ -251,7 +253,7 @@ document.write("Last Published: " + docuImplementation Status
- +@@ -272,7 +274,7 @@ document.write("Last Published: " + docu
Usage (command line)
- +@@ -285,7 +287,7 @@ document.write("Last Published: " + docu
Usage (embedded)
- +@@ -306,7 +308,7 @@ Fop fop = fopFactory.newFop(MimeConstant
PDF/A in Action
@@ -362,7 +364,7 @@ Fop fop = fopFactory.newFop(MimeConstant
PDF profile compatibility
- +@@ -371,7 +373,7 @@ Fop fop = fopFactory.newFop(MimeConstant
Interoperability
Modified: xmlgraphics/site/deploy/fop/1.0/pdfa.pdf URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/1.0/pdfa.pdf?rev=1032553&r1=1032552&r2=1032553&view=diff ============================================================================== Files xmlgraphics/site/deploy/fop/1.0/pdfa.pdf (original) and xmlgraphics/site/deploy/fop/1.0/pdfa.pdf Mon Nov 8 11:59:27 2010 differ Modified: xmlgraphics/site/deploy/fop/1.0/pdfa.xml URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/1.0/pdfa.xml?rev=1032553&r1=1032552&r2=1032553&view=diff ============================================================================== --- xmlgraphics/site/deploy/fop/1.0/pdfa.xml (original) +++ xmlgraphics/site/deploy/fop/1.0/pdfa.xml Mon Nov 8 11:59:27 2010 @@ -14,7 +14,7 @@ See the License for the specific language governing permissions and limitations under the License. --> -
- + \ No newline at end of file Modified: xmlgraphics/site/deploy/fop/1.0/pdfencryption.html URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/1.0/pdfencryption.html?rev=1032553&r1=1032552&r2=1032553&view=diff ============================================================================== --- xmlgraphics/site/deploy/fop/1.0/pdfencryption.html (original) +++ xmlgraphics/site/deploy/fop/1.0/pdfencryption.html Mon Nov 8 11:59:27 2010 @@ -3,7 +3,7 @@ - ++ PDF/A (ISO 19005) $Revision: 964711 $ @@ -162,4 +162,4 @@ Fop fop = fopFactory.newFop(MimeConstantPDF encryption. @@ -208,6 +208,7 @@ document.write("Last Published: " + docuPDF encryption.
+- ++
- @@ -227,8 +228,9 @@ document.write("Last Published: " + docu
Overview
- +@@ -248,7 +250,7 @@ document.write("Last Published: " + docu
Usage (command line)
- +@@ -280,7 +282,7 @@ document.write("Last Published: " + docu
Usage (embedded)
- +@@ -411,7 +413,7 @@ Fop fop = fopFactory.newFop(MimeConstant
Environment
- +@@ -440,7 +442,7 @@ Fop fop = fopFactory.newFop(MimeConstant
Installing a crypto provider
Modified: xmlgraphics/site/deploy/fop/1.0/pdfencryption.pdf URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/1.0/pdfencryption.pdf?rev=1032553&r1=1032552&r2=1032553&view=diff ============================================================================== Files xmlgraphics/site/deploy/fop/1.0/pdfencryption.pdf (original) and xmlgraphics/site/deploy/fop/1.0/pdfencryption.pdf Mon Nov 8 11:59:27 2010 differ Modified: xmlgraphics/site/deploy/fop/1.0/pdfencryption.xml URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/1.0/pdfencryption.xml?rev=1032553&r1=1032552&r2=1032553&view=diff ============================================================================== --- xmlgraphics/site/deploy/fop/1.0/pdfencryption.xml (original) +++ xmlgraphics/site/deploy/fop/1.0/pdfencryption.xml Mon Nov 8 11:59:27 2010 @@ -14,7 +14,7 @@ See the License for the specific language governing permissions and limitations under the License. --> -
- + \ No newline at end of file Modified: xmlgraphics/site/deploy/fop/1.0/pdfx.html URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/1.0/pdfx.html?rev=1032553&r1=1032552&r2=1032553&view=diff ============================================================================== --- xmlgraphics/site/deploy/fop/1.0/pdfx.html (original) +++ xmlgraphics/site/deploy/fop/1.0/pdfx.html Mon Nov 8 11:59:27 2010 @@ -3,7 +3,7 @@ - ++ PDF encryption. $Revision: 964711 $ @@ -218,4 +218,4 @@ Fop fop = fopFactory.newFop(MimeConstantPDF/X (ISO 15930) @@ -208,6 +208,7 @@ document.write("Last Published: " + docuPDF/X (ISO 15930)
+- ++
- @@ -230,8 +231,9 @@ document.write("Last Published: " + docu
Overview
@@ -245,13 +247,13 @@ document.write("Last Published: " + docu 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
- +@@ -279,7 +281,7 @@ document.write("Last Published: " + docu
Usage (command line)
- +@@ -289,7 +291,7 @@ document.write("Last Published: " + docu
Usage (embedded)
- +@@ -308,7 +310,7 @@ Fop fop = fopFactory.newFop(MimeConstant
PDF/X in Action
- +@@ -352,7 +354,7 @@ Fop fop = fopFactory.newFop(MimeConstant
PDF profile compatibility
Modified: xmlgraphics/site/deploy/fop/1.0/pdfx.pdf URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/1.0/pdfx.pdf?rev=1032553&r1=1032552&r2=1032553&view=diff ============================================================================== Files xmlgraphics/site/deploy/fop/1.0/pdfx.pdf (original) and xmlgraphics/site/deploy/fop/1.0/pdfx.pdf Mon Nov 8 11:59:27 2010 differ Modified: xmlgraphics/site/deploy/fop/1.0/pdfx.xml URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/1.0/pdfx.xml?rev=1032553&r1=1032552&r2=1032553&view=diff ============================================================================== --- xmlgraphics/site/deploy/fop/1.0/pdfx.xml (original) +++ xmlgraphics/site/deploy/fop/1.0/pdfx.xml Mon Nov 8 11:59:27 2010 @@ -13,7 +13,7 @@ See the License for the specific language governing permissions and limitations under the License. --> -
- + \ 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+ PDF/X (ISO 15930) $Revision: 964711 $ @@ -130,4 +130,4 @@ Fop fop = fopFactory.newFop(MimeConstant