xmlgraphics-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From psan...@apache.org
Subject svn commit: r1417307 [8/14] - 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 Wed, 05 Dec 2012 08:19:31 GMT
Modified: xmlgraphics/site/trunk/content/fop/1.1/embedding.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.1/embedding.mdtext?rev=1417307&r1=1417306&r2=1417307&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.1/embedding.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.1/embedding.mdtext Wed Dec  5 08:19:09 2012
@@ -95,7 +95,7 @@ This may look complicated at first, but 
 
 ### Logging <a id="basic-logging"></a>
 
-Logging is now a little different than it was in FOP 0.20.5. We've switched from Avalon Logging to [Jakarta Commons Logging](http://commons.apache.org/logging/) . While with Avalon Logging the loggers were directly given to FOP, FOP now retrieves its logger(s) through a statically available LogFactory. This is similar to the general pattern that you use when you work with Apache Log4J directly, for example. We call this "static logging" (Commons Logging, Log4J) as opposed to "instance logging" (Avalon Logging). This has a consequence: You can't give FOP a logger for each processing run anymore. The log output of multiple, simultaneously running FOP instances is sent to the same logger.
+Logging is now a little different than it was in FOP 0.20.5. We've switched from Avalon Logging to [Jakarta Commons Logging](http://commons.apache.org/logging/). While with Avalon Logging the loggers were directly given to FOP, FOP now retrieves its logger(s) through a statically available LogFactory. This is similar to the general pattern that you use when you work with Apache Log4J directly, for example. We call this "static logging" (Commons Logging, Log4J) as opposed to "instance logging" (Avalon Logging). This has a consequence: You can't give FOP a logger for each processing run anymore. The log output of multiple, simultaneously running FOP instances is sent to the same logger.
 
 By default, [Jakarta Commons Logging](http://commons.apache.org/logging/) uses JDK logging (available in JDKs 1.4 or higher) as its backend. You can configure Commons Logging to use an alternative backend, for example Log4J. Please consult the [documentation for Jakarta Commons Logging](http://commons.apache.org/logging/) on how to configure alternative backends.
 
@@ -106,7 +106,7 @@ As a result of the above we differentiat
 
 -  [User/Integrator-oriented feedback](events.html) (NEW!)
 
-The use of "feedback" instead of "logging" is intentional. Most people were using log output as a means to get feedback from events within FOP. Therefore, FOP now includes an `event` package which can be used to receive feedback from the layout engine and other components within FOP **per rendering run** . This feedback is not just some text but event objects with parameters so these events can be interpreted by code. Of course, there is a facility to turn these events into normal human-readable messages. For details, please read on on the [Events page](events.html) . This leaves normal logging to be mostly a thing used by the FOP developers although anyone can surely activate certain logging categories but the feedback from the loggers won't be separated by processing runs. If this is required, the [Events subsystem](events.html) is the right approach.
+The use of "feedback" instead of "logging" is intentional. Most people were using log output as a means to get feedback from events within FOP. Therefore, FOP now includes an `event` package which can be used to receive feedback from the layout engine and other components within FOP **per rendering run**. This feedback is not just some text but event objects with parameters so these events can be interpreted by code. Of course, there is a facility to turn these events into normal human-readable messages. For details, please read on on the [Events page](events.html). This leaves normal logging to be mostly a thing used by the FOP developers although anyone can surely activate certain logging categories but the feedback from the loggers won't be separated by processing runs. If this is required, the [Events subsystem](events.html) is the right approach.
 
 ### Processing XSL-FO <a id="render"></a>
 
@@ -143,7 +143,7 @@ However, you may not always have your in
 
 -  **Java Objects:** Please have a look at the [Embedding examples](#examples) which contain an example for this.
 
-There are a variety of upstream data manipulations possible. For example, you may have a DOM and an XSL stylesheet; or you may want to set variables in the stylesheet. Interface documentation and some cookbook solutions to these situations are provided in [Xalan Basic Usage Patterns](http://xml.apache.org/xalan-j/usagepatterns.html) .
+There are a variety of upstream data manipulations possible. For example, you may have a DOM and an XSL stylesheet; or you may want to set variables in the stylesheet. Interface documentation and some cookbook solutions to these situations are provided in [Xalan Basic Usage Patterns](http://xml.apache.org/xalan-j/usagepatterns.html).
 
 ## Configuring Apache FOP Programmatically <a id="config-internal"></a>
 
@@ -167,7 +167,7 @@ The **hyphenation base URL** to use when
     `fopFactory.setHyphenBaseURL("file:///C:/Temp/hyph");`
 
 -
-Disable **strict validation** . When disabled FOP is less strict about the rules established by the XSL-FO specification. Example:
+Disable **strict validation**. When disabled FOP is less strict about the rules established by the XSL-FO specification. Example:
 
     `fopFactory.setStrictValidation(false);`
 
@@ -182,7 +182,7 @@ Set the **source resolution** for the do
     `fopFactory.setSourceResolution(96); // =96dpi (dots/pixels per Inch)`
 
 -
-Manually add an **ElementMapping instance** . If you want to supply a special FOP extension you can give the instance to the FOUserAgent. Normally, the FOP extensions can be automatically detected (see the documentation on extension for more info). Example:
+Manually add an **ElementMapping instance**. If you want to supply a special FOP extension you can give the instance to the FOUserAgent. Normally, the FOP extensions can be automatically detected (see the documentation on extension for more info). Example:
 
     `fopFactory.addElementMapping(myElementMapping);// myElementMapping is a org.apache.fop.fo.ElementMapping`
 
@@ -246,12 +246,12 @@ Set the **target resolution** for the do
     `userAgent.setTargetResolution(300); // =300dpi (dots/pixels per Inch)`
 
 -
-Set **your own Document Handler** . This feature can be used for several purposes, the most likey usage of which would probably be binding a MIME type when the output is Intermediate Format (see [Document Handlers](#documenthandlers) ). This also allows advanced users to create their own implementation of the document handler.
+Set **your own Document Handler**. This feature can be used for several purposes, the most likey usage of which would probably be binding a MIME type when the output is Intermediate Format (see [Document Handlers](#documenthandlers) ). This also allows advanced users to create their own implementation of the document handler.
 
     `userAgent.setDocumentHandlerOverride(documentHandler) // documentHandler is an instance of org.apache.fop.render.intermediate.IFDocumentHandler`
 
 -
-Set **your own FOEventHandler instance** . If you want to supply your own FOEventHandler or configure an FOEventHandler subclass in a special way you can give the instance to the FOUserAgent. Normally, the FOEventHandler instance is created by FOP. Example:
+Set **your own FOEventHandler instance**. If you want to supply your own FOEventHandler or configure an FOEventHandler subclass in a special way you can give the instance to the FOUserAgent. Normally, the FOEventHandler instance is created by FOP. Example:
 
     `userAgent.setFOEventHandlerOverride(myFOEventHandler); // myFOEventHandler is an org.apache.fop.fo.FOEventHandler`
 
@@ -279,11 +279,11 @@ Instead of setting the parameters manual
 
     fopFactory.setUserConfig(new File("C:/Temp/mycfg.xml"));
 
-The layout of the configuration file is described on the [Configuration page](configuration.html) .
+The layout of the configuration file is described on the [Configuration page](configuration.html).
 
 ## Document Handlers <a id="documenthandlers"></a>
 
-The document handlers are classes that inherit from `org.apache.fop.render.intermediate.IFDocumentHandler` . This is an interface for which a MIME type specific implementation can be created. This same handler is used either when XSL-FO is used as the input or when Intermediate Format is used. Since IF is output format agnostic, if custom fonts or other configuration information that affect layout (specific to a particular MIME type) are given then FOP needs that contextual information. The document handler provides that context so that when the IF is rendered, it is more visually consistent with FO rendering. The code below shows an example of how a document handler can be used to provide PDF configuration data to the IFSerializer.
+The document handlers are classes that inherit from `org.apache.fop.render.intermediate.IFDocumentHandler`. This is an interface for which a MIME type specific implementation can be created. This same handler is used either when XSL-FO is used as the input or when Intermediate Format is used. Since IF is output format agnostic, if custom fonts or other configuration information that affect layout (specific to a particular MIME type) are given then FOP needs that contextual information. The document handler provides that context so that when the IF is rendered, it is more visually consistent with FO rendering. The code below shows an example of how a document handler can be used to provide PDF configuration data to the IFSerializer.
 
     :::java
     IFDocumentHandler targetHandler = userAgent.getRendererFactory().createDocumentHandler(userAgent, MimeConstants.MIME_PDF);
@@ -294,7 +294,7 @@ The document handlers are classes that i
 
     userAgent.setDocumentHandlerOverride(ifSerializer);  //Make sure the prepared document handler is used
 
-The rest of the code is the same as in [Basic Usage Patterns](#basics) .
+The rest of the code is the same as in [Basic Usage Patterns](#basics).
 
 ## Hints <a id="hints"></a>
 
@@ -306,13 +306,13 @@ Fop instances shouldn't (and can't) be r
 
 If your XSL-FO files contain SVG then Apache Batik will be used. When Batik is initialised it uses certain classes in `java.awt` that intialise the Java AWT classes. This means that a daemon thread is created by the JVM and on Unix it will need to connect to a DISPLAY.
 
-The thread means that the Java application may not automatically quit when finished, you will need to call `System.exit()` . These issues should be fixed in the JDK 1.4.
+The thread means that the Java application may not automatically quit when finished, you will need to call `System.exit()`. These issues should be fixed in the JDK 1.4.
 
-If you run into trouble running FOP on a head-less server, please see the [notes on Batik](graphics.html#batik) .
+If you run into trouble running FOP on a head-less server, please see the [notes on Batik](graphics.html#batik).
 
 ### Getting information on the rendering process <a id="render-info"></a>
 
-To get the number of pages that were rendered by FOP you can call `Fop.getResults()` . This returns a `FormattingResults` object where you can look up the number of pages produced. It also gives you the page-sequences that were produced along with their id attribute and their numbers of pages. This is particularly useful if you render multiple documents (each enclosed by a page-sequence) and have to know the number of pages of each document.
+To get the number of pages that were rendered by FOP you can call `Fop.getResults()`. This returns a `FormattingResults` object where you can look up the number of pages produced. It also gives you the page-sequences that were produced along with their id attribute and their numbers of pages. This is particularly useful if you render multiple documents (each enclosed by a page-sequence) and have to know the number of pages of each document.
 
 ## Improving performance <a id="performance"></a>
 
@@ -323,13 +323,13 @@ There are several options to consider:
 
 - Depending on the target OutputStream (in case of a FileOutputStream, but not for a ByteArrayOutputStream, for example) it may improve performance considerably if you buffer the OutputStream using a BufferedOutputStream: `out = new java.io.BufferedOutputStream(out);` <br></br>Make sure you properly close the OutputStream when FOP is finished.
 
-- Cache the stylesheet. If you use the same stylesheet multiple times you can set up a JAXP `Templates` object and reuse it each time you do the XSL transformation. (More information can be found [here](http://www.javaworld.com/javaworld/jw-05-2003/jw-0502-xsl.html) .)
+- Cache the stylesheet. If you use the same stylesheet multiple times you can set up a JAXP `Templates` object and reuse it each time you do the XSL transformation. (More information can be found [here](http://www.javaworld.com/javaworld/jw-05-2003/jw-0502-xsl.html).)
 
 - Use an XSLT compiler like [XSLTC](http://xml.apache.org/xalan-j/xsltc_usage.html) that comes with Xalan-J.
 
 - Fine-tune your stylesheet to make the XSLT process more efficient and to create XSL-FO that can be processed by FOP more efficiently. Less is more: Try to make use of property inheritance where possible.
 
-- You may also wish to consider trying to reduce [memory usage](http://xmlgraphics.apache.org/fop/trunk/running.html#memory) .
+- You may also wish to consider trying to reduce [memory usage](http://xmlgraphics.apache.org/fop/trunk/running.html#memory).
 
 ## Multithreading FOP <a id="multithreading"></a>
 

Modified: xmlgraphics/site/trunk/content/fop/1.1/events.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.1/events.mdtext?rev=1417307&r1=1417306&r2=1417307&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.1/events.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.1/events.mdtext Wed Dec  5 08:19:09 2012
@@ -13,7 +13,7 @@ On this page, we won't discuss logging a
 
 ## The consumer side <a id="consumer"></a>
 
-The event subsystem is located in the `org.apache.fop.events` package and its base is the `Event` class. An instance is created for each event and is sent to a set of `EventListener` instances by the `EventBroadcaster` . An `Event` contains:
+The event subsystem is located in the `org.apache.fop.events` package and its base is the `Event` class. An instance is created for each event and is sent to a set of `EventListener` instances by the `EventBroadcaster`. An `Event` contains:
 
 
 - an event ID,
@@ -26,7 +26,7 @@ The event subsystem is located in the `o
 
 The `EventFormatter` class can be used to translate the events into human-readable, localized messages.
 
-A full example of what is shown here can be found in the `examples/embedding/java/embedding/events` directory in the FOP distribution. The example can also be accessed [via the web](http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/examples/embedding/java/embedding/events/) .
+A full example of what is shown here can be found in the `examples/embedding/java/embedding/events` directory in the FOP distribution. The example can also be accessed [via the web](http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/examples/embedding/java/embedding/events/).
 
 ### Writing an EventListener <a id="write-listener"></a>
 
@@ -59,7 +59,7 @@ The following code sample shows a very s
         }
     }
 
-You can see that for every event the method `processEvent` of the `EventListener` will be called. Inside this method you can do whatever processing you would like including throwing a `RuntimeException` , if you want to abort the current processing run.
+You can see that for every event the method `processEvent` of the `EventListener` will be called. Inside this method you can do whatever processing you would like including throwing a `RuntimeException`, if you want to abort the current processing run.
 
 The code above also shows how you can turn an event into a human-readable, localized message that can be presented to a user. The `EventFormatter` class does this for you. It provides additional methods if you'd like to explicitly specify the locale.
 
@@ -140,9 +140,9 @@ The `Event.paramsBuilder()` is a [fluent
 
 ### The EventProducer interface <a id="event-producer"></a>
 
-To simplify event production, the event subsystem provides the `EventProducer` interface. You can create interfaces which extend `EventProducer` . These interfaces will contain one method per event to be generated. By contract, each event method must have as its first parameter a parameter named "source" (Type Object) which indicates the object that generated the event. After that come an arbitrary number of parameters of any type as needed by the event.
+To simplify event production, the event subsystem provides the `EventProducer` interface. You can create interfaces which extend `EventProducer`. These interfaces will contain one method per event to be generated. By contract, each event method must have as its first parameter a parameter named "source" (Type Object) which indicates the object that generated the event. After that come an arbitrary number of parameters of any type as needed by the event.
 
-The event producer interface does not need to have any implementation. The implementation is produced at runtime by a dynamic proxy created by `DefaultEventBroadcaster` . The dynamic proxy creates `Event` instances for each method call against the event producer interface. Each parameter (except "source") is added to the event's parameter map.
+The event producer interface does not need to have any implementation. The implementation is produced at runtime by a dynamic proxy created by `DefaultEventBroadcaster`. The dynamic proxy creates `Event` instances for each method call against the event producer interface. Each parameter (except "source") is added to the event's parameter map.
 
 To simplify the code needed to get an instance of the event producer interface it is suggested to create a public inner provider class inside the interface.
 
@@ -186,7 +186,7 @@ Primarily, the QDox-based collector task
 
 There's one more information that is extracted from the event producer information for the event model: an optional primary exception. The first exception in the "throws" declaration of an event method is noted. It is used to throw an exception from the invocation handler if the event has an event severity of "FATAL" when all listeners have been called (listeners can update the event severity). Please note that an implementation of `org.apache.fop.events.EventExceptionManager$ExceptionFactory` has to be registered for the `EventExceptionManager` to be able to construct the exception from an event.
 
-For a given application, there can be multiple event models active at the same time. In FOP, each renderer is considered to be a plug-in and provides its own specific event model. The individual event models are provided through an `EventModelFactory` . This interface is implemented for each event model and registered through the service provider mechanism (see the [plug-ins section](#plug-ins) for details).
+For a given application, there can be multiple event models active at the same time. In FOP, each renderer is considered to be a plug-in and provides its own specific event model. The individual event models are provided through an `EventModelFactory`. This interface is implemented for each event model and registered through the service provider mechanism (see the [plug-ins section](#plug-ins) for details).
 
 ### Event severity <a id="event-severity"></a>
 
@@ -212,7 +212,7 @@ The event subsystem is extensible. There
 
 -  **`org.apache.fop.events.EventExceptionManager$ExceptionFactory`:** Creates exceptions for events, i.e. turns an event into a specific exception.
 
-The names in bold above are used as filenames for the service provider files that are placed in the `META-INF/services` directory. That way, they are automatically detected. This is a mechanism defined by the [JAR file specification](http://java.sun.com/j2se/1.4.2/docs/guide/jar/jar.html#Service%20Provider) .
+The names in bold above are used as filenames for the service provider files that are placed in the `META-INF/services` directory. That way, they are automatically detected. This is a mechanism defined by the [JAR file specification](http://java.sun.com/j2se/1.4.2/docs/guide/jar/jar.html#Service%20Provider).
 
 ### Localization (L10n) <a id="l10n"></a>
 

Modified: xmlgraphics/site/trunk/content/fop/1.1/extensions.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.1/extensions.mdtext?rev=1417307&r1=1417306&r2=1417307&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.1/extensions.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.1/extensions.mdtext Wed Dec  5 08:19:09 2012
@@ -23,7 +23,7 @@ By convention, FO extensions in FOP use 
 
 ### PDF Bookmarks <a id="bookmarks"></a>
 
-In old 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 [bookmark feature defined in the W3C XSL 1.1 standard](http://www.w3.org/TR/xsl11/#fo_bookmark-tree) .
+In old 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 [bookmark feature defined in the W3C XSL 1.1 standard](http://www.w3.org/TR/xsl11/#fo_bookmark-tree).
 
 ### Anchors or Named Destinations <a id="named-destinations"></a>
 
@@ -48,7 +48,7 @@ This feature is incomplete. Support for 
 
 This is a proprietary extension element which allows to add whole images as pages to an FO document. For example, if you have a scanned document or a fax as multi-page TIFF file, you can append or insert this document using the `fox:external-document` element. Each page of the external document will create one full page in the target format.
 
-The `fox:external-document` element is structurally a peer to `fo:page-sequence` , so wherever you can put an `fo:page-sequence` you could also place a `fox:external-document` . Therefore, the specified contents for `fo:root` change to:
+The `fox:external-document` element is structurally a peer to `fo:page-sequence`, so wherever you can put an `fo:page-sequence` you could also place a `fox:external-document`. Therefore, the specified contents for `fo:root` change to:
 
     (layout-master-set, declarations?, bookmark-tree?, (page-sequence|page-sequence-wrapper|fox:external-document|fox:destination)+)
 
@@ -56,7 +56,7 @@ The `fox:external-document` element is s
 
 The `fox:external-document` extension formatting object is used to specify how to create a (sub-)sequence of pages within a document. The content of these pages comes from the individual subimages/pages of an image or paged document (for example: multi-page TIFF in the form of faxes or scanned documents, or PDF files). The formatting object creates the necessary areas to display one image per page.
 
-In terms of page numbers, the behaviour is the same as for `fo:page-sequence` . The placement of the image inside the page is similar to that of `fo:external-graphic` or `fo:instream-foreign-object` , i.e. the viewport (and therefore the page size) is defined by either the intrinsic size of the image or by the size properties that apply to this formatting object.
+In terms of page numbers, the behaviour is the same as for `fo:page-sequence`. The placement of the image inside the page is similar to that of `fo:external-graphic` or `fo:instream-foreign-object`, i.e. the viewport (and therefore the page size) is defined by either the intrinsic size of the image or by the size properties that apply to this formatting object.
 
 Content: EMPTY
 
@@ -103,7 +103,7 @@ Datatype "page-set": Value: auto | <inte
  `fox:external-document` is not suitable for concatenating FO documents. For this, XInclude is recommended.
 ### Free-form Transformation for fo:block-container <a id="transform"></a>
 
-For `fo:block-container` elements whose `absolute-position` set to "absolute" or "fixed" you can use the extension attribute `fox:transform` to apply a free-form transformation to the whole block-container. The content of the `fox:transform` attribute is the same as for [SVG's transform attribute](http://www.w3.org/TR/SVG/coords.html#TransformAttribute) . The transformation specified here is performed in addition to other implicit transformations of the block-container (resulting from top, left and other properties) and after them.
+For `fo:block-container` elements whose `absolute-position` set to "absolute" or "fixed" you can use the extension attribute `fox:transform` to apply a free-form transformation to the whole block-container. The content of the `fox:transform` attribute is the same as for [SVG's transform attribute](http://www.w3.org/TR/SVG/coords.html#TransformAttribute). The transformation specified here is performed in addition to other implicit transformations of the block-container (resulting from top, left and other properties) and after them.
 
 Examples: `fox:transform="rotate(45)"` would rotate the block-container by 45 degrees clock-wise around its upper-left corner. `fox:transform="translate(10000,0)"` would move the block-container to the right by 10 points (=10000 millipoints, FOP uses millipoints internally!).
 This extension attribute doesn't work for all output formats! It's currently only supported for PDF, PS and Java2D-based renderers.

Modified: xmlgraphics/site/trunk/content/fop/1.1/fonts.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.1/fonts.mdtext?rev=1417307&r1=1417306&r2=1417307&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.1/fonts.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.1/fonts.mdtext Wed Dec  5 08:19:09 2012
@@ -41,7 +41,7 @@ When FOP does not have a specific font a
 
 ## Missing Glyphs <a id="missing-glyphs"></a>
 
-Every font contains a particular set of [glyphs](http://en.wikipedia.org/wiki/Glyph) . If no glyph can be found for a given character, FOP will issue a warning and use the glpyh for "#" (if available) instead. Before it does that, it consults a (currently hard-coded) registry of glyph substitution groups (see Glyphs.java in Apache XML Graphics Commons). This registry can supply alternative glyphs in some cases (like using space when a no-break space is requested). But there's no guarantee that the result will be as expected (for example, in the case of hyphens and similar glyphs). A better way is to use a font that has all the necessary glyphs. This glyph substitution is only a last resort.
+Every font contains a particular set of [glyphs](http://en.wikipedia.org/wiki/Glyph). If no glyph can be found for a given character, FOP will issue a warning and use the glpyh for "#" (if available) instead. Before it does that, it consults a (currently hard-coded) registry of glyph substitution groups (see Glyphs.java in Apache XML Graphics Commons). This registry can supply alternative glyphs in some cases (like using space when a no-break space is requested). But there's no guarantee that the result will be as expected (for example, in the case of hyphens and similar glyphs). A better way is to use a font that has all the necessary glyphs. This glyph substitution is only a last resort.
 
 ## Java2D/AWT/Operating System Fonts <a id="awt"></a>
 
@@ -51,7 +51,7 @@ When working with one of these output fo
 
 ## Custom Fonts <a id="custom"></a>
 
-Support for custom fonts is highly output format dependent (see above table). This section shows how to add Type 1 and TrueType fonts to the PDF, PostScript and Java2D-based renderers. Other renderers (like AFP) support other font formats. Details in this case can be found on the page about [output formats](output.html) .
+Support for custom fonts is highly output format dependent (see above table). This section shows how to add Type 1 and TrueType fonts to the PDF, PostScript and Java2D-based renderers. Other renderers (like AFP) support other font formats. Details in this case can be found on the page about [output formats](output.html).
 
 In earlier FOP versions, it was always necessary to create an XML font metrics file if you wanted to add a custom font. This unconvenient step has been removed and in addition to that, FOP supports auto-registration of fonts, i.e. FOP can find fonts installed in your operating system or can scan user-specified directories for fonts. Font registration via XML font metrics file is still supported and may still be necessary for some very special cases as fallback variant while we stabilize font auto-detection.
 
@@ -86,7 +86,7 @@ Review the documentation for [FOP Config
 
 ### Register Fonts with FOP <a id="register"></a>
 
-You must tell FOP how to find and use the font files by registering them in the [FOP Configuration](configuration.html) . Add entries for your custom fonts, regardless of font type, to the configuration file in a manner similar to the following:
+You must tell FOP how to find and use the font files by registering them in the [FOP Configuration](configuration.html). Add entries for your custom fonts, regardless of font type, to the configuration file in a manner similar to the following:
 
     :::xml
     <renderers>
@@ -233,7 +233,7 @@ There are two different ways how you can
        </fonts>
     </fop>
 
-At the moment, you can only match fonts against their font-family. It is possible to use regular expressions as is shown in the second example above ("DejaVu.*"). The syntax for the regular expressions used here are the one used by the [package](http://java.sun.com/j2se/1.4/docs/api/java/util/regex/package-summary.html) . So, in the above snippet "Helvetica" and all variants of the "DejaVu" font family are referenced. If you want to reference all fonts, just specify `font-family=".*"` .
+At the moment, you can only match fonts against their font-family. It is possible to use regular expressions as is shown in the second example above ("DejaVu.*"). The syntax for the regular expressions used here are the one used by the [package](http://java.sun.com/j2se/1.4/docs/api/java/util/regex/package-summary.html). So, in the above snippet "Helvetica" and all variants of the "DejaVu" font family are referenced. If you want to reference all fonts, just specify `font-family=".*"`.
 
 The `referenced-fonts` element can be placed either inside the general `fonts` element (right under the root) or in the `fonts` element under the renderer configuration. In the first case, matches apply to all renderers. In the second case, matches only apply to the renderer where the element was specified. Both cases can be used at the same time.
 
@@ -296,4 +296,4 @@ Character-by-Character is NOT yet suppor
 
 ## Font List Command-Line Tool <a id="font-list"></a>
 
-FOP contains a small command-line tool that lets you generate a list of all configured fonts. Its class name is: `org.apache.fop.tools.fontlist.FontListMain` . Run it with the "-?" parameter to get help for the various options.
+FOP contains a small command-line tool that lets you generate a list of all configured fonts. Its class name is: `org.apache.fop.tools.fontlist.FontListMain`. Run it with the "-?" parameter to get help for the various options.

Modified: xmlgraphics/site/trunk/content/fop/1.1/graphics.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.1/graphics.mdtext?rev=1417307&r1=1417306&r2=1417307&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.1/graphics.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.1/graphics.mdtext Wed Dec  5 08:19:09 2012
@@ -14,7 +14,7 @@ Some noteworthy features of the image ha
 
 - A plug-in mechanism offers a possibility to add support for new formats without changing the FOP's source code.
 
-The actual [image loading framework](http://xmlgraphics.apache.org/commons/image-loader.html) does not reside in Apache FOP, but in [XML Graphics Commons](http://xmlgraphics.apache.org/commons/) .
+The actual [image loading framework](http://xmlgraphics.apache.org/commons/image-loader.html) does not reside in Apache FOP, but in [XML Graphics Commons](http://xmlgraphics.apache.org/commons/).
 
 ## Overview of Graphics Support <a id="support-overview"></a>
 
@@ -70,13 +70,13 @@ Legend:
 
 ### FOP Native <a id="fop-native"></a>
 
-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](http://xmlgraphics.apache.org/batik/) .
+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](http://xmlgraphics.apache.org/batik/).
 
 ### Apache Batik <a id="batik"></a>
 
  [Apache Batik](http://xmlgraphics.apache.org/batik/) will later receive the SVG and WMF plug-ins for the image loading framework that are currently hosted inside FOP.
 
-Current FOP distributions include a distribution of the [Apache Batik](http://xmlgraphics.apache.org/batik/) . Because Batik's API changes frequently, it is highly recommended that you use the version that ships with FOP, at least when running FOP.
+Current FOP distributions include a distribution of the [Apache Batik](http://xmlgraphics.apache.org/batik/). Because Batik's API changes frequently, it is highly recommended that you use the version that ships with FOP, at least when running FOP.
 <warning>Batik must be run in a graphical environment.</warning>
 Batik must be run in a graphical environment. It uses AWT classes for rendering SVG, which in turn require an X server on Unixish systems. If you run a server without X, or if you can't connect to the X server due to security restrictions or policies (a so-called "headless" environment), SVG rendering will fail.
 
@@ -87,7 +87,7 @@ Here are some workarounds:
 
 - Install an X server which provides an in-memory framebuffer without actually using a screen device or any display hardware. One example is Xvfb.
 
-- Install a toolkit which emulates AWT without the need for an underlying X server. One example is the [PJA toolkit](http://www.eteks.com/pja/en) , which is free and comes with detailed installation instructions.
+- Install a toolkit which emulates AWT without the need for an underlying X server. One example is the [PJA toolkit](http://www.eteks.com/pja/en), which is free and comes with detailed installation instructions.
 
 ### Image I/O <a id="imageio"></a>
 
@@ -125,13 +125,13 @@ PNG images are supported through an Imag
 
 #### Introduction<a id="svg-intro"></a>
 
-FOP uses [Apache Batik](#batik) for SVG support. This format can be handled as an `fo:instream-foreign-object` or in a separate file referenced with `fo:external-graphic` .
+FOP uses [Apache Batik](#batik) for SVG support. This format can be handled as an `fo:instream-foreign-object` or in a separate file referenced with `fo:external-graphic`.
 Batik's SVG Rasterizer utility may also be used to convert standalone SVG documents into PDF. For more information please see the [SVG Rasterizer documentation](http://xmlgraphics.apache.org/batik/svgrasterizer.html) on the Batik site.
 #### Placing SVG Graphics into PDF<a id="svg-pdf-graphics"></a>
 
 The SVG is rendered into PDF by using PDF commands to draw and fill lines and curves. This means that the graphical objects created with this remain as vector graphics. The same applies to PostScript output. For other output formats the SVG graphic may be converted to a bitmap image.
 
-There are a number of SVG things that cannot be converted directly into PDF. Parts of the graphic such as effects, patterns and images are inserted into the PDF as a raster graphic. The resolution of these raster images can be controlled through the "target resolution" setting in the [configuration](configuration.html) .
+There are a number of SVG things that cannot be converted directly into PDF. Parts of the graphic such as effects, patterns and images are inserted into the PDF as a raster graphic. The resolution of these raster images can be controlled through the "target resolution" setting in the [configuration](configuration.html).
 
 Currently transparency is limited in PDF so some SVG images that contain effects or graphics with transparent areas may not be displayed correctly.
 
@@ -151,7 +151,7 @@ Whenever an SVG is converted into a PDF 
 
 #### Scaling<a id="svg-scaling"></a>
 
-Currently, SVG images are rendered with the dimensions specified *in the SVG file* , within the viewport specified in the fo:external-graphic element. For everything to work properly, the two should be equal. The SVG standard leaves this issue as an implementation detail. Additional scaling options are available through XSL-FO means.
+Currently, SVG images are rendered with the dimensions specified *in the SVG file*, within the viewport specified in the fo:external-graphic element. For everything to work properly, the two should be equal. The SVG standard leaves this issue as an implementation detail. Additional scaling options are available through XSL-FO means.
 
 If you use pixels to specify the size of an SVG graphic the "source resolution" setting in the [configuration](configuration.html) will be used to determine the size of a pixel. The use of pixels to specify sizes is discouraged as they may be interpreted differently in different environments.
 
@@ -174,7 +174,7 @@ There may be some limitation concerning 
 
 ### WMF <a id="wmf"></a>
 
-Windows Metafiles (WMF) are supported through classes in [Apache Batik](http://xmlgraphics.apache.org/batik/) . At the moment, support for this format is experimental and may not always work as expected.
+Windows Metafiles (WMF) are supported through classes in [Apache Batik](http://xmlgraphics.apache.org/batik/). At the moment, support for this format is experimental and may not always work as expected.
 
 ## Graphics Resolution <a id="resolution"></a>
 
@@ -194,4 +194,4 @@ FOP caches images between runs. There is
 
 The image cache has been improved considerably in the redesigned code. Therefore, resetting the image cache should be a thing of the past. If you still experience OutOfMemoryErrors, please notify us.
 
-If all else fails, the image cache can be cleared like this: `fopFactory.getImageManager().getCache().clearCache();` 
+If all else fails, the image cache can be cleared like this: `fopFactory.getImageManager().getCache().clearCache();`

Modified: xmlgraphics/site/trunk/content/fop/1.1/hyphenation.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.1/hyphenation.mdtext?rev=1417307&r1=1417306&r2=1417307&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.1/hyphenation.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.1/hyphenation.mdtext Wed Dec  5 08:19:09 2012
@@ -10,27 +10,27 @@ Title: Apache(tm) FOP: Hyphenation
 Apache&trade; FOP uses Liang's hyphenation algorithm, well known from TeX. It needs language specific pattern and other data for operation.
 
 Because of [licensing issues](#license-issues) (and for convenience), all hyphenation patterns for FOP are made available through the [Objects For Formatting Objects](http://offo.sourceforge.net/hyphenation/index.html) project.
-If you have made improvements to an existing Apache&trade; FOP hyphenation pattern, or if you have created one from scratch, please consider contributing these to OFFO so that they can benefit other FOP users as well. Please inquire on the [FOP User mailing list](../maillist.html#fop-user) .
+If you have made improvements to an existing Apache&trade; FOP hyphenation pattern, or if you have created one from scratch, please consider contributing these to OFFO so that they can benefit other FOP users as well. Please inquire on the [FOP User mailing list](../maillist.html#fop-user).
 
 ### License Issues <a id="license-issues"></a>
 
-Many of the hyphenation files distributed with TeX and its offspring are licenced under the [LaTeX Project Public License (LPPL)](http://www.latex-project.org/lppl.html) , which prevents them from being distributed with Apache software. The LPPL puts restrictions on file names in redistributed derived works which we feel can't guarantee. Some hyphenation pattern files have other or additional restrictions, for example against use for commercial purposes.
+Many of the hyphenation files distributed with TeX and its offspring are licenced under the [LaTeX Project Public License (LPPL)](http://www.latex-project.org/lppl.html), which prevents them from being distributed with Apache software. The LPPL puts restrictions on file names in redistributed derived works which we feel can't guarantee. Some hyphenation pattern files have other or additional restrictions, for example against use for commercial purposes.
 
 Although Apache FOP cannot redistribute hyphenation pattern files that do not conform with its license scheme, that does not necessarily prevent users from using such hyphenation patterns with FOP. However, it does place on the user the responsibility for determining whether the user can rightly use such hyphenation patterns under the hyphenation pattern license.
 <warning>The user is responsible to settle license issues for hyphenation pattern files that are obtained from non-Apache sources.</warning>
 
 ### Sources of Custom Hyphenation Pattern Files <a id="sources"></a>
 
-The most important source of hyphenation pattern files is the [CTAN TeX Archive](http://www.ctan.org/tex-archive/language/hyphenation/) .
+The most important source of hyphenation pattern files is the [CTAN TeX Archive](http://www.ctan.org/tex-archive/language/hyphenation/).
 
 ### Installing Custom Hyphenation Patterns <a id="install"></a>
 
 To install a custom hyphenation pattern for use with FOP:
 
 
-1. Convert the TeX hyphenation pattern file to the FOP format. The FOP format is an xml file conforming to the DTD found at `{fop-dir}/hyph/hyphenation.dtd` .
+1. Convert the TeX hyphenation pattern file to the FOP format. The FOP format is an xml file conforming to the DTD found at `{fop-dir}/hyph/hyphenation.dtd`.
 
-1. Name this new file following this schema: `languageCode_countryCode.xml` . The country code is optional, and should be used only if needed. For example:
+1. Name this new file following this schema: `languageCode_countryCode.xml`. The country code is optional, and should be used only if needed. For example:
 
 -  `en_US.xml` would be the file name for American English hyphenation patterns.
 
@@ -41,12 +41,12 @@ The language and country codes must matc
 
 - Download the precompiled JAR from [OFFO](http://offo.sourceforge.net/hyphenation/index.html) and place it either in the `{fop-dir}/lib` directory, or in a directory of your choice (and append the full path to the JAR to the environment variable `FOP_HYPHENATION_PATH` ).
 
-- Download the desired FOP-compatible hyphenation pattern file(s) from [OFFO](http://offo.sourceforge.net/hyphenation/index.html) , and/or take your self created hyphenation pattern file(s),
+- Download the desired FOP-compatible hyphenation pattern file(s) from [OFFO](http://offo.sourceforge.net/hyphenation/index.html), and/or take your self created hyphenation pattern file(s),
 
-    - place them in the directory `{fop-dir}/hyph` ,
+    - place them in the directory `{fop-dir}/hyph`,
 
     - or place them in a directory of your choice and set the Ant variable `user.hyph.dir` to point to that directory (in `build-local.properties` ),
-and run Ant with build target `jar-hyphenation` . This will create a JAR containing the compiled patterns in `{fop-dir}/build` that will be added to the classpath on the next run. (When FOP is built from scratch, and there are pattern source file(s) present in the directory pointed to by the `user.hyph.dir` variable, this JAR will automatically be created from the supplied pattern(s)).
+and run Ant with build target `jar-hyphenation`. This will create a JAR containing the compiled patterns in `{fop-dir}/build` that will be added to the classpath on the next run. (When FOP is built from scratch, and there are pattern source file(s) present in the directory pointed to by the `user.hyph.dir` variable, this JAR will automatically be created from the supplied pattern(s)).
 
 - Put the pattern source file(s) into a directory of your choice and configure FOP to look for custom patterns in this directory, by setting the [<hyphenation-base>](configuration.html) configuration option.
 
@@ -54,7 +54,7 @@ and run Ant with build target `jar-hyphe
 ## Hyphenation Patterns <a id="patterns"></a>
 
 If you would like to build your own hyphenation pattern files, or modify existing ones, this section will help you understand how to do so. Even when creating a pattern file from scratch, it may be beneficial to start with an existing file and modify it. See [OFFO's Hyphenation page](http://offo.sourceforge.net/hyphenation/index.html) for examples. Here is a brief explanation of the contents of FOP's hyphenation patterns:
-<warning>The remaining content of this section should be considered "draft" quality. It was drafted from theoretical literature, and has not been tested against actual FOP behavior. It may contain errors or omissions. Do not rely on these instructions without testing everything stated here. If you use these instructions, please provide feedback on the [FOP User mailing list](../maillist.html#fop-user) , either confirming their accuracy, or raising specific problems that we can address.</warning>
+<warning>The remaining content of this section should be considered "draft" quality. It was drafted from theoretical literature, and has not been tested against actual FOP behavior. It may contain errors or omissions. Do not rely on these instructions without testing everything stated here. If you use these instructions, please provide feedback on the [FOP User mailing list](../maillist.html#fop-user), either confirming their accuracy, or raising specific problems that we can address.</warning>
 
 - The root of the pattern file is the <hyphenation-info> element.
 
@@ -80,7 +80,7 @@ This element is unused and not even read
     - numeric characters represent a scoring system for indicating the acceptability of a hyphen in this location. Odd numbers represent an acceptable location for a hyphen, with higher values overriding lower inhibiting values. Even numbers indicate an unacceptable location, with higher values overriding lower values indicating an acceptable position. A value of zero (inhibiting) is implied when there is no number present. Generally patterns are constructed so that valuse greater than 4 are rare. Due to a bug currently patterns with values of 8 and greater don't have an effect, so don't wonder.
 Here are some examples from the English patterns file:
 
-    - Knuth ( *The TeXBook* , Appendix H) uses the example **hach4** , which indicates that it is extremely undesirable to place a hyphen after the substring "hach", for example in the word "toothach-es".
+    - Knuth ( *The TeXBook*, Appendix H) uses the example **hach4**, which indicates that it is extremely undesirable to place a hyphen after the substring "hach", for example in the word "toothach-es".
 
     -  **.leg5e** indicates that "leg-e", when it occurs at the beginning of a word, is a very good place to place a hyphen, if one is needed. Words like "leg-end" and "leg-er-de-main" fit this pattern.
 Note that the algorithm that uses this data searches for each of the word's substrings in the patterns, and chooses the *highest* value found for letter combination.
@@ -89,4 +89,4 @@ If you want to convert a TeX hyphenation
 
 Note that FOP does not do Unicode character normalization. If you use combining chars for accents and other character decorations, you must declare character classes for them, and use the same sequence of base character and combining marks in the XSLFO source, otherwise the pattern wouldn't match. Fortunately, Unicode provides precomposed characters for all important cases in common languages, until now nobody run seriously into this issue. Some dead languages and dialects, especially ancient ones, may pose a real problem though.
 
-If you want to generate your own patterns, an open-source utility called patgen can be used to assist in creating pattern files from dictionaries. It is available in many Unix/Linux distributions and every TeX distribution. Pattern creation for languages like english or german is an art. Read Frank Liang's original paper ["Word Hy-phen-a-tion by Com-pu-ter"](http://www.tug.org/docs/liang/) (yes, with hyphens) for details. The original patgen.web source, included in the TeX source distributions, contains valuable comments, unfortunately technical details often obscure the high level issues. Another important source of information is [The TeX Book](http://mirrors.ctan.org/systems/knuth/dist/tex/texbook.tex) , appendix H (either read the TeX source, or run it through TeX to typeset it). Secondary articles, for example the works by Petr Sojka, may also give some much needed insight into problems arising in automated hyphenation.
+If you want to generate your own patterns, an open-source utility called patgen can be used to assist in creating pattern files from dictionaries. It is available in many Unix/Linux distributions and every TeX distribution. Pattern creation for languages like english or german is an art. Read Frank Liang's original paper ["Word Hy-phen-a-tion by Com-pu-ter"](http://www.tug.org/docs/liang/) (yes, with hyphens) for details. The original patgen.web source, included in the TeX source distributions, contains valuable comments, unfortunately technical details often obscure the high level issues. Another important source of information is [The TeX Book](http://mirrors.ctan.org/systems/knuth/dist/tex/texbook.tex), appendix H (either read the TeX source, or run it through TeX to typeset it). Secondary articles, for example the works by Petr Sojka, may also give some much needed insight into problems arising in automated hyphenation.

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=1417307&r1=1417306&r2=1417307&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.1/index.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.1/index.mdtext Wed Dec  5 08:19:09 2012
@@ -16,4 +16,4 @@ If you're upgrading to this version from
 
 ## Download <a id="download"></a>
 
-To download this version, please visit the [download page](../download.html) .
\ No newline at end of file
+To download this version, please visit the [download page](../download.html).
\ No newline at end of file

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=1417307&r1=1417306&r2=1417307&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.1/intermediate.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.1/intermediate.mdtext Wed Dec  5 08:19:09 2012
@@ -5,7 +5,7 @@ Title: Apache(tm) FOP: Intermediate Form
 Please note that the intermediate formats described here are **advanced features** and can be ignored by most users of Apache&trade; FOP.
 ## Introduction <a id="introduction"></a>
 
-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).
+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).
 
 The second intermediate format (which we shall name exactly like this: the intermediate format) is a recent addition which tries to meet a slightly different set of goals. It is highly optimized for speed.
 
@@ -37,7 +37,7 @@ Both formats have their use cases, so th
 
 - Recommended for use cases where documents are formatted concurrently and later concatenated to a single print job.
 
-More technical information about the two formats can be found on the [FOP Wiki](http://wiki.apache.org/xmlgraphics-fop/AreaTreeIntermediateXml/NewDesign) .
+More technical information about the two formats can be found on the [FOP Wiki](http://wiki.apache.org/xmlgraphics-fop/AreaTreeIntermediateXml/NewDesign).
 
 ## Architectural Overview <a id="architecture"></a>
 
@@ -159,4 +159,4 @@ For certain output formats there's a cav
 
 ### Advanced Use <a id="advanced-if"></a>
 
-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()` ).
+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=1417307&r1=1417306&r2=1417307&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.1/knownissues_overview.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.1/knownissues_overview.mdtext Wed Dec  5 08:19:09 2012
@@ -10,9 +10,9 @@ This page lists currently known issues i
 For additional information on known issues in Apache&trade; FOP, please have a look at the following pages, too:
 
 
--  [the bug list in Bugzilla](../bugs.html) 
+-  [the bug list in Bugzilla](../bugs.html)
 
--  [the task list in the Wiki](http://wiki.apache.org/xmlgraphics-fop/FOPProjectTasks) 
+-  [the task list in the Wiki](http://wiki.apache.org/xmlgraphics-fop/FOPProjectTasks)
 
 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.
 
@@ -20,7 +20,7 @@ Apache&trade; FOP has an extensive autom
 
 This section lists disabled test cases in the test suite for the FO tree tests, at the time of the release.
 
- **demo-test-failure.fo** (demo test failure):<br></br> *TODO: Add missing description in disabled-testcases.xml!* 
+ **demo-test-failure.fo** (demo test failure):<br></br> *TODO: Add missing description in disabled-testcases.xml!*
 
 
 
@@ -96,7 +96,7 @@ This section lists disabled test cases i
 
 
 
- **inline_word-spacing_text-align_justify.xml** (inline word-spacing text-align justify):<br></br> *TODO: Add missing description in disabled-testcases.xml!* 
+ **inline_word-spacing_text-align_justify.xml** (inline word-spacing text-align justify):<br></br> *TODO: Add missing description in disabled-testcases.xml!*
 
 
 
@@ -104,7 +104,7 @@ This section lists disabled test cases i
 
 
 
- **leader_leader-pattern_use-content_bug.xml** (leader-pattern="use-content": Problem with line height):<br></br>Line height is not correctly calculated for use-content leaders whose height is larger than the rest of the line.<br></br>See also: [http://www.nabble.com/leaders-with-leader-pattern%3D%22use-content%22-t546244.html](http://www.nabble.com/leaders-with-leader-pattern%3D%22use-content%22-t546244.html) 
+ **leader_leader-pattern_use-content_bug.xml** (leader-pattern="use-content": Problem with line height):<br></br>Line height is not correctly calculated for use-content leaders whose height is larger than the rest of the line.<br></br>See also: [http://www.nabble.com/leaders-with-leader-pattern%3D%22use-content%22-t546244.html](http://www.nabble.com/leaders-with-leader-pattern%3D%22use-content%22-t546244.html)
 
 
 
@@ -170,12 +170,12 @@ This section lists disabled test cases i
 
 ### Other known issues <a id="Other+known+issues"></a>
 
-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](http://issues.apache.org/bugzilla/buglist.cgi?chfieldto=2010-07-20&chfield=%5BBug%20creation%5D&query_format=advanced&chfieldfrom=2001-01-01&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=NEEDINFO&product=Fop) . For all open issues that post-date FOP 1.0, see [newer bugs that remain open](http://issues.apache.org/bugzilla/buglist.cgi?chfieldto=Now&chfield=%5BBug%20creation%5D&query_format=advanced&chfieldfrom=2010-07-20&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=NEEDINFO&product=Fop) .
+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](http://issues.apache.org/bugzilla/buglist.cgi?chfieldto=2010-07-20&chfield=%5BBug%20creation%5D&query_format=advanced&chfieldfrom=2001-01-01&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=NEEDINFO&product=Fop). For all open issues that post-date FOP 1.0, see [newer bugs that remain open](http://issues.apache.org/bugzilla/buglist.cgi?chfieldto=Now&chfield=%5BBug%20creation%5D&query_format=advanced&chfieldfrom=2010-07-20&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=NEEDINFO&product=Fop).
 
 
-- Support for Unicode characters outside of the Base Multilingual Plane (BMP), i.e., characters whose code points are greater than 65535, is not yet implemented. See [bug 51843](http://issues.apache.org/bugzilla/show_bug.cgi?id=51843) .
+- Support for Unicode characters outside of the Base Multilingual Plane (BMP), i.e., characters whose code points are greater than 65535, is not yet implemented. See [bug 51843](http://issues.apache.org/bugzilla/show_bug.cgi?id=51843).
 
-- The writing-mode property does not produce the expected behavior when specified on `fo:simple-page-master` or `fo:region-*` elements. See [bug 53276](http://issues.apache.org/bugzilla/show_bug.cgi?id=53276) .
+- The writing-mode property does not produce the expected behavior when specified on `fo:simple-page-master` or `fo:region-*` elements. See [bug 53276](http://issues.apache.org/bugzilla/show_bug.cgi?id=53276).
 
 - Support for Devanagari and other Indic scripts is not yet complete.
 

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=1417307&r1=1417306&r2=1417307&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.1/metadata.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.1/metadata.mdtext Wed Dec  5 08:19:09 2012
@@ -5,13 +5,13 @@ Title: Apache(tm) FOP: Metadata
 
 ## Overview <a id="overview"></a>
 
-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.
+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 <a id="xmp-in-fo"></a>
 
 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).
+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 <a id="xmp-example"></a>
 
@@ -48,7 +48,7 @@ Originally, you could set some metadata 
 
 Apache FOP now synchronizes the Info and the Metadata object in PDF, i.e. when you set the title and the author through the FOUserAgent, the two values will end up in the (old) Info object and in the new Metadata object as XMP content. If instead of FOUserAgent, you embed XMP metadata in the XSL-FO document (as shown above), the XMP metadata will be used as-is in the PDF Metadata object and some values from the XMP metadata will be copied to the Info object to maintain backwards-compatibility for PDF readers that don't support XMP metadata.
 
-The mapping between the Info and the Metadata object used by Apache FOP comes from the [PDF/A-1 specification](http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=38920) . For convenience, here's the mapping table:
+The mapping between the Info and the Metadata object used by Apache FOP comes from the [PDF/A-1 specification](http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=38920). For convenience, here's the mapping table:
 
 | Document information dictionary<br/>Entry | PDF type | XMP Property | XMP type | XMP Category |
 |-------|----------|----------|----------|----------|
@@ -60,7 +60,7 @@ The mapping between the Info and the Met
 | Producer | text string | pdf:Producer | Text | Internal |
 | CreationDate | date | xmp:CreationDate | Date | Internal |
 | ModDate | date | xmp:ModifyDate | Date | Internal |
-"Internal" in the Category column means that the user should not set this value. It is set by the application.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"]` .
+"Internal" in the Category column means that the user should not set this value. It is set by the application.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"]`.
 
 ### Namespaces <a id="namespaces"></a>
 
@@ -81,10 +81,10 @@ Property sets (Namespaces) not listed he
 ## Links <a id="links"></a>
 
 
--  [Adobe's Extensible Metadata Platform (XMP) website](http://www.adobe.com/products/xmp/) 
+-  [Adobe's Extensible Metadata Platform (XMP) website](http://www.adobe.com/products/xmp/)
 
--  [Adobe XMP Specification](http://partners.adobe.com/public/developer/en/xmp/sdk/XMPspecification.pdf) 
+-  [Adobe XMP Specification](http://partners.adobe.com/public/developer/en/xmp/sdk/XMPspecification.pdf)
 
--  [Adobe XMP Specification](http://partners.adobe.com/public/developer/en/xmp/sdk/XMPspecification.pdf) 
+-  [Adobe XMP Specification](http://partners.adobe.com/public/developer/en/xmp/sdk/XMPspecification.pdf)
 
--  [http://dublincore.org/](http://dublincore.org/) 
+-  [http://dublincore.org/](http://dublincore.org/)

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=1417307&r1=1417306&r2=1417307&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.1/output.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.1/output.mdtext Wed Dec  5 08:19:09 2012
@@ -13,7 +13,7 @@ Most FOP renderers use a FOP-specific sy
 
 Theoretically, there's some potential to make the output of the PDF/PS renderers match the output of the Java2D-based renderers. If FOP used the font metrics from its own font subsystem but still used Java2D for text painting in the Java2D-based renderers, this could probably be achieved. However, this approach hasn't been implemented, yet.
 
-With a work-around, it is possible to match the PDF/PS output in a Java2D-based renderer pretty closely. The clue is to use the [intermediate format](intermediate.html) . The trick is to layout the document using FOP's own font subsystem but then render the document using Java2D. Here are the necessary steps (using the command-line):
+With a work-around, it is possible to match the PDF/PS output in a Java2D-based renderer pretty closely. The clue is to use the [intermediate format](intermediate.html). The trick is to layout the document using FOP's own font subsystem but then render the document using Java2D. Here are the necessary steps (using the command-line):
 
 
 1. Produce an IF file: `fop -fo myfile.fo -at application/pdf myfile.at.xml` <br></br>Specifying "application/pdf" for the "-at" parameter causes FOP to use FOP's own font subsystem (which is used by the PDF renderer). Note that no PDF file is created in this step.
@@ -31,7 +31,7 @@ With a work-around, it is possible to ma
 
 ### Output to a Printer or Other Device <a id="general-direct-output"></a>
 
-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.
+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.
 
 Here are Windows command-line examples for Postscript and PCL:
 fop ... -ps \\computername\printerfop ... -pcl \\computername\printer
@@ -44,7 +44,7 @@ Set the output MIME type to "application
 
 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.
+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 <a id="pdf-fonts"></a>
 
@@ -54,9 +54,9 @@ PDF has a set of fonts that are always a
 
 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.
 
-Another popular post-processing tool is [iText](http://www.lowagie.com/iText) , which has tools for adding security features, document properties, watermarks, and many other features to PDF files.
+Another popular post-processing tool is [iText](http://www.lowagie.com/iText), which has tools for adding security features, document properties, watermarks, and many other features to PDF files.
 <warning>Caveat: iText may swallow PDF bookmarks. But [Jens Stavnstrup tells us](http://issues.apache.org/bugzilla/show_bug.cgi?id=37589) that this doesn't happen if you use iText's PDFStamper.</warning>
-Here is some sample code that uses iText to encrypt a FOP-generated PDF. (Note that FOP now supports [PDF encryption](pdfencryption.html) . However the principles for using iText for other PDF features are similar.)
+Here is some sample code that uses iText to encrypt a FOP-generated PDF. (Note that FOP now supports [PDF encryption](pdfencryption.html). However the principles for using iText for other PDF features are similar.)
 
     :::java
     public static void main(String args[]) {
@@ -130,9 +130,9 @@ It is possible to attach/embed arbitrary
       <pdf:embedded-file src="url(file:///C:/Temp/MyTextDoc.odt)"/>
     </fo:declarations>
 
- `pdf:embedded-file` must be a child of `fo:declarations` . The "src" property is used to reference the file that is to be embedded. This property uses the "uri-specification" datatype from the XSL-FO specification. The "filename" property is optional. If it is missing the filename is automatically set from the URI/IRI of the "src" property. An optional description can also be added to further describe the file attachment.
+ `pdf:embedded-file` must be a child of `fo:declarations`. The "src" property is used to reference the file that is to be embedded. This property uses the "uri-specification" datatype from the XSL-FO specification. The "filename" property is optional. If it is missing the filename is automatically set from the URI/IRI of the "src" property. An optional description can also be added to further describe the file attachment.
 
-It is also possible to reference an embedded file from an `fo:basic-link` . Use the special "embedded-file:" URI scheme with the filename as single argument after the URI scheme. Example:
+It is also possible to reference an embedded file from an `fo:basic-link`. Use the special "embedded-file:" URI scheme with the filename as single argument after the URI scheme. Example:
 
     :::xml
     <fo:basic-link external-destination="url(embedded-file:image.jpg)">Attached Image</fo:basic-link>
@@ -462,7 +462,7 @@ Experimentation has shown that the font 
       <font-triplet name="Courier" style="normal" weight="bold"/>
     </font>
 
-By default, all manually configured fonts are embedded, unless they are matched in the [section of the configuration file](fonts.html#embedding) . However, the default fonts shown above will not be embedded.
+By default, all manually configured fonts are embedded, unless they are matched in the [section of the configuration file](fonts.html#embedding). However, the default fonts shown above will not be embedded.
 
 For double byte EBCDIC encoded character sets, there is an optional tag that must be set to prevent characters from being miscoded. This defaults to "false" if not specified.
 
@@ -613,7 +613,7 @@ The include-page-segment extension eleme
 
 The effect here is that whenever FOP encounters the URI specified in the extension, it will effectively generate code to include the page segment with the given name instead of embedding the image referenced by the URI. The URI is still required as the underlying image serves as a provider for the intrinsic size of the image (At the moment, FOP is unable to extract the intrinsic size of the page segment from an AFP resource file). For the image to appear in an AFP viewer or to be printed, the AFP resource must be available on the target device. FOP does not embed the page segment in the generated file. Please also note that page segments cannot be scaled. They are always rendered in their intrinsic size.
 
-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.
+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<a id="afp-tag-logical-element"></a>
 
@@ -678,7 +678,7 @@ Apache FOP supports embedding an externa
         <afp:include-form-map name="F1SAMP1" src="file:f1samp1.fde"/>
       </fo:declarations>
 
-The `afp:include-form-map` is to be placed as a direct child of `fo:declarations` . The `name` is an AFP resource name (max. 8 characters) and the `src` attribute is the URI identifying the external form map resource. When such a form map is embedded, you can use the `afp:invoke-medium-map` extension (described above) to invoke any medium map included in the form map.
+The `afp:include-form-map` is to be placed as a direct child of `fo:declarations`. The `name` is an AFP resource name (max. 8 characters) and the `src` attribute is the URI identifying the external form map resource. When such a form map is embedded, you can use the `afp:invoke-medium-map` extension (described above) to invoke any medium map included in the form map.
 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.
 ### Foreign Attributes <a id="afp-foreign-attributes"></a>
 
@@ -744,7 +744,7 @@ These are some known restrictions compar
 
 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) .
+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 <a id="awt"></a>
 
@@ -785,23 +785,23 @@ The TIFF and PNG renderer configuration 
 The default value for the `"color-mode"` setting is `"rgba"` which is equivalent to a 24bit RGB image with an 8bit alpha channel for transparency. Valid values are:
 
 
--  `rgba` : RGB with alpha channel (24bit + 8bit = 32bit)
+-  `rgba`: RGB with alpha channel (24bit + 8bit = 32bit)
 
--  `rgb` : RGB (24bit)
+-  `rgb`: RGB (24bit)
 
--  `gray` : gray (8bit)
+-  `gray`: gray (8bit)
 
 -  `bi-level` (or `binary` ): bi-level (1bit)
 
 Please note that there is currently no dithering or error diffusion available for bi-level bitmap output.
 
-The default value for the `"transparent-page-background"` setting is `"false"` which paints an opaque, white background for the whole image. If you set this to `"true"` , no such background will be painted and you will get a transparent image if an alpha channel is available in the output format.
+The default value for the `"transparent-page-background"` setting is `"false"` which paints an opaque, white background for the whole image. If you set this to `"true"`, no such background will be painted and you will get a transparent image if an alpha channel is available in the output format.
 
-The default value for the `"background-color"` setting is `"white"` . The color specifies in which color the page background is painted. It will only be painted if `"transparent-page-background"` is not set to `"true"` . All XSL-FO colors (including color functions) can be used.
+The default value for the `"background-color"` setting is `"white"`. The color specifies in which color the page background is painted. It will only be painted if `"transparent-page-background"` is not set to `"true"`. All XSL-FO colors (including color functions) can be used.
 
-The default value for the `"anti-aliasing"` setting is `"true"` . You can set this value to `"false"` to disable anti-aliasing and thus improve rendering speeds a bit at the loss of some image quality.
+The default value for the `"anti-aliasing"` setting is `"true"`. You can set this value to `"false"` to disable anti-aliasing and thus improve rendering speeds a bit at the loss of some image quality.
 
-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.
+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 <a id="tiff-configuration"></a>
 
@@ -833,7 +833,7 @@ The default value for the "compression" 
 
 -  `CCITT T.6` (Fax Group 4)
 
-This setting may override any setting made using the `"color-mode"` . For example, if `"CCITT T.6"` is selected, the color mode is automatically forced to `"bi-level"` because this compression format only supports bi-level images.
+This setting may override any setting made using the `"color-mode"`. For example, if `"CCITT T.6"` is selected, the color mode is automatically forced to `"bi-level"` because this compression format only supports bi-level images.
 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.
 ### Runtime Rendering Options <a id="bitmap-rendering-options"></a>
 
@@ -873,4 +873,4 @@ This format creates an SVG document that
 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.
 
 
--  [ODF (Open Document Format)](http://en.wikipedia.org/wiki/OpenDocument) : The standardized successor to OpenOffice's file format.
+-  [ODF (Open Document Format)](http://en.wikipedia.org/wiki/OpenDocument): The standardized successor to OpenOffice's file format.

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=1417307&r1=1417306&r2=1417307&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.1/pdfa.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.1/pdfa.mdtext Wed Dec  5 08:19:09 2012
@@ -5,7 +5,7 @@ Title: Apache(tm) FOP: PDF/A (ISO 19005)
 
 ## Overview <a id="overview"></a>
 
-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) .
+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 [PDFA1ConformanceNotes](http://wiki.apache.org/xmlgraphics-fop/PDFA1ConformanceNotes) page.
 
@@ -15,7 +15,7 @@ Design documentation on PDF/A can be fou
 
 Tests have been performed against jHove and Adobe Acrobat 7.0.7 (Preflight function). FOP does not validate completely against Apago's PDF Appraiser. Reasons unknown due to lack of a full license to get a detailed error protocol.
 
- **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) .
+ **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) <a id="command-line"></a>
 
@@ -64,8 +64,8 @@ The PDF profiles "PDF/X-3:2003" and "PDF
 
 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:
 
-| http://www.aiim.org/pdfa/ns/id.html |  **obsolete** , from an early draft of ISO-19005-1, used by Adobe Acrobat 7.x |
-| http://www.aiim.org/pdfa/ns/id |  **obsolete** , found in the original ISO 19005-1:2005 document |
-| http://www.aiim.org/pdfa/ns/id/ |  **correct** , found in the technical corrigendum 1 of ISO 19005-1:2005 |
+| http://www.aiim.org/pdfa/ns/id.html |  **obsolete**, from an early draft of ISO-19005-1, used by Adobe Acrobat 7.x |
+| http://www.aiim.org/pdfa/ns/id |  **obsolete**, found in the original ISO 19005-1:2005 document |
+| http://www.aiim.org/pdfa/ns/id/ |  **correct**, found in the technical corrigendum 1 of ISO 19005-1:2005 |
 
 If you get an error validating a PDF/A file in Adobe Acrobat 7.x it doesn't mean that FOP did something wrong. It's Acrobat that is at fault. This is fixed in Adobe Acrobat 8.x which uses the correct namespace as described in the technical corrigendum 1.

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=1417307&r1=1417306&r2=1417307&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.1/pdfencryption.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.1/pdfencryption.mdtext Wed Dec  5 08:19:09 2012
@@ -118,7 +118,7 @@ Cryptography support must also be presen
 "Cannot find any provider supporting RC4"
 then you don't have the needed infrastructure.
 
-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.
+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 <a id="install_crypto"></a>
 
@@ -127,8 +127,8 @@ The pure Java implementation from [Bounc
 
 1. Download the binary distribution for your JDK version.
 
-1. Unpack the distribution. Add the jar file to your classpath. A convenient way to use the jar on Linux is to simply drop it into the FOP lib directory, it will be automatically picked up by `fop.sh` .
+1. Unpack the distribution. Add the jar file to your classpath. A convenient way to use the jar on Linux is to simply drop it into the FOP lib directory, it will be automatically picked up by `fop.sh`.
 
-1. Open the `java.security` file and add<br></br> `security.provider.6=org.bouncycastle.jce.provider.BouncyCastleProvider` ,<br></br>preferably at the end of the block defining the other crypto providers. For JDK 1.4 this is detailed on [Sun's web site](http://java.sun.com/j2se/1.4/docs/guide/security/jce/JCERefGuide.html#InstallProvider) .
+1. Open the `java.security` file and add<br></br> `security.provider.6=org.bouncycastle.jce.provider.BouncyCastleProvider`,<br></br>preferably at the end of the block defining the other crypto providers. For JDK 1.4 this is detailed on [Sun's web site](http://java.sun.com/j2se/1.4/docs/guide/security/jce/JCERefGuide.html#InstallProvider).
 
 If you have any experience with Mozilla JSS or any other cryptography provider, please post it to the fop-user list.

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=1417307&r1=1417306&r2=1417307&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.1/pdfx.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.1/pdfx.mdtext Wed Dec  5 08:19:09 2012
@@ -5,7 +5,7 @@ Title: Apache(tm) FOP: PDF/X (ISO 15930)
 
 ## Overview <a id="overview"></a>
 <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/) .
+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 <a id="status"></a>
 



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


Mime
View raw message