You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@xmlgraphics.apache.org by ss...@apache.org on 2017/02/16 13:05:11 UTC
svn commit: r1783200 [1/2] - in /xmlgraphics/site/trunk/content: ./ batik/
batik/dev/ batik/tools/ batik/using/ commons/ fop/ fop/0.95/ fop/1.0/
fop/1.1/ fop/2.0/ fop/2.1/ fop/dev/ fop/trunk/
Author: ssteiner
Date: Thu Feb 16 13:05:10 2017
New Revision: 1783200
URL: http://svn.apache.org/viewvc?rev=1783200&view=rev
Log:
Fix links
Modified:
xmlgraphics/site/trunk/content/batik/contributors.mdtext
xmlgraphics/site/trunk/content/batik/dev/svg12.mdtext
xmlgraphics/site/trunk/content/batik/tools/rasterizer.mdtext
xmlgraphics/site/trunk/content/batik/uses.mdtext
xmlgraphics/site/trunk/content/batik/using/extending.mdtext
xmlgraphics/site/trunk/content/batik/using/svg-generator.mdtext
xmlgraphics/site/trunk/content/commons/image-loader.mdtext
xmlgraphics/site/trunk/content/fop/0.95/anttask.mdtext
xmlgraphics/site/trunk/content/fop/0.95/graphics.mdtext
xmlgraphics/site/trunk/content/fop/0.95/hyphenation.mdtext
xmlgraphics/site/trunk/content/fop/0.95/output.mdtext
xmlgraphics/site/trunk/content/fop/0.95/pdfencryption.mdtext
xmlgraphics/site/trunk/content/fop/0.95/releaseNotes_0.95.mdtext
xmlgraphics/site/trunk/content/fop/0.95/running.mdtext
xmlgraphics/site/trunk/content/fop/1.0/anttask.mdtext
xmlgraphics/site/trunk/content/fop/1.0/events.mdtext
xmlgraphics/site/trunk/content/fop/1.0/fonts.mdtext
xmlgraphics/site/trunk/content/fop/1.0/graphics.mdtext
xmlgraphics/site/trunk/content/fop/1.0/hyphenation.mdtext
xmlgraphics/site/trunk/content/fop/1.0/output.mdtext
xmlgraphics/site/trunk/content/fop/1.0/pdfencryption.mdtext
xmlgraphics/site/trunk/content/fop/1.0/running.mdtext
xmlgraphics/site/trunk/content/fop/1.1/anttask.mdtext
xmlgraphics/site/trunk/content/fop/1.1/events.mdtext
xmlgraphics/site/trunk/content/fop/1.1/fonts.mdtext
xmlgraphics/site/trunk/content/fop/1.1/graphics.mdtext
xmlgraphics/site/trunk/content/fop/1.1/hyphenation.mdtext
xmlgraphics/site/trunk/content/fop/1.1/output.mdtext
xmlgraphics/site/trunk/content/fop/1.1/pdfencryption.mdtext
xmlgraphics/site/trunk/content/fop/1.1/running.mdtext
xmlgraphics/site/trunk/content/fop/2.0/anttask.mdtext
xmlgraphics/site/trunk/content/fop/2.0/events.mdtext
xmlgraphics/site/trunk/content/fop/2.0/fonts.mdtext
xmlgraphics/site/trunk/content/fop/2.0/graphics.mdtext
xmlgraphics/site/trunk/content/fop/2.0/hyphenation.mdtext
xmlgraphics/site/trunk/content/fop/2.0/output.mdtext
xmlgraphics/site/trunk/content/fop/2.0/running.mdtext
xmlgraphics/site/trunk/content/fop/2.1/anttask.mdtext
xmlgraphics/site/trunk/content/fop/2.1/events.mdtext
xmlgraphics/site/trunk/content/fop/2.1/fonts.mdtext
xmlgraphics/site/trunk/content/fop/2.1/graphics.mdtext
xmlgraphics/site/trunk/content/fop/2.1/hyphenation.mdtext
xmlgraphics/site/trunk/content/fop/2.1/output.mdtext
xmlgraphics/site/trunk/content/fop/2.1/running.mdtext
xmlgraphics/site/trunk/content/fop/changes.mdtext
xmlgraphics/site/trunk/content/fop/dev/rtflib.mdtext
xmlgraphics/site/trunk/content/fop/dev/tools.mdtext
xmlgraphics/site/trunk/content/fop/faq.mdtext
xmlgraphics/site/trunk/content/fop/resources.mdtext
xmlgraphics/site/trunk/content/fop/trunk/anttask.mdtext
xmlgraphics/site/trunk/content/fop/trunk/events.mdtext
xmlgraphics/site/trunk/content/fop/trunk/fonts.mdtext
xmlgraphics/site/trunk/content/fop/trunk/graphics.mdtext
xmlgraphics/site/trunk/content/fop/trunk/hyphenation.mdtext
xmlgraphics/site/trunk/content/fop/trunk/output.mdtext
xmlgraphics/site/trunk/content/fop/trunk/running.mdtext
xmlgraphics/site/trunk/content/index.mdtext
Modified: xmlgraphics/site/trunk/content/batik/contributors.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/batik/contributors.mdtext?rev=1783200&r1=1783199&r2=1783200&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/batik/contributors.mdtext (original)
+++ xmlgraphics/site/trunk/content/batik/contributors.mdtext Thu Feb 16 13:05:10 2017
@@ -34,7 +34,7 @@ The following people are some of the Bat
-- [Bill Haneman](mailto:bill.haneman@ireland.sun.com) works for Sun Microsystems’ Desktop Enabling Middleware group in Dublin, Ireland, and implemented much of the Batik’s text support (though not SVG Fonts, thanks Bella, Dean, and David!). He is also technical lead for the [GNOME Accessibility Project](http://developer.gnome.org/projects/gap), an open project to provide an accessibility framework for Linux and Solaris(TM) desktops. A twenty-year veteran of scientific programming and application development, he is a US expatriate who plays traditional Irish music on the uilleann pipes.
+- [Bill Haneman](mailto:bill.haneman@ireland.sun.com) works for Sun Microsystems’ Desktop Enabling Middleware group in Dublin, Ireland, and implemented much of the Batik’s text support (though not SVG Fonts, thanks Bella, Dean, and David!). He is also technical lead for the [GNOME Accessibility Project](https://wiki.gnome.org/Accessibility), an open project to provide an accessibility framework for Linux and Solaris(TM) desktops. A twenty-year veteran of scientific programming and application development, he is a US expatriate who plays traditional Irish music on the uilleann pipes.
- [Vincent Hardy](mailto:vincent.hardy@eng.sun.com) is one of the founders of the SVG Batik project at Apache. He is a Senior Staff Engineer at Sun Microsystems Inc., where he is part of the XML technology center. Vincent represented Sun in the W3C’s SVG Working Group and is currently a W3C fellow in the W3C office in Sophia Antipolis, France. Vincent is the author of papers and a book on the Java 2D API.
Modified: xmlgraphics/site/trunk/content/batik/dev/svg12.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/batik/dev/svg12.mdtext?rev=1783200&r1=1783199&r2=1783200&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/batik/dev/svg12.mdtext (original)
+++ xmlgraphics/site/trunk/content/batik/dev/svg12.mdtext Thu Feb 16 13:05:10 2017
@@ -24,7 +24,7 @@ There are a few issues with the DOM Leve
JREs before 1.5 include the DOM Level 2 interfaces and this can cause problems when trying to use the DOM Level 3 versions of these same interface files (`org.w3c.dom.*`). Though the concrete Batik DOM classes implement the DOM Level 3 functionality, you won’t be able to access those methods through the `org.w3c.dom` interfaces on these earlier JREs.
-There are two ways to overcome this problem. The first is to install the DOM Level 3 interfaces using the [Endorsed Standards Override Mechanism](http://java.sun.com/j2se/1.4.2/docs/guide/standards/). Copy the file `lib/xml-apis-ext.jar` into the endorsed standards override directory and the DOM Level 3 interfaces will be visible. You can then write code against them (for example, call `Document.renameNode` directly). However, this will mean that other people cannot run or compile your code unless they have JRE 1.5 or later, or they have also installed the `xml-apis-ext.jar` in the same way.
+There are two ways to overcome this problem. The first is to install the DOM Level 3 interfaces using the [Endorsed Standards Override Mechanism](https://docs.oracle.com/javase/6/docs/technotes/guides/standards/). Copy the file `lib/xml-apis-ext.jar` into the endorsed standards override directory and the DOM Level 3 interfaces will be visible. You can then write code against them (for example, call `Document.renameNode` directly). However, this will mean that other people cannot run or compile your code unless they have JRE 1.5 or later, or they have also installed the `xml-apis-ext.jar` in the same way.
The second method, which requires less messing about with the JRE, is to cast your DOM objects to the concrete Batik DOM objects and call your DOM Level 3 methods directly on them. The Batik DOM classes are in the `org.apache.batik.dom` package. The classes named `Abstract*` implement the DOM interfaces, and also contain the DOM Level 3 methods. The advantage of this method is that for your code to compile and run in others’ environments, they need not install any jars with the endorsed standards overrides.
Modified: xmlgraphics/site/trunk/content/batik/tools/rasterizer.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/batik/tools/rasterizer.mdtext?rev=1783200&r1=1783199&r2=1783200&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/batik/tools/rasterizer.mdtext (original)
+++ xmlgraphics/site/trunk/content/batik/tools/rasterizer.mdtext Thu Feb 16 13:05:10 2017
@@ -228,7 +228,7 @@ The following table lists the attributes
| destdir | Name of an output directory. Use this with the `srcdir` attribute or `fileset` elements. The task generates the names of the output images by changing the suffix of the input file names to correspond the result image type. A suffix is added if the input file doesn’t have one. Output directories are created if they don’t exist. | Required if `srcdir` attribute or `fileset` elements are used. |
| classname | Class name of the XML parser used to parse SVG images. The value can be either the complete classname with package information included or the special name `jaxp`, which means any available parser in the `CLASSPATH` that supports JAXP. See the Batik code for the default value. | No |
-You can use `fileset` elements to select input files and directories. See the [Ant](http://ant.apache.org/) documentation to learn how to use [filesets](http://ant.apache.org/manual/CoreTypes/fileset.html).
+You can use `fileset` elements to select input files and directories. See the [Ant](http://ant.apache.org/) documentation to learn how to use [filesets](https://ant.apache.org/manual/Types/fileset.html).
### Examples of using the rasterizer task { #taskExamples}
Modified: xmlgraphics/site/trunk/content/batik/uses.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/batik/uses.mdtext?rev=1783200&r1=1783199&r2=1783200&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/batik/uses.mdtext (original)
+++ xmlgraphics/site/trunk/content/batik/uses.mdtext Thu Feb 16 13:05:10 2017
@@ -16,7 +16,7 @@ While it is hard to track projects and p
- [eDoc Studio](http://www.exurbi.com/), a page layout package, uses the Batik SVG generator to export pages to SVG.
-- [ElixirTech’s ElixirReport](http://www.elixirtech.com/ElixirReport) uses Batik for charting and for its SVG component.
+- [ElixirTech’s ElixirReport](http://www.elixirtech.com/products/Reporting.html) uses Batik for charting and for its SVG component.
- [GLIPS Graffiti](http://glipssvgeditor.sourceforge.net/) is an Open Source Extensible Full Feature Native SVG Editor.
@@ -34,7 +34,7 @@ While it is hard to track projects and p
- [OptimalJ](http://www.optimalj.com), a UML Class Diagram Editor for NetBeans, uses Batik to export SVG.
-- [Oracle Corp.’s JDeveloper10i](http://otn.oracle.com/products/jdev/content.html) uses Batik to export class diagrams in SVG. It uses the SVG export module.
+- [Oracle Corp.’s JDeveloper10i](http://www.oracle.com/technetwork/developer-tools/jdev/overview/index-094652.html) uses Batik to export class diagrams in SVG. It uses the SVG export module.
- [Sketsa](http://www.kiyut.com/) is a vector drawing application based on Batik. With Sketsa, you can create vector graphics that can be scaled and printed at any resolution, without losing detail or clarity.
Modified: xmlgraphics/site/trunk/content/batik/using/extending.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/batik/using/extending.mdtext?rev=1783200&r1=1783199&r2=1783200&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/batik/using/extending.mdtext (original)
+++ xmlgraphics/site/trunk/content/batik/using/extending.mdtext Thu Feb 16 13:05:10 2017
@@ -5,7 +5,7 @@ Title: Extending Batik
This page provides an overview of the built in extension mechanisms of Batik. As an open source project, people can of course make any extension they feel is interesting, however Batik has been designed with several forms of extension in mind.
-In general, extensions are added through the Service Provider Interface mechanism as described in the [jar file documentation](http://java.sun.com/j2se/1.4/docs/guide/jar/jar.html#Service Provider). This allows for the extension of Batik simply by adding a new jar file(s) to the class path, and thus no modification of the Batik source is required!
+In general, extensions are added through the Service Provider Interface mechanism as described in the [jar file documentation](http://docs.oracle.com/javase/1.5.0/docs/guide/jar/jar.html#Service%20Provider). This allows for the extension of Batik simply by adding a new jar file(s) to the class path, and thus no modification of the Batik source is required!
If you feel that the Batik team has overlooked an important area for extension please let your feelings be known on the mailing lists.
# Custom XML elements { #customXMLTags}
Modified: xmlgraphics/site/trunk/content/batik/using/svg-generator.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/batik/using/svg-generator.mdtext?rev=1783200&r1=1783199&r2=1783200&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/batik/using/svg-generator.mdtext (original)
+++ xmlgraphics/site/trunk/content/batik/using/svg-generator.mdtext Thu Feb 16 13:05:10 2017
@@ -268,7 +268,7 @@ Then you can create and use an `SVGGraph
## Extending Paint object to SVG element translation { #Extending-Paint-object-to-SVG-element-translation}
-The `SVGGraphics2D` is able to generate SVG elements for generic Java 2D objects, but you sometimes have your own classes such as implementations of the Java 2D [Paint](http://java.sun.com/j2se/1.4.2/docs/api/java/awt/Paint.html) interface. In this case, you will need to write an [ExtensionHandler](../javadoc/org/apache/batik/svggen/ExtensionHandler.html) that you will set on your `SVGGeneratorContext`.
+The `SVGGraphics2D` is able to generate SVG elements for generic Java 2D objects, but you sometimes have your own classes such as implementations of the Java 2D [Paint](https://docs.oracle.com/javase/7/docs/api/java/awt/Paint.html) interface. In this case, you will need to write an [ExtensionHandler](../javadoc/org/apache/batik/svggen/ExtensionHandler.html) that you will set on your `SVGGeneratorContext`.
In the following example we define the first draft of an `ExtensionHandler` allowing to translate a Batik implementation of the `Paint` interface named [LinearGradientPaint](../javadoc/org/apache/batik/ext/awt/LinearGradientPaint.html).
Modified: xmlgraphics/site/trunk/content/commons/image-loader.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/commons/image-loader.mdtext?rev=1783200&r1=1783199&r2=1783200&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/commons/image-loader.mdtext (original)
+++ xmlgraphics/site/trunk/content/commons/image-loader.mdtext Thu Feb 16 13:05:10 2017
@@ -122,7 +122,7 @@ In [Apache FOP](http://xmlgraphics.apach
# Tips & Tricks { #tipsntricks}
If you are loading bitmap images and you get an error like `"Cannot load image (no suitable loader/converter combination available) for
- myimage.tif (image/tiff)`, you maybe be missing the necessary ImageIO codec to decode the image. A number of well-written codecs can be found in [JAI Image I/O Tools Project](https://jai-imageio.dev.java.net/). Just download the distribution and add the JAR to the classpath. ImageIO will automatically pick up the new codecs and they will subsequently be available to the image framework.
+ myimage.tif (image/tiff)`, you maybe be missing the necessary ImageIO codec to decode the image. A number of well-written codecs can be found in [JAI Image I/O Tools Project](https://github.com/jai-imageio/jai-imageio-core/releases). Just download the distribution and add the JAR to the classpath. ImageIO will automatically pick up the new codecs and they will subsequently be available to the image framework.
## Service Provider Interface (SPI, Plug-ins) { #spi}
Modified: xmlgraphics/site/trunk/content/fop/0.95/anttask.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/0.95/anttask.mdtext?rev=1783200&r1=1783199&r2=1783200&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/0.95/anttask.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/0.95/anttask.mdtext Thu Feb 16 13:05:10 2017
@@ -50,7 +50,7 @@ Then create FOP tasks within your Ant bu
<caption>Parameters specified as nested elements</caption>| Attribute | Description | Required |
|-----------|-------------|----------|
-| fileset | [FileSets](http://ant.apache.org/manual/CoreTypes/fileset.html) are used to specify multiple XSL-FO files to be rendered. | Yes, if no fofile attribute is supplied |
+| fileset | [FileSets](https://ant.apache.org/manual/Types/fileset.html) are used to specify multiple XSL-FO files to be rendered. | Yes, if no fofile attribute is supplied |
## Examples { #examples}
Modified: xmlgraphics/site/trunk/content/fop/0.95/graphics.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/0.95/graphics.mdtext?rev=1783200&r1=1783199&r2=1783200&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/0.95/graphics.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/0.95/graphics.mdtext Thu Feb 16 13:05:10 2017
@@ -37,8 +37,8 @@ Legend:
- "(X)" means restricted support. Please see the details below.
-- [1]: Requires the presence of [JAI Image I/O Tools](http://jai-imageio.dev.java.net/) (or an equivalent Image I/O compatible codec) in the classpath. JAI Image I/O Tools also adds support for JPEG 2000, WBMP, RAW and PNM. Other Image I/O codecs may provide support for additional formats.
- [JAI Image I/O Tools](http://jai-imageio.dev.java.net/) is not the same as the [JAI library](http://java.sun.com/javase/technologies/desktop/media/jai/) ! The former simply exposes JAI's codecs using the Image I/O API but does not include all the image manipulation functionality.
+- [1]: Requires the presence of [JAI Image I/O Tools](https://github.com/jai-imageio/jai-imageio-core) (or an equivalent Image I/O compatible codec) in the classpath. JAI Image I/O Tools also adds support for JPEG 2000, WBMP, RAW and PNM. Other Image I/O codecs may provide support for additional formats.
+ [JAI Image I/O Tools](https://github.com/jai-imageio/jai-imageio-core) is not the same as the [JAI library](http://java.sun.com/javase/technologies/desktop/media/jai/) ! The former simply exposes JAI's codecs using the Image I/O API but does not include all the image manipulation functionality.
### Map of supported image formats by output format { #format-map}
Not all image formats are supported for all output formats! For example, while you can use EPS (Encapsulated PostScript) files when you generate PostScript output, this format will not be supported by any other output format. Here's an overview of which image formats are supported by which output format:
Modified: xmlgraphics/site/trunk/content/fop/0.95/hyphenation.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/0.95/hyphenation.mdtext?rev=1783200&r1=1783199&r2=1783200&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/0.95/hyphenation.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/0.95/hyphenation.mdtext Thu Feb 16 13:05:10 2017
@@ -9,7 +9,7 @@ Title: Apache(tm) FOP: Hyphenation
Apache™ 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.
+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) project.
If you have made improvements to an existing 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 { #license-issues}
@@ -51,7 +51,7 @@ and run Ant with build target `jar-hyphe
<warning>Either of these three options will ensure hyphenation is working when using FOP from the command-line. If FOP is being embedded, remember to add the location(s) of the hyphenation JAR(s) to the CLASSPATH (option 1 and 2) or to set the [<hyphenation-dir>](configuration.html#hyphenation-dir) configuration option programmatically (option 3).</warning>
## Hyphenation Patterns { #patterns}
-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:
+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) 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>
- The root of the pattern file is the <hyphenation-info> element.
Modified: xmlgraphics/site/trunk/content/fop/0.95/output.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/0.95/output.mdtext?rev=1783200&r1=1783199&r2=1783200&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/0.95/output.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/0.95/output.mdtext Thu Feb 16 13:05:10 2017
@@ -163,7 +163,7 @@ The output created by the PCLRenderer is
- [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)
+- [Technical reference documents on PCL from Hewlett-Packard](http://www.hp.com/ctg/Manual/bpl13210.pdf)
### Limitations { #pcl-limitations}
Modified: xmlgraphics/site/trunk/content/fop/0.95/pdfencryption.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/0.95/pdfencryption.mdtext?rev=1783200&r1=1783199&r2=1783200&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/0.95/pdfencryption.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/0.95/pdfencryption.mdtext Thu Feb 16 13:05:10 2017
@@ -79,7 +79,7 @@ Alternatively, you can set each value se
## 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.
+In order to use PDF encryption, FOP has to be compiled with cryptography support. Currently, only [JCE](https://docs.oracle.com/javase/1.5.0/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.
Cryptography support must also be present at run time. In particular, a provider for the RC4 cipher is needed. Unfortunately, the sample JCE provider in Sun's JDK 1.4 does **not** provide RC4. If you get a message saying
"Cannot find any provider supporting RC4"
@@ -98,6 +98,6 @@ The pure Java implementation from [Bounc
`security.provider.6=org.bouncycastle.jce.provider.BouncyCastleProvider`,
- 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).
+ preferably at the end of the block defining the other crypto providers. For JDK 1.4 this is detailed on [Sun's web site](https://docs.oracle.com/javase/1.5.0/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/0.95/releaseNotes_0.95.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/0.95/releaseNotes_0.95.mdtext?rev=1783200&r1=1783199&r2=1783200&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/0.95/releaseNotes_0.95.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/0.95/releaseNotes_0.95.mdtext Thu Feb 16 13:05:10 2017
@@ -22,7 +22,7 @@ If an fo:table element contains explicit
If more flexibility is needed, then the fo:table-column elements may be just omitted. The final number of columns will then be set by the row that has the most cells.
-The image libraries Jimi and JAI are no longer needed (and used) for image loading. Instead we rely completely on the Image I/O API that has been introduced with Java 1.4. If you still need support for bitmap image formats that do not work out-of-the-box, we recommend adding [JAI Image I/O Tools](http://jai-imageio.dev.java.net/) (an Image I/O compatible image codec package) to the classpath. JAI is still required for building the FOP distribution but it is optional for normal builds and at run-time.
+The image libraries Jimi and JAI are no longer needed (and used) for image loading. Instead we rely completely on the Image I/O API that has been introduced with Java 1.4. If you still need support for bitmap image formats that do not work out-of-the-box, we recommend adding [JAI Image I/O Tools](https://github.com/jai-imageio/jai-imageio-core) (an Image I/O compatible image codec package) to the classpath. JAI is still required for building the FOP distribution but it is optional for normal builds and at run-time.
This final 0.95 release also includes all of the [changes made for Apache FOP 0.95beta](changes_0.95beta.html).</section></notes>
Modified: xmlgraphics/site/trunk/content/fop/0.95/running.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/0.95/running.mdtext?rev=1783200&r1=1783199&r2=1783200&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/0.95/running.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/0.95/running.mdtext Thu Feb 16 13:05:10 2017
@@ -52,7 +52,7 @@ Some Mac OSX users have experienced file
### 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.
+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](https://java.com/en/download/faq/java_mac.xml) for information as it becomes available.
USAGE
Fop [options] [-fo|-xml] infile [-xsl file] [-awt|-pdf|-mif|-rtf|-tiff|-png|-pcl|-ps|-txt|-at [mime]|-print] <outfile>
@@ -171,7 +171,7 @@ FOP can consume quite a bit of memory, e
If you are running out of memory when using FOP, here are some ideas that may help:
-- Increase memory available to the JVM. See [the -Xmx option](http://java.sun.com/j2se/1.4/docs/tooldocs/solaris/java.html) for more information.<warning>It is usually unwise to increase the memory allocated to the JVM beyond the amount of physical RAM, as this will generally cause significantly slower performance.</warning>
+- Increase memory available to the JVM. See [the -Xmx option](http://docs.oracle.com/javase/1.5.0/docs/tooldocs/solaris/java.html) for more information.<warning>It is usually unwise to increase the memory allocated to the JVM beyond the amount of physical RAM, as this will generally cause significantly slower performance.</warning>
- Avoid forward references. Forward references are references to some later part of a document. Examples include page number citations which refer to pages which follow the citation, tables of contents at the beginning of a document, and page numbering schemes that include the total number of pages in the document (["page N of TOTAL"](../faq.html#pagenum)). Forward references cause all subsequent pages to be held in memory until the reference can be resolved, i.e. until the page with the referenced element is encountered. Forward references may be required by the task, but if you are getting a memory overflow, at least consider the possibility of eliminating them. A table of contents could be replaced by PDF bookmarks instead or moved to the end of the document (reshuffle the paper could after printing).
Modified: xmlgraphics/site/trunk/content/fop/1.0/anttask.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.0/anttask.mdtext?rev=1783200&r1=1783199&r2=1783200&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.0/anttask.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.0/anttask.mdtext Thu Feb 16 13:05:10 2017
@@ -53,7 +53,7 @@ Then create FOP tasks within your Ant bu
<caption>Parameters specified as nested elements</caption>| Attribute | Description | Required |
|-----------|-------------|----------|
-| fileset | [FileSets](http://ant.apache.org/manual/CoreTypes/fileset.html) are used to specify multiple XSL-FO files to be rendered. | Yes, if no fofile attribute is supplied |
+| fileset | [FileSets](https://ant.apache.org/manual/Types/fileset.html) are used to specify multiple XSL-FO files to be rendered. | Yes, if no fofile attribute is supplied |
## Examples { #examples}
Modified: xmlgraphics/site/trunk/content/fop/1.0/events.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.0/events.mdtext?rev=1783200&r1=1783199&r2=1783200&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.0/events.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.0/events.mdtext Thu Feb 16 13:05:10 2017
@@ -180,7 +180,7 @@ To produce the same event as in the firs
### The event model { #event-model}
-Inside an invocation handler for a dynamic proxy, there's no information about the names of each parameter. The JVM doesn't provide it. The only thing you know is the interface and method name. In order to properly fill the `Event` 's parameter map we need to know the parameter names. These are retrieved from an event object model. This is found in the `org.apache.fop.events.model` package. The data for the object model is retrieved from an XML representation of the event model that is loaded as a resource. The XML representation is generated using an Ant task at build time (`ant resourcegen`). The Ant task (found in `src/codegen/java/org/apache/fop/tools/EventProducerCollectorTask.java`) scans FOP's sources for descendants of the `EventProducer` interface and uses [QDox](http://qdox.codehaus.org/) to parse these interfaces.
+Inside an invocation handler for a dynamic proxy, there's no information about the names of each parameter. The JVM doesn't provide it. The only thing you know is the interface and method name. In order to properly fill the `Event` 's parameter map we need to know the parameter names. These are retrieved from an event object model. This is found in the `org.apache.fop.events.model` package. The data for the object model is retrieved from an XML representation of the event model that is loaded as a resource. The XML representation is generated using an Ant task at build time (`ant resourcegen`). The Ant task (found in `src/codegen/java/org/apache/fop/tools/EventProducerCollectorTask.java`) scans FOP's sources for descendants of the `EventProducer` interface and uses [QDox](https://github.com/codehaus/qdox) to parse these interfaces.
The event model XML files are generated during build by the Ant task mentioned above when running the "resourcegen" task. So just run `"ant resourcegen"` if you receive a `MissingResourceException` at runtime indicating that `"event-model.xml"` is missing.
@@ -214,7 +214,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://docs.oracle.com/javase/1.5.0/docs/guide/jar/jar.html#Service%20Provider).
### Localization (L10n) { #l10n}
Modified: xmlgraphics/site/trunk/content/fop/1.0/fonts.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.0/fonts.mdtext?rev=1783200&r1=1783199&r2=1783200&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.0/fonts.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.0/fonts.mdtext Thu Feb 16 13:05:10 2017
@@ -244,7 +244,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](https://docs.oracle.com/javase/7/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.
Modified: xmlgraphics/site/trunk/content/fop/1.0/graphics.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.0/graphics.mdtext?rev=1783200&r1=1783199&r2=1783200&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.0/graphics.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.0/graphics.mdtext Thu Feb 16 13:05:10 2017
@@ -36,9 +36,9 @@ Legend:
- "(X)" means restricted support. Please see the details below.
-- [1]: Requires the presence of [JAI Image I/O Tools](http://jai-imageio.dev.java.net/) (or an equivalent Image I/O compatible codec) in the classpath. JAI Image I/O Tools also adds support for JPEG 2000, WBMP, RAW and PNM. Other Image I/O codecs may provide support for additional formats.
+- [1]: Requires the presence of [JAI Image I/O Tools](https://github.com/jai-imageio/jai-imageio-core) (or an equivalent Image I/O compatible codec) in the classpath. JAI Image I/O Tools also adds support for JPEG 2000, WBMP, RAW and PNM. Other Image I/O codecs may provide support for additional formats.
-<note>[JAI Image I/O Tools](http://jai-imageio.dev.java.net/) is not the same as the [JAI library](http://java.sun.com/javase/technologies/desktop/media/jai/) ! The former simply exposes JAI's codecs using the Image I/O API but does not include all the image manipulation functionality.</note>
+<note>[JAI Image I/O Tools](https://github.com/jai-imageio/jai-imageio-core) is not the same as the [JAI library](http://java.sun.com/javase/technologies/desktop/media/jai/) ! The former simply exposes JAI's codecs using the Image I/O API but does not include all the image manipulation functionality.</note>
### Map of supported image formats by output format { #format-map}
Modified: xmlgraphics/site/trunk/content/fop/1.0/hyphenation.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.0/hyphenation.mdtext?rev=1783200&r1=1783199&r2=1783200&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.0/hyphenation.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.0/hyphenation.mdtext Thu Feb 16 13:05:10 2017
@@ -9,7 +9,7 @@ Title: Apache(tm) FOP: Hyphenation
Apache™ 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.
+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) project.
<note>If you have made improvements to an existing Apache™ 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).</note>
@@ -57,7 +57,7 @@ and run Ant with build target `jar-hyphe
## Hyphenation Patterns { #patterns}
-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:
+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) 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>
- The root of the pattern file is the <hyphenation-info> element.
Modified: xmlgraphics/site/trunk/content/fop/1.0/output.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.0/output.mdtext?rev=1783200&r1=1783199&r2=1783200&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.0/output.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.0/output.mdtext Thu Feb 16 13:05:10 2017
@@ -175,7 +175,7 @@ The output created by the PCLRenderer is
- [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)
+- [Technical reference documents on PCL from Hewlett-Packard](http://www.hp.com/ctg/Manual/bpl13210.pdf)
### Limitations { #pcl-limitations}
Modified: xmlgraphics/site/trunk/content/fop/1.0/pdfencryption.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.0/pdfencryption.mdtext?rev=1783200&r1=1783199&r2=1783200&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.0/pdfencryption.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.0/pdfencryption.mdtext Thu Feb 16 13:05:10 2017
@@ -81,7 +81,7 @@ Alternatively, you can set each value se
## 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.
+In order to use PDF encryption, FOP has to be compiled with cryptography support. Currently, only [JCE](https://docs.oracle.com/javase/1.5.0/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.
Cryptography support must also be present at run time. In particular, a provider for the RC4 cipher is needed. Unfortunately, the sample JCE provider in Sun's JDK 1.4 does **not** provide RC4. If you get a message saying
"Cannot find any provider supporting RC4"
@@ -101,6 +101,6 @@ The pure Java implementation from [Bounc
`security.provider.6=org.bouncycastle.jce.provider.BouncyCastleProvider`,
- 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).
+ preferably at the end of the block defining the other crypto providers. For JDK 1.4 this is detailed on [Sun's web site](https://docs.oracle.com/javase/1.5.0/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.0/running.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.0/running.mdtext?rev=1783200&r1=1783199&r2=1783200&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.0/running.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.0/running.mdtext Thu Feb 16 13:05:10 2017
@@ -52,7 +52,7 @@ Some Mac OSX users have experienced file
### 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.
+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](https://java.com/en/download/faq/java_mac.xml) for information as it becomes available.
USAGE
Fop [options] [-fo|-xml] infile [-xsl file] [-awt|-pdf|-mif|-rtf|-tiff|-png|-pcl|-ps|-txt|-at [mime]|-print] <outfile>
@@ -186,7 +186,7 @@ FOP can consume quite a bit of memory, e
If you are running out of memory when using FOP, here are some ideas that may help:
-- Increase memory available to the JVM. See [the -Xmx option](http://java.sun.com/j2se/1.4/docs/tooldocs/solaris/java.html) for more information.<warning>It is usually unwise to increase the memory allocated to the JVM beyond the amount of physical RAM, as this will generally cause significantly slower performance.</warning>
+- Increase memory available to the JVM. See [the -Xmx option](http://docs.oracle.com/javase/1.5.0/docs/tooldocs/solaris/java.html) for more information.<warning>It is usually unwise to increase the memory allocated to the JVM beyond the amount of physical RAM, as this will generally cause significantly slower performance.</warning>
- Avoid forward references. Forward references are references to some later part of a document. Examples include page number citations which refer to pages which follow the citation, tables of contents at the beginning of a document, and page numbering schemes that include the total number of pages in the document (["page N of TOTAL"](../faq.html#pagenum)). Forward references cause all subsequent pages to be held in memory until the reference can be resolved, i.e. until the page with the referenced element is encountered. Forward references may be required by the task, but if you are getting a memory overflow, at least consider the possibility of eliminating them. A table of contents could be replaced by PDF bookmarks instead or moved to the end of the document (reshuffle the paper could after printing).
Modified: xmlgraphics/site/trunk/content/fop/1.1/anttask.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.1/anttask.mdtext?rev=1783200&r1=1783199&r2=1783200&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.1/anttask.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.1/anttask.mdtext Thu Feb 16 13:05:10 2017
@@ -53,7 +53,7 @@ Then create FOP tasks within your Ant bu
<caption>Parameters specified as nested elements</caption>| Attribute | Description | Required |
|-----------|-------------|----------|
-| fileset | [FileSets](http://ant.apache.org/manual/CoreTypes/fileset.html) are used to specify multiple XSL-FO files to be rendered. | Yes, if no fofile attribute is supplied |
+| fileset | [FileSets](https://ant.apache.org/manual/Types/fileset.html) are used to specify multiple XSL-FO files to be rendered. | Yes, if no fofile attribute is supplied |
## Examples { #examples}
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=1783200&r1=1783199&r2=1783200&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.1/events.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.1/events.mdtext Thu Feb 16 13:05:10 2017
@@ -180,7 +180,7 @@ To produce the same event as in the firs
### The event model { #event-model}
-Inside an invocation handler for a dynamic proxy, there's no information about the names of each parameter. The JVM doesn't provide it. The only thing you know is the interface and method name. In order to properly fill the `Event` 's parameter map we need to know the parameter names. These are retrieved from an event object model. This is found in the `org.apache.fop.events.model` package. The data for the object model is retrieved from an XML representation of the event model that is loaded as a resource. The XML representation is generated using an Ant task at build time (`ant resourcegen`). The Ant task (found in `src/codegen/java/org/apache/fop/tools/EventProducerCollectorTask.java`) scans FOP's sources for descendants of the `EventProducer` interface and uses [QDox](http://qdox.codehaus.org/) to parse these interfaces.
+Inside an invocation handler for a dynamic proxy, there's no information about the names of each parameter. The JVM doesn't provide it. The only thing you know is the interface and method name. In order to properly fill the `Event` 's parameter map we need to know the parameter names. These are retrieved from an event object model. This is found in the `org.apache.fop.events.model` package. The data for the object model is retrieved from an XML representation of the event model that is loaded as a resource. The XML representation is generated using an Ant task at build time (`ant resourcegen`). The Ant task (found in `src/codegen/java/org/apache/fop/tools/EventProducerCollectorTask.java`) scans FOP's sources for descendants of the `EventProducer` interface and uses [QDox](https://github.com/codehaus/qdox) to parse these interfaces.
The event model XML files are generated during build by the Ant task mentioned above when running the "resourcegen" task. So just run `"ant resourcegen"` if you receive a `MissingResourceException` at runtime indicating that `"event-model.xml"` is missing.
@@ -214,7 +214,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://docs.oracle.com/javase/1.5.0/docs/guide/jar/jar.html#Service%20Provider).
### Localization (L10n) { #l10n}
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=1783200&r1=1783199&r2=1783200&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.1/fonts.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.1/fonts.mdtext Thu Feb 16 13:05:10 2017
@@ -241,7 +241,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](https://docs.oracle.com/javase/7/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.
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=1783200&r1=1783199&r2=1783200&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.1/graphics.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.1/graphics.mdtext Thu Feb 16 13:05:10 2017
@@ -36,9 +36,9 @@ Legend:
- "(X)" means restricted support. Please see the details below.
-- [1]: Requires the presence of [JAI Image I/O Tools](http://jai-imageio.dev.java.net/) (or an equivalent Image I/O compatible codec) in the classpath. JAI Image I/O Tools also adds support for JPEG 2000, WBMP, RAW and PNM. Other Image I/O codecs may provide support for additional formats.
+- [1]: Requires the presence of [JAI Image I/O Tools](https://github.com/jai-imageio/jai-imageio-core) (or an equivalent Image I/O compatible codec) in the classpath. JAI Image I/O Tools also adds support for JPEG 2000, WBMP, RAW and PNM. Other Image I/O codecs may provide support for additional formats.
-<note>[JAI Image I/O Tools](http://jai-imageio.dev.java.net/) is not the same as the [JAI library](http://java.sun.com/javase/technologies/desktop/media/jai/) ! The former simply exposes JAI's codecs using the Image I/O API but does not include all the image manipulation functionality.</note>
+<note>[JAI Image I/O Tools](https://github.com/jai-imageio/jai-imageio-core) is not the same as the [JAI library](http://java.sun.com/javase/technologies/desktop/media/jai/) ! The former simply exposes JAI's codecs using the Image I/O API but does not include all the image manipulation functionality.</note>
### Map of supported image formats by output format { #format-map}
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=1783200&r1=1783199&r2=1783200&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.1/hyphenation.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.1/hyphenation.mdtext Thu Feb 16 13:05:10 2017
@@ -9,7 +9,7 @@ Title: Apache(tm) FOP: Hyphenation
Apache™ 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.
+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) project.
<note>If you have made improvements to an existing Apache™ 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).</note>
@@ -57,7 +57,7 @@ and run Ant with build target `jar-hyphe
## Hyphenation Patterns { #patterns}
-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:
+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) 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>
- The root of the pattern file is the <hyphenation-info> element.
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=1783200&r1=1783199&r2=1783200&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.1/output.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.1/output.mdtext Thu Feb 16 13:05:10 2017
@@ -205,7 +205,7 @@ The output created by the PCLRenderer is
- [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)
+- [Technical reference documents on PCL from Hewlett-Packard](http://www.hp.com/ctg/Manual/bpl13210.pdf)
### Limitations { #pcl-limitations}
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=1783200&r1=1783199&r2=1783200&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.1/pdfencryption.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.1/pdfencryption.mdtext Thu Feb 16 13:05:10 2017
@@ -113,7 +113,7 @@ Alternatively, you can set each value se
## 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.
+In order to use PDF encryption, FOP has to be compiled with cryptography support. Currently, only [JCE](https://docs.oracle.com/javase/1.5.0/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.
Cryptography support must also be present at run time. In particular, a provider for the RC4 cipher is needed. Unfortunately, the sample JCE provider in Sun's JDK 1.4 does **not** provide RC4. If you get a message saying
"Cannot find any provider supporting RC4"
@@ -133,6 +133,6 @@ The pure Java implementation from [Bounc
`security.provider.6=org.bouncycastle.jce.provider.BouncyCastleProvider`,
- 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).
+ preferably at the end of the block defining the other crypto providers. For JDK 1.4 this is detailed on [Sun's web site](https://docs.oracle.com/javase/1.5.0/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/running.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.1/running.mdtext?rev=1783200&r1=1783199&r2=1783200&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.1/running.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.1/running.mdtext Thu Feb 16 13:05:10 2017
@@ -50,7 +50,7 @@ Some Mac OSX users have experienced file
### 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.
+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](https://java.com/en/download/faq/java_mac.xml) for information as it becomes available.
USAGE
Fop [options] [-fo|-xml] infile [-xsl file] [-awt|-pdf|-mif|-rtf|-tiff|-png|-pcl|-ps|-txt|-at [mime]|-print] <outfile>
@@ -193,7 +193,7 @@ FOP can consume quite a bit of memory, e
If you are running out of memory when using FOP, here are some ideas that may help:
-- Increase memory available to the JVM. See [the -Xmx option](http://java.sun.com/j2se/1.4/docs/tooldocs/solaris/java.html) for more information.<warning>It is usually unwise to increase the memory allocated to the JVM beyond the amount of physical RAM, as this will generally cause significantly slower performance.</warning>
+- Increase memory available to the JVM. See [the -Xmx option](http://docs.oracle.com/javase/1.5.0/docs/tooldocs/solaris/java.html) for more information.<warning>It is usually unwise to increase the memory allocated to the JVM beyond the amount of physical RAM, as this will generally cause significantly slower performance.</warning>
- Avoid forward references. Forward references are references to some later part of a document. Examples include page number citations which refer to pages which follow the citation, tables of contents at the beginning of a document, and page numbering schemes that include the total number of pages in the document (["page N of TOTAL"](../faq.html#pagenum)). Forward references cause all subsequent pages to be held in memory until the reference can be resolved, i.e. until the page with the referenced element is encountered. Forward references may be required by the task, but if you are getting a memory overflow, at least consider the possibility of eliminating them. A table of contents could be replaced by PDF bookmarks instead or moved to the end of the document (reshuffle the paper could after printing).
Modified: xmlgraphics/site/trunk/content/fop/2.0/anttask.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/2.0/anttask.mdtext?rev=1783200&r1=1783199&r2=1783200&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/2.0/anttask.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/2.0/anttask.mdtext Thu Feb 16 13:05:10 2017
@@ -53,7 +53,7 @@ Then create FOP tasks within your Ant bu
<caption>Parameters specified as nested elements</caption>| Attribute | Description | Required |
|-----------|-------------|----------|
-| fileset | [FileSets](http://ant.apache.org/manual/CoreTypes/fileset.html) are used to specify multiple XSL-FO files to be rendered. | Yes, if no fofile attribute is supplied |
+| fileset | [FileSets](https://ant.apache.org/manual/Types/fileset.html) are used to specify multiple XSL-FO files to be rendered. | Yes, if no fofile attribute is supplied |
## Examples { #examples}
Modified: xmlgraphics/site/trunk/content/fop/2.0/events.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/2.0/events.mdtext?rev=1783200&r1=1783199&r2=1783200&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/2.0/events.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/2.0/events.mdtext Thu Feb 16 13:05:10 2017
@@ -180,7 +180,7 @@ To produce the same event as in the firs
### The event model { #event-model}
-Inside an invocation handler for a dynamic proxy, there's no information about the names of each parameter. The JVM doesn't provide it. The only thing you know is the interface and method name. In order to properly fill the `Event` 's parameter map we need to know the parameter names. These are retrieved from an event object model. This is found in the `org.apache.fop.events.model` package. The data for the object model is retrieved from an XML representation of the event model that is loaded as a resource. The XML representation is generated using an Ant task at build time (`ant resourcegen`). The Ant task (found in `src/codegen/java/org/apache/fop/tools/EventProducerCollectorTask.java`) scans FOP's sources for descendants of the `EventProducer` interface and uses [QDox](http://qdox.codehaus.org/) to parse these interfaces.
+Inside an invocation handler for a dynamic proxy, there's no information about the names of each parameter. The JVM doesn't provide it. The only thing you know is the interface and method name. In order to properly fill the `Event` 's parameter map we need to know the parameter names. These are retrieved from an event object model. This is found in the `org.apache.fop.events.model` package. The data for the object model is retrieved from an XML representation of the event model that is loaded as a resource. The XML representation is generated using an Ant task at build time (`ant resourcegen`). The Ant task (found in `src/codegen/java/org/apache/fop/tools/EventProducerCollectorTask.java`) scans FOP's sources for descendants of the `EventProducer` interface and uses [QDox](https://github.com/codehaus/qdox) to parse these interfaces.
The event model XML files are generated during build by the Ant task mentioned above when running the "resourcegen" task. So just run `"ant resourcegen"` if you receive a `MissingResourceException` at runtime indicating that `"event-model.xml"` is missing.
@@ -214,7 +214,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://docs.oracle.com/javase/1.5.0/docs/guide/jar/jar.html#Service%20Provider).
### Localization (L10n) { #l10n}
Modified: xmlgraphics/site/trunk/content/fop/2.0/fonts.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/2.0/fonts.mdtext?rev=1783200&r1=1783199&r2=1783200&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/2.0/fonts.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/2.0/fonts.mdtext Thu Feb 16 13:05:10 2017
@@ -181,7 +181,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](https://docs.oracle.com/javase/7/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.
Modified: xmlgraphics/site/trunk/content/fop/2.0/graphics.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/2.0/graphics.mdtext?rev=1783200&r1=1783199&r2=1783200&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/2.0/graphics.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/2.0/graphics.mdtext Thu Feb 16 13:05:10 2017
@@ -36,9 +36,9 @@ Legend:
- "(X)" means restricted support. Please see the details below.
-- [1]: Requires the presence of [JAI Image I/O Tools](http://jai-imageio.dev.java.net/) (or an equivalent Image I/O compatible codec) in the classpath. JAI Image I/O Tools also adds support for JPEG 2000, WBMP, RAW and PNM. Other Image I/O codecs may provide support for additional formats.
+- [1]: Requires the presence of [JAI Image I/O Tools](https://github.com/jai-imageio/jai-imageio-core) (or an equivalent Image I/O compatible codec) in the classpath. JAI Image I/O Tools also adds support for JPEG 2000, WBMP, RAW and PNM. Other Image I/O codecs may provide support for additional formats.
-<note>[JAI Image I/O Tools](http://jai-imageio.dev.java.net/) is not the same as the [JAI library](http://java.sun.com/javase/technologies/desktop/media/jai/) ! The former simply exposes JAI's codecs using the Image I/O API but does not include all the image manipulation functionality.</note>
+<note>[JAI Image I/O Tools](https://github.com/jai-imageio/jai-imageio-core) is not the same as the [JAI library](http://java.sun.com/javase/technologies/desktop/media/jai/) ! The former simply exposes JAI's codecs using the Image I/O API but does not include all the image manipulation functionality.</note>
### Map of supported image formats by output format { #format-map}
Modified: xmlgraphics/site/trunk/content/fop/2.0/hyphenation.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/2.0/hyphenation.mdtext?rev=1783200&r1=1783199&r2=1783200&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/2.0/hyphenation.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/2.0/hyphenation.mdtext Thu Feb 16 13:05:10 2017
@@ -9,7 +9,7 @@ Title: Apache(tm) FOP: Hyphenation
Apache™ 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.
+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) project.
<note>If you have made improvements to an existing Apache™ 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).</note>
@@ -57,7 +57,7 @@ and run Ant with build target `jar-hyphe
## Hyphenation Patterns { #patterns}
-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:
+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) 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>
- The root of the pattern file is the <hyphenation-info> element.
Modified: xmlgraphics/site/trunk/content/fop/2.0/output.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/2.0/output.mdtext?rev=1783200&r1=1783199&r2=1783200&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/2.0/output.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/2.0/output.mdtext Thu Feb 16 13:05:10 2017
@@ -234,7 +234,7 @@ The output created by the PCLRenderer is
- [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)
+- [Technical reference documents on PCL from Hewlett-Packard](http://www.hp.com/ctg/Manual/bpl13210.pdf)
### Limitations { #pcl-limitations}
Modified: xmlgraphics/site/trunk/content/fop/2.0/running.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/2.0/running.mdtext?rev=1783200&r1=1783199&r2=1783200&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/2.0/running.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/2.0/running.mdtext Thu Feb 16 13:05:10 2017
@@ -50,7 +50,7 @@ Some Mac OSX users have experienced file
### 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.
+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](https://java.com/en/download/faq/java_mac.xml) for information as it becomes available.
USAGE
Fop [options] [-fo|-xml] infile [-xsl file] [-awt|-pdf|-mif|-rtf|-tiff|-png|-pcl|-ps|-txt|-at [mime]|-print] <outfile>
@@ -193,7 +193,7 @@ FOP can consume quite a bit of memory, e
If you are running out of memory when using FOP, here are some ideas that may help:
-- Increase memory available to the JVM. See [the -Xmx option](http://java.sun.com/j2se/1.4/docs/tooldocs/solaris/java.html) for more information.<warning>It is usually unwise to increase the memory allocated to the JVM beyond the amount of physical RAM, as this will generally cause significantly slower performance.</warning>
+- Increase memory available to the JVM. See [the -Xmx option](http://docs.oracle.com/javase/1.5.0/docs/tooldocs/solaris/java.html) for more information.<warning>It is usually unwise to increase the memory allocated to the JVM beyond the amount of physical RAM, as this will generally cause significantly slower performance.</warning>
- Avoid forward references. Forward references are references to some later part of a document. Examples include page number citations which refer to pages which follow the citation, tables of contents at the beginning of a document, and page numbering schemes that include the total number of pages in the document (["page N of TOTAL"](../faq.html#pagenum)). Forward references cause all subsequent pages to be held in memory until the reference can be resolved, i.e. until the page with the referenced element is encountered. Forward references may be required by the task, but if you are getting a memory overflow, at least consider the possibility of eliminating them. A table of contents could be replaced by PDF bookmarks instead or moved to the end of the document (reshuffle the paper could after printing).
Modified: xmlgraphics/site/trunk/content/fop/2.1/anttask.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/2.1/anttask.mdtext?rev=1783200&r1=1783199&r2=1783200&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/2.1/anttask.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/2.1/anttask.mdtext Thu Feb 16 13:05:10 2017
@@ -53,7 +53,7 @@ Then create FOP tasks within your Ant bu
<caption>Parameters specified as nested elements</caption>| Attribute | Description | Required |
|-----------|-------------|----------|
-| fileset | [FileSets](http://ant.apache.org/manual/CoreTypes/fileset.html) are used to specify multiple XSL-FO files to be rendered. | Yes, if no fofile attribute is supplied |
+| fileset | [FileSets](https://ant.apache.org/manual/Types/fileset.html) are used to specify multiple XSL-FO files to be rendered. | Yes, if no fofile attribute is supplied |
## Examples { #examples}
Modified: xmlgraphics/site/trunk/content/fop/2.1/events.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/2.1/events.mdtext?rev=1783200&r1=1783199&r2=1783200&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/2.1/events.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/2.1/events.mdtext Thu Feb 16 13:05:10 2017
@@ -180,7 +180,7 @@ To produce the same event as in the firs
### The event model { #event-model}
-Inside an invocation handler for a dynamic proxy, there's no information about the names of each parameter. The JVM doesn't provide it. The only thing you know is the interface and method name. In order to properly fill the `Event` 's parameter map we need to know the parameter names. These are retrieved from an event object model. This is found in the `org.apache.fop.events.model` package. The data for the object model is retrieved from an XML representation of the event model that is loaded as a resource. The XML representation is generated using an Ant task at build time (`ant resourcegen`). The Ant task (found in `src/codegen/java/org/apache/fop/tools/EventProducerCollectorTask.java`) scans FOP's sources for descendants of the `EventProducer` interface and uses [QDox](http://qdox.codehaus.org/) to parse these interfaces.
+Inside an invocation handler for a dynamic proxy, there's no information about the names of each parameter. The JVM doesn't provide it. The only thing you know is the interface and method name. In order to properly fill the `Event` 's parameter map we need to know the parameter names. These are retrieved from an event object model. This is found in the `org.apache.fop.events.model` package. The data for the object model is retrieved from an XML representation of the event model that is loaded as a resource. The XML representation is generated using an Ant task at build time (`ant resourcegen`). The Ant task (found in `src/codegen/java/org/apache/fop/tools/EventProducerCollectorTask.java`) scans FOP's sources for descendants of the `EventProducer` interface and uses [QDox](https://github.com/codehaus/qdox) to parse these interfaces.
The event model XML files are generated during build by the Ant task mentioned above when running the "resourcegen" task. So just run `"ant resourcegen"` if you receive a `MissingResourceException` at runtime indicating that `"event-model.xml"` is missing.
@@ -214,7 +214,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://docs.oracle.com/javase/1.5.0/docs/guide/jar/jar.html#Service%20Provider).
### Localization (L10n) { #l10n}
Modified: xmlgraphics/site/trunk/content/fop/2.1/fonts.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/2.1/fonts.mdtext?rev=1783200&r1=1783199&r2=1783200&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/2.1/fonts.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/2.1/fonts.mdtext Thu Feb 16 13:05:10 2017
@@ -181,7 +181,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](https://docs.oracle.com/javase/7/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.
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: commits-help@xmlgraphics.apache.org