Apache FOP Font Config

- Register Fonts with FOP + Register Fonts with FOP - Auto-Detect Fonts

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

@@ -254,7 +254,18 @@ It will display all of the font names and exit with an Exception.

]]> - Review the documentation for FOP Configuration for instructions on making the FOP configuration available to FOP when it runs. Otherwise, FOP has no way of finding your custom font information. + + Review the documentation for FOP Configuration for + instructions on making the FOP configuration available to FOP when it runs. Otherwise, + FOP has no way of finding your custom font information. + + The Unix autodetect feature looks in the following locations for fonts it can use: +

java user.home + "/.fonts"
"/usr/local/fonts"
"/usr/share/fonts"
"/usr/X11R6/lib/X11/fonts"

URLs are used to access the font metric and font files. diff --git a/src/documentation/content/xdocs/0.94/index.xml b/src/documentation/content/xdocs/0.94/index.xml index 80092d054..750047678 100644 --- a/src/documentation/content/xdocs/0.94/index.xml +++ b/src/documentation/content/xdocs/0.94/index.xml @@ -19,24 +19,21 @@
- Apache FOP Trunk (Development code) + Apache FOP Version 0.94 $Revision: 201586 $

Introduction
- FOP Trunk is the name for the current - development code as found in the Subversion repository. This - section of the FOP web site provides the documentation for - this version. + The Apache FOP team is proud to present to you this production quality release. + We're still in the process of adding new features. We welcome any feedback you + might have and even more, any other form of help to get the project forward.

- The Apache FOP team is proud to present to you this production quality codebase. It has taken - over three years to get this far and over two years without a new release from the FOP - project. We're still in the process of adding new features. We welcome any feedback you - might have and even more, any other form of help to get the project forward. + This fifth release contains many bug fix release and new features compared + to 0.92beta. To see what has changed since the last release, please visit the + Changes Page and the Release Notes.

@@ -46,5 +43,11 @@ information contained on the Upgrading page!

+
+ Download +
+ To download this version, please visit the download page. +
+
diff --git a/src/documentation/content/xdocs/0.94/pdfx.xml b/src/documentation/content/xdocs/0.94/pdfx.xml index cf796c74d..342a0ca4c 100644 --- a/src/documentation/content/xdocs/0.94/pdfx.xml +++ b/src/documentation/content/xdocs/0.94/pdfx.xml @@ -28,8 +28,8 @@
Overview - 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. + Support for PDF/X was made available beginning with version 0.93. + This feature is new and may not be 100% complete, yet. Feedback is welcome.
PDF/X is a standard which faciliates prepress digital data exchange using PDF. diff --git a/src/documentation/content/xdocs/0.94/upgrading.xml b/src/documentation/content/xdocs/0.94/upgrading.xml index 46c9cff3b..f99cdc93a 100644 --- a/src/documentation/content/xdocs/0.94/upgrading.xml +++ b/src/documentation/content/xdocs/0.94/upgrading.xml @@ -31,7 +31,8 @@
- - More than half of the codebase has been rewritten over the last three years. With version 0.93 the code has reached production level. + More than half of the codebase has been rewritten over the last three years. With version 0.93 the code has reached production level, and + the tradition continues with version 0.94.
- The API of FOP has changed considerably and is not diff --git a/src/documentation/content/xdocs/dev/release.xml b/src/documentation/content/xdocs/dev/release.xml index 8785d8789..7d6ca5734 100644 --- a/src/documentation/content/xdocs/dev/release.xml +++ b/src/documentation/content/xdocs/dev/release.xml @@ -38,12 +38,12 @@ The purpose of documenting it here is to facilitate consistency, ensure that the
- Determine whether further testing is required.
- Commit any outstanding changes
- Create a branch called branches/fop-v_vv
- Edit release notes (README and status.xml in the root).
- Update the index.xml and site.xml for the new version.
- Edit release notes (README and status.xml in the root).
- Update the index.xml and site.xml for the new version.
- Update the version numbers in the release column on the - compliance page; update the compliance in the release column + compliance page (compliance.xml); update the compliance in the release column to the current state (development column).
- Update version number in build.xml (not to be merged back +
- Update version number in build.xml (not to be merged back into trunk).
- Copy trunk documentation directory to a new directory with the version number, and update any links and the .htaccess @@ -62,10 +62,10 @@ The purpose of documenting it here is to facilitate consistency, ensure that the people.apache.org
- Ask on fop-dev to check the branch and the generated dist files for errors.
- Tag the source tree with the release ID. For example, if the release is 0.93: - svn copy https://svn.apache.org/repos/asf/xmlgraphics/fop/branches/fop-0_93 https://svn.apache.org/repos/asf/xmlgraphics/fop/tags/fop-0_93
- Tag the source tree with the release ID. For example, if the release is 0.94: + svn copy https://svn.apache.org/repos/asf/xmlgraphics/fop/branches/fop-0_94 https://svn.apache.org/repos/asf/xmlgraphics/fop/tags/fop-0_94
- Make a fresh checkout with the just created tag: - svn co https://svn.apache.org/repos/asf/xmlgraphics/fop/tags/fop-0_93
- Copy jimi and jai to lib/ (jimi-1.0.jar, jai_core.jar, jai_codec.jar)
- Copy jce-jdk13-119.jar from from http://www.bouncycastle.org/latest_releases.html to lib/
- Alternatively, create a build-local.properties file that points to the above libs.
- Run build[.sh] dist. Do this once using Sun JDK 1.3.1_15 or later and once with Sun JDK 1.4.2_08 or later. A Forrest installation is needed.
- Create signatures. Don't forget to upload your KEY: - gpg -a -b --force-v3-sigs fop-0.93-src.tar.gz etc.
- Upload the dist and signature files to your web directory on people.apache.org (An account on minotaur is needed): - scp fop-0.93*.tar.gz* + scp fop-0.94*.tar.gz* chrisg@people.apache.org:public_html/
Known Issues: @@ -318,7 +318,7 @@


     
       You may experience different behaviour compared to version 0.20.5.
-      Please consult the "Upgrading" page indicated above for details.
+      Please consult the "Upgrading" page indicated above for details.


   Known Issues:
@@ -430,7 +430,7 @@