You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@xmlgraphics.apache.org by ps...@apache.org on 2010/02/19 14:14:53 UTC
svn commit: r911805 [2/2] - in /xmlgraphics/site/deploy/fop: ./ 0.94/ 0.95/
dev/ dev/design/ trunk/
Modified: xmlgraphics/site/deploy/fop/dev/rtflib.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/dev/rtflib.xml?rev=911805&r1=911804&r2=911805&view=diff
==============================================================================
--- xmlgraphics/site/deploy/fop/dev/rtflib.xml (original)
+++ xmlgraphics/site/deploy/fop/dev/rtflib.xml Fri Feb 19 13:14:50 2010
@@ -13,11 +13,11 @@
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
---><!-- $Id$ --><!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN" "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/core/context/resources/schema/dtd/document-v12.dtd">
+--><!-- $Id$ --><!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "http://forrest.apache.org/dtd/document-v13.dtd">
<document>
<header>
<title>FOP Development: RTFLib (jfor)</title>
- <version>$Revision: 627324 $</version>
+ <version>$Revision: 911792 $</version>
</header>
<body>
<section id="general">
Modified: xmlgraphics/site/deploy/fop/dev/svg.html
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/dev/svg.html?rev=911805&r1=911804&r2=911805&view=diff
==============================================================================
--- xmlgraphics/site/deploy/fop/dev/svg.html (original)
+++ xmlgraphics/site/deploy/fop/dev/svg.html Fri Feb 19 13:14:50 2010
@@ -432,7 +432,7 @@
</div>
<span class="version">
- version 627324</span>
+ version 911792</span>
</div>
<!--+
|end content
Modified: xmlgraphics/site/deploy/fop/dev/svg.pdf
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/dev/svg.pdf?rev=911805&r1=911804&r2=911805&view=diff
==============================================================================
Files xmlgraphics/site/deploy/fop/dev/svg.pdf (original) and xmlgraphics/site/deploy/fop/dev/svg.pdf Fri Feb 19 13:14:50 2010 differ
Modified: xmlgraphics/site/deploy/fop/dev/svg.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/dev/svg.xml?rev=911805&r1=911804&r2=911805&view=diff
==============================================================================
--- xmlgraphics/site/deploy/fop/dev/svg.xml (original)
+++ xmlgraphics/site/deploy/fop/dev/svg.xml Fri Feb 19 13:14:50 2010
@@ -13,11 +13,11 @@
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
---><!-- $Id$ --><!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN" "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/core/context/resources/schema/dtd/document-v12.dtd">
+--><!-- $Id$ --><!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "http://forrest.apache.org/dtd/document-v13.dtd">
<document>
<header>
<title>FOP Development: SVG Issues</title>
- <version>$Revision: 627324 $</version>
+ <version>$Revision: 911792 $</version>
</header>
<body>
<p>See also <link href="../trunk/graphics.html#svg">SVG User Documentation</link> for more information.</p>
Modified: xmlgraphics/site/deploy/fop/download.html
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/download.html?rev=911805&r1=911804&r2=911805&view=diff
==============================================================================
--- xmlgraphics/site/deploy/fop/download.html (original)
+++ xmlgraphics/site/deploy/fop/download.html Fri Feb 19 13:14:50 2010
@@ -224,8 +224,8 @@
<h2 class="underlined_10">Binary or Source?</h2>
<div class="section">
<p>
- Most FOP users will want to download the latest binary distribution,
- which is ready to run "out of the box." However, a source distribution
+ Most FOP users will want to download the latest binary distribution,
+ which is ready to run "out of the box." However, a source distribution
will be preferable if you fall into one of the following categories:
</p>
<ul>
@@ -235,10 +235,10 @@
</li>
<li>
- You wish to use a version more recent than the latest release. For
- example, if you have read on the user mailing list that a bug has
- been fixed or a feature added that you are eager to try, you might
- download a source distribution from the CVS repository so that you
+ You wish to use a version more recent than the latest release. For
+ example, if you have read on the user mailing list that a bug has
+ been fixed or a feature added that you are eager to try, you might
+ download a source distribution from the SVN repository so that you
don't have to wait for the next release.
</li>
@@ -262,29 +262,29 @@
<h2 class="underlined_10">Source Download</h2>
<div class="section">
<p>
- There are several ways to obtain a source distribution. Please note that they
+ There are several ways to obtain a source distribution. Please note that they
are listed from least current to most current:
</p>
<ul>
<li>
- Download a released version from a
+ Download a released version from a
<a class="external" href="http://www.apache.org/dyn/closer.cgi/xmlgraphics/fop">FOP Distribution mirror</a>.
Source distributions include "-src" in their names.
</li>
<!--li>
- Download a CVS snapshot from the cvs files
- <link href="http://xml.apache.org/from-cvs/xml-fop/">here</link>.
- These snapshots are built approximately every six hours, and have the GMT of
- their creation time embedded in their names. Please note that CVS snapshots
+ Download a CVS snapshot from the cvs files
+ <link href="http://xml.apache.org/from-cvs/xml-fop/">here</link>.
+ These snapshots are built approximately every six hours, and have the GMT of
+ their creation time embedded in their names. Please note that CVS snapshots
are made only for the "redesign" branch.
</li-->
<li>
Download directly from the SVN repository.
- Anyone can do this using the
+ Anyone can do this using the
<a href="http://xmlgraphics.apache.org/repo.html">Anonymous SVN Server</a>.
- By default, the code in SVN is up-to-the-minute, the same code that the developers
+ By default, the code in SVN is up-to-the-minute, the same code that the developers
are modifying. See the <a href="dev/tools.html#svn">SVN section of Developer Tools</a>
for more information on using SVN.
</li>
@@ -369,7 +369,7 @@
<a class="external" href="http://svn.eu.apache.org/repos/asf/xmlgraphics/fop/trunk/">
<span class="codefrag">http://svn.eu.apache.org/repos/asf/xmlgraphics/fop/trunk/</span>
</a>
-
+
</td>
</tr>
@@ -394,7 +394,7 @@
</table>
<p>
- With any source distribution, you will need to
+ With any source distribution, you will need to
build FOP from the source files. For details please see the "Build" page on the documentation tab
for the version you've downloaded.
</p>
@@ -404,15 +404,15 @@
<h2 class="underlined_10">Archive Download</h2>
<div class="section">
<p>
- FOP Archive distributions are linked from the upper portion of the Apache FOP
- Download Mirror Page and can be downloaded from the FOP Archives
- <a class="external" href="http://archive.apache.org/dist/xmlgraphics/fop/binaries/">binaries</a> &
+ FOP Archive distributions are linked from the upper portion of the Apache FOP
+ Download Mirror Page and can be downloaded from the FOP Archives
+ <a class="external" href="http://archive.apache.org/dist/xmlgraphics/fop/binaries/">binaries</a> &
<a class="external" href="http://archive.apache.org/dist/xmlgraphics/fop/source/">source</a> links.
</p>
</div>
<span class="version">
- version 682604</span>
+ version 911753</span>
</div>
<!--+
|end content
Modified: xmlgraphics/site/deploy/fop/download.pdf
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/download.pdf?rev=911805&r1=911804&r2=911805&view=diff
==============================================================================
Files xmlgraphics/site/deploy/fop/download.pdf (original) and xmlgraphics/site/deploy/fop/download.pdf Fri Feb 19 13:14:50 2010 differ
Modified: xmlgraphics/site/deploy/fop/download.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/download.xml?rev=911805&r1=911804&r2=911805&view=diff
==============================================================================
--- xmlgraphics/site/deploy/fop/download.xml (original)
+++ xmlgraphics/site/deploy/fop/download.xml Fri Feb 19 13:14:50 2010
@@ -17,14 +17,14 @@
<document>
<header>
<title>Apache FOP: Downloading A Distribution</title>
- <version>$Revision: 682604 $</version>
+ <version>$Revision: 911753 $</version>
</header>
<body>
<section id="dist-type">
<title>Binary or Source?</title>
<p>
- Most FOP users will want to download the latest binary distribution,
- which is ready to run "out of the box." However, a source distribution
+ Most FOP users will want to download the latest binary distribution,
+ which is ready to run "out of the box." However, a source distribution
will be preferable if you fall into one of the following categories:
</p>
<ul>
@@ -32,10 +32,10 @@
You wish to modify FOP.
</li>
<li>
- You wish to use a version more recent than the latest release. For
- example, if you have read on the user mailing list that a bug has
- been fixed or a feature added that you are eager to try, you might
- download a source distribution from the CVS repository so that you
+ You wish to use a version more recent than the latest release. For
+ example, if you have read on the user mailing list that a bug has
+ been fixed or a feature added that you are eager to try, you might
+ download a source distribution from the SVN repository so that you
don't have to wait for the next release.
</li>
<li>
@@ -53,27 +53,27 @@
<section id="source">
<title>Source Download</title>
<p>
- There are several ways to obtain a source distribution. Please note that they
+ There are several ways to obtain a source distribution. Please note that they
are listed from least current to most current:
</p>
<ul>
<li>
- Download a released version from a
+ Download a released version from a
<link href="http://www.apache.org/dyn/closer.cgi/xmlgraphics/fop">FOP Distribution mirror</link>.
Source distributions include "-src" in their names.
</li>
<!--li>
- Download a CVS snapshot from the cvs files
- <link href="http://xml.apache.org/from-cvs/xml-fop/">here</link>.
- These snapshots are built approximately every six hours, and have the GMT of
- their creation time embedded in their names. Please note that CVS snapshots
+ Download a CVS snapshot from the cvs files
+ <link href="http://xml.apache.org/from-cvs/xml-fop/">here</link>.
+ These snapshots are built approximately every six hours, and have the GMT of
+ their creation time embedded in their names. Please note that CVS snapshots
are made only for the "redesign" branch.
</li-->
<li>
Download directly from the SVN repository.
- Anyone can do this using the
+ Anyone can do this using the
<link href="http://xmlgraphics.apache.org/repo.html">Anonymous SVN Server</link>.
- By default, the code in SVN is up-to-the-minute, the same code that the developers
+ By default, the code in SVN is up-to-the-minute, the same code that the developers
are modifying. See the <link href="dev/tools.html#svn">SVN section of Developer Tools</link>
for more information on using SVN.
</li>
@@ -133,7 +133,7 @@
<link href="http://svn.eu.apache.org/repos/asf/xmlgraphics/fop/trunk/">
<code>http://svn.eu.apache.org/repos/asf/xmlgraphics/fop/trunk/</code>
</link>
-
+
</td>
</tr>
<tr>
@@ -152,7 +152,7 @@
</tr>
</table>
<p>
- With any source distribution, you will need to
+ With any source distribution, you will need to
build FOP from the source files. For details please see the "Build" page on the documentation tab
for the version you've downloaded.
</p>
@@ -163,9 +163,9 @@
<section id="archives">
<title>Archive Download</title>
<p>
- FOP Archive distributions are linked from the upper portion of the Apache FOP
- Download Mirror Page and can be downloaded from the FOP Archives
- <link href="http://archive.apache.org/dist/xmlgraphics/fop/binaries/">binaries</link> &
+ FOP Archive distributions are linked from the upper portion of the Apache FOP
+ Download Mirror Page and can be downloaded from the FOP Archives
+ <link href="http://archive.apache.org/dist/xmlgraphics/fop/binaries/">binaries</link> &
<link href="http://archive.apache.org/dist/xmlgraphics/fop/source/">source</link> links.
</p>
</section>
Modified: xmlgraphics/site/deploy/fop/examples.html
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/examples.html?rev=911805&r1=911804&r2=911805&view=diff
==============================================================================
--- xmlgraphics/site/deploy/fop/examples.html (original)
+++ xmlgraphics/site/deploy/fop/examples.html Fri Feb 19 13:14:50 2010
@@ -380,7 +380,7 @@
</div>
<span class="version">
- version 627324</span>
+ version 911792</span>
</div>
<!--+
|end content
Modified: xmlgraphics/site/deploy/fop/examples.pdf
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/examples.pdf?rev=911805&r1=911804&r2=911805&view=diff
==============================================================================
Files xmlgraphics/site/deploy/fop/examples.pdf (original) and xmlgraphics/site/deploy/fop/examples.pdf Fri Feb 19 13:14:50 2010 differ
Modified: xmlgraphics/site/deploy/fop/examples.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/examples.xml?rev=911805&r1=911804&r2=911805&view=diff
==============================================================================
--- xmlgraphics/site/deploy/fop/examples.xml (original)
+++ xmlgraphics/site/deploy/fop/examples.xml Fri Feb 19 13:14:50 2010
@@ -13,11 +13,11 @@
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
---><!-- $Id$ --><!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN" "http://svn.apache.org/viewvc/forrest/trunk/main/webapp/resources/schema/dtd/document-v12.dtd?view=co">
+--><!-- $Id$ --><!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "http://forrest.apache.org/dtd/document-v13.dtd">
<document>
<header>
<title>Examples</title>
- <version>$Revision: 627324 $</version>
+ <version>$Revision: 911792 $</version>
</header>
<body>
<section>
Modified: xmlgraphics/site/deploy/fop/faq.html
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/faq.html?rev=911805&r1=911804&r2=911805&view=diff
==============================================================================
--- xmlgraphics/site/deploy/fop/faq.html (original)
+++ xmlgraphics/site/deploy/fop/faq.html Fri Feb 19 13:14:50 2010
@@ -329,11 +329,11 @@
<a href="#table-cell-wrap">3.9. The contents of table cells don’t wrap</a>
</li>
<li>
-<a href="#keep-together">3.10. FOP 0.95 and FOP 0.94 behave differently when keep-together="always"
+<a href="#keep-together">3.10. FOP 0.95 and FOP 0.94 behave differently when keep-together="always"
is set on table cells</a>
</li>
<li>
-<a href="#row-height-constraint">3.11. FOP tells me: "The contents of row 1 are taller than they should be".
+<a href="#row-height-constraint">3.11. FOP tells me: "The contents of row 1 are taller than they should be".
What does that mean?</a>
</li>
<li>
@@ -636,7 +636,7 @@
<a name="N1009D"></a><a name="next-release"></a>
<h3 class="underlined_5">1.9. When is the next released planned?</h3>
<p>
- When it's ready and the committers have enough time to go through
+ When it's ready and the committers have enough time to go through
the time-consuming process of creating a release. We
released version 0.95 on August 6th, 2008, and intend to
release version 1.0 once we consider it "feature complete", major
@@ -869,7 +869,7 @@
import javax.xml.transform.TransformerException;
public class DefaultErrorListener implements ErrorListener {
-
+
public void warning(TransformerException exc) {
System.err.println(exc.toString());
}
@@ -892,8 +892,8 @@
-9075848379822693399, local class serialVersionUID = 8755432068669997367).
Discarding font cache file."</h3>
<p>
- This message is a warning that FOP failed to read from the Font cache.
- Which means any Font auto detection or Font directories will be re-scanned.
+ This message is a warning that FOP failed to read from the Font cache.
+ Which means any Font auto detection or Font directories will be re-scanned.
So this failure doesn't break anything.
</p>
<p>
@@ -1093,25 +1093,25 @@
<h3 class="underlined_5">3.9. The contents of table cells don’t wrap</h3>
<p>You probably have <span class="codefrag">keep-together="always"</span> set on the table cell. See <a href="#keep-together">next question</a>.</p>
<a name="N102DD"></a><a name="keep-together"></a>
-<h3 class="underlined_5">3.10. FOP 0.95 and FOP 0.94 behave differently when keep-together="always"
+<h3 class="underlined_5">3.10. FOP 0.95 and FOP 0.94 behave differently when keep-together="always"
is set on table cells</h3>
-<p>Support for inline-level keeps has been added in FOP 0.95, and setting
- <span class="codefrag">keep-together="always"</span> also implicitly sets
+<p>Support for inline-level keeps has been added in FOP 0.95, and setting
+ <span class="codefrag">keep-together="always"</span> also implicitly sets
<span class="codefrag">keep-together.within-line="always"</span>, which forbids FOP
- to break the text into multiple lines. Set
- <span class="codefrag">keep-together.within-column="always"</span> on table-cell instead. It’s a good idea
+ to break the text into multiple lines. Set
+ <span class="codefrag">keep-together.within-column="always"</span> on table-cell instead. It’s a good idea
not to use the shorthand <span class="codefrag">keep-together="always"</span> at all!</p>
<a name="N102F4"></a><a name="row-height-constraint"></a>
-<h3 class="underlined_5">3.11. FOP tells me: "The contents of row 1 are taller than they should be".
+<h3 class="underlined_5">3.11. FOP tells me: "The contents of row 1 are taller than they should be".
What does that mean?</h3>
<p>
This is usually caused by setting a "height" on a table-row or table-cell and when
- the content is higher than the specified height. By setting "height" (a so-called
- corresponding property) you
+ the content is higher than the specified height. By setting "height" (a so-called
+ corresponding property) you
<a class="external" href="http://www.w3.org/TR/xsl11/#d0e4413">implicitely set</a>
- block-progression-dimension.minimum, block-progression-dimension.optimum and
- block-progression-dimension.maximum to the same value. You'll get some information
- about that in the warning message. Look for something like:
+ block-progression-dimension.minimum, block-progression-dimension.optimum and
+ block-progression-dimension.maximum to the same value. You'll get some information
+ about that in the warning message. Look for something like:
"MinOptMax[min=opt=max=14000]".
</p>
<p>
@@ -1146,16 +1146,16 @@
<h3 class="underlined_5">3.14. When I use margins, my content in a nested table or block-containers gets indented twice. Is this a bug?</h3>
<p>
(Applies to version 0.90 and later)
- No, although you might easily think so. The problem has to do
- with property inheritance of the start-indent and end-indent
- properties to which the margin properties are mapped. Apache
- FOP strictly adheres to the XSL-FO specification here which many
- other commercial FO implementations don't do to better meet end-user
- expectations. You can make FOP behave like these if you set
- <span class="codefrag">setBreakIndentInheritanceOnReferenceAreaBoundary(true)</span>
+ No, although you might easily think so. The problem has to do
+ with property inheritance of the start-indent and end-indent
+ properties to which the margin properties are mapped. Apache
+ FOP strictly adheres to the XSL-FO specification here which many
+ other commercial FO implementations don't do to better meet end-user
+ expectations. You can make FOP behave like these if you set
+ <span class="codefrag">setBreakIndentInheritanceOnReferenceAreaBoundary(true)</span>
on the FOUserAgent. The better way is to reset <span class="codefrag">start-indent</span>
- and <span class="codefrag">end-indent</span> to "0pt" on table-body or block-container.
- For further details, please consult the
+ and <span class="codefrag">end-indent</span> to "0pt" on table-body or block-container.
+ For further details, please consult the
<a class="external" href="http://wiki.apache.org/xmlgraphics-fop/IndentInheritance">Wiki page on Indent Inheritance</a>.
</p>
<a name="N10340"></a><a name="pdf-ps-java2d-differences"></a>
@@ -1293,19 +1293,19 @@
<h3 class="underlined_5">5.6. FOP fails with something like "The attribute "width" of the element <rect> is required". What's wrong?</h3>
<p>
This phenomenon occurs since FOP 0.92 beta. It surfaced due to a change in the handling of non-FO namespaces. It's not a
- bug in FOP, but rather in the dependent packages: Apache Batik, Apache Xalan-J and SAXON. The bug in Apache Batik will be
+ bug in FOP, but rather in the dependent packages: Apache Batik, Apache Xalan-J and SAXON. The bug in Apache Batik will be
fixed in the next release. In the latest release of Apache Xalan-J, the bug is already fixed. It only occurs in the Xalan
version bundled with Sun's JVM, because Sun uses a rather old version.
</p>
<p>
- Bug description: In a namespace-enabled Level 3 DOM, an attribute in the default namespace must be set with
- <span class="codefrag">"null"</span> as the value for the namespace URI. SAX, on the other side, uses an empty string ("") to designate
- the default namespace. Many packages appear to not properly handle this difference in which case they still use the empty
+ Bug description: In a namespace-enabled Level 3 DOM, an attribute in the default namespace must be set with
+ <span class="codefrag">"null"</span> as the value for the namespace URI. SAX, on the other side, uses an empty string ("") to designate
+ the default namespace. Many packages appear to not properly handle this difference in which case they still use the empty
string as the namespace URI parameter for <span class="codefrag">org.w3c.dom.Element.setAttributeNS()</span>.
</p>
<p>
- Work-around: Use the latest version of Apache Xalan-J. Note that starting with JDK 1.4 it's not enough to replace Xalan-J
- on the normal application classpath and you need to override the Xalan-J version bundled with the Sun JVM using the
+ Work-around: Use the latest version of Apache Xalan-J. Note that starting with JDK 1.4 it's not enough to replace Xalan-J
+ on the normal application classpath and you need to override the Xalan-J version bundled with the Sun JVM using the
<a class="external" href="http://java.sun.com/j2se/1.4.2/docs/guide/standards/">Endorsed Standards Override Mechanism</a>, i.e.
you must place Xalan-J in the <span class="codefrag">"lib/endorsed"</span> directory of your JRE.
</p>
@@ -1382,8 +1382,8 @@
<p>
FOP versions 0.93 and later support the starting-state property of the XSL 1.1
<a class="external" href="http://www.w3.org/TR/xsl11/#fo_bookmark">fo:bookmark</a>
- element which can be used for this. The color, font-style and
- font-weight properties on
+ element which can be used for this. The color, font-style and
+ font-weight properties on
<a class="external" href="http://www.w3.org/TR/xsl11/#fo_bookmark-title">fo:bookmark-title</a>
are not yet supported, though.
</p>
Modified: xmlgraphics/site/deploy/fop/faq.pdf
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/faq.pdf?rev=911805&r1=911804&r2=911805&view=diff
==============================================================================
Files xmlgraphics/site/deploy/fop/faq.pdf (original) and xmlgraphics/site/deploy/fop/faq.pdf Fri Feb 19 13:14:50 2010 differ
Modified: xmlgraphics/site/deploy/fop/faq.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/faq.xml?rev=911805&r1=911804&r2=911805&view=diff
==============================================================================
--- xmlgraphics/site/deploy/fop/faq.xml (original)
+++ xmlgraphics/site/deploy/fop/faq.xml Fri Feb 19 13:14:50 2010
@@ -91,7 +91,7 @@
<p>The short answer is "Don't ask." For more details, see <link href="gethelp.html#limitations">Understand FOP's Limitations</link>.</p>
</section><section id="next-release"><title>1.9. When is the next released planned?</title>
<p>
- When it's ready and the committers have enough time to go through
+ When it's ready and the committers have enough time to go through
the time-consuming process of creating a release. We
released version 0.95 on August 6th, 2008, and intend to
release version 1.0 once we consider it "feature complete", major
@@ -301,7 +301,7 @@
import javax.xml.transform.TransformerException;
public class DefaultErrorListener implements ErrorListener {
-
+
public void warning(TransformerException exc) {
System.err.println(exc.toString());
}
@@ -323,8 +323,8 @@
-9075848379822693399, local class serialVersionUID = 8755432068669997367).
Discarding font cache file."</title>
<p>
- This message is a warning that FOP failed to read from the Font cache.
- Which means any Font auto detection or Font directories will be re-scanned.
+ This message is a warning that FOP failed to read from the Font cache.
+ Which means any Font auto detection or Font directories will be re-scanned.
So this failure doesn't break anything.
</p>
<p>
@@ -498,24 +498,24 @@
</p>
</section><section id="table-cell-wrap"><title>3.9. The contents of table cells don’t wrap</title>
<p>You probably have <code>keep-together="always"</code> set on the table cell. See <link href="#keep-together">next question</link>.</p>
- </section><section id="keep-together"><title>3.10. FOP 0.95 and FOP 0.94 behave differently when <code>keep-together="always"</code>
+ </section><section id="keep-together"><title>3.10. FOP 0.95 and FOP 0.94 behave differently when <code>keep-together="always"</code>
is set on table cells</title>
- <p>Support for inline-level keeps has been added in FOP 0.95, and setting
- <code>keep-together="always"</code> also implicitly sets
+ <p>Support for inline-level keeps has been added in FOP 0.95, and setting
+ <code>keep-together="always"</code> also implicitly sets
<code>keep-together.within-line="always"</code>, which forbids FOP
- to break the text into multiple lines. Set
- <code>keep-together.within-column="always"</code> on table-cell instead. It’s a good idea
+ to break the text into multiple lines. Set
+ <code>keep-together.within-column="always"</code> on table-cell instead. It’s a good idea
not to use the shorthand <code>keep-together="always"</code> at all!</p>
- </section><section id="row-height-constraint"><title>3.11. FOP tells me: "The contents of row 1 are taller than they should be".
+ </section><section id="row-height-constraint"><title>3.11. FOP tells me: "The contents of row 1 are taller than they should be".
What does that mean?</title>
<p>
This is usually caused by setting a "height" on a table-row or table-cell and when
- the content is higher than the specified height. By setting "height" (a so-called
- corresponding property) you
+ the content is higher than the specified height. By setting "height" (a so-called
+ corresponding property) you
<link href="http://www.w3.org/TR/xsl11/#d0e4413">implicitely set</link>
- block-progression-dimension.minimum, block-progression-dimension.optimum and
- block-progression-dimension.maximum to the same value. You'll get some information
- about that in the warning message. Look for something like:
+ block-progression-dimension.minimum, block-progression-dimension.optimum and
+ block-progression-dimension.maximum to the same value. You'll get some information
+ about that in the warning message. Look for something like:
"MinOptMax[min=opt=max=14000]".
</p>
<p>
@@ -547,16 +547,16 @@
</section><section id="indent-inheritance"><title>3.14. When I use margins, my content in a nested table or block-containers gets indented twice. Is this a bug?</title>
<p>
(Applies to version 0.90 and later)
- No, although you might easily think so. The problem has to do
- with property inheritance of the start-indent and end-indent
- properties to which the margin properties are mapped. Apache
- FOP strictly adheres to the XSL-FO specification here which many
- other commercial FO implementations don't do to better meet end-user
- expectations. You can make FOP behave like these if you set
- <code>setBreakIndentInheritanceOnReferenceAreaBoundary(true)</code>
+ No, although you might easily think so. The problem has to do
+ with property inheritance of the start-indent and end-indent
+ properties to which the margin properties are mapped. Apache
+ FOP strictly adheres to the XSL-FO specification here which many
+ other commercial FO implementations don't do to better meet end-user
+ expectations. You can make FOP behave like these if you set
+ <code>setBreakIndentInheritanceOnReferenceAreaBoundary(true)</code>
on the FOUserAgent. The better way is to reset <code>start-indent</code>
- and <code>end-indent</code> to "0pt" on table-body or block-container.
- For further details, please consult the
+ and <code>end-indent</code> to "0pt" on table-body or block-container.
+ For further details, please consult the
<link href="http://wiki.apache.org/xmlgraphics-fop/IndentInheritance">Wiki page on Indent Inheritance</link>.
</p>
</section><section id="pdf-ps-java2d-differences"><title>3.15. Why is the output of Java2D/AWT-based renderers different than, for example, PDF or PS?</title>
@@ -665,19 +665,19 @@
</section><section id="svg-attribute-required"><title>5.6. FOP fails with something like "The attribute "width" of the element <rect> is required". What's wrong?</title>
<p>
This phenomenon occurs since FOP 0.92 beta. It surfaced due to a change in the handling of non-FO namespaces. It's not a
- bug in FOP, but rather in the dependent packages: Apache Batik, Apache Xalan-J and SAXON. The bug in Apache Batik will be
+ bug in FOP, but rather in the dependent packages: Apache Batik, Apache Xalan-J and SAXON. The bug in Apache Batik will be
fixed in the next release. In the latest release of Apache Xalan-J, the bug is already fixed. It only occurs in the Xalan
version bundled with Sun's JVM, because Sun uses a rather old version.
</p>
<p>
- Bug description: In a namespace-enabled Level 3 DOM, an attribute in the default namespace must be set with
- <code>"null"</code> as the value for the namespace URI. SAX, on the other side, uses an empty string ("") to designate
- the default namespace. Many packages appear to not properly handle this difference in which case they still use the empty
+ Bug description: In a namespace-enabled Level 3 DOM, an attribute in the default namespace must be set with
+ <code>"null"</code> as the value for the namespace URI. SAX, on the other side, uses an empty string ("") to designate
+ the default namespace. Many packages appear to not properly handle this difference in which case they still use the empty
string as the namespace URI parameter for <code>org.w3c.dom.Element.setAttributeNS()</code>.
</p>
<p>
- Work-around: Use the latest version of Apache Xalan-J. Note that starting with JDK 1.4 it's not enough to replace Xalan-J
- on the normal application classpath and you need to override the Xalan-J version bundled with the Sun JVM using the
+ Work-around: Use the latest version of Apache Xalan-J. Note that starting with JDK 1.4 it's not enough to replace Xalan-J
+ on the normal application classpath and you need to override the Xalan-J version bundled with the Sun JVM using the
<link href="http://java.sun.com/j2se/1.4.2/docs/guide/standards/">Endorsed Standards Override Mechanism</link>, i.e.
you must place Xalan-J in the <code>"lib/endorsed"</code> directory of your JRE.
</p>
@@ -742,8 +742,8 @@
<p>
FOP versions 0.93 and later support the starting-state property of the XSL 1.1
<link href="http://www.w3.org/TR/xsl11/#fo_bookmark">fo:bookmark</link>
- element which can be used for this. The color, font-style and
- font-weight properties on
+ element which can be used for this. The color, font-style and
+ font-weight properties on
<link href="http://www.w3.org/TR/xsl11/#fo_bookmark-title">fo:bookmark-title</link>
are not yet supported, though.
</p>
Modified: xmlgraphics/site/deploy/fop/fo.html
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/fo.html?rev=911805&r1=911804&r2=911805&view=diff
==============================================================================
--- xmlgraphics/site/deploy/fop/fo.html (original)
+++ xmlgraphics/site/deploy/fop/fo.html Fri Feb 19 13:14:50 2010
@@ -284,7 +284,7 @@
<p>
FOP uses XSL-FO as input.
It is the responsibility of the user to make sure that the XSL-FO submitted to FOP is correct.
-The tutorial items presented here are not comprehensive, but are of the FAQ variety. Another
+The tutorial items presented here are not comprehensive, but are of the FAQ variety. Another
good FAQ is <a class="external" href="http://www.dpawson.co.uk/xsl/">Dave Pawson's XSL FAQ</a>.
</p>
</div>
@@ -446,8 +446,8 @@
<a name="N100D4"></a><a name="fo-right-align-table-horizon"></a>
<h3 class="underlined_5">Right-Aligning (Tables)</h3>
<p>
- To right-align a table, you can use the same approach as above for centering tables.
- Just remove the last table-column element which causes all the left-over space not
+ To right-align a table, you can use the same approach as above for centering tables.
+ Just remove the last table-column element which causes all the left-over space not
used by the columns with a fixed column-width to be assigned to the first column which
effectively right-aligns the table.
</p>
@@ -778,7 +778,7 @@
</div>
<span class="version">
- version 627324</span>
+ version 911792</span>
</div>
<!--+
|end content
Modified: xmlgraphics/site/deploy/fop/fo.pdf
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/fo.pdf?rev=911805&r1=911804&r2=911805&view=diff
==============================================================================
Files xmlgraphics/site/deploy/fop/fo.pdf (original) and xmlgraphics/site/deploy/fop/fo.pdf Fri Feb 19 13:14:50 2010 differ
Modified: xmlgraphics/site/deploy/fop/fo.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/fo.xml?rev=911805&r1=911804&r2=911805&view=diff
==============================================================================
--- xmlgraphics/site/deploy/fop/fo.xml (original)
+++ xmlgraphics/site/deploy/fop/fo.xml Fri Feb 19 13:14:50 2010
@@ -13,12 +13,12 @@
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
---><!-- $Id$ --><!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN" "http://svn.apache.org/viewvc/forrest/trunk/main/webapp/resources/schema/dtd/document-v12.dtd?view=co">
+--><!-- $Id$ --><!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "http://forrest.apache.org/dtd/document-v13.dtd">
<document>
<header>
<title>XSL-FO Input</title>
<subtitle>Basic Help for Using XML, XSLT, and XSL-FO</subtitle>
- <version>$Revision: 627324 $</version>
+ <version>$Revision: 911792 $</version>
</header>
<body>
<section id="overview">
@@ -26,7 +26,7 @@
<p>
FOP uses XSL-FO as input.
It is the responsibility of the user to make sure that the XSL-FO submitted to FOP is correct.
-The tutorial items presented here are not comprehensive, but are of the FAQ variety. Another
+The tutorial items presented here are not comprehensive, but are of the FAQ variety. Another
good FAQ is <fork href="http://www.dpawson.co.uk/xsl/">Dave Pawson's XSL FAQ</fork>.
</p>
</section>
@@ -188,8 +188,8 @@
<section id="fo-right-align-table-horizon">
<title>Right-Aligning (Tables)</title>
<p>
- To right-align a table, you can use the same approach as above for centering tables.
- Just remove the last table-column element which causes all the left-over space not
+ To right-align a table, you can use the same approach as above for centering tables.
+ Just remove the last table-column element which causes all the left-over space not
used by the columns with a fixed column-width to be assigned to the first column which
effectively right-aligns the table.
</p>
Modified: xmlgraphics/site/deploy/fop/index.html
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/index.html?rev=911805&r1=911804&r2=911805&view=diff
==============================================================================
--- xmlgraphics/site/deploy/fop/index.html (original)
+++ xmlgraphics/site/deploy/fop/index.html Fri Feb 19 13:14:50 2010
@@ -285,7 +285,7 @@
</div>
<span class="version">
- version 738774</span>
+ version 911792</span>
</div>
<!--+
|end content
Modified: xmlgraphics/site/deploy/fop/index.pdf
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/index.pdf?rev=911805&r1=911804&r2=911805&view=diff
==============================================================================
Files xmlgraphics/site/deploy/fop/index.pdf (original) and xmlgraphics/site/deploy/fop/index.pdf Fri Feb 19 13:14:50 2010 differ
Modified: xmlgraphics/site/deploy/fop/index.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/index.xml?rev=911805&r1=911804&r2=911805&view=diff
==============================================================================
--- xmlgraphics/site/deploy/fop/index.xml (original)
+++ xmlgraphics/site/deploy/fop/index.xml Fri Feb 19 13:14:50 2010
@@ -13,11 +13,11 @@
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
---><!-- $Id$ --><!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN" "http://forrest.apache.org/dtd/document-v11.dtd">
+--><!-- $Id$ --><!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "http://forrest.apache.org/dtd/document-v13.dtd">
<document>
<header>
<title>Apache FOP</title>
- <version>$Revision: 738774 $</version>
+ <version>$Revision: 911792 $</version>
</header>
<body>
<section id="intro">
Modified: xmlgraphics/site/deploy/fop/license.html
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/license.html?rev=911805&r1=911804&r2=911805&view=diff
==============================================================================
--- xmlgraphics/site/deploy/fop/license.html (original)
+++ xmlgraphics/site/deploy/fop/license.html Fri Feb 19 13:14:50 2010
@@ -215,7 +215,7 @@
<h2 class="underlined_10">License</h2>
<div class="section">
<p>
- All new Apache FOP releases will be licensed under the <strong>Apache License, version 2.0</strong>.
+ All new Apache FOP releases will be licensed under the <strong>Apache License, version 2.0</strong>.
Releases until version 0.20.5 are released unter the Apache License, version 1.1.
</p>
<p>
@@ -233,7 +233,7 @@
</div>
<span class="version">
- version 627324</span>
+ version 911792</span>
</div>
<!--+
|end content
Modified: xmlgraphics/site/deploy/fop/license.pdf
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/license.pdf?rev=911805&r1=911804&r2=911805&view=diff
==============================================================================
Files xmlgraphics/site/deploy/fop/license.pdf (original) and xmlgraphics/site/deploy/fop/license.pdf Fri Feb 19 13:14:50 2010 differ
Modified: xmlgraphics/site/deploy/fop/license.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/license.xml?rev=911805&r1=911804&r2=911805&view=diff
==============================================================================
--- xmlgraphics/site/deploy/fop/license.xml (original)
+++ xmlgraphics/site/deploy/fop/license.xml Fri Feb 19 13:14:50 2010
@@ -13,17 +13,17 @@
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
---><!-- $Id$ --><!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN" "http://svn.apache.org/viewvc/forrest/trunk/main/webapp/resources/schema/dtd/document-v12.dtd?view=co">
+--><!-- $Id$ --><!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "http://forrest.apache.org/dtd/document-v13.dtd">
<document>
<header>
<title>Apache FOP License</title>
- <version>$Revision: 627324 $</version>
+ <version>$Revision: 911792 $</version>
</header>
<body>
<section>
<title>License</title>
<p>
- All new Apache FOP releases will be licensed under the <strong>Apache License, version 2.0</strong>.
+ All new Apache FOP releases will be licensed under the <strong>Apache License, version 2.0</strong>.
Releases until version 0.20.5 are released unter the Apache License, version 1.1.
</p>
<p>
Modified: xmlgraphics/site/deploy/fop/trunk/upgrading.html
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/upgrading.html?rev=911805&r1=911804&r2=911805&view=diff
==============================================================================
--- xmlgraphics/site/deploy/fop/trunk/upgrading.html (original)
+++ xmlgraphics/site/deploy/fop/trunk/upgrading.html Fri Feb 19 13:14:50 2010
@@ -218,7 +218,7 @@
<h2 class="underlined_10">Important!</h2>
<div class="section">
<p>
- If you're planning to upgrade to the latest FOP version there are a few very important things
+ If you're planning to upgrade to the latest FOP version there are a few very important things
to consider:
</p>
<ul>
@@ -263,7 +263,7 @@
<li>
<p>
- The new code is much more strict about the interpretation of the XSL-FO 1.0 specification.
+ The new code is much more strict about the interpretation of the XSL-FO 1.1 specification.
Things that worked fine in version 0.20.5 might start to produce warnings or even errors
now. FOP 0.20.5 contains many bugs which have been corrected in the new code.
</p>
@@ -273,8 +273,8 @@
<div class="content">
While FOP 0.20.5 allowed you to have empty <span class="codefrag">fo:table-cell</span> elements, the new code
will complain about that (unless relaxed validation is enabled) because the specification
- demands at least one block-level element (<span class="codefrag">(%block;)+</span>, see
- <a class="external" href="http://www.w3.org/TR/2001/REC-xsl-20011015/slice6.html#fo_table-cell">XSL-FO 1.0, 6.7.10</a>)
+ demands at least one block-level element (<span class="codefrag">(%block;)+</span>, see
+ <a class="external" href="http://www.w3.org/TR/xsl/#fo_table-cell">XSL-FO 1.1, 6.7.10</a>)
inside an <span class="codefrag">fo:table-cell</span> element.
</div>
</div>
@@ -282,8 +282,8 @@
</li>
<li>
- Extensions and Renderers written for version 0.20.5 will not work with the new code! The new FOP
- extension for <a class="external" href="http://barcode4j.sourceforge.net">Barcode4J</a> is available since
+ Extensions and Renderers written for version 0.20.5 will not work with the new code! The new FOP
+ extension for <a class="external" href="http://barcode4j.sourceforge.net">Barcode4J</a> is available since
January 2007.
</li>
@@ -322,18 +322,18 @@
</li>
<li>
- 0.20.5 is not XSL-FO compliant with respect to sizing images (<span class="codefrag">external-graphic</span>)
+ 0.20.5 is not XSL-FO compliant with respect to sizing images (<span class="codefrag">external-graphic</span>)
or <span class="codefrag">instream-foreign-object</span>
objects. If images or SVGs are sized differently in your outputs with the new FOP version
check <a class="external" href="http://issues.apache.org/bugzilla/show_bug.cgi?id=37136">Bug 37136</a>
- as it contains some hints on what to do. The file
+ as it contains some hints on what to do. The file
<a class="external" href="http://svn.apache.org/viewcvs.cgi/xmlgraphics/fop/trunk/examples/fo/basic/images.fo?view=markup">
<span class="codefrag">"examples/fo/basic/images.fo"</span></a> has
a number of good examples that show the new, more correct behaviour.
</li>
<li>
- The <span class="codefrag">fox:outline</span> extension is not implemented in this version anymore.
+ The <span class="codefrag">fox:outline</span> extension is not implemented in this version anymore.
It has been superseded by the new bookmark elements from XSL-FO 1.1.
</li>
@@ -341,7 +341,7 @@
</div>
<span class="version">
- version 733034</span>
+ version 911800</span>
</div>
<!--+
|end content
Modified: xmlgraphics/site/deploy/fop/trunk/upgrading.pdf
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/upgrading.pdf?rev=911805&r1=911804&r2=911805&view=diff
==============================================================================
Files xmlgraphics/site/deploy/fop/trunk/upgrading.pdf (original) and xmlgraphics/site/deploy/fop/trunk/upgrading.pdf Fri Feb 19 13:14:50 2010 differ
Modified: xmlgraphics/site/deploy/fop/trunk/upgrading.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/upgrading.xml?rev=911805&r1=911804&r2=911805&view=diff
==============================================================================
--- xmlgraphics/site/deploy/fop/trunk/upgrading.xml (original)
+++ xmlgraphics/site/deploy/fop/trunk/upgrading.xml Fri Feb 19 13:14:50 2010
@@ -17,13 +17,13 @@
<document>
<header>
<title>Upgrading from an Earlier Version of Apache FOP</title>
- <version>$Revision: 733034 $</version>
+ <version>$Revision: 911800 $</version>
</header>
<body>
<section id="important">
<title>Important!</title>
<p>
- If you're planning to upgrade to the latest FOP version there are a few very important things
+ If you're planning to upgrade to the latest FOP version there are a few very important things
to consider:
</p>
<ul>
@@ -61,21 +61,21 @@
</li>
<li>
<p>
- The new code is much more strict about the interpretation of the XSL-FO 1.0 specification.
+ The new code is much more strict about the interpretation of the XSL-FO 1.1 specification.
Things that worked fine in version 0.20.5 might start to produce warnings or even errors
now. FOP 0.20.5 contains many bugs which have been corrected in the new code.
</p>
<note label="An example">
While FOP 0.20.5 allowed you to have empty <code>fo:table-cell</code> elements, the new code
will complain about that (unless relaxed validation is enabled) because the specification
- demands at least one block-level element (<code>(%block;)+</code>, see
- <link href="http://www.w3.org/TR/2001/REC-xsl-20011015/slice6.html#fo_table-cell">XSL-FO 1.0, 6.7.10</link>)
+ demands at least one block-level element (<code>(%block;)+</code>, see
+ <link href="http://www.w3.org/TR/xsl/#fo_table-cell">XSL-FO 1.1, 6.7.10</link>)
inside an <code>fo:table-cell</code> element.
</note>
</li>
<li>
- Extensions and Renderers written for version 0.20.5 will not work with the new code! The new FOP
- extension for <link href="http://barcode4j.sourceforge.net">Barcode4J</link> is available since
+ Extensions and Renderers written for version 0.20.5 will not work with the new code! The new FOP
+ extension for <link href="http://barcode4j.sourceforge.net">Barcode4J</link> is available since
January 2007.
</li>
<li>
@@ -106,17 +106,17 @@
and <code>block-container</code> elements, for example.
</li>
<li>
- 0.20.5 is not XSL-FO compliant with respect to sizing images (<code>external-graphic</code>)
+ 0.20.5 is not XSL-FO compliant with respect to sizing images (<code>external-graphic</code>)
or <code>instream-foreign-object</code>
objects. If images or SVGs are sized differently in your outputs with the new FOP version
check <link href="http://issues.apache.org/bugzilla/show_bug.cgi?id=37136">Bug 37136</link>
- as it contains some hints on what to do. The file
+ as it contains some hints on what to do. The file
<link href="http://svn.apache.org/viewcvs.cgi/xmlgraphics/fop/trunk/examples/fo/basic/images.fo?view=markup">
<code>"examples/fo/basic/images.fo"</code></link> has
a number of good examples that show the new, more correct behaviour.
</li>
<li>
- The <code>fox:outline</code> extension is 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>
</ul>
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: commits-help@xmlgraphics.apache.org