summaryrefslogtreecommitdiffstats
path: root/src/documentation/content/xdocs/trunk
diff options
context:
space:
mode:
Diffstat (limited to 'src/documentation/content/xdocs/trunk')
-rw-r--r--src/documentation/content/xdocs/trunk/anttask.xml35
-rw-r--r--src/documentation/content/xdocs/trunk/graphics.xml6
-rw-r--r--src/documentation/content/xdocs/trunk/index.xml13
-rw-r--r--src/documentation/content/xdocs/trunk/output.xml5
-rw-r--r--[-rwxr-xr-x]src/documentation/content/xdocs/trunk/pdfencryption.xml0
-rw-r--r--src/documentation/content/xdocs/trunk/upgrading.xml38
6 files changed, 58 insertions, 39 deletions
diff --git a/src/documentation/content/xdocs/trunk/anttask.xml b/src/documentation/content/xdocs/trunk/anttask.xml
index 9831f2c01..44550c3d7 100644
--- a/src/documentation/content/xdocs/trunk/anttask.xml
+++ b/src/documentation/content/xdocs/trunk/anttask.xml
@@ -37,17 +37,19 @@
One method of defining the task is as follows:
</p>
<source><![CDATA[
-<property name="fop.dir" value="....path to your FOP jar files..."/>
+<property name="fop.home" value="....path to your FOP HOME directory..."/>
<taskdef name="fop"
classname="org.apache.fop.tools.anttasks.Fop">
- <classpath>
- <pathelement location="${fop.dir}\fop.jar"/>
- <pathelement location="${fop.dir}\batik.jar"/>
- <pathelement location="${fop.dir}\avalon-framework.jar"/>
- <pathelement location="${fop.dir}\commons-logging.jar"/>
- <pathelement location="${fop.dir}\commons-io.jar"/>
- </classpath>
+ <classpath>
+ <fileset dir="${fop.home}/lib">
+ <include name="*.jar"/>
+ </fileset>
+ <fileset dir="${fop.home}/build">
+ <include name="fop.jar"/>
+ <include name="fop-hyph.jar" />
+ </fileset>
+ </classpath>
</taskdef>
]]></source>
<p>
@@ -74,13 +76,24 @@
<tr>
<td>format</td>
<td>Possible output formats:<br/>
+ <code>application/X-fop-awt-preview</code><br/>
+ <code>application/X-fop-print</code><br/>
+ <code>application/X-fop-areatree</code><br/>
<code>application/pdf</code><br/>
<code>application/postscript</code><br/>
- <code>application/vnd.mif</code><br/>
- <code>application/rtf</code><br/>
+ <code>application/mif</code><br/>
+ <code>application/rtf</code>,
+ <code>text/richtext</code>,
+ <code>text/rtf</code><br/>
+ <code>application/x-pcl</code>,
<code>application/vnd.hp-PCL</code><br/>
+ <code>application/x-afp</code>,
+ <code>application/vnd.ibm.modcap</code><br/>
<code>text/plain</code><br/>
- <code>text/xml</code><br/>
+ <code>image/svg+xml</code><br/>
+ <code>image/gif</code><br/>
+ <code>image/png</code><br/>
+ <code>image/tiff</code><br/>
</td>
<td>No, defaults to <code>application/pdf</code></td>
</tr>
diff --git a/src/documentation/content/xdocs/trunk/graphics.xml b/src/documentation/content/xdocs/trunk/graphics.xml
index 9f56f0526..beb860223 100644
--- a/src/documentation/content/xdocs/trunk/graphics.xml
+++ b/src/documentation/content/xdocs/trunk/graphics.xml
@@ -256,12 +256,6 @@ Smooth Line Art in the Acrobat preferences will fix this).
If the text is inserted into the PDF using the inbuilt text commands
for PDF it will use a single character.
</p>
- <p>
-For PDF output, there is a <a href="configuration.html#svg-strokeSVGText">configuration option to force SVG text to be rendered as text</a>.
-The drawback to this approach is that it is effective only for available fonts (including embedded fonts).
-Font sizes are rounded to the next integer point size.
-This will be improved in the future.
- </p>
<p>Note that because SVG text can be rendered as either text or a vector graphic, you may need to consider settings in your viewer for both.
The Acrobat viewer has both "smooth line art" and "smooth text" settings that may need to be set for SVG images to be displayed nicely on your screen (see Edit / Preferences / Display).
This setting will not affect the printing of your document, which should be OK in any case, but will only affect the quality of the screen display.</p>
diff --git a/src/documentation/content/xdocs/trunk/index.xml b/src/documentation/content/xdocs/trunk/index.xml
index dfa92c3b9..e150ffe9a 100644
--- a/src/documentation/content/xdocs/trunk/index.xml
+++ b/src/documentation/content/xdocs/trunk/index.xml
@@ -26,16 +26,17 @@
<section id="intro">
<title>Introduction</title>
<p>
- <strong>FOP Trunk</strong> is the name for the current development code as found in the
- <a href="ext:svn-repo/trunk">Subversion repository</a>. This section of the FOP provides
- the documentation for this version.
+ <strong>FOP Trunk</strong> is the name for the current
+ development code as found in the <a
+ href="ext:svn-repo/trunk">Subversion repository</a>. This
+ section of the FOP web site provides the documentation for
+ this version.
</p>
<p>
The Apache FOP team is proud to present to you the largely rewritten codebase which is
finally in a state where you can start to use it. It has taken over three years to get this
- far and over two years without a new release from the FOP project. We would like to encourage
- you to download the code and to play with it. We're still in the process of adding new major
- features and stabilizing the code. We welcome any feedback you might have and even more, any
+ 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.
</p>
</section>
diff --git a/src/documentation/content/xdocs/trunk/output.xml b/src/documentation/content/xdocs/trunk/output.xml
index 117a49574..8c2c0213e 100644
--- a/src/documentation/content/xdocs/trunk/output.xml
+++ b/src/documentation/content/xdocs/trunk/output.xml
@@ -84,8 +84,9 @@ out = proc.getOutputStream();]]></source>
compatible.
</p>
<p>
- Note that FOP does not currently support "tagged PDF", PDF/X or PDF/A-1a.
- <a href="pdfa.html">Support for PDF/A-1b</a> has recently been added, however.
+ Note that FOP does not currently support "tagged PDF" or PDF/A-1a.
+ Support for <a href="pdfa.html">PDF/A-1b</a> and <a
+ href="pdfx.html">PDF/X</a> has recently been added, however.
</p>
<section id="pdf-fonts">
<title>Fonts</title>
diff --git a/src/documentation/content/xdocs/trunk/pdfencryption.xml b/src/documentation/content/xdocs/trunk/pdfencryption.xml
index f68eae437..f68eae437 100755..100644
--- a/src/documentation/content/xdocs/trunk/pdfencryption.xml
+++ b/src/documentation/content/xdocs/trunk/pdfencryption.xml
diff --git a/src/documentation/content/xdocs/trunk/upgrading.xml b/src/documentation/content/xdocs/trunk/upgrading.xml
index 4772fcb4c..b8aa58200 100644
--- a/src/documentation/content/xdocs/trunk/upgrading.xml
+++ b/src/documentation/content/xdocs/trunk/upgrading.xml
@@ -31,24 +31,34 @@
</p>
<ul>
<li>
- More than half of the codebase has been rewritten over the last three years. The code is
- relatively new and possibly not as stable as version 0.20.5 in every regard. But the code
- is <strong>quickly approaching production level</strong>, especially when you're happy
- with only PDF and PostScript output.
+ More than half of the codebase has been rewritten over the last three years. With version 0.93 the code has reached <strong>production level</strong>.
</li>
<li>
- The API of FOP has changed considerably and is not backwards-compatible with version 0.20.5.
+ The API of FOP has changed considerably and is not
+ backwards-compatible with versions 0.20.5 and
+ 0.91beta. Version 0.92 introduced the <strong>new stable
+ API</strong>.
</li>
<li>
- If you are using a configuration file, you have to rebuild it in the new format. The format
+ Since version 0.92 some deprecated methods which were part
+ of the old API have been removed. If you upgrade from 0.91
+ beta, you will need to adjust your Java code. Similarly if
+ you upgrade from 0.92 and use deprecated methods.
+ </li>
+ <li>
+ If you are using a configuration file for version 0.20.5, you have to rebuild it in the new format. The format
of the configuration files has changed since version 0.20.5. See conf/fop.xconf for
an example configuration file. A XML Schema file can be found under
src/foschema/fop-configuration.xsd.
</li>
- <li>
- There have been changes to the end-user API between 0.91 beta and 0.92 beta. With version 0.92,
- the API is now considered stable. Some methods have been deprecated and will be removed with
- the next release. If you upgrade from 0.91 beta, you will need to adjust your Java code.
+ <li>
+ If you are using font metrics files for version 0.20.5 or
+ 0.92 or earlier, you have to regenerate them in the new
+ format. The new format is characterized by a version
+ attribute on the top-level font-metrics element, whose value
+ is 2.0. The absence of a version attribute will be
+ interpreted as version 1.0, and such metrics files will no
+ longer be parsed.
</li>
<li>
<p>
@@ -67,7 +77,7 @@
<li>
Extensions and Renderers written for version 0.20.5 will not work with the new code! The new FOP
extension for <a href="http://barcode4j.krysalis.org">Barcode4J</a> will be available in
- January 2006.
+ January 2007.
</li>
<li>
The PCL Renderer and the MIF Handler have not been resurrected, yet! They are currently non-functional
@@ -106,13 +116,13 @@
or <code>instream-foreign-object</code>
objects. If images or SVGs are sized differently in your outputs with the new FOP version
check <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=37136">Bug 37136</a>
- as it contains some hints on what to. The file
+ as it contains some hints on what to do. The file
<a href="http://svn.apache.org/viewcvs.cgi/xmlgraphics/fop/trunk/examples/fo/basic/images.fo?view=markup">
<code>"examples/fo/basic/images.fo"</code></a> has
- a number of good examples that shows the new, more correct behaviour.
+ a number of good examples that show the new, more correct behaviour.
</li>
<li>
- The <code>fox:outline</code> extension not implemented in this version anymore.
+ The <code>fox:outline</code> extension is not implemented in this version anymore.
It has been superseded by the new bookmark elements from XSL-FO 1.1.
</li>
<li>