xmlgraphics-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From vhenneb...@apache.org
Subject svn commit: r1613173 [8/15] - in /xmlgraphics/site/trunk/content: ./ batik/ batik/dev/ batik/tools/ batik/using/ batik/using/scripting/ commons/ fop/ fop/0.95/ fop/1.0/ fop/1.1/ fop/dev/ fop/dev/design/ fop/trunk/
Date Thu, 24 Jul 2014 16:21:24 GMT
Modified: xmlgraphics/site/trunk/content/fop/1.1/index.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.1/index.mdtext?rev=1613173&r1=1613172&r2=1613173&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.1/index.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.1/index.mdtext Thu Jul 24 16:21:20 2014
@@ -3,16 +3,16 @@ Title: Apache(tm) FOP Version 1.1
 #Apache™ FOP Version 1.1
 
 
-## Introduction {#intro}
+## Introduction { #intro}
 
 This is Version 1.1 of Apache FOP. FOP 1.1 contains many bug fixes and a number of improvements, including important features such as support for Complex Scripts (e.g., Arabic, Hebrew, Indic, and Southeast Asian scripts). To see what has changed since the last release, please visit [Release Notes](releaseNotes_1.1.html).
 
 This release implements a substantial subset of the W3C XSL-FO 1.1 Recommendation. For a detailed overview of FOP's compliance with this recommendation, see [Compliance](../compliance.html).
 
-## Upgrading from an earlier version {#upgrading}
+## Upgrading from an earlier version { #upgrading}
 
 If you're upgrading to this version from an earlier version of FOP, please read the information contained on the [Upgrading page](upgrading.html) !
 
-## Download {#download}
+## Download { #download}
 
 To download this version, please visit the [download page](../download.html).

Modified: xmlgraphics/site/trunk/content/fop/1.1/intermediate.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.1/intermediate.mdtext?rev=1613173&r1=1613172&r2=1613173&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.1/intermediate.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.1/intermediate.mdtext Thu Jul 24 16:21:20 2014
@@ -4,7 +4,7 @@ Title: Apache(tm) FOP: Intermediate Form
 
 <note>Please note that the intermediate formats described here are **advanced features** and can be ignored by most users of Apache&trade; FOP.</note>
 
-## Introduction {#introduction}
+## Introduction { #introduction}
 
 Apache&trade; FOP now provides two different so-called intermediate formats. The first one (let's call it the area tree XML format) is basically a 1:1 XML representation of FOP's area tree as generated by the layout engine. The area tree is conceptually defined in the [XSL-FO specification in chapter 1.1.2](http://www.w3.org/TR/2001/REC-xsl-20011015/slice1.html#section-N742-Formatting). Even though the area tree is mentioned in the XSL-FO specification, this part is not standardized. Therefore, the area tree XML format is a FOP-proprietary XML file format. The area tree XML can be generated through the area tree XML Renderer (the XMLRenderer).
 
@@ -12,11 +12,11 @@ The second intermediate format (which we
 
 The intermediate format can be used to generate intermediate documents that are modified before they are finally rendered to their ultimate output format. Modifications include adjusting and changing trait values, adding or modifying area objects, inserting prefabricated pages, overlays, imposition (n-up, rotation, scaling etc.). Multiple IF files can be combined to a single output file.
 
-## Which Intermediate Format to choose? {#which-if}
+## Which Intermediate Format to choose? { #which-if}
 
 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) {#strengths-at}
+### Area Tree XML (AT XML) { #strengths-at}
 
 
 - 1:1 representation of FOP's area tree in XML.
@@ -25,7 +25,7 @@ Both formats have their use cases, so th
 
 - Used in FOP's layout engine test suite for regression testing.
 
-### Intermediate Format (IF) {#strengths-if}
+### Intermediate Format (IF) { #strengths-if}
 
 
 - Highly optimized for speed.
@@ -40,11 +40,11 @@ Both formats have their use cases, so th
 
 More technical information about the two formats can be found on the [FOP Wiki](http://wiki.apache.org/xmlgraphics-fop/AreaTreeIntermediateXml/NewDesign).
 
-## Architectural Overview {#architecture}
+## Architectural Overview { #architecture}
 
 ![Diagram with an architectural overview over the intermediate formats](images/if-architecture-overview.png)
 
-## Usage of the Area Tree XML format (AT XML) {#usage}
+## Usage of the Area Tree XML format (AT XML) { #usage}
 
 As already mentioned, the area tree XML format is generated by using the **XMLRenderer** (MIME type: **application/X-fop-areatree**). So, you basically set the right MIME type for the output format and process your FO files as if you would create a PDF file.
 
@@ -84,21 +84,21 @@ This example simply reads an area tree f
 
 The area tree XML format can also be used from the [command-line](running.html#standalone-start) 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 {#concat}
+### Concatenating Documents { #concat}
 
 This initial example is obviously not very useful. It would be faster to create the PDF file directly. As the [ExampleConcat.java](http://svn.apache.org/repos/asf/xmlgraphics/fop/trunk/examples/embedding/java/embedding/atxml/ExampleConcat.java) example shows you can easily parse multiple area tree files in a row and add the parsed pages to the same AreaTreeModel instance which essentially concatenates all the input document to one single output document.
 
-### Modifying Documents {#modifying}
+### Modifying Documents { #modifying}
 
 One of the most important use cases for this format is obviously modifying the area tree XML before finally rendering it to the target format. You can easily use XSLT to process the AT XML file according to your needs. Please note, that we will currently not formally describe the area tree XML format. You need to have a good understanding its structure so you don't create any non-parseable files. We may add an XML Schema and more detailed documentation at a later time. You're invited to help us with that.
 
 <note>The area tree XML format is sensitive to changes in whitespace. If you're not careful, the modified file may not render correctly.</note>
 
-### Advanced Use {#advanced}
+### Advanced Use { #advanced}
 
 The generation of the area tree format as well as it parsing process has been designed to allow for maximum flexibility and optimization. Please note that you can call `setTransformerHandler()` on XMLRenderer to give the XMLRenderer your own TransformerHandler instance in case you would like to do custom serialization (to a W3C DOM, for example) and/or to directly modify the area tree using XSLT. The AreaTreeParser on the other side allows you to retrieve a ContentHandler instance where you can manually send SAX events to to start the parsing process (see `getContentHandler()`).
 
-## Usage of the Intermediate Format (IF) {#usage-if}
+## Usage of the Intermediate Format (IF) { #usage-if}
 
 The Intermediate Format (IF) is generated by the **IFSerializer** (MIME type: **application/X-fop-intermediate-format**). So, you basically set the right MIME type for the output format and process your FO files as if you would create a PDF file.
 
@@ -148,11 +148,11 @@ The basic pattern to parse the intermedi
 
 This example simply reads an intermediate file and renders it to a PDF file. Here IFParser.parse() is used, but you can also just get a SAX ContentHandler by using the IFParser.getContentHandler() method.
 
-### Concatenating Documents {#concat-if}
+### Concatenating Documents { #concat-if}
 
 This initial example is obviously not very useful. It would be faster to create the PDF file directly (without the intermediate step). As the [ExampleConcat.java](http://svn.apache.org/repos/asf/xmlgraphics/fop/trunk/examples/embedding/java/embedding/intermediate/ExampleConcat.java) example shows you can easily parse multiple intermediate files in a row and use the IFConcatenator class to concatenate page sequences from multiple source files to a single output file. This particular example does the concatenation on the level of the IFDocumentHandler interface. You could also do this in XSLT or using SAX on the XML level. Whatever suits your process best.
 
-### Modifying Documents {#modifying-if}
+### Modifying Documents { #modifying-if}
 
 One of the most important use cases for this format is obviously modifying the intermediate format before finally rendering it to the target format. You can easily use XSLT to process the IF file according to your needs.
 
@@ -160,6 +160,6 @@ There is an XML Schema (located under [s
 
 For certain output formats there's a caveat: Formats like AFP and PCL do not support arbitrary transformations on the IF's "viewport" and "g" elements. Possible are only rotations in 90 degree steps and translations.
 
-### Advanced Use {#advanced-if}
+### Advanced Use { #advanced-if}
 
 The generation of the intermediate format as well as it parsing process has been designed to allow for maximum flexibility and optimization. So rather than just passing in a StreamResult to IFSerializer's setResult() method, you can also use a SAXResult or a DOMResult. And as you've already seen, the IFParser on the other side allows you to retrieve a ContentHandler instance where you can manually send SAX events to start the parsing process (see `getContentHandler()`).

Modified: xmlgraphics/site/trunk/content/fop/1.1/knownissues_overview.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.1/knownissues_overview.mdtext?rev=1613173&r1=1613172&r2=1613173&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.1/knownissues_overview.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.1/knownissues_overview.mdtext Thu Jul 24 16:21:20 2014
@@ -3,7 +3,7 @@ Title: Apache(tm) FOP: Known Issues
 #Apache&trade; FOP: Known Issues
 
 
-## Known issues {#Known-issues}
+## Known issues { #Known-issues}
 
 This page lists currently known issues in the current release.
 
@@ -11,7 +11,7 @@ This page lists currently known issues i
 
 Apache&trade; FOP has an extensive automated testing infrastructure. Parts of this infrastructure are several sets of test cases. When a test case is listed in disabled-testcases.xml it is disabled in the JUnit 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.
 
-### FO Tree {#FO-Tree}
+### FO Tree { #FO-Tree}
 
 This section lists disabled test cases in the test suite for the FO tree tests, at the time of the release.
 
@@ -23,7 +23,7 @@ This section lists disabled test cases i
 
 The code currently evaluates this function according to the column in which the marker appears in the source document, rather than the column it is retrieved in.
 
-### Layout Engine {#Layout-Engine}
+### Layout Engine { #Layout-Engine}
 
 This section lists disabled test cases in the test suite for the layout engine tests, at the time of the release.
 
@@ -165,7 +165,7 @@ An assert is failing
 
 Test erroneously depends upon incorrect implementation of writing-mode trait derivation on fo:region-*.
 
-### Other known issues {#Other-known-issues}
+### Other known issues { #Other-known-issues}
 
 This section lists some other issues that post-date the release of FOP 1.0. For known issues that pre-date FOP 1.0, see [older bugs that remain open](https://issues.apache.org/jira/issues/?jql=project %3D FOP AND status in (Open%2C "In Progress"%2C Reopened) AND created < 2010-07-20 ORDER BY reporter ASC%2C key ASC%2C priority DESC). For all open issues that post-date FOP 1.0, see [newer bugs that remain open](https://issues.apache.org/jira/issues/?jql=project %3D FOP AND status in (Open%2C "In Progress"%2C Reopened) AND created >%3D 2010-07-20 ORDER BY reporter ASC%2C key ASC%2C priority DESC).
 

Modified: xmlgraphics/site/trunk/content/fop/1.1/metadata.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.1/metadata.mdtext?rev=1613173&r1=1613172&r2=1613173&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.1/metadata.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.1/metadata.mdtext Thu Jul 24 16:21:20 2014
@@ -3,17 +3,17 @@ Title: Apache(tm) FOP: Metadata
 #Apache&trade; FOP: Metadata
 
 
-## Overview {#overview}
+## Overview { #overview}
 
 Document metadata is an important tool for categorizing and finding documents. Various formats support different kinds of metadata representation and to different levels. One of the more popular and flexible means of representing document or object metadata is [XMP (eXtensible Metadata Platform, specified by Adobe)](http://www.adobe.com/products/xmp/). PDF 1.4 introduced the use of XMP. The XMP specification lists recommendation for embedding XMP metdata in other document and image formats. Given its flexibility it makes sense to make use this approach in the XSL-FO context. Unfortunately, unlike SVG which also refers to XMP, XSL-FO doesn't recommend a preferred way of specifying document and object metadata. Therefore, there's no portable way to represent metadata in XSL-FO documents. Each implementation does it differently.
 
-## Embedding XMP in an XSL-FO document {#xmp-in-fo}
+## Embedding XMP in an XSL-FO document { #xmp-in-fo}
 
 As noted above, there's no officially recommended way to embed metadata in XSL-FO. Apache&trade; FOP supports embedding XMP in XSL-FO. Currently, only support for document-level metadata is implemented. Object-level metadata will be implemented when there's interest.
 
 Document-level metadata can be specified in the `fo:declarations` element. XMP specification recommends to use `x:xmpmeta`, `rdf:RDF`, and `rdf:Description` elements as shown in example below. Both `x:xmpmeta` and `rdf:RDF` elements are recognized as the top-level element introducing an XMP fragment (as per the XMP specification).
 
-### Example {#xmp-example}
+### Example { #xmp-example}
 
     :::xml
     [..]
@@ -41,7 +41,7 @@ Document-level metadata can be specified
 
 <note>`fo:declarations` **must** be declared after `fo:layout-master-set` and before the first `page-sequence`.</note>
 
-## Implementation in Apache FOP {#xmp-impl-in-fop}
+## Implementation in Apache FOP { #xmp-impl-in-fop}
 
 Currently, XMP support is only available for PDF output.
 
@@ -66,7 +66,7 @@ The mapping between the Info and the Met
 
 <note>The "Subject" used to be mapped to `dc:subject` in the initial publication of PDF/A-1 (ISO 19005-1). In the [Technical Corrigendum 1](http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=45613) this was changed to map to `dc:description["x-default"]`.</note>
 
-### Namespaces {#namespaces}
+### Namespaces { #namespaces}
 
 Metadata is made of property sets where each property set uses a different namespace URI.
 
@@ -82,7 +82,7 @@ Please refer to the [XMP Specification](
 
 Property sets (Namespaces) not listed here are simply passed through to the final document (if supported). That is useful if you want to specify a custom metadata schema.
 
-## Links {#links}
+## Links { #links}
 
 
 -  [Adobe's Extensible Metadata Platform (XMP) website](http://www.adobe.com/products/xmp/)

Modified: xmlgraphics/site/trunk/content/fop/1.1/output.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.1/output.mdtext?rev=1613173&r1=1613172&r2=1613173&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.1/output.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.1/output.mdtext Thu Jul 24 16:21:20 2014
@@ -4,9 +4,9 @@ Title: Apache(tm) FOP Output Formats
 
 Apache&trade; FOP supports multiple output formats by using a different renderer for each format. The renderers do not all have the same set of capabilities, sometimes because of the output format itself, sometimes because some renderers get more development attention than others.
 
-## General Information {#general}
+## General Information { #general}
 
-### Fonts {#general-fonts}
+### Fonts { #general-fonts}
 
 Most FOP renderers use a FOP-specific system for font registration. However, the Java2D/AWT and print renderers use the Java AWT package, which gets its font information from the operating system registration. This can result in several differences, including actually using different fonts, and having different font metrics for the same font. The net effect is that the layout of a given FO document can be quite different between renderers that do not use the same font information.
 
@@ -34,7 +34,7 @@ With a work-around, it is possible to ma
     -  `fop -atin myfile.at.xml -tiff myfile.tiff`
 
 
-### Output to a Printer or Other Device {#general-direct-output}
+### Output to a Printer or Other Device { #general-direct-output}
 
 The most obvious way to print your document is to use the FOP [print renderer](#print), which uses the Java2D API (AWT). However, you can also send output from the Postscript renderer directly to a Postscript device, or output from the PCL renderer directly to a PCL device.
 
@@ -52,19 +52,19 @@ Here is some Java code to accomplish the
 
 Set the output MIME type to "`application/x-pcl`" (`MimeConstants.MIME_PCL`) and it happily sends the PCL to the UNIX printer queue.
 
-## PDF {#pdf}
+## PDF { #pdf}
 
 PDF is the best supported output format. It is also the most accurate with text and layout. This creates a PDF document that is streamed out as each page is rendered. This means that the internal page index information is stored near the end of the document. The PDF version supported is 1.4. PDF versions are forwards/backwards compatible.
 
 Note that FOP does not currently support PDF/A-1a. Support for [Tagged PDF](accessibility.html), [PDF/A-1b](pdfa.html) and [PDF/X](pdfx.html) has recently been added, however.
 
-### Fonts {#pdf-fonts}
+### Fonts { #pdf-fonts}
 
 PDF has a set of fonts that are always available to all PDF viewers; to quote from the PDF Specification:
 
 *"PDF prescribes a set of 14 standard fonts that can be used without prior definition. These include four faces each of three Latin text typefaces (Courier, Helvetica, and Times), as well as two symbolic fonts (Symbol and ITC Zapf Dingbats). These fonts, or suitable substitute fonts with the same metrics, are guaranteed to be available in all PDF viewer applications."*
 
-### Post-processing {#pdf-postprocess}
+### Post-processing { #pdf-postprocess}
 
 FOP does not currently support several desirable PDF features: watermarks and signatures. One workaround is to use Adobe Acrobat (the full version, not the Reader) to process the file manually or with scripting that it supports.
 
@@ -117,7 +117,7 @@ Here is some sample code that uses iText
 
 Check the iText tutorial and documentation for setting access flags, password, encryption strength and other parameters.
 
-### Watermarks {#pdf-watermark}
+### Watermarks { #pdf-watermark}
 
 In addition to the [PDF Post-processing](#pdf-postprocess) options, consider the following workarounds:
 
@@ -126,7 +126,7 @@ In addition to the [PDF Post-processing]
 
 - (submitted by Trevor Campbell) Place an image in a region that overlaps the flowing text. For example, make region-before large enough to contain your image. Then include a block (if necessary, use an absolutely positioned block-container) containing the watermark image in the static-content for the region-before. Note that the image will be drawn on top of the normal content.
 
-### Extensions {#pdf-extensions}
+### Extensions { #pdf-extensions}
 
 The PDF Renderer supports some PDF 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:
 
@@ -134,7 +134,7 @@ The PDF Renderer supports some PDF speci
     <fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format"
              xmlns:pdf="http://xmlgraphics.apache.org/fop/extensions/pdf">
 
-#### Embedded Files {#pdf-embedded-file}
+#### Embedded Files { #pdf-embedded-file}
 
 It is possible to attach/embed arbitrary files into a PDF file. You can give a name and a description of the file. Example:
 
@@ -153,11 +153,11 @@ It is also possible to reference an embe
 
 Note: Not all PDF Viewers (including some Acrobat Versions) will open the embedded file when clicking on the link. In that case, the user will have to open he attachment via the separate list of file attachments.
 
-## PostScript {#ps}
+## PostScript { #ps}
 
 The PostScript renderer has been brought up to a similar quality as the PDF renderer, but may still be missing certain features. It provides good support for most text and layout. Images and SVG are not fully supported, yet. Currently, the PostScript renderer generates PostScript Level 3 with most DSC comments. Actually, the only Level 3 features used are the FlateDecode and DCTDecode filter (the latter is used for 1:1 embedding of JPEG images), everything else is Level 2.
 
-### Configuration {#ps-configuration}
+### Configuration { #ps-configuration}
 
 The PostScript renderer configuration currently allows the following settings:
 
@@ -183,7 +183,7 @@ The default value for the "dsc-compliant
 
 The default value for the "rendering" setting is "quality". Setting it to "size" optimizes rendering for smaller file sizes which can involve minor compromises in rendering quality. For example, solid borders are then painted as plain rectangles instead of the elaborate painting instructions required for mixed-color borders.
 
-### Limitations {#ps-limitations}
+### Limitations { #ps-limitations}
 
 
 - Images and SVG may not be displayed correctly. SVG support is far from being complete. No image transparency is available.
@@ -194,20 +194,20 @@ The default value for the "rendering" se
 
 - PPD support is still missing.
 
-## PCL {#pcl}
+## PCL { #pcl}
 
 This format is for the Hewlett-Packard PCL printers and other printers supporting PCL. It should produce output as close to identical as possible to the printed output of the PDFRenderer within the limitations of the renderer, and output device.
 
 The output created by the PCLRenderer is generic PCL 5, HP GL/2 and PJL. This should allow any device fully supporting PCL 5 to be able to print the output generated by the PCLRenderer. PJL is used to control the print job and switch to the PCL language. PCL 5 is used for text, raster graphics and rectangular fill graphics. HP GL/2 is used for more complex painting operations. Certain painting operations are done off-screen and rendered to PCL as bitmaps because of limitations in PCL 5.
 
-### References {#pcl-references}
+### References { #pcl-references}
 
 
 -  [WikiPedia entry on PCL](http://en.wikipedia.org/wiki/Printer_Control_Language)
 
 -  [Technical reference documents on PCL from Hewlett-Packard](http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=bpl04568)
 
-### Limitations {#pcl-limitations}
+### Limitations { #pcl-limitations}
 
 
 - Text or graphics outside the left or top of the printable area are not rendered properly. This is a limitation of PCL, not FOP. In general, things that should print to the left of the printable area are shifted to the right so that they start at the left edge of the printable area.
@@ -226,7 +226,7 @@ The output created by the PCLRenderer is
 
 - Currently, there's no support for clipping and image transparency, largely because PCL 5 has certain limitations.
 
-### Configuration {#pcl-configuration}
+### Configuration { #pcl-configuration}
 
 The PCL renderer configuration currently allows the following settings:
 
@@ -245,7 +245,7 @@ The default value for the "disable-pjl" 
 
 You can control the output resolution for the PCL using the "target resolution" setting on the FOUserAgent. The actual value will be rounded up to the next supported PCL resolution. Currently, only 300 and 600 dpi are supported which should be enough for most use cases. Note that this setting directly affects the size of the output file and the print quality.
 
-### Extensions {#pcl-extensions}
+### Extensions { #pcl-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 be declared in the fo:root element like this:
 
@@ -253,7 +253,7 @@ The PCL Renderer supports some PCL speci
     <fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format"
              xmlns:pcl="http://xmlgraphics.apache.org/fop/extensions/pcl">
 
-#### Page Source (Tray selection) {#pcl-page-source}
+#### Page Source (Tray selection) { #pcl-page-source}
 
 The page-source extension attribute on fo:simple-page-master allows to select the paper tray the sheet for a particular simple-page-master is to be taken from. Example:
 
@@ -266,7 +266,7 @@ The page-source extension attribute on f
 
 Note: the tray number is a positive integer and the value depends on the target printer. Not all PCL printers support the same paper trays. Usually, "1" is the default tray, "2" is the manual paper feed, "3" is the manual envelope feed, "4" is the "lower" tray and "7" is "auto-select". Consult the technical reference for your printer for all available values.
 
-#### Output Bin {#pcl-output-bin}
+#### Output Bin { #pcl-output-bin}
 
 The `output-bin` extension attribute on fo:simple-page-master allows to select the output bin into which the printed output should be fed. Example:
 
@@ -279,7 +279,7 @@ The `output-bin` extension attribute on 
 
 Note: the output bin number is a positive integer and the value depends on the target printer. Not all PCL printers support the same output bins. Usually, "1" is the upper output bin, "2" is the lower (rear) output bin. Consult the technical reference for your printer for all available values.
 
-#### Page Duplex Mode {#pcl-duplex-mode}
+#### Page Duplex Mode { #pcl-duplex-mode}
 
 The duplex-mode extension attribute on fo:simple-page-master allows to select the duplex mode to be used for a particular simple-page-master. Example:
 
@@ -292,7 +292,7 @@ The duplex-mode extension attribute on f
 
 Note: the duplex is a positive integer and the value depends on the target printer. Not all PCL printers support duplexing. Usually, "0" is simplex, "1" is duplex (long-edge binding), "2" is duplex (short-edge binding). Consult the technical reference for your printer for all available values.
 
-## AFP {#afp}
+## AFP { #afp}
 
 The FOP AFP Renderer deals with creating documents conforming to the IBM AFP document architecture also refered to as MO:DCA (Mixed Object Document Content Architecture).
 
@@ -306,7 +306,7 @@ The mapping of XSL-FO elements to the ma
 
 FOP creates exactly one Document per Printfile with an optional Resource Group at the beginning. FOP does not create document indices.
 
-### References {#afp-references}
+### References { #afp-references}
 
 
 -  [AFP (Advanced Function Presentation)](http://en.wikipedia.org/wiki/Advanced_Function_Presentation)
@@ -315,7 +315,7 @@ FOP creates exactly one Document per Pri
 
 -  [Technical notes on AFP output in FOP](http://wiki.apache.org/xmlgraphics-fop/AFPOutput)
 
-### Limitations {#afp-limitations}
+### Limitations { #afp-limitations}
 
 This list is most likely badly incomplete.
 
@@ -324,13 +324,13 @@ This list is most likely badly incomplet
 
 - Only IBM outline and raster fonts and to a limited extend the original fonts built into FOP are supported. Support for TrueType fonts may be added later.
 
-### Deployment in older environments {#afp-compatibility}
+### Deployment in older environments { #afp-compatibility}
 
 There are still a big number of older (or limited) MO:DCA/IPDS environments in production out there. AFP has grown in functionality over time and not every environment supports the latest features. We're trying to make AFP output work in as many environments as possible. However, to make AFP output work on older environments it is recommended to set to configuration to 1 bit per pixel (see below on how to do this). In this case, all images are converted to bi-level images using IOCA function set 10 (FS10) and are enclosed in page-segments since some implementation cannot deal with IOCA objects directly. If a higher number of bits per pixel is configured, FOP has to switch to at least FS11 which may not work everywhere.
 
-### Configuration {#afp-configuration}
+### Configuration { #afp-configuration}
 
-#### Fonts {#afp-font-config}
+#### Fonts { #afp-font-config}
 
 The AFP Renderer requires special configuration particularly related to fonts. AFP Render configuration is done through the normal FOP configuration file. The MIME type for the AFP Renderer is application/x-afp which means the AFP Renderer section in the FOP configuration file looks like:
 
@@ -487,21 +487,21 @@ For double byte EBCDIC encoded character
     :::xml
     <afp-font type="CIDKeyed" codepage="T10835  " encoding="Cp937" characterset="CZTKAI" ebcdic-dbcs="true"/>
 
-#### Output Resolution {#afp-renderer-resolution-config}
+#### Output Resolution { #afp-renderer-resolution-config}
 
 By default the AFP Renderer creates output with a resolution of 240 dpi. This can be overridden by the <renderer-resolution/> configuration element. Example:
 
     :::xml
     <renderer-resolution>240</renderer-resolution>
 
-#### Line Width Correction {#afp-line-width-correction-config}
+#### Line Width Correction { #afp-line-width-correction-config}
 
 The default line width in AFP is device dependent. This means that a line width specified in, say, a SVG source file may not render the way it was intended. The output AFP line with can be corrected by the <line-width-correction/> configuration element. Example:
 
     :::xml
     <line-width-correction>2.5</line-width-correction>
 
-#### Images {#afp-image-config}
+#### Images { #afp-image-config}
 
 By default the AFP Renderer converts all images to 8 bit grey level. This can be overridden by the <images/> configuration element. Example:
 
@@ -549,7 +549,7 @@ By default, JPEG images are rasterized t
       <jpeg allow-embedding="false" bitmap-encoding-quality="0.8"/>
     </images>
 
-#### GOCA (Vector Graphics) {#afp-goca-config}
+#### GOCA (Vector Graphics) { #afp-goca-config}
 
 Not all AFP implementations support GOCA. Some also have bugs related to GOCA. Therefore, it is desirable to have some control over the generation of GOCA graphics.
 
@@ -565,14 +565,14 @@ Some AFP implementations have trouble re
 
 If you disable GOCA or let text render as shapes, the size of the generated AFP usually increases considerably.
 
-#### Shading {#afp-shading-config}
+#### Shading { #afp-shading-config}
 
 By default, filled rectangles are painted using their given color using a PTOCA I-axis rule (DIR). But not all environments handle these colors correctly. That's why a setting is supported that paints the rectangles using an ordered dither pattern (bi-level) with an inline IOCA FS10 image that is used together with the "replicate and trim" mapping. The optional "shading" element can be used to control the shading mode. Its default value is "color". To enable the dithered mode, use "dithered". Example:
 
     :::xml
     <shading>dithered</shading>
 
-#### Resource Group File {#afp-resource-group-file}
+#### Resource Group File { #afp-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 may be specified with the <resource-group-file/> configuration element. Example:
 
@@ -581,7 +581,7 @@ By default the AFP Renderer will place a
 
 <note>Be careful when using this option not to overwrite existing resource files from previous rendering runs.</note>
 
-#### Resource Level Defaults {#afp-resource-level-defaults}
+#### Resource Level Defaults { #afp-resource-level-defaults}
 
 By default, bitmap image objects (or page segments derived from them) are put in the print-file-level resource group and GOCA graphics are inlined for compatibility with the AFP Workbench tool.
 
@@ -592,7 +592,7 @@ It is possible to override these default
 
 "goca" refers to GOCA graphics and "bitmap" refers to IOCA images. The possible values for the attributes are "inline" and "print-file". In the future, additional possibilities may be added.
 
-### Extensions {#afp-extensions}
+### Extensions { #afp-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:
 
@@ -600,7 +600,7 @@ The AFP Renderer supports some AFP speci
     <fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format"
              xmlns:afp="http://xmlgraphics.apache.org/fop/extensions/afp">
 
-#### Page Overlay (IPO) Extension {#afp-page-overlay}
+#### Page Overlay (IPO) Extension { #afp-page-overlay}
 
 The include-page-overlay extension element allows to define on a per simple-page-master basis a page overlay resource. Example:
 
@@ -614,7 +614,7 @@ The include-page-overlay extension eleme
 
 The 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 {#afp-page-segment}
+#### Page Segment (IPS) Extension { #afp-page-segment}
 
 The include-page-segment extension element allows to define resource substitution for fo:external-graphics elements. Example:
 
@@ -634,7 +634,7 @@ The effect here is that whenever FOP enc
 
 The include-page-segment extension element has the optional attribute *resource-file*. The value of this is a URI to a resource containing a page segment with the declared name. In this case FOP embeds the page segment into the generated document so that the external resource does not have to be supplied in the print job.
 
-#### Tag Logical Element (TLE) Extension {#afp-tag-logical-element}
+#### Tag Logical Element (TLE) Extension { #afp-tag-logical-element}
 
 The tag-logical-element extension element allows to injects TLEs into the AFP output stream. Example:
 
@@ -655,7 +655,7 @@ The tag-logical-element extension elemen
 
 The tag-logical-element extension element can appear within a simple-page-master (page level) or it can appear as child of page-sequence (page group level). 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 {#afp-no-operation}
+#### No Operation (NOP) Extension { #afp-no-operation}
 
 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:
 
@@ -670,7 +670,7 @@ The no-operation extension provides the 
 
 The no-operation extension element can appear as child of `simple-page-master` (appears after "Begin Page" BPG), `page-sequence` (appears after "Begin Named Page Group" BNG and `declarations` (appears after "Begin Document" BDT). Multiple no-operation extension elements inside the same formatting object are allowed. Each NOP will appear right after the respective "Begin" field indicated above even if it is specified as the last child under its parent. The order inside the parent will be maintained. The "placement" attribute can be used to have the NOP appear before the "End" field of the object rather than after the "Begin" field. Specify `placement="before-end"` to do that. Please note that, at the moment, this only has an effect for NOPs that are children of the `page-sequence` formatting object. The "name" attribute is mandatory but will not appear inside the AFP stream.
 
-#### Invoke Medium Map (IMM) Extension {#afp-invoke-medium-map}
+#### Invoke Medium Map (IMM) Extension { #afp-invoke-medium-map}
 
 The invoke-medium-map extension allows to generate IMM fields (Invoke Medium Map) in the generated AFP output. Example:
 
@@ -685,7 +685,7 @@ The invoke-medium-map extension allows t
 
 The invoke-medium-map element is allowed as child of fo:page-sequence (page group level) or fo:simple-page-master. It is NOT supported on document level (fo:root), yet. FOP also doesn't support specifying medium maps inside XML (using BMM/EMM). It can 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 {#afp-form-maps}
+#### Form Maps/Defs { #afp-form-maps}
 
 Apache FOP supports embedding an external form map resource in the generated AFP output. This is done using the `afp:include-form-map` extension. An example:
 
@@ -701,9 +701,9 @@ The `afp:include-form-map` is to be plac
 
 <note>Apache FOP doesn't support a way to define a form map or medium map using XML means inside an XSL-FO document. You will have to build the form map with some third-party tool.</note>
 
-### Foreign Attributes {#afp-foreign-attributes}
+### Foreign Attributes { #afp-foreign-attributes}
 
-#### Resource {#afp-foreign-attributes-resource}
+#### Resource { #afp-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. The afp foreign attributes are only used in conjuntion with <fo:external-graphic/> and <instream-foreign-object/>. Example:
 
@@ -733,7 +733,7 @@ The resource-level attribute where the r
 
 
 
-## RTF {#rtf}
+## RTF { #rtf}
 
 JFOR, an open source XSL-FO to RTF converter has been integrated into Apache FOP. This will create an RTF (rich text format) document that will attempt to contain as much information from the XSL-FO document as possible. It should be noted that is not possible (due to RTF's limitations) to map all XSL-FO features to RTF. For complex documents, the RTF output will never reach the feature level from PDF, for example. Thus, using RTF output is only recommended for simple documents such as letters.
 
@@ -763,27 +763,27 @@ These are some known restrictions compar
 
 - percentages are not supported everywhere
 
-## XML (Area Tree XML) {#xml}
+## XML (Area Tree XML) { #xml}
 
 This is primarily for testing and verification. The XML created is simply a representation of the internal area tree put into XML. We use that to verify the functionality of FOP's layout engine.
 
 The other use case of the Area Tree XML is as FOP's "intermediate format". More information on that can be found on the page dedicated to the [Intermediate Format](intermediate.html).
 
-## Java2D/AWT {#awt}
+## Java2D/AWT { #awt}
 
 The Java2DRenderer provides the basic functionality for all Java2D-based output formats (AWT viewer, direct print, PNG, TIFF).
 
 The AWT viewer shows a window with the pages displayed inside a Java graphic. It displays one page at a time. The fonts used for the formatting and viewing depend on the fonts available to your JRE.
 
-## Print {#print}
+## Print { #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 {#print-issues}
+### Known issues { #print-issues}
 
 If you run into the problem that the printed output is incomplete on Windows: this often happens to users printing to a PCL printer. There seems to be an incompatibility between Java and certain PCL printer drivers on Windows. Since most network-enabled laser printers support PostScript, try switching to the PostScript printer driver for that printer model.
 
-## Bitmap (TIFF/PNG) {#bitmap}
+## Bitmap (TIFF/PNG) { #bitmap}
 
 It is possible to directly create bitmap images from the individual pages generated by the layout engine. This is done with the same code that renders to the Java2D/AWT renderer.
 
@@ -791,7 +791,7 @@ Currently, two output formats are suppor
 
 The quality of the bitmap depends on the target resolution setting on the FOUserAgent and on further settings described below.
 
-### Configuration {#bitmap-configuration}
+### Configuration { #bitmap-configuration}
 
 The TIFF and PNG renderer configuration currently allows the following settings:
 
@@ -826,7 +826,7 @@ The default value for the `"anti-aliasin
 
 The default value for the `"rendering"` setting is `"true"`. You can set this value to `"false"` to improve rendering speeds a bit at the loss of some image quality. If this setting has an actual effect depends on the JVM's Java2D backend.
 
-### TIFF-specific Configuration {#tiff-configuration}
+### TIFF-specific Configuration { #tiff-configuration}
 
 In addition to the above values the TIFF renderer configuration allows some additional settings:
 
@@ -859,7 +859,7 @@ This setting may override any setting ma
 
 <note>If you want to use CCITT compression, please make sure you've got [Java Advanced Imaging Image I/O Tools](http://java.sun.com/products/java-media/jai/current.html) in your classpath. The Sun JRE doesn't come with a TIFF codec built in, so it has to be added separately. The internal TIFF codec from XML Graphics Commons only supports PackBits, Deflate and JPEG compression for writing.</note>
 
-### Runtime Rendering Options {#bitmap-rendering-options}
+### Runtime Rendering Options { #bitmap-rendering-options}
 
 The IF-based bitmap output implementations support a rendering option with the key "target-bitmap-size" (value: java.awt.Dimension) that allows to force the pages to be proportionally fit into a bitmap of a given size. This can be used to produce thumbnails or little preview images of the individual pages. An example:
 
@@ -867,7 +867,7 @@ The IF-based bitmap output implementatio
     userAgent.getRenderingOptions().put(
         "target-bitmap-size", new Dimension(320, 200));
 
-## TXT {#txt}
+## TXT { #txt}
 
 The text renderer produces plain ASCII text output that attempts to match the output of the PDFRenderer as closely as possible. This was originally developed to accommodate an archive system that could only accept plain text files, and is primarily useful for getting a quick-and-dirty view of the document text. The renderer is very limited, so do not be surprised if it gives unsatisfactory results.
 
@@ -880,19 +880,19 @@ Because FOP lays the text onto a grid du
 
 - line-height="10pt"
 
-## Output Formats in the Sandbox {#sandbox}
+## Output Formats in the Sandbox { #sandbox}
 
 Due to the state of certain renderers we moved some of them to a "sandbox" area until they are ready for more serious use. The renderers and FOEventHandlers in the sandbox can be found under src/sandbox and are compiled into build/fop-sandbox.jar during the main build. The output formats in the sandbox are marked as such below.
 
-### MIF {#mif}
+### MIF { #mif}
 <warning>The MIF handler is in the sandbox and not yet functional in FOP Trunk!!! Please help us ressurrect this feature.</warning>
 This format is the Maker Interchange Format which is used by Adobe Framemaker.
 
-### SVG {#svg}
+### SVG { #svg}
 <warning>The SVG renderer is in the sandbox and may not work as expected in FOP Trunk!!! Please help us improve this feature.</warning>
 This format creates an SVG document that has links between the pages. This is primarily for slides and creating svg images of pages. Large documents will create SVG files that are far too large for an SVG viewer to handle. Since FO documents usually have text the SVG document will have a large number of text elements. The font information for the text is obtained from the JVM in the same way as for the AWT viewer. If the SVG is viewed on a system where the fonts are different, such as another platform, then the page may look wrong.
 
-## Wish list {#wishlist}
+## Wish list { #wishlist}
 
 Apache FOP is easily extensible and allows you to add new output formats to enhance FOP's functionality. There's a number of output formats which are on our wish list. We're looking for volunteers to help us implement them.
 

Modified: xmlgraphics/site/trunk/content/fop/1.1/pdfa.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.1/pdfa.mdtext?rev=1613173&r1=1613172&r2=1613173&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.1/pdfa.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.1/pdfa.mdtext Thu Jul 24 16:21:20 2014
@@ -3,13 +3,13 @@ Title: Apache(tm) FOP: PDF/A (ISO 19005)
 #Apache&trade; FOP: PDF/A (ISO 19005)
 <authors><person email="jeremias@apache.org" name="Jeremias Märki"></person></authors>
 
-## Overview {#overview}
+## Overview { #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)](http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=38920&ICS1=37&ICS2=100&ICS3=99). Work on PDF/A-2 is in progress at [AIIM](http://www.aiim.org/standards.asp?ID=25013).
 
 Design documentation on PDF/A can be found on FOP's Wiki on the [PDFAConformanceNotes](http://wiki.apache.org/xmlgraphics-fop/PDFAConformanceNotes) page.
 
-## Implementation Status {#status}
+## Implementation Status { #status}
 
  **PDF/A-1b** is implemented to the degree that FOP supports the creation of the elements described in ISO 19005-1.
 
@@ -17,13 +17,13 @@ Tests have been performed against jHove 
 
  **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](accessibility.html).
 
-## Usage (command line) {#command-line}
+## Usage (command line) { #command-line}
 
 To activate PDF/A-1b from the command-line, specify "-pdfprofile PDF/A-1b" 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) {#embedded}
+## Usage (embedded) { #embedded}
 
 When FOP is embedded in another Java application you can set a special option on the renderer options in the user agent to activate the PDF/A-1b profile. Here's an example:
 
@@ -36,7 +36,7 @@ If one of the validation rules of PDF/A 
 
 For PDF/A-1a, just use the string "PDF/A-1a" instead of "PDF/A-1b".
 
-## PDF/A in Action {#rules}
+## PDF/A in Action { #rules}
 
 There are a number of things that must be looked after if you activate a PDF/A profile. If you receive a PDFConformanceException, have a look at the following list (not necessarily comprehensive):
 
@@ -56,11 +56,11 @@ There are a number of things that must b
 
 <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](accessibility.html) for details.</note>
 
-## PDF profile compatibility {#profile-compatibility}
+## PDF profile compatibility { #profile-compatibility}
 
 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 {#interoperability}
+## Interoperability { #interoperability}
 
 There has been some confusion about the namespace for the PDF/A indicator in the XMP metadata. At least three variants have been seen in the wild:
 

Modified: xmlgraphics/site/trunk/content/fop/1.1/pdfencryption.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.1/pdfencryption.mdtext?rev=1613173&r1=1613172&r2=1613173&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.1/pdfencryption.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.1/pdfencryption.mdtext Thu Jul 24 16:21:20 2014
@@ -3,13 +3,13 @@ Title: Apache(tm) FOP: PDF encryption.
 #Apache&trade; FOP: PDF encryption.
 <authors><person email="pietsch@apache.org" name="J.Pietschmann"></person><person email="jeremias@apache.org" name="Jeremias Märki"></person></authors>
 
-## Overview {#Overview}
+## Overview { #Overview}
 
 Apache&trade; FOP supports encryption of PDF output, thanks to Patrick C. Lankswert. This feature is commonly used to prevent unauthorized viewing, printing, editing, copying text from the document and doing annotations. It is also possible to ask the user for a password in order to view the contents. Note that there already exist third party applications which can decrypt an encrypted PDF without effort and allow the aforementioned operations, therefore the degree of protection is limited.
 
 For further information about features and restrictions regarding PDF encryption, look at the documentation coming with Adobe Acrobat or the technical documentation on the Adobe web site.
 
-## Usage (command line) {#commandline}
+## Usage (command line) { #commandline}
 
 Encryption is enabled by supplying any of the encryption related options.
 
@@ -32,7 +32,7 @@ Further restrictions can be imposed by u
 |  `-noassembledoc`  | disable assembling documents |
 |  `-noprinthq`  | disable high quality printing |
 
-## Usage (embedded) {#embedded}
+## Usage (embedded) { #embedded}
 
 When FOP is embedded in another Java application you need to set an options map on the renderer. These are the supported options:
 
@@ -111,7 +111,7 @@ Alternatively, you can set each value se
 
 1. noprinthq: Boolean or "true"/"false"
 
-## Environment {#Environment}
+## Environment { #Environment}
 
 In order to use PDF encryption, FOP has to be compiled with cryptography support. Currently, only [JCE](http://java.sun.com/j2se/1.4/docs/guide/security/jce/JCERefGuide.html) is supported. JCE is part of JDK 1.4. For earlier JDKs, it can be installed separately. The build process automatically detects JCE presence and installs PDF encryption support if possible, otherwise a stub is compiled in.
 
@@ -121,7 +121,7 @@ then you don't have the needed infrastru
 
 There are several commercial and a few Open Source packages which provide RC4. A pure Java implementation is produced by [The Legion of the Bouncy Castle](http://www.bouncycastle.org/). [Mozilla JSS](http://www.mozilla.org/projects/security/pki/jss/) is an interface to a native implementation.
 
-## Installing a crypto provider {#install_crypto}
+## Installing a crypto provider { #install_crypto}
 
 The pure Java implementation from [Bouncy Castle](http://www.bouncycastle.org/) is easy to install.
 

Modified: xmlgraphics/site/trunk/content/fop/1.1/pdfx.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.1/pdfx.mdtext?rev=1613173&r1=1613172&r2=1613173&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.1/pdfx.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.1/pdfx.mdtext Thu Jul 24 16:21:20 2014
@@ -3,13 +3,13 @@ Title: Apache(tm) FOP: PDF/X (ISO 15930)
 #Apache&trade; FOP: PDF/X (ISO 15930)
 <authors><person email="jeremias@apache.org" name="Jeremias Märki"></person></authors>
 
-## Overview {#overview}
+## Overview { #overview}
 
 <warning>Support for PDF/X is available beginning with version 0.93. This feature is new and may not be 100% complete, yet. Feedback is welcome.</warning>
 
 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)](http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=39940&ICS1=37&ICS2=100&ICS3=99). More info on PDF/X can be found on the [PDF/X info site](http://www.pdfx.info/).
 
-## Implementation Status {#status}
+## Implementation Status { #status}
 
  **PDF/X-3:2003** is implemented to the degree that FOP supports the creation of the elements described in ISO 15930-6.
 
@@ -17,11 +17,11 @@ An important restriction of the current 
 
 Tests have been performed against Adobe Acrobat 7.0.7 (Preflight function). Note that there are bugs in Adobe Acrobat which cause false alarms if both PDF/A-1b and PDF/X-3:2003 are activated at the same time.
 
-## Usage (command line) {#command-line}
+## Usage (command line) { #command-line}
 
 To activate PDF/X-3:2003 from the command-line, specify "-pdfprofile PDF/X-3:2003" as a parameter. If there is a violation of one of the validation rules for PDF/X, an error message is presented and the processing stops.
 
-## Usage (embedded) {#embedded}
+## Usage (embedded) { #embedded}
 
 When FOP is embedded in another Java application you can set a special option on the renderer options in the user agent to activate the PDF/A-1b profile. Here's an example:
 
@@ -33,7 +33,7 @@ When FOP is embedded in another Java app
 
 If one of the validation rules of PDF/X is violated, an PDFConformanceException (descendant of RuntimeException) is thrown.
 
-## PDF/X in Action {#rules}
+## PDF/X in Action { #rules}
 
 There are a number of things that must be looked after if you activate a PDF/X profile. If you receive a PDFConformanceException, have a look at the following list (not necessarily comprehensive):
 
@@ -50,6 +50,6 @@ There are a number of things that must b
 
 - PDF is forced to version 1.4 if PDF/X-3:2003 is activated.
 
-## PDF profile compatibility {#profile-compatibility}
+## PDF profile compatibility { #profile-compatibility}
 
 The PDF profiles "PDF/X-3:2003" and "PDF/A-1b" are compatible and can both be activated at the same time.

Modified: xmlgraphics/site/trunk/content/fop/1.1/releaseNotes_1.1.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.1/releaseNotes_1.1.mdtext?rev=1613173&r1=1613172&r2=1613173&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.1/releaseNotes_1.1.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.1/releaseNotes_1.1.mdtext Thu Jul 24 16:21:20 2014
@@ -3,9 +3,9 @@ Title: Release Notes for Apache FOP 1.1
 #Release Notes for Apache FOP 1.1
 
 
-## Major Changes in Version 1.1 {#version_1.1}
+## Major Changes in Version 1.1 { #version_1.1}
 This is not a complete list of changes, just some of the more important ones. A full list of changes in this release [is available](changes_1.1.html).
-## Changes to the Code Base {#Changes-to-the-Code-Base}
+## Changes to the Code Base { #Changes-to-the-Code-Base}
 
 
 - ![fix](/images/fix.jpg) Update to use of checkstyle-5.5 as default configuration. Remove checkstyle-4.0 configuration. Also, import environment build properties before local properties, so that latter can refer to former. Committed by GA. See issue [FOP-2042](https://issues.apache.org/jira/browse/FOP-2042).
@@ -34,12 +34,12 @@ This is not a complete list of changes, 
 
 - ![add](/images/add.jpg) Added support for resolution of relative URIs against a specified xml:base during property refinement. Committed by AD. See issue [FOP-1744](https://issues.apache.org/jira/browse/FOP-1744).
 
-### Changes to the User Configuration {#Changes-to-the-User-Configuration}
+### Changes to the User Configuration { #Changes-to-the-User-Configuration}
 
 
 - ![add](/images/add.jpg) Added configuration option to set the version of the output PDF document. Committed by VH. Thanks to Mehdi Houshmand. See issue [FOP-1945](https://issues.apache.org/jira/browse/FOP-1945).
 
-### Changes to the Font Subsystem {#Changes-to-the-Font-Subsystem}
+### Changes to the Font Subsystem { #Changes-to-the-Font-Subsystem}
 
 
 - ![add](/images/add.jpg) Add support for OpenType advanced typographic tables (GDEF, GSUB, GPOS). Committed by GA.
@@ -52,12 +52,12 @@ This is not a complete list of changes, 
 
 - ![add](/images/add.jpg) Added convenience support for the flushing of the Fop font cache file from the command line. Committed by AC.
 
-### Changes to the Image Support {#Changes-to-the-Image-Support}
+### Changes to the Image Support { #Changes-to-the-Image-Support}
 
 
 - ![fix](/images/fix.jpg) Support use of ImageLoaderRawPNG decoder in order to prevent re-encoding of PNG images (and unnecssary output file bloat). Committed by GA. Thanks to Luis Bernardo, Matthias Reischenbacher. See issue [FOP-1256](https://issues.apache.org/jira/browse/FOP-1256).
 
-### Changes to the Layout Engine {#Changes-to-the-Layout-Engine}
+### Changes to the Layout Engine { #Changes-to-the-Layout-Engine}
 
 
 - ![fix](/images/fix.jpg) Fix for break before (break-before) not respected on blocks nested in inlines. Committed by GA. Thanks to Luis Bernardo. See issue [FOP-1567](https://issues.apache.org/jira/browse/FOP-1567).
@@ -76,7 +76,7 @@ This is not a complete list of changes, 
 
 - ![fix](/images/fix.jpg) Fix for correct behavior of keep-together.within-line in case there are nested inlines Committed by AD. See issue [FOP-1847](https://issues.apache.org/jira/browse/FOP-1847).
 
-### Changes to Renderers (Output Formats) {#Changes-to-Renderers-%28Output-Formats%29}
+### Changes to Renderers (Output Formats) { #Changes-to-Renderers-%28Output-Formats%29}
 
 
 - ![add](/images/add.jpg) Added possibility to embed TrueType fonts in PostScript. Committed by VH. See issue [FOP-2004](https://issues.apache.org/jira/browse/FOP-2004).

Modified: xmlgraphics/site/trunk/content/fop/1.1/running.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.1/running.mdtext?rev=1613173&r1=1613172&r2=1613173&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.1/running.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.1/running.mdtext Thu Jul 24 16:21:20 2014
@@ -3,7 +3,7 @@ Title: Running Apache&trade; FOP
 #Running Apache&trade; FOP
 
 
-## System Requirements {#require}
+## System Requirements { #require}
 
 The following software must be installed:
 
@@ -36,19 +36,19 @@ In addition, the following system requir
 
 - If you will be using FOP to process SVG, you must do so in a graphical environment. See [FOP: Graphics (Batik)](graphics.html#batik) for details.
 
-## Installation {#install}
+## Installation { #install}
 
-### Instructions {#install-instruct}
+### Instructions { #install-instruct}
 
 Basic FOP installation consists of first unzipping the `.gz` file that is the distribution medium, then unarchiving the resulting `.tar` file in a directory/folder that is convenient on your system. Please consult your operating system documentation or Zip application software documentation for instructions specific to your site.
 
-### Problems {#install-problems}
+### Problems { #install-problems}
 
 Some Mac OSX users have experienced filename truncation problems using Stuffit to unzip and unarchive their distribution media. This is a legacy of older Mac operating systems, which had a 31-character pathname limit. Several Mac OSX users have recommended that Mac OSX users use the shell command `tar -xzf` instead.
 
-## Starting FOP as a Standalone Application {#standalone-start}
+## Starting FOP as a Standalone Application { #standalone-start}
 
-### Using the fop script or batch file {#fop-script}
+### Using the fop script or batch file { #fop-script}
 
 The usual and recommended practice for starting FOP from the command line is to run the batch file fop.bat (Windows) or the shell script fop (Unix/Linux). These scripts require that the environment variable JAVA_HOME be set to a path pointing to the appropriate Java installation on your system. Macintosh OSX includes a Java environment as part of its distribution. We are told by Mac OSX users that the path to use in this case is `/Library/Java/Home`. **Caveat:** We suspect that, as Apple releases new Java environments and as FOP upgrades the minimum Java requirements, the two will inevitably not match on some systems. Please see [Java on Mac OSX FAQ](http://developer.apple.com/java/faq) for information as it becomes available.
 
@@ -147,12 +147,12 @@ The usual and recommended practice for s
 
 PDF encryption is only available if FOP was compiled with encryption support **and** if compatible encryption support is available at run time. Currently, only the JCE is supported. Check the [Details](pdfencryption.html).
 
-### Writing your own script {#your-own-script}
+### Writing your own script { #your-own-script}
 
 FOP's entry point for your own scripts is the class `org.apache.fop.cli.Main`. The general pattern for the command line is: `java -classpath <CLASSPATH>
         org.apache.fop.cli.Main <arguments>`. The arguments consist of the options and infile and outfile specifications as shown above for the standard scripts. You may wish to review the standard scripts to make sure that you get your environment properly configured.
 
-### Running with java's -jar option {#jar-option}
+### Running with java's -jar option { #jar-option}
 
 As an alternative to the start scripts you can run `java
         -jar path/to/build/fop.jar <arguments>`, relying on FOP to build the classpath for running FOP dynamically, see [below](#dynamical-classpath). If you use hyphenation, you must put `fop-hyph.jar` in the `lib` directory.
@@ -162,7 +162,7 @@ You can also run `java -jar path/to/fop.
 
 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 {#dynamical-classpath}
+### FOP's dynamical classpath construction { #dynamical-classpath}
 
 If FOP is started without a proper classpath, it tries to add its dependencies dynamically. If the system property `fop.home` contains the name of a directory, then FOP uses that directory as the base directory for its search. Otherwise the current working directory is the base directory. If the base directory is called `build`, then its parent directory becomes the base directory.
 
@@ -170,7 +170,7 @@ FOP expects to find `fop.jar` in the `bu
 
 If the system property `fop.optional.lib` contains the name of a directory, then all `jar` files in that directory are also added to the classpath. See the methods `getJARList` and `checkDependencies` in `org.apache.fop.cli.Main`.
 
-## Using Xalan to Check XSL-FO Input {#check-input}
+## Using Xalan to Check XSL-FO Input { #check-input}
 
 FOP sessions that use -xml and -xsl input instead of -fo input are actually controlling two distinct conversions: Tranforming XML to XSL-FO, then formatting the XSL-FO to PDF (or another FOP output format). Although FOP controls both of these processes, the first is included merely as a convenience and for performance reasons. Only the second is part of FOP's core processing. If a user has a problem running FOP, it is important to determine which of these two processes is causing the problem. If the problem is in the first process, the user's stylesheet is likely the cause. The FOP development team does not have resources to help with stylesheet issues, although we have included links to some useful [Specifications](../resources.html#specs) and [Books/Articles](../resources.html#articles). If the problem is in the second process, FOP may have a bug or an unimplemented feature that does require attention from the FOP development team.
 
@@ -186,7 +186,7 @@ The -foout option works the same way as 
 
 Note that there are some subtle differences between the FOP and Xalan command-lines.
 
-## Memory Usage {#memory}
+## Memory Usage { #memory}
 
 FOP can consume quite a bit of memory, even though this has been continually improved. This is partly inherent to the formatting process and partly caused by implementation choices. All FO processors currently on the market have memory problems with certain layouts.
 
@@ -201,6 +201,6 @@ If you are running out of memory when us
 
 - Use multiple page sequences. FOP starts rendering after the end of a page sequence is encountered. While the actual rendering is done page-by-page, some additional memory is freed after the page sequence has been rendered. This can be substantial if the page sequence contains lots of FO elements.
 
-## Problems {#problems}
+## Problems { #problems}
 
 If you have problems running FOP, please see the ["How to get Help" page](../gethelp.html).

Modified: xmlgraphics/site/trunk/content/fop/1.1/servlets.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.1/servlets.mdtext?rev=1613173&r1=1613172&r2=1613173&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.1/servlets.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.1/servlets.mdtext Thu Jul 24 16:21:20 2014
@@ -3,11 +3,11 @@ Title: Apache(tm) FOP: Servlets
 #Apache&trade; FOP: Servlets
 <subtitle>How to use Apache&trade; FOP in a Servlet</subtitle>
 
-## Overview {#overview}
+## Overview { #overview}
 
 This page discusses topic all around using Apache&trade; FOP in a servlet environment.
 
-## Example Servlets in the FOP distribution {#example-servlets}
+## Example Servlets in the FOP distribution { #example-servlets}
 
 In the directory {fop-dir}/src/java/org/apache/fop/servlet, you'll find a working example of a FOP-enabled servlet.
 
@@ -22,11 +22,11 @@ The source code for the servlet can be f
 
 <note>This example servlet should not be used on a public web server connected to the Internet as it does not contain any measures to prevent Denial-of-Service-Attacks. It is provided as an example and as a starting point for your own servlet.</note>
 
-## Create your own Servlet {#servlet}
+## Create your own Servlet { #servlet}
 
 <note>This section assumes you are familiar with [embedding FOP](embedding.html).</note>
 
-### A minimal Servlet {#minimal-servlet}
+### A minimal Servlet { #minimal-servlet}
 
 Here is a minimal code snippet to demonstrate the basics:
 
@@ -50,7 +50,7 @@ Here is a minimal code snippet to demons
 
 <note>There are numerous problems with the code snippet above. Its purpose is only to demonstrate the basic concepts. See below for details.</note>
 
-### Adding XSL tranformation (XSLT) {#xslt}
+### Adding XSL tranformation (XSLT) { #xslt}
 
 A common requirement is to transform an XML source to XSL-FO using an XSL transformation. It is recommended to use JAXP for this task. The following snippet shows the basic code:
 
@@ -98,11 +98,11 @@ The `Source` instance used above is simp
 
 Because you have an explicit `Transformer` object, you can also use it to explicitely set parameters for the transformation run.
 
-### Custom configuration {#cfg}
+### Custom configuration { #cfg}
 
 You can easily set up your own FOUserAgent as demonstrated on the [Embedding page](embedding.html).
 
-### Improving performance {#performance}
+### Improving performance { #performance}
 
 There are several options to consider:
 
@@ -113,7 +113,7 @@ There are several options to consider:
 
 Of course, the [performance hints from the Embedding page](embedding.html#performance) apply here, too.
 
-### Accessing resources in your web application {#uriresolver}
+### Accessing resources in your web application { #uriresolver}
 
 Often, you will want to use resources (stylesheets, images etc.) which are bundled with your web application. FOP provides a URIResolver implementation that lets you access files via the Servlet's ServletContext. The class is called `org.apache.fop.servlet.ServletContextURIResolver`.
 
@@ -160,7 +160,7 @@ Here are some example snippets:
     Transformer transformer = this.transFactory.newTransformer(xsltSrc);
     transformer.setURIResolver(this.uriResolver);
 
-## Notes on Microsoft Internet Explorer {#ie}
+## Notes on Microsoft Internet Explorer { #ie}
 
 Some versions of Internet Explorer will not automatically show the PDF or call the servlet multiple times. These are well-known limitations of Internet Explorer and are not a problem of the servlet. However, Internet Explorer can still be used to download the PDF so that it can be viewed later. Here are some suggestions in this context:
 
@@ -176,18 +176,18 @@ Some versions of Internet Explorer will 
 
 - Cache in the server. It may help to include a parameter in the URL which has a timestamp as the value min order to decide whether a request is repeated. IEx is reported to retrieve a document up to three times, but never more often.
 
-## Servlet Engines {#servlet-engine}
+## Servlet Engines { #servlet-engine}
 
 When using a servlet engine, there are potential CLASSPATH issues, and potential conflicts with existing XML/XSLT libraries. Servlet containers also often use their own classloaders for loading webapps, which can cause bugs and security problems.
 
-### Tomcat {#tomcat}
+### Tomcat { #tomcat}
 
 Check Tomcat's documentation for detailed instructions about installing FOP and Cocoon. There are known bugs that must be addressed, particularly for Tomcat 4.0.3.
 
-### WebSphere 3.5 {#websphere}
+### WebSphere 3.5 { #websphere}
 
 Put a copy of a working parser in some directory where WebSphere can access it. For example, if /usr/webapps/yourapp/servlets is the CLASSPATH for your servlets, copy the Xerces jar into it (any other directory would also be fine). Do not add the jar to the servlet CLASSPATH, but add it to the CLASSPATH of the application server which contains your web application. In the WebSphere administration console, click on the "environment" button in the "general" tab. In the "variable name" box, enter "CLASSPATH". In the "value" box, enter the correct path to the parser jar file (/usr/webapps/yourapp/servlets/Xerces.jar in our example here). Press "OK", then apply the change and restart the application server.
 
-## Handling complex use cases {#complex-usecases}
+## Handling complex use cases { #complex-usecases}
 
 Sometimes the requirements for a servlet get quite sophisticated: SQL data sources, multiple XSL transformations, merging of several datasources etc. In such a case consider using [Apache Cocoon](http://cocoon.apache.org/) instead of a custom servlet to accomplish your goal.

Modified: xmlgraphics/site/trunk/content/fop/1.1/upgrading.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.1/upgrading.mdtext?rev=1613173&r1=1613172&r2=1613173&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.1/upgrading.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.1/upgrading.mdtext Thu Jul 24 16:21:20 2014
@@ -2,7 +2,7 @@ Title: Upgrading from an Earlier Version
 
 #Upgrading from an Earlier Version of Apache&trade; FOP
 
-## Upgrading from Version 1.0 {#fop-1.0}
+## Upgrading from Version 1.0 { #fop-1.0}
 
 You should encounter very few issues in upgrading from FOP 1.0, except as noted in the following:
 
@@ -26,7 +26,7 @@ You should encounter very few issues in 
 
 - Because complex script features are now enabled by default, it is possible that different font specific data will be used for kerning than was previously used. This may be the case if a font supports a traditional TrueType `kern` table and also supports the advanced typographic `kern` feature with a `GPOS` table. In FOP 1.0, the former is used for kerning, while in FOP 1.1 with complex script features enabled, the latter is used. If it is desired to explicitly use the `kern` table (rather than the `GPOS` table) in such a case, then the `-nocs` command line option may be used when invoking FOP in order to disable complex script features.
 
-## Upgrading from Pre-1.0 Versions {#pre-1.0}
+## Upgrading from Pre-1.0 Versions { #pre-1.0}
 
 If you're planning to upgrade to the latest Apache&trade; FOP version from a pre-1.0 version, there are a few very important things to consider:
 

Modified: xmlgraphics/site/trunk/content/fop/bugs.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/bugs.mdtext?rev=1613173&r1=1613172&r2=1613173&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/bugs.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/bugs.mdtext Thu Jul 24 16:21:20 2014
@@ -6,7 +6,7 @@ Title: Apache(tm) FOP: Bugs and Other Tr
 
 Information on this page applies to enhancement requests and other trackable issues as well as bugs.
 
-## Reported Issues {#issues_existing}
+## Reported Issues { #issues_existing}
 
 A list of unresolved reported bugs can be found at [FOP Open Bugs (Jira)](https://issues.apache.org/jira/issues/?jql=project%20%3D%20FOP%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC). If you have an interest in an issue already reported, please consider the following:
 
@@ -15,7 +15,7 @@ A list of unresolved reported bugs can b
 
 - If you would like to track the status of the issue, consider adding your email address to the list of "CC" recipients, so that you will receive an email as changes are made to the issue.
 
-## Unreported Issues (Reporting New Issues) {#issues_new}
+## Unreported Issues (Reporting New Issues) { #issues_new}
 
 User reports of bugs and requests for enhancements are extremely important parts of FOP development, and we appreciate the time you take to help us track these issues down.
 



---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: commits-help@xmlgraphics.apache.org


Mime
View raw message