xmlgraphics-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r840806 [13/19] - in /websites/staging/xmlgraphics/trunk/content: ./ batik/ batik/dev/ batik/tools/ batik/using/ batik/using/scripting/ commons/ fop/ fop/0.95/ fop/1.0/ fop/1.1/ fop/dev/ fop/dev/design/ fop/trunk/
Date Wed, 05 Dec 2012 08:23:58 GMT
Modified: websites/staging/xmlgraphics/trunk/content/fop/1.1/upgrading.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.1/upgrading.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.1/upgrading.html Wed Dec  5 08:23:47
2012
@@ -349,13 +349,13 @@ $(document).ready(function () {
 <p>The intermediate format (IF) output format has underwent minor modification as follows:</p>
 <ul>
 <li>
-<p>In order to track changes to the IF format, a <code>version</code> attribute
has been added to the root <code>document</code> element. Since no version information
was provided previously, the initial value of this attribute is <code>2.0</code>
. Future backward compatible changes will update the minor version number, while future non-backward
compatible changes will update the major version number.</p>
+<p>In order to track changes to the IF format, a <code>version</code> attribute
has been added to the root <code>document</code> element. Since no version information
was provided previously, the initial value of this attribute is <code>2.0</code>.
Future backward compatible changes will update the minor version number, while future non-backward
compatible changes will update the major version number.</p>
 </li>
 <li>
-<p>On the <code>text</code> element, a new alternate representation is
used for adjustments to glyph positions as expressed by a <code>dp</code> attribute
instead of the <code>dx</code> attribute. For further information, see <a href="http://mail-archives.apache.org/mod_mbox/xmlgraphics-fop-dev/201202.mbox/%3cCACQ=j+evStXx=7hW=CHVNKCrZHUso9FHZCSk_5EoENOHcGpGOg@mail.gmail.com%3e">complex
script patch - intermediate format changes</a> .</p>
+<p>On the <code>text</code> element, a new alternate representation is
used for adjustments to glyph positions as expressed by a <code>dp</code> attribute
instead of the <code>dx</code> attribute. For further information, see <a href="http://mail-archives.apache.org/mod_mbox/xmlgraphics-fop-dev/201202.mbox/%3cCACQ=j+evStXx=7hW=CHVNKCrZHUso9FHZCSk_5EoENOHcGpGOg@mail.gmail.com%3e">complex
script patch - intermediate format changes</a>.</p>
 </li>
 <li>
-<p>On the <code>border-rect</code> element, the attributes { <code>before</code>
, <code>after</code> , <code>start</code> , <code>end</code>
} have been renamed to { <code>top</code> , <code>bottom</code> ,
<code>left</code> , <code>right</code> }, respectively. For further
information, see <a href="http://mail-archives.apache.org/mod_mbox/xmlgraphics-fop-dev/201202.mbox/%3cCACQ=j+evStXx=7hW=CHVNKCrZHUso9FHZCSk_5EoENOHcGpGOg@mail.gmail.com%3e">complex
script patch - intermediate format changes</a> .</p>
+<p>On the <code>border-rect</code> element, the attributes { <code>before</code>,
<code>after</code>, <code>start</code>, <code>end</code>
} have been renamed to { <code>top</code>, <code>bottom</code>, <code>left</code>,
<code>right</code> }, respectively. For further information, see <a href="http://mail-archives.apache.org/mod_mbox/xmlgraphics-fop-dev/201202.mbox/%3cCACQ=j+evStXx=7hW=CHVNKCrZHUso9FHZCSk_5EoENOHcGpGOg@mail.gmail.com%3e">complex
script patch - intermediate format changes</a>.</p>
 </li>
 </ul>
 </li>
@@ -366,7 +366,7 @@ $(document).ready(function () {
 <p>The area tree (AT) output format has underwent minor modification as follows:</p>
 <ul>
 <li>
-<p>In order to track changes to the AT format, a <code>version</code> attribute
has been added to the root <code>areaTree</code> element. Since no version information
was provided previously, the initial value of this attribute is <code>2.0</code>
. Future backward compatible changes will update the minor version number, while future non-backward
compatible changes will update the major version number.</p>
+<p>In order to track changes to the AT format, a <code>version</code> attribute
has been added to the root <code>areaTree</code> element. Since no version information
was provided previously, the initial value of this attribute is <code>2.0</code>.
Future backward compatible changes will update the minor version number, while future non-backward
compatible changes will update the major version number.</p>
 </li>
 <li>
 <p>An optional <code>level</code> attribute has been added to a number
of element types to express resolved bidirectional level.</p>
@@ -384,7 +384,7 @@ $(document).ready(function () {
 <p>If you're planning to upgrade to the latest Apache&trade; FOP version from a
pre-1.0 version, there are a few very important things to consider:</p>
 <ul>
 <li>
-<p>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>
.</p>
+<p>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>.</p>
 </li>
 <li>
 <p>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.</p>
@@ -395,10 +395,11 @@ $(document).ready(function () {
 <li>
 <p>Beginning with version 0.94 you can skip the generation of font metric files and
remove the "font-metrics" attribute in the font configuration. In the unlikely case that due
to a bug you still need to use font metrics files you will need to regenerate the font metrics
file if yours are from a FOP version before 0.93.</p>
 </li>
-<li>
-<p>The new code is much more strict about the interpretation of the XSL-FO 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.
-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 <a
href="http://www.w3.org/TR/xsl/#fo_table-cell">XSL-FO 1.1, 6.7.10</a> ) inside an
<code>fo:table-cell</code> element.</p>
-</li>
+</ul>
+<p>-
+The new code is much more strict about the interpretation of the XSL-FO 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.
+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 <a
href="http://www.w3.org/TR/xsl/#fo_table-cell">XSL-FO 1.1, 6.7.10</a> ) inside an
<code>fo:table-cell</code> element.</p>
+<ul>
 <li>
 <p>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.sourceforge.net">Barcode4J</a>
is available since January 2007.</p>
 </li>

Modified: websites/staging/xmlgraphics/trunk/content/fop/bugs.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/bugs.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/bugs.html Wed Dec  5 08:23:47 2012
@@ -344,7 +344,7 @@ $(document).ready(function () {
       	<div class="section-content"><h1 id="apachewzxhzdk0-fop-bugs-and-other-trackable-issues">Apache&trade;
FOP: Bugs and Other Trackable Issues</h1>
 <p>Information on this page applies to enhancement requests and other trackable issues
as well as bugs.</p>
 <h2 id="reported-issues-wzxhzdk1wzxhzdk2">Reported Issues <a id="issues_existing"></a></h2>
-<p>A list of unresolved reported bugs can be found at <a href="http://issues.apache.org/bugzilla/buglist.cgi?bug_status=NEW&amp;bug_status=ASSIGNED&amp;bug_status=REOPENED&amp;email1=&amp;emailtype1=substring&amp;emailassigned_to1=1&amp;email2=&amp;emailtype2=substring&amp;emailreporter2=1&amp;bugidtype=include&amp;bug_id=&amp;changedin=&amp;votes=&amp;chfieldfrom=&amp;chfieldto=Now&amp;chfieldvalue=&amp;product=Fop&amp;short_desc=&amp;short_desc_type=allwordssubstr&amp;long_desc=&amp;long_desc_type=allwordssubstr&amp;bug_file_loc=&amp;bug_file_loc_type=allwordssubstr&amp;keywords=&amp;keywords_type=anywords&amp;field0-0-0=noop&amp;type0-0-0=noop&amp;value0-0-0=">FOP
Open Bugs (Bugzilla)</a> . If you have an interest in an issue already reported, please
consider the following:</p>
+<p>A list of unresolved reported bugs can be found at <a href="http://issues.apache.org/bugzilla/buglist.cgi?bug_status=NEW&amp;bug_status=ASSIGNED&amp;bug_status=REOPENED&amp;email1=&amp;emailtype1=substring&amp;emailassigned_to1=1&amp;email2=&amp;emailtype2=substring&amp;emailreporter2=1&amp;bugidtype=include&amp;bug_id=&amp;changedin=&amp;votes=&amp;chfieldfrom=&amp;chfieldto=Now&amp;chfieldvalue=&amp;product=Fop&amp;short_desc=&amp;short_desc_type=allwordssubstr&amp;long_desc=&amp;long_desc_type=allwordssubstr&amp;bug_file_loc=&amp;bug_file_loc_type=allwordssubstr&amp;keywords=&amp;keywords_type=anywords&amp;field0-0-0=noop&amp;type0-0-0=noop&amp;value0-0-0=">FOP
Open Bugs (Bugzilla)</a>. If you have an interest in an issue already reported, please
consider the following:</p>
 <ul>
 <li>
 <p>If you have insight that may help developers solve an existing problem, please add
comments and/or file attachments to the existing issue.</p>
@@ -363,7 +363,7 @@ $(document).ready(function () {
 <p>Review the <a href="http://issues.apache.org/bugzilla/page.cgi?id=bug-writing.html">Apache
Bug Writing Guidelines</a> before submitting your report.</p>
 </li>
 <li>
-<p>Enter a new issue report at <a href="http://issues.apache.org/bugzilla/enter_bug.cgi?product=Fop">The
FOP issue database (Bugzilla)</a> . You will be asked to login to an existing Bugzilla
account or to create a new one. When entering the bug report, please make your description
complete and concise. If the issue involves a specific input or output file, then please include
the following information in the bug report (preferably as one or more attachments):</p>
+<p>Enter a new issue report at <a href="http://issues.apache.org/bugzilla/enter_bug.cgi?product=Fop">The
FOP issue database (Bugzilla)</a>. You will be asked to login to an existing Bugzilla
account or to create a new one. When entering the bug report, please make your description
complete and concise. If the issue involves a specific input or output file, then please include
the following information in the bug report (preferably as one or more attachments):</p>
 <ul>
 <li>an input XSL-FO file (if you generate the XSL-FO file from an input XML using XSLT,
then please directly provide the result of the transformation--the XSL-FO output--not the
XML input and XSLT). Please try and make the XSL-FO input as small as possible; Ideally it
would contain nothing more than the minimum needed to demonstrate the problem. By doing this
you increase your chance that a developer will take the time to look at your file.</li>
 <li>a resulting output file, preferably in PDF format, unless the issue being reported
involves a different output format; In which case please provide the output in that format;</li>



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


Mime
View raw message