xmlgraphics-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r840806 [17/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/resources.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/resources.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/resources.html Wed Dec  5 08:23:47 2012
@@ -347,7 +347,7 @@ $(document).ready(function () {
 <h3 id="xsl-fo-wzxhzdk6wzxhzdk7">XSL-FO <a id="specs-xslfo"></a></h3>
 <ul>
 <li>
-<p><a href="http://www.w3.org/TR/xsl11/">XSL-FO Recommendation (05 December 2006)</a> </p>
+<p><a href="http://www.w3.org/TR/xsl11/">XSL-FO Recommendation (05 December 2006)</a></p>
 </li>
 <li>
 <p><a href="http://www.renderx.com/Tests/validator/fo.dtd.html">Unofficial DTD for the XSL-FO Recommendation</a> provided by N. Grigoriev from RenderX.</p>
@@ -356,156 +356,156 @@ $(document).ready(function () {
 <h3 id="xslt-wzxhzdk8wzxhzdk9">XSLT <a id="specs-xslt"></a></h3>
 <ul>
 <li>
-<p><a href="http://www.w3.org/TR/xslt">XSLT 1.0 Recommendation</a> </p>
+<p><a href="http://www.w3.org/TR/xslt">XSLT 1.0 Recommendation</a></p>
 </li>
 <li>
-<p><a href="http://www.w3.org/TR/xslt20">XSLT 2.0 Recommendation</a> </p>
+<p><a href="http://www.w3.org/TR/xslt20">XSLT 2.0 Recommendation</a></p>
 </li>
 </ul>
 <h3 id="xml-wzxhzdk10wzxhzdk11">XML <a id="specs-xml"></a></h3>
 <ul>
 <li>
-<p><a href="http://www.w3.org/TR/xml">XML 1.0</a> </p>
+<p><a href="http://www.w3.org/TR/xml">XML 1.0</a></p>
 </li>
 <li>
-<p><a href="http://www.w3.org/TR/xml11">XML 1.1</a> </p>
+<p><a href="http://www.w3.org/TR/xml11">XML 1.1</a></p>
 </li>
 <li>
-<p><a href="http://sax.sourceforge.net/">Simple API for XML (SAX)</a> </p>
+<p><a href="http://sax.sourceforge.net/">Simple API for XML (SAX)</a></p>
 </li>
 <li>
-<p><a href="http://www.w3.org/TR/REC-DOM-Level-1">Document Object Model (DOM)</a> </p>
+<p><a href="http://www.w3.org/TR/REC-DOM-Level-1">Document Object Model (DOM)</a></p>
 </li>
 <li>
-<p><a href="http://www.w3.org/TR/DOM-Level-2-Core">Document Object Model (DOM) Level 2 Core Specification</a> </p>
+<p><a href="http://www.w3.org/TR/DOM-Level-2-Core">Document Object Model (DOM) Level 2 Core Specification</a></p>
 </li>
 <li>
-<p><a href="http://www.w3.org/TR/DOM-Level-3-Core">Document Object Model (DOM) Level 3 Core Specification</a> </p>
+<p><a href="http://www.w3.org/TR/DOM-Level-3-Core">Document Object Model (DOM) Level 3 Core Specification</a></p>
 </li>
 <li>
-<p><a href="http://www.w3.org/TR/xml-names/">Namespaces in XML 1.0</a> </p>
+<p><a href="http://www.w3.org/TR/xml-names/">Namespaces in XML 1.0</a></p>
 </li>
 <li>
-<p><a href="http://www.w3.org/TR/xml-names11/">Namespaces in XML 1.1</a> </p>
+<p><a href="http://www.w3.org/TR/xml-names11/">Namespaces in XML 1.1</a></p>
 </li>
 </ul>
 <h3 id="java-wzxhzdk12wzxhzdk13">Java <a id="specs-java"></a></h3>
 <ul>
 <li>
-<p><a href="http://java.sun.com/j2se/1.4/docs/api/index.html">Java 2 Platform, Standard Edition, v 1.4.2 API Specification</a> </p>
+<p><a href="http://java.sun.com/j2se/1.4/docs/api/index.html">Java 2 Platform, Standard Edition, v 1.4.2 API Specification</a></p>
 </li>
 <li>
-<p><a href="http://java.sun.com/j2se/1.5/docs/api/index.html">Java 2 Platform Standard Edition 5.0 API Specification</a> </p>
+<p><a href="http://java.sun.com/j2se/1.5/docs/api/index.html">Java 2 Platform Standard Edition 5.0 API Specification</a></p>
 </li>
 <li>
-<p><a href="http://java.sun.com/javase/6/docs/api/index.html">Java Platform, Standard Edition 6 API Specification</a> </p>
+<p><a href="http://java.sun.com/javase/6/docs/api/index.html">Java Platform, Standard Edition 6 API Specification</a></p>
 </li>
 </ul>
 <h3 id="pdf-wzxhzdk14wzxhzdk15">PDF <a id="specs-pdf"></a></h3>
 <ul>
-<li><a href="http://partners.adobe.com/asn/tech/pdf/specifications.jsp">Portable Document Format (PDF) Reference Manual</a> </li>
+<li><a href="http://partners.adobe.com/asn/tech/pdf/specifications.jsp">Portable Document Format (PDF) Reference Manual</a></li>
 </ul>
 <h3 id="unicode-wzxhzdk16wzxhzdk17">Unicode <a id="specs-unicode"></a></h3>
 <ul>
-<li><a href="http://www.unicode.org/reports/tr14">UTR-14 (Unicode Standard Annex #14: Line Breaking Properties)</a> </li>
+<li><a href="http://www.unicode.org/reports/tr14">UTR-14 (Unicode Standard Annex #14: Line Breaking Properties)</a></li>
 </ul>
 <h3 id="other-wzxhzdk18wzxhzdk19">Other <a id="specs-other"></a></h3>
 <ul>
-<li><a href="http://www.w3.org/TR/SVG/">Supported SVG Recommendation (04 September 2001)</a> </li>
+<li><a href="http://www.w3.org/TR/SVG/">Supported SVG Recommendation (04 September 2001)</a></li>
 </ul>
 <h2 id="books-tutorials-articles-wzxhzdk20wzxhzdk21">Books, Tutorials, Articles <a id="documents"></a></h2>
 <h3 id="xsl-fo-wzxhzdk22wzxhzdk23">XSL-FO <a id="documents-xslfo"></a></h3>
 <ul>
 <li>
-<p>[online book] <a href="http://www.ibiblio.org/xml/books/bible2/chapters/ch18.html">The XML Bible</a> , by Elliotte Rusty Harold. Chapter 18 of XSL Formatting Objects</p>
+<p>[online book] <a href="http://www.ibiblio.org/xml/books/bible2/chapters/ch18.html">The XML Bible</a>, by Elliotte Rusty Harold. Chapter 18 of XSL Formatting Objects</p>
 </li>
 <li>
-<p>[online article] <a href="http://www.xml.com/pub/a/2001/01/17/xsl-fo/index.html">Using XSL Formatting Objects</a> , by J. David Eisenberg.</p>
+<p>[online article] <a href="http://www.xml.com/pub/a/2001/01/17/xsl-fo/index.html">Using XSL Formatting Objects</a>, by J. David Eisenberg.</p>
 </li>
 <li>
-<p>[online reference] <a href="http://zvon.org/xxl/xslfoReference/Output/index.html">XSL FO reference</a> , by Miloslav Nic.</p>
+<p>[online reference] <a href="http://zvon.org/xxl/xslfoReference/Output/index.html">XSL FO reference</a>, by Miloslav Nic.</p>
 </li>
 <li>
-<p>[online reference] <a href="http://www.dpawson.co.uk/xsl/sect3/index.html">Dave Pawson's XSL-FO FAQ</a> .</p>
+<p>[online reference] <a href="http://www.dpawson.co.uk/xsl/sect3/index.html">Dave Pawson's XSL-FO FAQ</a>.</p>
 </li>
 <li>
-<p>[book] <a href="http://www.oreilly.com/catalog/xslfo">XSL-FO</a> , by Dave Pawson, O'Reilly &amp; Associates, 2002, ISBN 0-596-00355-2. See online version above.</p>
+<p>[book] <a href="http://www.oreilly.com/catalog/xslfo">XSL-FO</a>, by Dave Pawson, O'Reilly &amp; Associates, 2002, ISBN 0-596-00355-2. See online version above.</p>
 </li>
 <li>
-<p>[book] <a href="http://www.amazon.com/exec/obidos/ASIN/0131403745/ref=ase_cranesoftwrig-20">Definitive XSL-FO</a> , by G. Ken Holman, Prentice Hall PTR, 2003, ISBN 0-131-40374-5.</p>
+<p>[book] <a href="http://www.amazon.com/exec/obidos/ASIN/0131403745/ref=ase_cranesoftwrig-20">Definitive XSL-FO</a>, by G. Ken Holman, Prentice Hall PTR, 2003, ISBN 0-131-40374-5.</p>
 </li>
 <li>
-<p>[book] <a href="http://www.amazon.com/XSL-Formatting-Objects-Developers-Handbook/dp/0672322811">XSL Formatting Objects Developer's Handbook</a> , by Doug Lovell, Sams, 2002, ISBN 0-672-32281-1.</p>
+<p>[book] <a href="http://www.amazon.com/XSL-Formatting-Objects-Developers-Handbook/dp/0672322811">XSL Formatting Objects Developer's Handbook</a>, by Doug Lovell, Sams, 2002, ISBN 0-672-32281-1.</p>
 </li>
 <li>
-<p>[book] <a href="http://www.cranesoftwrights.com/training/index.htm#pfux">Practical Formatting Using XSLFO</a> , Crane Softwrights Ltd., 2003, ISBN 1-894049-11-X.</p>
+<p>[book] <a href="http://www.cranesoftwrights.com/training/index.htm#pfux">Practical Formatting Using XSLFO</a>, Crane Softwrights Ltd., 2003, ISBN 1-894049-11-X.</p>
 </li>
 </ul>
 <h3 id="xslt-wzxhzdk24wzxhzdk25">XSLT <a id="documents-xslt"></a></h3>
 <ul>
 <li>
-<p>[online resource] <a href="http://www.w3.org/Style/XSL/">Extensible Stylesheet Language Family (XSL)</a> , W3C XSL Family page.</p>
+<p>[online resource] <a href="http://www.w3.org/Style/XSL/">Extensible Stylesheet Language Family (XSL)</a>, W3C XSL Family page.</p>
 </li>
 <li>
-<p>[book] <a href="http://www.amazon.com/XSLT-Programmers-Reference-2nd-Michael/dp/1861005067">XSLT Programmer's Reference</a> , by Michael H. Kay, Wrox Press, ISBN 1-861-00506-7.</p>
+<p>[book] <a href="http://www.amazon.com/XSLT-Programmers-Reference-2nd-Michael/dp/1861005067">XSLT Programmer's Reference</a>, by Michael H. Kay, Wrox Press, ISBN 1-861-00506-7.</p>
 </li>
 <li>
-<p>[book] <a href="http://www.wrox.com/WileyCDA/WroxTitle/XSLT-2-0-and-XPath-2-0-Programmer-s-Reference-4th-Edition.productCd-0470192747.html">XSLT2 and XPath2 Programmer's Reference</a> , by Michael H. Kay, Wrox Press, ISBN: 978-0-470-19274-0.</p>
+<p>[book] <a href="http://www.wrox.com/WileyCDA/WroxTitle/XSLT-2-0-and-XPath-2-0-Programmer-s-Reference-4th-Edition.productCd-0470192747.html">XSLT2 and XPath2 Programmer's Reference</a>, by Michael H. Kay, Wrox Press, ISBN: 978-0-470-19274-0.</p>
 </li>
 <li>
-<p>[book] <a href="http://www.oreilly.com/catalog/xslt">XSLT</a> , by Doug Tidwell, O'Reilly &amp; Associates, 2001, ISBN 0-596-00053-7.</p>
+<p>[book] <a href="http://www.oreilly.com/catalog/xslt">XSLT</a>, by Doug Tidwell, O'Reilly &amp; Associates, 2001, ISBN 0-596-00053-7.</p>
 </li>
 <li>
-<p>[book] <a href="http://www.oreilly.com/catalog/xsltckbk">XSLT Cookbook</a> , by Sal Mangano, O'Reilly &amp; Associates, 2002, ISBN 0-596-00372-2.</p>
+<p>[book] <a href="http://www.oreilly.com/catalog/xsltckbk">XSLT Cookbook</a>, by Sal Mangano, O'Reilly &amp; Associates, 2002, ISBN 0-596-00372-2.</p>
 </li>
 <li>
-<p>[article] <a href="http://www.dpawson.co.uk/xsl/index.html">Dave Pawson's XSL FAQ</a> .</p>
+<p>[article] <a href="http://www.dpawson.co.uk/xsl/index.html">Dave Pawson's XSL FAQ</a>.</p>
 </li>
 <li>
-<p>[book] <a href="http://www.oreilly.com/catalog/xpathpointer">XPath and XPointer: Locating Content in XML Documents</a> , by John E. Simpson, O'Reilly &amp; Associates, 2002, ISBN 0-596-00291-2.</p>
+<p>[book] <a href="http://www.oreilly.com/catalog/xpathpointer">XPath and XPointer: Locating Content in XML Documents</a>, by John E. Simpson, O'Reilly &amp; Associates, 2002, ISBN 0-596-00291-2.</p>
 </li>
 <li>
-<p>[book] <a href="http://www.amazon.com/XSL-Essentials-Michael-Fitzgerald/dp/0471416207">XSL Essentials</a> , by Michael Fitzgerald, John Wiley &amp; Sons, 2001, ISBN 0-471-41620-7.</p>
+<p>[book] <a href="http://www.amazon.com/XSL-Essentials-Michael-Fitzgerald/dp/0471416207">XSL Essentials</a>, by Michael Fitzgerald, John Wiley &amp; Sons, 2001, ISBN 0-471-41620-7.</p>
 </li>
 <li>
-<p>[book] <a href="http://www.oreilly.com/catalog/javaxslt">Java and XSLT</a> , by Eric M. Burke, O'Reilly &amp; Associates, 2001, ISBN 0-596-00143-6.</p>
+<p>[book] <a href="http://www.oreilly.com/catalog/javaxslt">Java and XSLT</a>, by Eric M. Burke, O'Reilly &amp; Associates, 2001, ISBN 0-596-00143-6.</p>
 </li>
 </ul>
 <h3 id="xml-wzxhzdk26wzxhzdk27">XML <a id="documents-xml"></a></h3>
 <ul>
 <li>
-<p>[online book] <a href="http://www.ibiblio.org/xml/books/bible2">The XML Bible</a> , by Elliotte Rusty Harold. See hardcopy version below.</p>
+<p>[online book] <a href="http://www.ibiblio.org/xml/books/bible2">The XML Bible</a>, by Elliotte Rusty Harold. See hardcopy version below.</p>
 </li>
 <li>
-<p>[book] <a href="http://www.amazon.com/XML-Bible-Elliotte-Rusty-Harold/dp/0764547607">The XML Bible</a> , by Elliotte Rusty Harold, John Wiley &amp; Sons, ISBN 0-764-54760-7. See online version above.</p>
+<p>[book] <a href="http://www.amazon.com/XML-Bible-Elliotte-Rusty-Harold/dp/0764547607">The XML Bible</a>, by Elliotte Rusty Harold, John Wiley &amp; Sons, ISBN 0-764-54760-7. See online version above.</p>
 </li>
 <li>
-<p>[online resource] A great number of additional XML-related books and articles can be found at the <a href="http://xml.oreilly.com">O'Reilly XML Site</a> .</p>
+<p>[online resource] A great number of additional XML-related books and articles can be found at the <a href="http://xml.oreilly.com">O'Reilly XML Site</a>.</p>
 </li>
 </ul>
 <h3 id="java-wzxhzdk28wzxhzdk29">Java <a id="documents-java"></a></h3>
 <ul>
-<li>[online resource] A great number of Java-related books and articles can be found at the <a href="http://java.oreilly.com">O'Reilly Java Site</a> .</li>
+<li>[online resource] A great number of Java-related books and articles can be found at the <a href="http://java.oreilly.com">O'Reilly Java Site</a>.</li>
 </ul>
 <h3 id="pdf-wzxhzdk30wzxhzdk31">PDF <a id="documents-pdf"></a></h3>
 <ul>
 <li>
-<p>[online resource] Links to the various PDF file format specifications and numerous other documents can be found at Adobe Solutions Network, Acrobat Resources, <a href="http://partners.adobe.com/asn/acrobat/docs.jsp#filefmtspecs">Acrobat 5.0 SDK Documentation</a> .</p>
+<p>[online resource] Links to the various PDF file format specifications and numerous other documents can be found at Adobe Solutions Network, Acrobat Resources, <a href="http://partners.adobe.com/asn/acrobat/docs.jsp#filefmtspecs">Acrobat 5.0 SDK Documentation</a>.</p>
 </li>
 <li>
-<p>[online resource] A list of PDF technical resources can be found at Adobe Solutions Network, Acrobat Resources, <a href="http://partners.adobe.com/asn/acrobat/technotes.jsp">Acrobat/PDF Technical Notes</a> </p>
+<p>[online resource] A list of PDF technical resources can be found at Adobe Solutions Network, Acrobat Resources, <a href="http://partners.adobe.com/asn/acrobat/technotes.jsp">Acrobat/PDF Technical Notes</a></p>
 </li>
 <li>
-<p>[online resource] A list of Acrobat and PDF developer resources can be found at Adobe Solutions Network, Acrobat Resources, <a href="http://partners.adobe.com/asn/acrobat">Resources for Developers</a> .</p>
+<p>[online resource] A list of Acrobat and PDF developer resources can be found at Adobe Solutions Network, Acrobat Resources, <a href="http://partners.adobe.com/asn/acrobat">Resources for Developers</a>.</p>
 </li>
 </ul>
 <h3 id="postscript-wzxhzdk32wzxhzdk33">PostScript <a id="documents-ps"></a></h3>
 <ul>
 <li>
-<p>[online resource] A list of PostScript-related technical resources can be found at Adobe Solutions Network, <a href="http://partners.adobe.com/asn/tech/ps/technotes.jsp">PostScript Language Technical Notes</a> </p>
+<p>[online resource] A list of PostScript-related technical resources can be found at Adobe Solutions Network, <a href="http://partners.adobe.com/asn/tech/ps/technotes.jsp">PostScript Language Technical Notes</a></p>
 </li>
 <li>
-<p>[online resource] Additional PostScript-related developer resources can be found at Adobe Solutions Network, <a href="http://partners.adobe.com/asn/tech/ps/index.jsp">PostScript SDK Archive</a> .</p>
+<p>[online resource] Additional PostScript-related developer resources can be found at Adobe Solutions Network, <a href="http://partners.adobe.com/asn/tech/ps/index.jsp">PostScript SDK Archive</a>.</p>
 </li>
 </ul>
 <h2 id="mailing-lists-wzxhzdk34wzxhzdk35">Mailing Lists <a id="mailing-lists"></a></h2>
@@ -524,65 +524,65 @@ $(document).ready(function () {
 <p>Use a mail client that respects the <em>References</em> and/or <em>In-Reply-To</em> mail header entries. This is important for mail clients that can display threads as trees. <strong>Compliant mail clients</strong> include Microsoft Outlook, Becky!, KMail, Apple Mail, Ximian Evolution, Mozilla (version 1.2 or greater). Non-compliant mail clients include Microsoft Exchange, Lotus Notes, Internet Mail Service (MUA or MTA), and dtmail.</p>
 </li>
 </ul>
-<p>For help in understanding email acronyms, see the <a href="http://www.lingo2word.com/lists/acronym_listA.html">Lingo2Word Acronym List</a> , or the <a href="http://www.keno.org/web_design/acronyms.htm">Keno Internet Services Internet Glossary</a> .</p>
+<p>For help in understanding email acronyms, see the <a href="http://www.lingo2word.com/lists/acronym_listA.html">Lingo2Word Acronym List</a>, or the <a href="http://www.keno.org/web_design/acronyms.htm">Keno Internet Services Internet Glossary</a>.</p>
 <h3 id="apache-fop-mailing-list-wzxhzdk36wzxhzdk37">Apache FOP Mailing List <a id="Apache-FOP"></a></h3>
 <ul>
 <li>
-<p>[mailing list info] <a href="http://xml.apache.org/fop/maillist.html">http://xml.apache.org/fop/maillist.html</a> </p>
+<p>[mailing list info] <a href="http://xml.apache.org/fop/maillist.html">http://xml.apache.org/fop/maillist.html</a></p>
 </li>
 <li>
-<p>[fop-users mod_mbox archives] <a href="http://mail-archives.eu.apache.org/mod_mbox/xmlgraphics-fop-users/">http://mail-archives.eu.apache.org/mod_mbox/xmlgraphics-fop-users/</a> </p>
+<p>[fop-users mod_mbox archives] <a href="http://mail-archives.eu.apache.org/mod_mbox/xmlgraphics-fop-users/">http://mail-archives.eu.apache.org/mod_mbox/xmlgraphics-fop-users/</a></p>
 </li>
 <li>
-<p>[fop-users archives] <a href="http://marc.theaimsgroup.com/?l=fop-user">http://marc.theaimsgroup.com/?l=fop-user</a> </p>
+<p>[fop-users archives] <a href="http://marc.theaimsgroup.com/?l=fop-user">http://marc.theaimsgroup.com/?l=fop-user</a></p>
 </li>
 <li>
-<p>[fop-users gzip'd archives] <a href="http://xmlgraphics.apache.org/mail/fop-users/">http://xmlgraphics.apache.org/mail/fop-users/</a> </p>
+<p>[fop-users gzip'd archives] <a href="http://xmlgraphics.apache.org/mail/fop-users/">http://xmlgraphics.apache.org/mail/fop-users/</a></p>
 </li>
 <li>
-<p>[fop-users-subscribe] <a href="mailto:fop-users-subscribe@xmlgraphics.apache.org">fop-users-subscribe@xmlgraphics.apache.org</a> </p>
+<p>[fop-users-subscribe] <a href="mailto:fop-users-subscribe@xmlgraphics.apache.org">fop-users-subscribe@xmlgraphics.apache.org</a></p>
 </li>
 <li>
-<p>[fop-users-digest-subscribe] <a href="mailto:fop-users-digest-subscribe@xmlgraphics.apache.org">fop-users-digest-subscribe@xmlgraphics.apache.org</a> </p>
+<p>[fop-users-digest-subscribe] <a href="mailto:fop-users-digest-subscribe@xmlgraphics.apache.org">fop-users-digest-subscribe@xmlgraphics.apache.org</a></p>
 </li>
 <li>
-<p>[fop-users-unsubscribe] <a href="mailto:fop-users-unsubscribe@xmlgraphics.apache.org">fop-users-subscribe@xmlgraphics.apache.org</a> </p>
+<p>[fop-users-unsubscribe] <a href="mailto:fop-users-unsubscribe@xmlgraphics.apache.org">fop-users-subscribe@xmlgraphics.apache.org</a></p>
 </li>
 <li>
-<p>[fop-dev mod_mbox archives] <a href="http://mail-archives.eu.apache.org/mod_mbox/xmlgraphics-fop-dev/">http://mail-archives.eu.apache.org/mod_mbox/xmlgraphics-fop-dev/</a> </p>
+<p>[fop-dev mod_mbox archives] <a href="http://mail-archives.eu.apache.org/mod_mbox/xmlgraphics-fop-dev/">http://mail-archives.eu.apache.org/mod_mbox/xmlgraphics-fop-dev/</a></p>
 </li>
 <li>
-<p>[fop-dev archives] <a href="http://marc.theaimsgroup.com/?l=fop-dev">http://marc.theaimsgroup.com/?l=fop-dev</a> </p>
+<p>[fop-dev archives] <a href="http://marc.theaimsgroup.com/?l=fop-dev">http://marc.theaimsgroup.com/?l=fop-dev</a></p>
 </li>
 <li>
-<p>[fop-dev gzip'd archives] <a href="http://xmlgraphics.apache.org/mail/fop-dev/">http://xmlgraphics.apache.org/mail/fop-dev/</a> </p>
+<p>[fop-dev gzip'd archives] <a href="http://xmlgraphics.apache.org/mail/fop-dev/">http://xmlgraphics.apache.org/mail/fop-dev/</a></p>
 </li>
 <li>
-<p>[fop-dev-subscribe] <a href="mailto:fop-dev-subscribe@xmlgraphics.apache.org">fop-dev-subscribe@xmlgraphics.apache.org</a> </p>
+<p>[fop-dev-subscribe] <a href="mailto:fop-dev-subscribe@xmlgraphics.apache.org">fop-dev-subscribe@xmlgraphics.apache.org</a></p>
 </li>
 <li>
-<p>[fop-dev-digest-subscribe] <a href="mailto:fop-dev-digest-subscribe@xmlgraphics.apache.org">fop-dev-digest-subscribe@xmlgraphics.apache.org</a> </p>
+<p>[fop-dev-digest-subscribe] <a href="mailto:fop-dev-digest-subscribe@xmlgraphics.apache.org">fop-dev-digest-subscribe@xmlgraphics.apache.org</a></p>
 </li>
 <li>
-<p>[fop-dev-unsubscribe] <a href="mailto:fop-dev-unsubscribe@xmlgraphics.apache.org">fop-dev-unsubscribe@xmlgraphics.apache.org</a> </p>
+<p>[fop-dev-unsubscribe] <a href="mailto:fop-dev-unsubscribe@xmlgraphics.apache.org">fop-dev-unsubscribe@xmlgraphics.apache.org</a></p>
 </li>
 </ul>
 <h3 id="xsl-fo-mailing-list-at-w3c-wzxhzdk38wzxhzdk39">XSL-FO Mailing List (at W3C) <a id="XSL-FO-at-W3C"></a></h3>
 <ul>
 <li>
-<p>[mailing list info] <a href="http://www.w3.org/Mail/Request">http://www.w3.org/Mail/Request</a> </p>
+<p>[mailing list info] <a href="http://www.w3.org/Mail/Request">http://www.w3.org/Mail/Request</a></p>
 </li>
 <li>
-<p>[mailing list archives] <a href="http://lists.w3.org/Archives/Public/www-xsl-fo/">http://lists.w3.org/Archives/Public/www-xsl-fo/</a> </p>
+<p>[mailing list archives] <a href="http://lists.w3.org/Archives/Public/www-xsl-fo/">http://lists.w3.org/Archives/Public/www-xsl-fo/</a></p>
 </li>
 </ul>
 <h3 id="xsl-fo-mailing-list-at-yahoogroups-wzxhzdk40wzxhzdk41">XSL-FO Mailing List (at YahooGroups) <a id="XSL-FO-at-YahooGroups"></a></h3>
 <ul>
-<li>[mailing list info &amp; archives] <a href="http://groups.yahoo.com/group/XSL-FO">http://groups.yahoo.com/group/XSL-FO</a> </li>
+<li>[mailing list info &amp; archives] <a href="http://groups.yahoo.com/group/XSL-FO">http://groups.yahoo.com/group/XSL-FO</a></li>
 </ul>
 <h3 id="xslt-list-mulberry-tech-wzxhzdk42wzxhzdk43">XSLT List (Mulberry Tech) <a id="XSLT-at-Mulberry-Tech"></a></h3>
 <ul>
-<li>[mailing list info &amp; archives] <a href="http://www.mulberrytech.com/xsl/xsl-list">http://www.mulberrytech.com/xsl/xsl-list</a> </li>
+<li>[mailing list info &amp; archives] <a href="http://www.mulberrytech.com/xsl/xsl-list">http://www.mulberrytech.com/xsl/xsl-list</a></li>
 </ul>
 <h2 id="relateduseful-products-wzxhzdk44wzxhzdk45">Related/Useful Products <a id="products"></a></h2>
 <h3 id="fop-add-ons-wzxhzdk46wzxhzdk47">FOP add-ons <a id="products-fop-add-ons"></a></h3>
@@ -666,7 +666,7 @@ $(document).ready(function () {
 <p>[software] <a href="http://www.ahmadsoft.org/fopbridge.html">FOP Bridge</a> is an Eclipse plug-in that allows to convert FO documents using Apache FOP directly inside the Eclipse workbench (LGPL).</p>
 </li>
 <li>
-<p>[software] <a href="http://maven.apache.org/doxia/doxia/doxia-modules/doxia-module-fo/">Maven Doxia FO Module</a> . Doxia is a content generation framework which aims to provide its users with powerful techniques for generating static and dynamic content: Doxia can be used in web-based publishing context to generate static sites, in addition to being incorporated into dynamic content generation systems like blogs, wikis and content management systems. Doxia provides a module providing XSL Formatting Objects.</p>
+<p>[software] <a href="http://maven.apache.org/doxia/doxia/doxia-modules/doxia-module-fo/">Maven Doxia FO Module</a>. Doxia is a content generation framework which aims to provide its users with powerful techniques for generating static and dynamic content: Doxia can be used in web-based publishing context to generate static sites, in addition to being incorporated into dynamic content generation systems like blogs, wikis and content management systems. Doxia provides a module providing XSL Formatting Objects.</p>
 </li>
 </ul></div>
       </div>

Modified: websites/staging/xmlgraphics/trunk/content/fop/team.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/team.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/team.html Wed Dec  5 08:23:47 2012
@@ -399,7 +399,7 @@ $(document).ready(function () {
 </li>
 </ul>
 <h2 id="founder-wzxhzdk5wzxhzdk6">Founder <a id="founder"></a></h2>
-<p>FOP was originally created and donated to the Apache Software Foundation by <a href="mailto:jtauber@jtauber.com">James Tauber</a> . Information about him can be found at<fork href="http://www.jtauber.com">his website</fork>.</p>
+<p>FOP was originally created and donated to the Apache Software Foundation by <a href="mailto:jtauber@jtauber.com">James Tauber</a>. Information about him can be found at<fork href="http://www.jtauber.com">his website</fork>.</p>
 <h2 id="inactive-committers-wzxhzdk9wzxhzdk10">Inactive Committers <a id="commit-inactive"></a></h2>
 <ul>
 <li>
@@ -412,16 +412,16 @@ $(document).ready(function () {
 <p><a href="mailto:jay@bryantcs.com">Jay Bryant</a> (JB)</p>
 </li>
 <li>
-<p><a href="mailto:kellyc@apache.org">Kelly Campbell</a> </p>
+<p><a href="mailto:kellyc@apache.org">Kelly Campbell</a></p>
 </li>
 <li>
-<p><a href="mailto:gears@apache.org">Steven Coffman</a> </p>
+<p><a href="mailto:gears@apache.org">Steven Coffman</a></p>
 </li>
 <li>
-<p><a href="mailto:bdelacretaz@apache.org">Bertrand Delacretaz</a> </p>
+<p><a href="mailto:bdelacretaz@apache.org">Bertrand Delacretaz</a></p>
 </li>
 <li>
-<p><a href="mailto:tore@apache.org">Tore Engvig</a> </p>
+<p><a href="mailto:tore@apache.org">Tore Engvig</a></p>
 </li>
 <li>
 <p><a href="mailto:lfurini AT cs.unibo.it">Luca Furini</a> (LF)</p>
@@ -430,46 +430,46 @@ $(document).ready(function () {
 <p><a href="mailto:chrisg@apache.org">Christian Geisert</a> (CG)</p>
 </li>
 <li>
-<p><a href="mailto:stanislav@apache.org">Stanislav Gorkhover</a> </p>
+<p><a href="mailto:stanislav@apache.org">Stanislav Gorkhover</a></p>
 </li>
 <li>
-<p><a href="mailto:pherweg@web.de">Peter Herweg</a> </p>
+<p><a href="mailto:pherweg@web.de">Peter Herweg</a></p>
 </li>
 <li>
-<p><a href="mailto:fotis@apache.org">Fotis Jannidis</a> </p>
+<p><a href="mailto:fotis@apache.org">Fotis Jannidis</a></p>
 </li>
 <li>
-<p><a href="mailto:klease@apache.org">Karen Lease</a> </p>
+<p><a href="mailto:klease@apache.org">Karen Lease</a></p>
 </li>
 <li>
-<p><a href="mailto:keiron@apache.org">Keiron Liddle</a> </p>
+<p><a href="mailto:keiron@apache.org">Keiron Liddle</a></p>
 </li>
 <li>
 <p><a href="mailto:manuel@apache.org">Manuel Mall</a> (MM)</p>
 </li>
 <li>
-<p><a href="mailto:gmazza@apache.org">Glen Mazza</a> </p>
+<p><a href="mailto:gmazza@apache.org">Glen Mazza</a></p>
 </li>
 <li>
-<p><a href="mailto:vmote@apache.org">Victor Mote</a> </p>
+<p><a href="mailto:vmote@apache.org">Victor Mote</a></p>
 </li>
 <li>
-<p><a href="mailto:jordan@apache.org">Jordan Naftolin</a> </p>
+<p><a href="mailto:jordan@apache.org">Jordan Naftolin</a></p>
 </li>
 <li>
-<p><a href="mailto:arved@apache.org">Arved Sandstrom</a> </p>
+<p><a href="mailto:arved@apache.org">Arved Sandstrom</a></p>
 </li>
 <li>
-<p><a href="mailto:eschaeffer@apache.org">Eric Schaeffer</a> </p>
+<p><a href="mailto:eschaeffer@apache.org">Eric Schaeffer</a></p>
 </li>
 <li>
 <p><a href="mailto:olegt@apache.org">Oleg Tkachenko</a> (OT)</p>
 </li>
 <li>
-<p><a href="mailto:artw@apache.org">Art Welch</a> </p>
+<p><a href="mailto:artw@apache.org">Art Welch</a></p>
 </li>
 <li>
-<p><a href="mailto:pbwest@apache.org">Peter B. West</a> </p>
+<p><a href="mailto:pbwest@apache.org">Peter B. West</a></p>
 </li>
 </ul></div>
       </div>

Modified: websites/staging/xmlgraphics/trunk/content/fop/trunk/accessibility.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/trunk/accessibility.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/trunk/accessibility.html Wed Dec  5 08:23:47 2012
@@ -529,7 +529,7 @@ The processing of the logical structure 
 <p>It's currently not possible to specify the expanded form of an abbreviation or acronym.</p>
 </li>
 <li>
-<p>SVG graphics (or images in general) are treated as a single figure. Text contained in SVGs is not accessible. It's only possible to work with <code>fox:alt-text</code> .</p>
+<p>SVG graphics (or images in general) are treated as a single figure. Text contained in SVGs is not accessible. It's only possible to work with <code>fox:alt-text</code>.</p>
 </li>
 <li>
 <p>The side regions (region-before, region-after etc.) are currently not specially identified. Screen readers may read their content at page changes.</p>

Modified: websites/staging/xmlgraphics/trunk/content/fop/trunk/anttask.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/trunk/anttask.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/trunk/anttask.html Wed Dec  5 08:23:47 2012
@@ -397,7 +397,7 @@ $(document).ready(function () {
 </tr>
 <tr>
 <td>format</td>
-<td>Possible output formats:<br></br> <code>application/X-fop-awt-preview</code> <br></br> <code>application/X-fop-print</code> <br></br> <code>application/X-fop-areatree</code> <br></br> <code>application/pdf</code> <br></br> <code>application/postscript</code> <br></br> <code>application/mif</code> <br></br> <code>application/rtf</code> , <code>text/richtext</code> , <code>text/rtf</code> <br></br> <code>application/x-pcl</code> , <code>application/vnd.hp-PCL</code> <br></br> <code>application/x-afp</code> , <code>application/vnd.ibm.modcap</code> <br></br> <code>text/plain</code> <br></br> <code>image/svg+xml</code> <br></br> <code>image/gif</code> <br></br> <code>image/png</code> <br></br> <code>image/tiff</code> <br></br></td>
+<td>Possible output formats:<br></br> <code>application/X-fop-awt-preview</code> <br></br> <code>application/X-fop-print</code> <br></br> <code>application/X-fop-areatree</code> <br></br> <code>application/pdf</code> <br></br> <code>application/postscript</code> <br></br> <code>application/mif</code> <br></br> <code>application/rtf</code>, <code>text/richtext</code>, <code>text/rtf</code> <br></br> <code>application/x-pcl</code>, <code>application/vnd.hp-PCL</code> <br></br> <code>application/x-afp</code>, <code>application/vnd.ibm.modcap</code> <br></br> <code>text/plain</code> <br></br> <code>image/svg+xml</code> <br></br> <code>image/gif</code> <br></br> <code>image/png</code> <br></br> <code>image/tiff</code> <br></br></td>
 <td>No, defaults to <code>application/pdf</code></td>
 </tr>
 <tr>
@@ -418,7 +418,7 @@ $(document).ready(function () {
 <tr>
 <td>relativebase</td>
 <td>For fileset usage only. A value of <code>true</code> specifies using the location of each .fo file as the base directory for resolving relative file references located within that .fo file. A value of <code>false</code> specifies using the value of basedir for all files within the fileset, or just the current working directory if basedir is not specified.</td>
-<td>No, default is <code>false</code> .</td>
+<td>No, default is <code>false</code>.</td>
 </tr>
 <tr>
 <td>userconfig</td>
@@ -427,7 +427,7 @@ $(document).ready(function () {
 </tr>
 <tr>
 <td>messagelevel</td>
-<td>Logging level<br></br>Possible values: <code>error</code> , <code>warn</code> , <code>info</code> , <code>verbose</code> , <code>debug</code> . <strong>Currently doesn't work in FOP Trunk!!!</strong></td>
+<td>Logging level<br></br>Possible values: <code>error</code>, <code>warn</code>, <code>info</code>, <code>verbose</code>, <code>debug</code>. <strong>Currently doesn't work in FOP Trunk!!!</strong></td>
 <td>No, defaults to <code>verbose</code></td>
 </tr>
 <tr>

Modified: websites/staging/xmlgraphics/trunk/content/fop/trunk/compiling.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/trunk/compiling.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/trunk/compiling.html Wed Dec  5 08:23:47 2012
@@ -350,7 +350,7 @@ $(document).ready(function () {
 <h3 id="classpath-wzxhzdk8wzxhzdk9">CLASSPATH <a id="env-classpath"></a></h3>
 <p>There is generally no need to setup a classpath. All libraries needed to compile FOP are included in the source distribution and are referenced by the build script. You will only need to adjust the classpath if you build FOP in some other way. See the build script build.xml for details.</p>
 <h3 id="java_home-wzxhzdk10wzxhzdk11">JAVA_HOME <a id="env-java-home"></a></h3>
-<p>The build script uses <a href="http://ant.apache.org/">Apache Ant</a> , a popular Java-based build tool, which usually requires that the environment variable JAVA_HOME point to your local JDK root directory. This is true even if you use JDK 1.4 or above, which normally does not need this setting.</p>
+<p>The build script uses <a href="http://ant.apache.org/">Apache Ant</a>, a popular Java-based build tool, which usually requires that the environment variable JAVA_HOME point to your local JDK root directory. This is true even if you use JDK 1.4 or above, which normally does not need this setting.</p>
 <h3 id="apache-ant-wzxhzdk12wzxhzdk13">Apache Ant <a id="env-ant"></a></h3>
 <p><a href="http://ant.apache.org/">Apache Ant</a> (Version 1.7 or later) must be installed in order to build FOP. Following best practices we don't include Ant with FOP anymore. You can find the <a href="http://ant.apache.org/manual/">instructions to install Ant in the Ant manual</a> on the web.</p>
 <h2 id="run-the-build-script-wzxhzdk14wzxhzdk15">Run the Build Script <a id="build-script"></a></h2>
@@ -361,13 +361,13 @@ ant -projecthelp
 The most useful targets are:</p>
 <ul>
 <li>
-<p><strong>package</strong> : Generates the JAR files (default). This is the normal build that produces a jar file usable for running FOP.</p>
+<p><strong>package</strong>: Generates the JAR files (default). This is the normal build that produces a jar file usable for running FOP.</p>
 </li>
 <li>
-<p><strong>clean</strong> : Cleans the build directory. This is useful for making sure that any build errors are cleaned up before starting a new build. It should not ordinarily be needed, but may be helpful if you are having problems with the build process itself.</p>
+<p><strong>clean</strong>: Cleans the build directory. This is useful for making sure that any build errors are cleaned up before starting a new build. It should not ordinarily be needed, but may be helpful if you are having problems with the build process itself.</p>
 </li>
 <li>
-<p><strong>javadocs</strong> : Creates the FOP API documentation.A minimum JDK version of 1.4.2 is required for generating the javadocs.</p>
+<p><strong>javadocs</strong>: Creates the FOP API documentation.A minimum JDK version of 1.4.2 is required for generating the javadocs.</p>
 </li>
 </ul>
 <p>To run the build:

Modified: websites/staging/xmlgraphics/trunk/content/fop/trunk/complexscripts.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/trunk/complexscripts.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/trunk/complexscripts.html Wed Dec  5 08:23:47 2012
@@ -361,8 +361,8 @@ $(document).ready(function () {
 <h2 id="disabling-complex-scripts-wzxhzdk4wzxhzdk5">Disabling complex scripts <a id="Disabling+complex+scripts"></a></h2>
 <p>Complex script features are enabled by default. If some application of FOP does not require this support, then it can be disabled in three ways:</p>
 <ol>
-<li><strong>Command line:</strong><br/>The command line option <code>-nocs</code> turns off complex script features:<br/><code>fop -nocs -fo mydocument.fo -pdf mydocument.pdf</code><br/> </li>
-<li><strong>Embedding:</strong><br/><code>userAgent.setComplexScriptFeaturesEnabled(false);</code> </li>
+<li><strong>Command line:</strong><br/>The command line option <code>-nocs</code> turns off complex script features:<br/><code>fop -nocs -fo mydocument.fo -pdf mydocument.pdf</code><br/></li>
+<li><strong>Embedding:</strong><br/><code>userAgent.setComplexScriptFeaturesEnabled(false);</code></li>
 <li><strong>Optional setting in fop.xconf file:</strong><br/><code>&lt;fop version="1.0"&gt;</code><br/><code>&lt;complex-scripts disabled="true"/&gt;</code><br/><code>...</code><br/><code>&lt;/fop&gt;</code></li>
 </ol>
 <p>When complex scripts features are enabled, additional information related to bidirectional level resolution, the association between characters and glyphs, and glyph position adjustments are added to the internal, parsed representation of the XSL-FO tree and its corresponding formatted area tree. This additional information will somewhat increase the memory requirements for processing documents that use these features.
@@ -380,7 +380,7 @@ A document author need not make explicit
 <p>The <a href="http://www.w3.org/TR/2006/REC-xsl11-20061205/#writing-mode">writing-mode</a> property.</p>
 </li>
 <li>
-<p>The number to string conversion properties: <a href="http://www.w3.org/TR/2006/REC-xsl11-20061205/#format">format</a> , <a href="http://www.w3.org/TR/2006/REC-xsl11-20061205/#grouping-separator">grouping-separator</a> , <a href="http://www.w3.org/TR/2006/REC-xsl11-20061205/#grouping-size">grouping-size</a> , <a href="http://www.w3.org/TR/2006/REC-xsl11-20061205/#letter-value">letter-value</a> , and <code>fox:number-conversion-features</code> .</p>
+<p>The number to string conversion properties: <a href="http://www.w3.org/TR/2006/REC-xsl11-20061205/#format">format</a>, <a href="http://www.w3.org/TR/2006/REC-xsl11-20061205/#grouping-separator">grouping-separator</a>, <a href="http://www.w3.org/TR/2006/REC-xsl11-20061205/#grouping-size">grouping-size</a>, <a href="http://www.w3.org/TR/2006/REC-xsl11-20061205/#letter-value">letter-value</a>, and <code>fox:number-conversion-features</code>.</p>
 </li>
 <li>
 <p>The <a href="http://www.w3.org/TR/2006/REC-xsl11-20061205/#fo_bidi-override">fo:bidi-override</a> element.</p>
@@ -398,7 +398,7 @@ A document author need not make explicit
 <p>In order to apply font specific complex script features, it is necessary to know the script that applies to the text undergoing layout processing. This script is determined using the following algorithm:</p>
 <ol>
 <li>
-<p>If the FO element that governs the text specifies a <a href="http://www.w3.org/TR/2006/REC-xsl11-20061205/#script">http://www.w3.org/TR/2006/REC-xsl11-20061205/#script</a> property and its value is not the empty string or <code>"auto"</code> , then that script is used.</p>
+<p>If the FO element that governs the text specifies a <a href="http://www.w3.org/TR/2006/REC-xsl11-20061205/#script">http://www.w3.org/TR/2006/REC-xsl11-20061205/#script</a> property and its value is not the empty string or <code>"auto"</code>, then that script is used.</p>
 </li>
 <li>
 <p>Otherwise, the dominant script of the text is determined automatically by finding the script whose constituent characters appear most frequently in the text.</p>
@@ -606,52 +606,52 @@ A document author need not make explicit
 <p><warning>Explicit use of one of the above extended script codes is not portable, and should be limited to use with FOP only.</warning>When performing automatic script determination, FOP selects the OpenType Indic Version 2 script codes by default. If the author requires Version 1 behavior, then an explicit, non-extension script code should be specified in a governing <code>script</code> property.</p>
 <h3 id="language-property-wzxhzdk18wzxhzdk19">Language Property <a id="language_property"></a></h3>
 <p>Certain fonts that support complex script features can make use of language information in order for language specific processing rules to be applied. For example, a font designed for the Arabic script may support typographic variations according to whether the written language is Arabic, Farsi (Persian), Sindhi, Urdu, or another language written with the Arabic script. In order to apply these language specific features, the author may explicitly mark the text with a <a href="http://www.w3.org/TR/2006/REC-xsl11-20061205/#language">http://www.w3.org/TR/2006/REC-xsl11-20061205/#language</a> property.</p>
-<p>When specifying the <code>language</code> property, the value of the property must be either an <a href="http://en.wikipedia.org/wiki/List_of_ISO_639-2_codes">ISO639-2 3-letter code</a> or an <a href="http://en.wikipedia.org/wiki/List_of_ISO_639-1_codes">ISO639-1 2-letter code</a> . Comparison of language codes is performed in a case-insensitive manner, so it does not matter what case is used when specifying these codes in an XSL-FO document.</p>
+<p>When specifying the <code>language</code> property, the value of the property must be either an <a href="http://en.wikipedia.org/wiki/List_of_ISO_639-2_codes">ISO639-2 3-letter code</a> or an <a href="http://en.wikipedia.org/wiki/List_of_ISO_639-1_codes">ISO639-1 2-letter code</a>. Comparison of language codes is performed in a case-insensitive manner, so it does not matter what case is used when specifying these codes in an XSL-FO document.</p>
 <h3 id="writing-mode-property-wzxhzdk20wzxhzdk21">Writing Mode Property <a id="writing_mode_property"></a></h3>
 <p>The <code>writing-mode</code> property is used to determine the axes and direction of the inline progression direction, the block progression direction, the column progression direction (in tables and flows), the shift direction, region placement, the resolution of writing-mode relative property values (such as start, end, before, after), and the default block (paragraph) bidirectionality level.</p>
 <p>The <code>writing-mode</code> property is inherited, so it can appear on any XSL-FO element type; however, it applies (semantically) only to the following element types:</p>
 <ul>
 <li>
-<p><code>fo:page-sequence</code> </p>
+<p><code>fo:page-sequence</code></p>
 </li>
 <li>
-<p><code>fo:simple-page-master</code> </p>
+<p><code>fo:simple-page-master</code></p>
 </li>
 <li>
-<p><code>fo:region-*</code> </p>
+<p><code>fo:region-*</code></p>
 </li>
 <li>
-<p><code>fo:block-container</code> </p>
+<p><code>fo:block-container</code></p>
 </li>
 <li>
-<p><code>fo:inline-container</code> </p>
+<p><code>fo:inline-container</code></p>
 </li>
 <li>
-<p><code>fo:table</code> </p>
+<p><code>fo:table</code></p>
 </li>
 </ul>
 <p>If it is not specified on one of these element types, but is specified on an ancestor element, then the value specified on that ancestor element (the inherited value) is used; otherwise, the initial value <code>lr-tb</code> is used.</p>
 <p>At present, only the following values of the <code>writing-mode</code> property are supported:</p>
 <ul>
 <li>
-<p><code>lr-tb</code> </p>
+<p><code>lr-tb</code></p>
 </li>
 <li>
-<p><code>rl-tb</code> </p>
+<p><code>rl-tb</code></p>
 </li>
 <li>
-<p><code>lr</code> </p>
+<p><code>lr</code></p>
 </li>
 <li>
-<p><code>rl</code> </p>
+<p><code>rl</code></p>
 </li>
 </ul>
 <p>Writing modes that employ a vertical inline progression direction are not yet supported.</p>
 <h3 id="number-conversion-properties-wzxhzdk22wzxhzdk23">Number Conversion Properties <a id="number_conversion_properties"></a></h3>
 <h3 id="bidi-override-element-wzxhzdk24wzxhzdk25">Bidi Override Element <a id="bidi_override_element"></a></h3>
-<p>The <a href="http://www.w3.org/TR/2006/REC-xsl11-20061205/#fo_bidi-override">fo:bidi-override</a> element may be used to override default bidirectional processing behavior, including default embedding levels and default character directionality. In the absence of either this element or use of explicit <a href="#bidi_controls">Bidi Control Characters</a> , the default behavior prescribed by the <a href="http://www.w3.org/TR/2006/REC-xsl11-20061205/#fo_bidi-override">Unicode Bidirectional Algorithm</a> applies.</p>
+<p>The <a href="http://www.w3.org/TR/2006/REC-xsl11-20061205/#fo_bidi-override">fo:bidi-override</a> element may be used to override default bidirectional processing behavior, including default embedding levels and default character directionality. In the absence of either this element or use of explicit <a href="#bidi_controls">Bidi Control Characters</a>, the default behavior prescribed by the <a href="http://www.w3.org/TR/2006/REC-xsl11-20061205/#fo_bidi-override">Unicode Bidirectional Algorithm</a> applies.</p>
 <h3 id="bidi-control-characters-wzxhzdk26wzxhzdk27">Bidi Control Characters <a id="bidi_controls"></a></h3>
-<p>In addition to the use of the <a href="#bidi_override_element">Bidi Override Element</a> , an author may make use of the following explicit Unicode Bidi Control Characters:</p>
+<p>In addition to the use of the <a href="#bidi_override_element">Bidi Override Element</a>, an author may make use of the following explicit Unicode Bidi Control Characters:</p>
 <ul>
 <li>
 <p>U+200E - LEFT-TO-RIGHT MARK (LRM)</p>
@@ -675,7 +675,7 @@ A document author need not make explicit
 <p>U+202E - RIGHT-TO-LEFT OVERRIDE (RLO)</p>
 </li>
 </ul>
-<p>If an embedding or override is not terminated (using U+202C PDF) prior to the end of a <a href="http://www.w3.org/TR/2006/REC-xsl11-20061205/#d0e4879">delimited text range</a> , then it is automatically terminated by FOP.</p>
+<p>If an embedding or override is not terminated (using U+202C PDF) prior to the end of a <a href="http://www.w3.org/TR/2006/REC-xsl11-20061205/#d0e4879">delimited text range</a>, then it is automatically terminated by FOP.</p>
 <h3 id="join-control-characters-wzxhzdk28wzxhzdk29">Join Control Characters <a id="join_controls"></a></h3>
 <p>In order to prevent joining behavior in contexts where joining occurs by default, for example, between U+0628 ARABIC LETTER BEH and U+0646 ARABIC LETTER NOON, an author may used a U+200C ZERO WIDTH NON-JOINER (ZWNJ).</p>
 <p>Conversely, in order to force joining behavior in contexts where joining does not occur by default, for example, between U+0628 ARABIC LETTER BEH and U+0020 SPACE, an author may used a U+200D ZERO WIDTH JOINER (ZWJ).</p>
@@ -909,23 +909,23 @@ A document author need not make explicit
 <p>Only the PDF output format fully supports complex scripts features at the present time.</p>
 </li>
 <li>
-<p>Shaping context does not extend across an element boundary. This limitation prevents the use of <code>fo:character</code> , <code>fo:inline</code> or <code>fo:wrapper</code> in order to colorize individual Arabic letters without affecting shaping behavior across the element boundary.</p>
+<p>Shaping context does not extend across an element boundary. This limitation prevents the use of <code>fo:character</code>, <code>fo:inline</code> or <code>fo:wrapper</code> in order to colorize individual Arabic letters without affecting shaping behavior across the element boundary.</p>
 </li>
 </ul>
 <h2 id="related-links-wzxhzdk40wzxhzdk41">Related Links <a id="links"></a></h2>
 <p>In addition to the XSL-FO specification, a number of external resources provide guidance about authoring documents that employ complex scripts and the features described above:</p>
 <ul>
 <li>
-<p><a href="http://www.unicode.org/">The Unicode Standard</a> </p>
+<p><a href="http://www.unicode.org/">The Unicode Standard</a></p>
 </li>
 <li>
-<p><a href="http://www.w3.org/TR/2006/REC-xsl11-20061205/#fo_bidi-override">Unicode Bidirectional Algorithm</a> </p>
+<p><a href="http://www.w3.org/TR/2006/REC-xsl11-20061205/#fo_bidi-override">Unicode Bidirectional Algorithm</a></p>
 </li>
 <li>
-<p><a href="http://www.microsoft.com/typography/otspec/ttochap1.htm">OpenType Advanced Typographic Extensions</a> </p>
+<p><a href="http://www.microsoft.com/typography/otspec/ttochap1.htm">OpenType Advanced Typographic Extensions</a></p>
 </li>
 <li>
-<p><a href="http://scripts.sil.org/cms/scripts/page.php?site_id=nrsi&amp;item_id=CmplxRndExamples">Examples of Complex Rendering</a> </p>
+<p><a href="http://scripts.sil.org/cms/scripts/page.php?site_id=nrsi&amp;item_id=CmplxRndExamples">Examples of Complex Rendering</a></p>
 </li>
 </ul></div>
       </div>

Modified: websites/staging/xmlgraphics/trunk/content/fop/trunk/configuration.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/trunk/configuration.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/trunk/configuration.html Wed Dec  5 08:23:47 2012
@@ -349,10 +349,10 @@ $(document).ready(function () {
 <p>After creating your configuration file, you must tell FOP how to find it:</p>
 <ul>
 <li>
-<p>If running FOP from the command-line, see the "-c" command-line option in <a href="running.html">Running FOP</a> .</p>
+<p>If running FOP from the command-line, see the "-c" command-line option in <a href="running.html">Running FOP</a>.</p>
 </li>
 <li>
-<p>If running FOP as an embedded application, see <a href="embedding.html#config-external">Embedding, Using a Configuration File</a> .</p>
+<p>If running FOP as an embedded application, see <a href="embedding.html#config-external">Embedding, Using a Configuration File</a>.</p>
 </li>
 </ul>
 <p>See <a href="embedding.html#config-internal">Setting the Configuration Programmatically</a> for instructions on how to do so in an embedded environment.</p>
@@ -529,7 +529,7 @@ $(document).ready(function () {
 </pre></div>
 
 
-<p>The details on the font configuration can be found on the separate <a href="fonts.html">Fonts</a> page. Note especially the section entitled <a href="fonts.html#register">Register Fonts with FOP</a> .</p>
+<p>The details on the font configuration can be found on the separate <a href="fonts.html">Fonts</a> page. Note especially the section entitled <a href="fonts.html#register">Register Fonts with FOP</a>.</p>
 <h3 id="special-settings-for-the-pdf-renderer-wzxhzdk21wzxhzdk22">Special Settings for the PDF Renderer <a id="pdf-renderer"></a></h3>
 <p>The configuration element for the PDF renderer contains two elements. One is for the font configuration (please follow the link above) and one is for the "filter list". The filter list controls how the individual objects in a PDF file are encoded. By default, all objects get "flate" encoded (i.e. simply compressed with the same algorithm that is also used in ZIP files). Most users don't need to change that setting. For debugging purposes, it may be desired not to compress the internal objects at all so the generated PDF commands can be read. In that case, you can simply use the following filter list. The second filter list (type="image") ensures that all images still get compressed but also ASCII-85 encoded so the produced PDF file is still easily readable in a text editor.</p>
 <div class="codehilite"><pre><span class="nt">&lt;renderer</span> <span class="na">mime=</span><span class="s">&quot;application/pdf&quot;</span><span class="nt">&gt;</span>

Modified: websites/staging/xmlgraphics/trunk/content/fop/trunk/embedding.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/trunk/embedding.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/trunk/embedding.html Wed Dec  5 08:23:47 2012
@@ -432,7 +432,7 @@ $(document).ready(function () {
 <p>If you're not totally familiar with JAXP Transformers, please have a look at the <a href="#examples">Embedding examples</a> below. The section contains examples for all sorts of use cases. If you look at all of them in turn you should be able to see the patterns in use and the flexibility this approach offers without adding too much complexity.</p>
 <p>This may look complicated at first, but it's really just the combination of an XSL transformation and a FOP run. It's also easy to comment out the FOP part for debugging purposes, for example when you're tracking down a bug in your stylesheet. You can easily write the XSL-FO output from the XSL transformation to a file to check if that part generates the expected output. An example for that can be found in the <a href="#examples">Embedding examples</a> (See "ExampleXML2FO").</p>
 <h3 id="logging-wzxhzdk34wzxhzdk35">Logging <a id="basic-logging"></a></h3>
-<p>Logging is now a little different than it was in FOP 0.20.5. We've switched from Avalon Logging to <a href="http://commons.apache.org/logging/">Jakarta Commons Logging</a> . While with Avalon Logging the loggers were directly given to FOP, FOP now retrieves its logger(s) through a statically available LogFactory. This is similar to the general pattern that you use when you work with Apache Log4J directly, for example. We call this "static logging" (Commons Logging, Log4J) as opposed to "instance logging" (Avalon Logging). This has a consequence: You can't give FOP a logger for each processing run anymore. The log output of multiple, simultaneously running FOP instances is sent to the same logger.</p>
+<p>Logging is now a little different than it was in FOP 0.20.5. We've switched from Avalon Logging to <a href="http://commons.apache.org/logging/">Jakarta Commons Logging</a>. While with Avalon Logging the loggers were directly given to FOP, FOP now retrieves its logger(s) through a statically available LogFactory. This is similar to the general pattern that you use when you work with Apache Log4J directly, for example. We call this "static logging" (Commons Logging, Log4J) as opposed to "instance logging" (Avalon Logging). This has a consequence: You can't give FOP a logger for each processing run anymore. The log output of multiple, simultaneously running FOP instances is sent to the same logger.</p>
 <p>By default, <a href="http://commons.apache.org/logging/">Jakarta Commons Logging</a> uses JDK logging (available in JDKs 1.4 or higher) as its backend. You can configure Commons Logging to use an alternative backend, for example Log4J. Please consult the <a href="http://commons.apache.org/logging/">documentation for Jakarta Commons Logging</a> on how to configure alternative backends.</p>
 <p>As a result of the above we differentiate between two kinds of "logging":</p>
 <ul>
@@ -443,7 +443,7 @@ $(document).ready(function () {
 <p><a href="events.html">User/Integrator-oriented feedback</a> (NEW!)</p>
 </li>
 </ul>
-<p>The use of "feedback" instead of "logging" is intentional. Most people were using log output as a means to get feedback from events within FOP. Therefore, FOP now includes an <code>event</code> package which can be used to receive feedback from the layout engine and other components within FOP <strong>per rendering run</strong> . This feedback is not just some text but event objects with parameters so these events can be interpreted by code. Of course, there is a facility to turn these events into normal human-readable messages. For details, please read on on the <a href="events.html">Events page</a> . This leaves normal logging to be mostly a thing used by the FOP developers although anyone can surely activate certain logging categories but the feedback from the loggers won't be separated by processing runs. If this is required, the <a href="events.html">Events subsystem</a> is the right approach.</p>
+<p>The use of "feedback" instead of "logging" is intentional. Most people were using log output as a means to get feedback from events within FOP. Therefore, FOP now includes an <code>event</code> package which can be used to receive feedback from the layout engine and other components within FOP <strong>per rendering run</strong>. This feedback is not just some text but event objects with parameters so these events can be interpreted by code. Of course, there is a facility to turn these events into normal human-readable messages. For details, please read on on the <a href="events.html">Events page</a>. This leaves normal logging to be mostly a thing used by the FOP developers although anyone can surely activate certain logging categories but the feedback from the loggers won't be separated by processing runs. If this is required, the <a href="events.html">Events subsystem</a> is the right approach.</p>
 <h3 id="processing-xsl-fo-wzxhzdk36wzxhzdk37">Processing XSL-FO <a id="render"></a></h3>
 <p>Once the Fop instance is set up, call <code>getDefaultHandler()</code> to obtain a SAX DefaultHandler instance to which you can send the SAX events making up the XSL-FO document you'd like to render. FOP processing starts as soon as the DefaultHandler's <code>startDocument()</code> method is called. Processing stops again when the DefaultHandler's <code>endDocument()</code> method is called. Please refer to the basic usage pattern shown above to render a simple XSL-FO document.</p>
 <h3 id="processing-xsl-fo-generated-from-xmlxslt-wzxhzdk38wzxhzdk39">Processing XSL-FO generated from XML+XSLT <a id="render-with-xslt"></a></h3>
@@ -483,7 +483,7 @@ $(document).ready(function () {
 <p><strong>Java Objects:</strong> Please have a look at the <a href="#examples">Embedding examples</a> which contain an example for this.</p>
 </li>
 </ul>
-<p>There are a variety of upstream data manipulations possible. For example, you may have a DOM and an XSL stylesheet; or you may want to set variables in the stylesheet. Interface documentation and some cookbook solutions to these situations are provided in <a href="http://xml.apache.org/xalan-j/usagepatterns.html">Xalan Basic Usage Patterns</a> .</p>
+<p>There are a variety of upstream data manipulations possible. For example, you may have a DOM and an XSL stylesheet; or you may want to set variables in the stylesheet. Interface documentation and some cookbook solutions to these situations are provided in <a href="http://xml.apache.org/xalan-j/usagepatterns.html">Xalan Basic Usage Patterns</a>.</p>
 <h2 id="configuring-apache-fop-programmatically-wzxhzdk42wzxhzdk43">Configuring Apache FOP Programmatically <a id="config-internal"></a></h2>
 <p>Apache FOP provides two levels on which you can customize FOP's behaviour: the FopFactory and the user agent.</p>
 <h3 id="customizing-the-fopfactory-wzxhzdk44wzxhzdk45">Customizing the FopFactory <a id="fop-factory"></a></h3>
@@ -502,7 +502,7 @@ The <strong>hyphenation base URL</strong
 
 
 <p>-
-Disable <strong>strict validation</strong> . When disabled FOP is less strict about the rules established by the XSL-FO specification. Example:</p>
+Disable <strong>strict validation</strong>. When disabled FOP is less strict about the rules established by the XSL-FO specification. Example:</p>
 <div class="codehilite"><pre><span class="sb">`fopFactory.setStrictValidation(false);`</span>
 </pre></div>
 
@@ -520,7 +520,7 @@ Set the <strong>source resolution</stron
 
 
 <p>-
-Manually add an <strong>ElementMapping instance</strong> . If you want to supply a special FOP extension you can give the instance to the FOUserAgent. Normally, the FOP extensions can be automatically detected (see the documentation on extension for more info). Example:</p>
+Manually add an <strong>ElementMapping instance</strong>. If you want to supply a special FOP extension you can give the instance to the FOUserAgent. Normally, the FOP extensions can be automatically detected (see the documentation on extension for more info). Example:</p>
 <div class="codehilite"><pre><span class="sb">`fopFactory.addElementMapping(myElementMapping); // myElementMapping is a org.apache.fop.fo.ElementMapping`</span>
 </pre></div>
 
@@ -592,13 +592,13 @@ Set the <strong>target resolution</stron
 
 
 <p>-
-Set <strong>your own Document Handler</strong> . This feature can be used for several purposes, the most likey usage of which would probably be binding a MIME type when the output is Intermediate Format (see <a href="#documenthandlers">Document Handlers</a> ). This also allows advanced users to create their own implementation of the document handler.</p>
+Set <strong>your own Document Handler</strong>. This feature can be used for several purposes, the most likey usage of which would probably be binding a MIME type when the output is Intermediate Format (see <a href="#documenthandlers">Document Handlers</a> ). This also allows advanced users to create their own implementation of the document handler.</p>
 <div class="codehilite"><pre><span class="sb">`userAgent.setDocumentHandlerOverride(documentHandler) // documentHandler is an instance of org.apache.fop.render.intermediate.IFDocumentHandler`</span>
 </pre></div>
 
 
 <p>-
-Set <strong>your own FOEventHandler instance</strong> . If you want to supply your own FOEventHandler or configure an FOEventHandler subclass in a special way you can give the instance to the FOUserAgent. Normally, the FOEventHandler instance is created by FOP. Example:</p>
+Set <strong>your own FOEventHandler instance</strong>. If you want to supply your own FOEventHandler or configure an FOEventHandler subclass in a special way you can give the instance to the FOUserAgent. Normally, the FOEventHandler instance is created by FOP. Example:</p>
 <div class="codehilite"><pre><span class="sb">`userAgent.setFOEventHandlerOverride(myFOEventHandler); // myFOEventHandler is an org.apache.fop.fo.FOEventHandler`</span>
 </pre></div>
 
@@ -627,9 +627,9 @@ Set a <strong>URIResolver</strong> for c
 </pre></div>
 
 
-<p>The layout of the configuration file is described on the <a href="configuration.html">Configuration page</a> .</p>
+<p>The layout of the configuration file is described on the <a href="configuration.html">Configuration page</a>.</p>
 <h2 id="document-handlers-wzxhzdk50wzxhzdk51">Document Handlers <a id="documenthandlers"></a></h2>
-<p>The document handlers are classes that inherit from <code>org.apache.fop.render.intermediate.IFDocumentHandler</code> . This is an interface for which a MIME type specific implementation can be created. This same handler is used either when XSL-FO is used as the input or when Intermediate Format is used. Since IF is output format agnostic, if custom fonts or other configuration information that affect layout (specific to a particular MIME type) are given then FOP needs that contextual information. The document handler provides that context so that when the IF is rendered, it is more visually consistent with FO rendering. The code below shows an example of how a document handler can be used to provide PDF configuration data to the IFSerializer.</p>
+<p>The document handlers are classes that inherit from <code>org.apache.fop.render.intermediate.IFDocumentHandler</code>. This is an interface for which a MIME type specific implementation can be created. This same handler is used either when XSL-FO is used as the input or when Intermediate Format is used. Since IF is output format agnostic, if custom fonts or other configuration information that affect layout (specific to a particular MIME type) are given then FOP needs that contextual information. The document handler provides that context so that when the IF is rendered, it is more visually consistent with FO rendering. The code below shows an example of how a document handler can be used to provide PDF configuration data to the IFSerializer.</p>
 <div class="codehilite"><pre><span class="n">IFDocumentHandler</span> <span class="n">targetHandler</span> <span class="o">=</span> <span class="n">userAgent</span><span class="o">.</span><span class="na">getRendererFactory</span><span class="o">().</span><span class="na">createDocumentHandler</span><span class="o">(</span><span class="n">userAgent</span><span class="o">,</span> <span class="n">MimeConstants</span><span class="o">.</span><span class="na">MIME_PDF</span><span class="o">);</span>
 
 <span class="n">IFSerializer</span> <span class="n">ifSerializer</span> <span class="o">=</span> <span class="k">new</span> <span class="n">IFSerializer</span><span class="o">();</span>  <span class="c1">//Create the IFSerializer to write the intermediate format</span>
@@ -640,16 +640,16 @@ Set a <strong>URIResolver</strong> for c
 </pre></div>
 
 
-<p>The rest of the code is the same as in <a href="#basics">Basic Usage Patterns</a> .</p>
+<p>The rest of the code is the same as in <a href="#basics">Basic Usage Patterns</a>.</p>
 <h2 id="hints-wzxhzdk52wzxhzdk53">Hints <a id="hints"></a></h2>
 <h3 id="object-reuse-wzxhzdk54wzxhzdk55">Object reuse <a id="object-reuse"></a></h3>
 <p>Fop instances shouldn't (and can't) be reused. Please recreate Fop and FOUserAgent instances for each rendering run using the FopFactory. This is a cheap operation as all reusable information is held in the FopFactory. That's why it's so important to reuse the FopFactory instance.</p>
 <h3 id="awt-issues-wzxhzdk56wzxhzdk57">AWT issues <a id="awt"></a></h3>
 <p>If your XSL-FO files contain SVG then Apache Batik will be used. When Batik is initialised it uses certain classes in <code>java.awt</code> that intialise the Java AWT classes. This means that a daemon thread is created by the JVM and on Unix it will need to connect to a DISPLAY.</p>
-<p>The thread means that the Java application may not automatically quit when finished, you will need to call <code>System.exit()</code> . These issues should be fixed in the JDK 1.4.</p>
-<p>If you run into trouble running FOP on a head-less server, please see the <a href="graphics.html#batik">notes on Batik</a> .</p>
+<p>The thread means that the Java application may not automatically quit when finished, you will need to call <code>System.exit()</code>. These issues should be fixed in the JDK 1.4.</p>
+<p>If you run into trouble running FOP on a head-less server, please see the <a href="graphics.html#batik">notes on Batik</a>.</p>
 <h3 id="getting-information-on-the-rendering-process-wzxhzdk58wzxhzdk59">Getting information on the rendering process <a id="render-info"></a></h3>
-<p>To get the number of pages that were rendered by FOP you can call <code>Fop.getResults()</code> . This returns a <code>FormattingResults</code> object where you can look up the number of pages produced. It also gives you the page-sequences that were produced along with their id attribute and their numbers of pages. This is particularly useful if you render multiple documents (each enclosed by a page-sequence) and have to know the number of pages of each document.</p>
+<p>To get the number of pages that were rendered by FOP you can call <code>Fop.getResults()</code>. This returns a <code>FormattingResults</code> object where you can look up the number of pages produced. It also gives you the page-sequences that were produced along with their id attribute and their numbers of pages. This is particularly useful if you render multiple documents (each enclosed by a page-sequence) and have to know the number of pages of each document.</p>
 <h2 id="improving-performance-wzxhzdk60wzxhzdk61">Improving performance <a id="performance"></a></h2>
 <p>There are several options to consider:</p>
 <ul>
@@ -660,7 +660,7 @@ Set a <strong>URIResolver</strong> for c
 <p>Depending on the target OutputStream (in case of a FileOutputStream, but not for a ByteArrayOutputStream, for example) it may improve performance considerably if you buffer the OutputStream using a BufferedOutputStream: <code>out = new java.io.BufferedOutputStream(out);</code> <br></br>Make sure you properly close the OutputStream when FOP is finished.</p>
 </li>
 <li>
-<p>Cache the stylesheet. If you use the same stylesheet multiple times you can set up a JAXP <code>Templates</code> object and reuse it each time you do the XSL transformation. (More information can be found <a href="http://www.javaworld.com/javaworld/jw-05-2003/jw-0502-xsl.html">here</a> .)</p>
+<p>Cache the stylesheet. If you use the same stylesheet multiple times you can set up a JAXP <code>Templates</code> object and reuse it each time you do the XSL transformation. (More information can be found <a href="http://www.javaworld.com/javaworld/jw-05-2003/jw-0502-xsl.html">here</a>.)</p>
 </li>
 <li>
 <p>Use an XSLT compiler like <a href="http://xml.apache.org/xalan-j/xsltc_usage.html">XSLTC</a> that comes with Xalan-J.</p>
@@ -669,7 +669,7 @@ Set a <strong>URIResolver</strong> for c
 <p>Fine-tune your stylesheet to make the XSLT process more efficient and to create XSL-FO that can be processed by FOP more efficiently. Less is more: Try to make use of property inheritance where possible.</p>
 </li>
 <li>
-<p>You may also wish to consider trying to reduce <a href="http://xmlgraphics.apache.org/fop/trunk/running.html#memory">memory usage</a> .</p>
+<p>You may also wish to consider trying to reduce <a href="http://xmlgraphics.apache.org/fop/trunk/running.html#memory">memory usage</a>.</p>
 </li>
 </ul>
 <h2 id="multithreading-fop-wzxhzdk62wzxhzdk63">Multithreading FOP <a id="multithreading"></a></h2>

Modified: websites/staging/xmlgraphics/trunk/content/fop/trunk/events.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/trunk/events.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/trunk/events.html Wed Dec  5 08:23:47 2012
@@ -347,7 +347,7 @@ $(document).ready(function () {
 <p>With FOP's event subsystem, we'd like to close this gap again and even go further. The first point is to realize that we have two kinds of "logging". Firstly, we have the logging infrastructure for the (FOP) developer who needs to be able to enable finer log messages for certain parts of FOP to track down a certain problem. Secondly, we have the user who would like to be informed about missing images, overflowing lines or substituted fonts. These messages (or events) are targeted at less technical people and may ideally be localized (translated). Furthermore, tool and solution builders would like to integrate FOP into their own solutions. For example, an FO editor should be able to point the user to the right place where a particular problem occurred while developing a document template. Finally, some integrators would like to abort processing if a resource (an image or a font) has not been found, while others would simply continue. The event system allows to react on the
 se events.</p>
 <p>On this page, we won't discuss logging as such. We will show how the event subsystem can be used for various tasks. We'll first look at the event subsystem from the consumer side. Finally, the production of events inside FOP will be discussed (this is mostly interesting for FOP developers only).</p>
 <h2 id="the-consumer-side-wzxhzdk12wzxhzdk13">The consumer side <a id="consumer"></a></h2>
-<p>The event subsystem is located in the <code>org.apache.fop.events</code> package and its base is the <code>Event</code> class. An instance is created for each event and is sent to a set of <code>EventListener</code> instances by the <code>EventBroadcaster</code> . An <code>Event</code> contains:</p>
+<p>The event subsystem is located in the <code>org.apache.fop.events</code> package and its base is the <code>Event</code> class. An instance is created for each event and is sent to a set of <code>EventListener</code> instances by the <code>EventBroadcaster</code>. An <code>Event</code> contains:</p>
 <ul>
 <li>
 <p>an event ID,</p>
@@ -363,7 +363,7 @@ $(document).ready(function () {
 </li>
 </ul>
 <p>The <code>EventFormatter</code> class can be used to translate the events into human-readable, localized messages.</p>
-<p>A full example of what is shown here can be found in the <code>examples/embedding/java/embedding/events</code> directory in the FOP distribution. The example can also be accessed <a href="http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/examples/embedding/java/embedding/events/">via the web</a> .</p>
+<p>A full example of what is shown here can be found in the <code>examples/embedding/java/embedding/events</code> directory in the FOP distribution. The example can also be accessed <a href="http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/examples/embedding/java/embedding/events/">via the web</a>.</p>
 <h3 id="writing-an-eventlistener-wzxhzdk14wzxhzdk15">Writing an EventListener <a id="write-listener"></a></h3>
 <p>The following code sample shows a very simple EventListener. It basically just sends all events to System.out (stdout) or System.err (stderr) depending on the event severity.</p>
 <div class="codehilite"><pre><span class="kn">import</span> <span class="nn">org.apache.fop.events.Event</span><span class="o">;</span>
@@ -394,7 +394,7 @@ $(document).ready(function () {
 </pre></div>
 
 
-<p>You can see that for every event the method <code>processEvent</code> of the <code>EventListener</code> will be called. Inside this method you can do whatever processing you would like including throwing a <code>RuntimeException</code> , if you want to abort the current processing run.</p>
+<p>You can see that for every event the method <code>processEvent</code> of the <code>EventListener</code> will be called. Inside this method you can do whatever processing you would like including throwing a <code>RuntimeException</code>, if you want to abort the current processing run.</p>
 <p>The code above also shows how you can turn an event into a human-readable, localized message that can be presented to a user. The <code>EventFormatter</code> class does this for you. It provides additional methods if you'd like to explicitly specify the locale.</p>
 <p>It is possible to gather all events for a whole processing run so they can be evaluated afterwards. However, care should be taken about memory consumption since the events provide references to objects inside FOP which may themselves have references to other objects. So holding on to these objects may mean that whole object trees cannot be released!</p>
 <h3 id="adding-an-eventlistener-wzxhzdk16wzxhzdk17">Adding an EventListener <a id="add-listener"></a></h3>
@@ -462,8 +462,8 @@ The event package has been designed in o
 
 <p>The <code>Event.paramsBuilder()</code> is a <a href="http://en.wikipedia.org/wiki/Fluent_interface">fluent interface</a> to help with the build-up of the parameters. You could just as well instantiate a <code>Map</code> ( <code>Map&lt;String, Object&gt;</code> ) and fill it with values.</p>
 <h3 id="the-eventproducer-interface-wzxhzdk24wzxhzdk25">The EventProducer interface <a id="event-producer"></a></h3>
-<p>To simplify event production, the event subsystem provides the <code>EventProducer</code> interface. You can create interfaces which extend <code>EventProducer</code> . These interfaces will contain one method per event to be generated. By contract, each event method must have as its first parameter a parameter named "source" (Type Object) which indicates the object that generated the event. After that come an arbitrary number of parameters of any type as needed by the event.</p>
-<p>The event producer interface does not need to have any implementation. The implementation is produced at runtime by a dynamic proxy created by <code>DefaultEventBroadcaster</code> . The dynamic proxy creates <code>Event</code> instances for each method call against the event producer interface. Each parameter (except "source") is added to the event's parameter map.</p>
+<p>To simplify event production, the event subsystem provides the <code>EventProducer</code> interface. You can create interfaces which extend <code>EventProducer</code>. These interfaces will contain one method per event to be generated. By contract, each event method must have as its first parameter a parameter named "source" (Type Object) which indicates the object that generated the event. After that come an arbitrary number of parameters of any type as needed by the event.</p>
+<p>The event producer interface does not need to have any implementation. The implementation is produced at runtime by a dynamic proxy created by <code>DefaultEventBroadcaster</code>. The dynamic proxy creates <code>Event</code> instances for each method call against the event producer interface. Each parameter (except "source") is added to the event's parameter map.</p>
 <p>To simplify the code needed to get an instance of the event producer interface it is suggested to create a public inner provider class inside the interface.</p>
 <p>Here's an example of such an event producer interface:</p>
 <div class="codehilite"><pre><span class="kd">public</span> <span class="kd">interface</span> <span class="nc">MyEventProducer</span> <span class="kd">extends</span> <span class="n">EventProducer</span> <span class="o">{</span>
@@ -500,7 +500,7 @@ The event package has been designed in o
 <p>The event model XML files are generated during build by the Ant task mentioned above when running the "resourcegen" task. So just run <code>"ant resourcegen"</code> if you receive a <code>MissingResourceException</code> at runtime indicating that <code>"event-model.xml"</code> is missing.</p>
 <p>Primarily, the QDox-based collector task records the parameters' names and types. Furthermore, it extracts additional attributes embedded as Javadoc comments from the methods. At the moment, the only such attribute is "@event.severity" which indicates the default event severity (which can be changed by event listeners). The example event producer above shows the Javadocs for an event method.</p>
 <p>There's one more information that is extracted from the event producer information for the event model: an optional primary exception. The first exception in the "throws" declaration of an event method is noted. It is used to throw an exception from the invocation handler if the event has an event severity of "FATAL" when all listeners have been called (listeners can update the event severity). Please note that an implementation of <code>org.apache.fop.events.EventExceptionManager$ExceptionFactory</code> has to be registered for the <code>EventExceptionManager</code> to be able to construct the exception from an event.</p>
-<p>For a given application, there can be multiple event models active at the same time. In FOP, each renderer is considered to be a plug-in and provides its own specific event model. The individual event models are provided through an <code>EventModelFactory</code> . This interface is implemented for each event model and registered through the service provider mechanism (see the <a href="#plug-ins">plug-ins section</a> for details).</p>
+<p>For a given application, there can be multiple event models active at the same time. In FOP, each renderer is considered to be a plug-in and provides its own specific event model. The individual event models are provided through an <code>EventModelFactory</code>. This interface is implemented for each event model and registered through the service provider mechanism (see the <a href="#plug-ins">plug-ins section</a> for details).</p>
 <h3 id="event-severity-wzxhzdk28wzxhzdk29">Event severity <a id="event-severity"></a></h3>
 <p>Four different levels of severity for events has been defined:</p>
 <ol>
@@ -528,7 +528,7 @@ The event package has been designed in o
 <p><strong><code>org.apache.fop.events.EventExceptionManager$ExceptionFactory</code>:</strong> Creates exceptions for events, i.e. turns an event into a specific exception.</p>
 </li>
 </ul>
-<p>The names in bold above are used as filenames for the service provider files that are placed in the <code>META-INF/services</code> directory. That way, they are automatically detected. This is a mechanism defined by the <a href="http://java.sun.com/j2se/1.4.2/docs/guide/jar/jar.html#Service%20Provider">JAR file specification</a> .</p>
+<p>The names in bold above are used as filenames for the service provider files that are placed in the <code>META-INF/services</code> directory. That way, they are automatically detected. This is a mechanism defined by the <a href="http://java.sun.com/j2se/1.4.2/docs/guide/jar/jar.html#Service%20Provider">JAR file specification</a>.</p>
 <h3 id="localization-l10n-wzxhzdk32wzxhzdk33">Localization (L10n) <a id="l10n"></a></h3>
 <p>One goal of the event subsystem was to have localized (translated) event messages. The <code>EventFormatter</code> class can be used to convert an event to a human-readable message. Each <code>EventProducer</code> can provide its own XML-based translation file. If there is none, a central translation file is used, called "EventFormatter.xml" (found in the same directory as the <code>EventFormatter</code> class).</p>
 <p>The XML format used by the <code>EventFormatter</code> is the same as <a href="http://cocoon.apache.org/">Apache Cocoon's</a> catalog format. Here's an example:</p>

Modified: websites/staging/xmlgraphics/trunk/content/fop/trunk/extensions.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/trunk/extensions.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/trunk/extensions.html Wed Dec  5 08:23:47 2012
@@ -356,7 +356,7 @@ All extensions require the correct use o
 
 
 <h3 id="pdf-bookmarks-wzxhzdk11wzxhzdk12">PDF Bookmarks <a id="bookmarks"></a></h3>
-<p>In old versions of Apache FOP there was a <code>fox:outline</code> element which was used to create outlines in PDF files. The redesigned code makes use of the <a href="http://www.w3.org/TR/xsl11/#fo_bookmark-tree">bookmark feature defined in the W3C XSL 1.1 standard</a> .</p>
+<p>In old versions of Apache FOP there was a <code>fox:outline</code> element which was used to create outlines in PDF files. The redesigned code makes use of the <a href="http://www.w3.org/TR/xsl11/#fo_bookmark-tree">bookmark feature defined in the W3C XSL 1.1 standard</a>.</p>
 <h3 id="anchors-or-named-destinations-wzxhzdk13wzxhzdk14">Anchors or Named Destinations <a id="named-destinations"></a></h3>
 <p>Use the fox:destination element to define "named destinations" inside a PDF document. These are useful as fragment identifiers, e.g. "http://server/document.pdf#anchor-name". fox:destination elements can be placed almost anywhere in the fo document, including a child of root, a block-level element, or an inline-level element. For the destination to actually work, it must correspond to an "id" attribute on some fo element within the document. In other words, the "id" attribute actually creates the "view" within the PDF document. The fox:destination simply gives that view an independent name.</p>
 <div class="codehilite"><pre><span class="nt">&lt;fox:destination</span> <span class="na">internal-destination=</span><span class="s">&quot;table-of-contents&quot;</span><span class="nt">/&gt;</span>
@@ -375,14 +375,14 @@ All extensions require the correct use o
 <h3 id="foxexternal-document-wzxhzdk21wzxhzdk22">fox:external-document <a id="external-document"></a></h3>
 <p>This feature is incomplete. Support for multi-page documents will be added shortly. At the moment, only single-page images will work. And this will not work with RTF output.</p>
 <p>This is a proprietary extension element which allows to add whole images as pages to an FO document. For example, if you have a scanned document or a fax as multi-page TIFF file, you can append or insert this document using the <code>fox:external-document</code> element. Each page of the external document will create one full page in the target format.</p>
-<p>The <code>fox:external-document</code> element is structurally a peer to <code>fo:page-sequence</code> , so wherever you can put an <code>fo:page-sequence</code> you could also place a <code>fox:external-document</code> . Therefore, the specified contents for <code>fo:root</code> change to:</p>
+<p>The <code>fox:external-document</code> element is structurally a peer to <code>fo:page-sequence</code>, so wherever you can put an <code>fo:page-sequence</code> you could also place a <code>fox:external-document</code>. Therefore, the specified contents for <code>fo:root</code> change to:</p>
 <div class="codehilite"><pre><span class="p">(</span><span class="n">layout</span><span class="o">-</span><span class="n">master</span><span class="o">-</span><span class="n">set</span><span class="p">,</span> <span class="n">declarations</span><span class="p">?,</span> <span class="n">bookmark</span><span class="o">-</span><span class="n">tree</span><span class="p">?,</span> <span class="p">(</span><span class="n">page</span><span class="o">-</span><span class="n">sequence</span><span class="o">|</span><span class="n">page</span><span class="o">-</span><span class="n">sequence</span><span class="o">-</span><span class="n">wrapper</span><span class="o">|</span><span class="n">fox:external</span><span class="o">-</span><span class="n">document</span><span class="o">|</span><span class="n">fox:destination</span><span class="p">)</span><span class="o">+</span><span class="p">)</span>
 </pre></div>
 
 
 <h4 id="specificationwzxhzdk23wzxhzdk24">Specification<a id="Specification"></a></h4>
 <p>The <code>fox:external-document</code> extension formatting object is used to specify how to create a (sub-)sequence of pages within a document. The content of these pages comes from the individual subimages/pages of an image or paged document (for example: multi-page TIFF in the form of faxes or scanned documents, or PDF files). The formatting object creates the necessary areas to display one image per page.</p>
-<p>In terms of page numbers, the behaviour is the same as for <code>fo:page-sequence</code> . The placement of the image inside the page is similar to that of <code>fo:external-graphic</code> or <code>fo:instream-foreign-object</code> , i.e. the viewport (and therefore the page size) is defined by either the intrinsic size of the image or by the size properties that apply to this formatting object.</p>
+<p>In terms of page numbers, the behaviour is the same as for <code>fo:page-sequence</code>. The placement of the image inside the page is similar to that of <code>fo:external-graphic</code> or <code>fo:instream-foreign-object</code>, i.e. the viewport (and therefore the page size) is defined by either the intrinsic size of the image or by the size properties that apply to this formatting object.</p>
 <p>Content: EMPTY</p>
 <p>The following properties apply to this formatting object:</p>
 <ul>
@@ -444,7 +444,7 @@ All extensions require the correct use o
 <p>Datatype "page-set": Value: auto | <integer-range>, Default: "auto" which means all pages/subimages of the document. <integer-range> allows values such as "7" or "1-3"
  <code>fox:external-document</code> is not suitable for concatenating FO documents. For this, XInclude is recommended.</p>
 <h3 id="free-form-transformation-for-foblock-container-wzxhzdk27wzxhzdk28">Free-form Transformation for fo:block-container <a id="transform"></a></h3>
-<p>For <code>fo:block-container</code> elements whose <code>absolute-position</code> set to "absolute" or "fixed" you can use the extension attribute <code>fox:transform</code> to apply a free-form transformation to the whole block-container. The content of the <code>fox:transform</code> attribute is the same as for <a href="http://www.w3.org/TR/SVG/coords.html#TransformAttribute">SVG's transform attribute</a> . The transformation specified here is performed in addition to other implicit transformations of the block-container (resulting from top, left and other properties) and after them.</p>
+<p>For <code>fo:block-container</code> elements whose <code>absolute-position</code> set to "absolute" or "fixed" you can use the extension attribute <code>fox:transform</code> to apply a free-form transformation to the whole block-container. The content of the <code>fox:transform</code> attribute is the same as for <a href="http://www.w3.org/TR/SVG/coords.html#TransformAttribute">SVG's transform attribute</a>. The transformation specified here is performed in addition to other implicit transformations of the block-container (resulting from top, left and other properties) and after them.</p>
 <p>Examples: <code>fox:transform="rotate(45)"</code> would rotate the block-container by 45 degrees clock-wise around its upper-left corner. <code>fox:transform="translate(10000,0)"</code> would move the block-container to the right by 10 points (=10000 millipoints, FOP uses millipoints internally!).
 This extension attribute doesn't work for all output formats! It's currently only supported for PDF, PS and Java2D-based renderers.</p>
 <h3 id="color-functions-wzxhzdk29wzxhzdk30">Color functions <a id="color-functions"></a></h3>



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


Mime
View raw message