You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@xmlgraphics.apache.org by bu...@apache.org on 2012/12/05 09:23:58 UTC
svn commit: r840806 [1/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/
Author: buildbot
Date: Wed Dec 5 08:23:47 2012
New Revision: 840806
Log:
Staging update by buildbot for xmlgraphics
Modified:
websites/staging/xmlgraphics/trunk/content/ (props changed)
websites/staging/xmlgraphics/trunk/content/batik/contributors.html
websites/staging/xmlgraphics/trunk/content/batik/demo.html
websites/staging/xmlgraphics/trunk/content/batik/dev/svg12.html
websites/staging/xmlgraphics/trunk/content/batik/dev/test.html
websites/staging/xmlgraphics/trunk/content/batik/download.html
websites/staging/xmlgraphics/trunk/content/batik/faq.html
websites/staging/xmlgraphics/trunk/content/batik/index.html
websites/staging/xmlgraphics/trunk/content/batik/install.html
websites/staging/xmlgraphics/trunk/content/batik/mailing-lists.html
websites/staging/xmlgraphics/trunk/content/batik/status.html
websites/staging/xmlgraphics/trunk/content/batik/tools/browser.html
websites/staging/xmlgraphics/trunk/content/batik/tools/font-converter.html
websites/staging/xmlgraphics/trunk/content/batik/tools/pretty-printer.html
websites/staging/xmlgraphics/trunk/content/batik/tools/rasterizer.html
websites/staging/xmlgraphics/trunk/content/batik/uses.html
websites/staging/xmlgraphics/trunk/content/batik/using/architecture.html
websites/staging/xmlgraphics/trunk/content/batik/using/dom-api.html
websites/staging/xmlgraphics/trunk/content/batik/using/extending.html
websites/staging/xmlgraphics/trunk/content/batik/using/index.html
websites/staging/xmlgraphics/trunk/content/batik/using/parsers.html
websites/staging/xmlgraphics/trunk/content/batik/using/scripting/ecmascript.html
websites/staging/xmlgraphics/trunk/content/batik/using/scripting/java.html
websites/staging/xmlgraphics/trunk/content/batik/using/scripting/security.html
websites/staging/xmlgraphics/trunk/content/batik/using/svg-generator.html
websites/staging/xmlgraphics/trunk/content/batik/using/swing.html
websites/staging/xmlgraphics/trunk/content/batik/using/transcoder.html
websites/staging/xmlgraphics/trunk/content/commons/bugs.html
websites/staging/xmlgraphics/trunk/content/commons/changes.html
websites/staging/xmlgraphics/trunk/content/commons/download.html
websites/staging/xmlgraphics/trunk/content/commons/image-loader.html
websites/staging/xmlgraphics/trunk/content/commons/index.html
websites/staging/xmlgraphics/trunk/content/commons/postscript.html
websites/staging/xmlgraphics/trunk/content/fop/0.95/anttask.html
websites/staging/xmlgraphics/trunk/content/fop/0.95/changes_0.95.html
websites/staging/xmlgraphics/trunk/content/fop/0.95/changes_0.95beta.html
websites/staging/xmlgraphics/trunk/content/fop/0.95/compiling.html
websites/staging/xmlgraphics/trunk/content/fop/0.95/configuration.html
websites/staging/xmlgraphics/trunk/content/fop/0.95/embedding.html
websites/staging/xmlgraphics/trunk/content/fop/0.95/extensions.html
websites/staging/xmlgraphics/trunk/content/fop/0.95/fonts.html
websites/staging/xmlgraphics/trunk/content/fop/0.95/graphics.html
websites/staging/xmlgraphics/trunk/content/fop/0.95/hyphenation.html
websites/staging/xmlgraphics/trunk/content/fop/0.95/index.html
websites/staging/xmlgraphics/trunk/content/fop/0.95/intermediate.html
websites/staging/xmlgraphics/trunk/content/fop/0.95/metadata.html
websites/staging/xmlgraphics/trunk/content/fop/0.95/output.html
websites/staging/xmlgraphics/trunk/content/fop/0.95/pdfa.html
websites/staging/xmlgraphics/trunk/content/fop/0.95/pdfencryption.html
websites/staging/xmlgraphics/trunk/content/fop/0.95/pdfx.html
websites/staging/xmlgraphics/trunk/content/fop/0.95/releaseNotes_0.95.html
websites/staging/xmlgraphics/trunk/content/fop/0.95/running.html
websites/staging/xmlgraphics/trunk/content/fop/0.95/servlets.html
websites/staging/xmlgraphics/trunk/content/fop/0.95/upgrading.html
websites/staging/xmlgraphics/trunk/content/fop/1.0/accessibility.html
websites/staging/xmlgraphics/trunk/content/fop/1.0/anttask.html
websites/staging/xmlgraphics/trunk/content/fop/1.0/changes_1.0.html
websites/staging/xmlgraphics/trunk/content/fop/1.0/compiling.html
websites/staging/xmlgraphics/trunk/content/fop/1.0/configuration.html
websites/staging/xmlgraphics/trunk/content/fop/1.0/embedding.html
websites/staging/xmlgraphics/trunk/content/fop/1.0/events.html
websites/staging/xmlgraphics/trunk/content/fop/1.0/extensions.html
websites/staging/xmlgraphics/trunk/content/fop/1.0/fonts.html
websites/staging/xmlgraphics/trunk/content/fop/1.0/graphics.html
websites/staging/xmlgraphics/trunk/content/fop/1.0/hyphenation.html
websites/staging/xmlgraphics/trunk/content/fop/1.0/index.html
websites/staging/xmlgraphics/trunk/content/fop/1.0/intermediate.html
websites/staging/xmlgraphics/trunk/content/fop/1.0/metadata.html
websites/staging/xmlgraphics/trunk/content/fop/1.0/output.html
websites/staging/xmlgraphics/trunk/content/fop/1.0/pdfa.html
websites/staging/xmlgraphics/trunk/content/fop/1.0/pdfencryption.html
websites/staging/xmlgraphics/trunk/content/fop/1.0/pdfx.html
websites/staging/xmlgraphics/trunk/content/fop/1.0/releaseNotes_1.0.html
websites/staging/xmlgraphics/trunk/content/fop/1.0/running.html
websites/staging/xmlgraphics/trunk/content/fop/1.0/servlets.html
websites/staging/xmlgraphics/trunk/content/fop/1.0/upgrading.html
websites/staging/xmlgraphics/trunk/content/fop/1.1/accessibility.html
websites/staging/xmlgraphics/trunk/content/fop/1.1/anttask.html
websites/staging/xmlgraphics/trunk/content/fop/1.1/changes_1.1.html
websites/staging/xmlgraphics/trunk/content/fop/1.1/compiling.html
websites/staging/xmlgraphics/trunk/content/fop/1.1/complexscripts.html
websites/staging/xmlgraphics/trunk/content/fop/1.1/configuration.html
websites/staging/xmlgraphics/trunk/content/fop/1.1/embedding.html
websites/staging/xmlgraphics/trunk/content/fop/1.1/events.html
websites/staging/xmlgraphics/trunk/content/fop/1.1/extensions.html
websites/staging/xmlgraphics/trunk/content/fop/1.1/fonts.html
websites/staging/xmlgraphics/trunk/content/fop/1.1/graphics.html
websites/staging/xmlgraphics/trunk/content/fop/1.1/hyphenation.html
websites/staging/xmlgraphics/trunk/content/fop/1.1/index.html
websites/staging/xmlgraphics/trunk/content/fop/1.1/intermediate.html
websites/staging/xmlgraphics/trunk/content/fop/1.1/knownissues_overview.html
websites/staging/xmlgraphics/trunk/content/fop/1.1/metadata.html
websites/staging/xmlgraphics/trunk/content/fop/1.1/output.html
websites/staging/xmlgraphics/trunk/content/fop/1.1/pdfa.html
websites/staging/xmlgraphics/trunk/content/fop/1.1/pdfencryption.html
websites/staging/xmlgraphics/trunk/content/fop/1.1/pdfx.html
websites/staging/xmlgraphics/trunk/content/fop/1.1/releaseNotes_1.1.html
websites/staging/xmlgraphics/trunk/content/fop/1.1/running.html
websites/staging/xmlgraphics/trunk/content/fop/1.1/servlets.html
websites/staging/xmlgraphics/trunk/content/fop/1.1/upgrading.html
websites/staging/xmlgraphics/trunk/content/fop/bugs.html
websites/staging/xmlgraphics/trunk/content/fop/changes.html
websites/staging/xmlgraphics/trunk/content/fop/dev/conventions.html
websites/staging/xmlgraphics/trunk/content/fop/dev/design/breakpos.html
websites/staging/xmlgraphics/trunk/content/fop/dev/design/embedding.html
websites/staging/xmlgraphics/trunk/content/fop/dev/design/fotree.html
websites/staging/xmlgraphics/trunk/content/fop/dev/design/index.html
websites/staging/xmlgraphics/trunk/content/fop/dev/design/parsing.html
websites/staging/xmlgraphics/trunk/content/fop/dev/design/pdf-library.html
websites/staging/xmlgraphics/trunk/content/fop/dev/design/properties.html
websites/staging/xmlgraphics/trunk/content/fop/dev/doc.html
websites/staging/xmlgraphics/trunk/content/fop/dev/implement.html
websites/staging/xmlgraphics/trunk/content/fop/dev/index.html
websites/staging/xmlgraphics/trunk/content/fop/dev/release.html
websites/staging/xmlgraphics/trunk/content/fop/dev/rtflib.html
websites/staging/xmlgraphics/trunk/content/fop/dev/svg.html
websites/staging/xmlgraphics/trunk/content/fop/dev/testing.html
websites/staging/xmlgraphics/trunk/content/fop/dev/tools.html
websites/staging/xmlgraphics/trunk/content/fop/download.html
websites/staging/xmlgraphics/trunk/content/fop/examples.html
websites/staging/xmlgraphics/trunk/content/fop/faq.html
websites/staging/xmlgraphics/trunk/content/fop/fo.html
websites/staging/xmlgraphics/trunk/content/fop/gethelp.html
websites/staging/xmlgraphics/trunk/content/fop/index.html
websites/staging/xmlgraphics/trunk/content/fop/knownissues.html
websites/staging/xmlgraphics/trunk/content/fop/license.html
websites/staging/xmlgraphics/trunk/content/fop/maillist.html
websites/staging/xmlgraphics/trunk/content/fop/news.html
websites/staging/xmlgraphics/trunk/content/fop/quickstartguide.html
websites/staging/xmlgraphics/trunk/content/fop/resources.html
websites/staging/xmlgraphics/trunk/content/fop/team.html
websites/staging/xmlgraphics/trunk/content/fop/trunk/accessibility.html
websites/staging/xmlgraphics/trunk/content/fop/trunk/anttask.html
websites/staging/xmlgraphics/trunk/content/fop/trunk/compiling.html
websites/staging/xmlgraphics/trunk/content/fop/trunk/complexscripts.html
websites/staging/xmlgraphics/trunk/content/fop/trunk/configuration.html
websites/staging/xmlgraphics/trunk/content/fop/trunk/embedding.html
websites/staging/xmlgraphics/trunk/content/fop/trunk/events.html
websites/staging/xmlgraphics/trunk/content/fop/trunk/extensions.html
websites/staging/xmlgraphics/trunk/content/fop/trunk/fonts.html
websites/staging/xmlgraphics/trunk/content/fop/trunk/graphics.html
websites/staging/xmlgraphics/trunk/content/fop/trunk/hyphenation.html
websites/staging/xmlgraphics/trunk/content/fop/trunk/index.html
websites/staging/xmlgraphics/trunk/content/fop/trunk/intermediate.html
websites/staging/xmlgraphics/trunk/content/fop/trunk/metadata.html
websites/staging/xmlgraphics/trunk/content/fop/trunk/output.html
websites/staging/xmlgraphics/trunk/content/fop/trunk/pdfa.html
websites/staging/xmlgraphics/trunk/content/fop/trunk/pdfencryption.html
websites/staging/xmlgraphics/trunk/content/fop/trunk/pdfx.html
websites/staging/xmlgraphics/trunk/content/fop/trunk/running.html
websites/staging/xmlgraphics/trunk/content/fop/trunk/servlets.html
websites/staging/xmlgraphics/trunk/content/fop/trunk/upgrading.html
websites/staging/xmlgraphics/trunk/content/legal.html
websites/staging/xmlgraphics/trunk/content/mail.html
websites/staging/xmlgraphics/trunk/content/repo.html
websites/staging/xmlgraphics/trunk/content/team.html
Propchange: websites/staging/xmlgraphics/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Dec 5 08:23:47 2012
@@ -1 +1 @@
-1417009
+1417307
Modified: websites/staging/xmlgraphics/trunk/content/batik/contributors.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/batik/contributors.html (original)
+++ websites/staging/xmlgraphics/trunk/content/batik/contributors.html Wed Dec 5 08:23:47 2012
@@ -171,71 +171,60 @@ $(document).ready(function () {
<h2 id="committers-wzxhzdk0wzxhzdk1">Committers <a id="committers"></a></h2>
<p>This section lists all developers with commit access to the Batik subversion repository.</p>
<p>The following people are active Batik developers:</p>
-<dl>
-<dt>Thomas DeWeese (TD)</dt>
-<dd><a href="mailto:Thomas.DeWeese@Kodak.com">Thomas.DeWeese@Kodak.com</a> </dd>
-</dl>
+<p>Thomas DeWeese (TD)
+:
+ <a href="mailto:Thomas.DeWeese@Kodak.com">Thomas.DeWeese@Kodak.com</a></p>
<p>Thomas DeWeese is a Senior Software Engineer at Eastman Kodak Company, in Rochester New York where he has worked for the Image Science Divisionâs image application development group since 1994. Thomas has made contributions to the imaging portions of the Java2D API, and was a major contributor to the Java Advanced Image API (version 1.0). Since then he has participated in the Jini Printing Working group and has recently become a member of Kodakâs SVG Working Group team.</p>
-<dl>
-<dt>Cameron McCormack (CM)</dt>
-<dd><a href="mailto:cam@mcc.id.au">cam@mcc.id.au</a> </dd>
-</dl>
+<p>Cameron McCormack (CM)
+:
+ <a href="mailto:cam@mcc.id.au">cam@mcc.id.au</a></p>
<p>Cameron McCormack is a postgraduate student at Monash University in Melbourne, Australia, where he is undertaking his PhD. His thesis relates to adaptive layout of diagrams, and he has worked on an extension to SVG to allow expressions as attribute values. He also is an invited expert on the SVG Working Group. Cameron has been a committer since 2004, and has contributed code mostly related to SMIL animation and upcoming SVG 1.2 support.</p>
-<dl>
-<dt>Dieter von Holten (DH)</dt>
-<dd>Dieter is a freelance programmer living in Hamburg, Germany. He spends his time on projects in refineries and tankfarms, chasing bits from ERP to PLC and back. Although not specifically an expert with graphics, he tries to help out âmaintaining and enhancing this interesting, non-trivial piece of codeâ.</dd>
-<dt>Helder Magalhães (HM)</dt>
-<dd><a href="mailto:helder.magalhaes@gmail.com">helder.magalhaes@gmail.com</a> </dd>
-</dl>
+<p>Dieter von Holten (DH)
+:
+Dieter is a freelance programmer living in Hamburg, Germany. He spends his time on projects in refineries and tankfarms, chasing bits from ERP to PLC and back. Although not specifically an expert with graphics, he tries to help out âmaintaining and enhancing this interesting, non-trivial piece of codeâ.</p>
+<p>Helder Magalhães (HM)
+:
+ <a href="mailto:helder.magalhaes@gmail.com">helder.magalhaes@gmail.com</a></p>
<p>Helder is a software engineer at the Power Systems Automation unit of Efacec, in Maia, Portugal. He is an SVG enthusiast and has been involved with the technology since 2005. In his spare time, he tries to help out in several open-source projects, mostly SVG-related, with an emphasis in Batik. He is also an invited expert on the SVG Interest Group.</p>
<p>The following people are some of the Batik project founders and helped define and implement the initial Batik architecture:</p>
-<dl>
-<dt>Bill Haneman</dt>
-<dd><a href="mailto:bill.haneman@ireland.sun.com">bill.haneman@ireland.sun.com</a> </dd>
-</dl>
-<p>Bill Haneman works for Sun Microsystemsâ Desktop Enabling Middleware group in Dublin, Ireland, and implemented much of the Batikâs text support (though not SVG Fonts, thanks Bella, Dean, and David!). He is also technical lead for the <a href="http://developer.gnome.org/projects/gap">GNOME Accessibility Project</a> , an open project to provide an accessibility framework for Linux and Solaris(TM) desktops. A twenty-year veteran of scientific programming and application development, he is a US expatriate who plays traditional Irish music on the uilleann pipes.</p>
-<dl>
-<dt>Vincent Hardy</dt>
-<dd><a href="mailto:vincent.hardy@eng.sun.com">vincent.hardy@eng.sun.com</a> </dd>
-</dl>
+<p>Bill Haneman
+:
+ <a href="mailto:bill.haneman@ireland.sun.com">bill.haneman@ireland.sun.com</a></p>
+<p>Bill Haneman works for Sun Microsystemsâ Desktop Enabling Middleware group in Dublin, Ireland, and implemented much of the Batikâs text support (though not SVG Fonts, thanks Bella, Dean, and David!). He is also technical lead for the <a href="http://developer.gnome.org/projects/gap">GNOME Accessibility Project</a>, an open project to provide an accessibility framework for Linux and Solaris(TM) desktops. A twenty-year veteran of scientific programming and application development, he is a US expatriate who plays traditional Irish music on the uilleann pipes.</p>
+<p>Vincent Hardy
+:
+ <a href="mailto:vincent.hardy@eng.sun.com">vincent.hardy@eng.sun.com</a></p>
<p>Vincent is one of the founders of the SVG Batik project at Apache. He is a Senior Staff Engineer at Sun Microsystems Inc., where he is part of the XML technology center. Vincent represented Sun in the W3Câs SVG Working Group and is currently a W3C fellow in the W3C office in Sophia Antipolis, France. Vincent is the author of papers and a book on the Java 2D API.</p>
-<dl>
-<dt>Stephane Hillion</dt>
-<dd><a href="mailto:shillion@ilog.fr">shillion@ilog.fr</a> </dd>
-</dl>
+<p>Stephane Hillion
+:
+ <a href="mailto:shillion@ilog.fr">shillion@ilog.fr</a></p>
<p>Stephane is a software engineer at the Koala project, part of ILOGâs visualization R&D team, located in Sophia-Antipolis, France. His main interests are in programming languages and web standards. He wrote the Apache Batikâs DOM, CSS and Swing modules.</p>
-<dl>
-<dt>Dean Jackson</dt>
-<dd><a href="mailto:dean.jackson@cmis.csiro.au">dean.jackson@cmis.csiro.au</a> </dd>
-</dl>
+<p>Dean Jackson
+:
+ <a href="mailto:dean.jackson@cmis.csiro.au">dean.jackson@cmis.csiro.au</a></p>
<p>Dean is employed by CSIRO Australia and is currently working at the World Wide Web Consortium (W3C) full time on SVG. He is a member of the W3Câs SVG working group, and was a developer of the CSIRO SVG Toolkit, one of the first and most complete open source SVG libraries.</p>
-<dl>
-<dt>Christophe Jolif</dt>
-<dd><a href="mailto:cjolif@ilog.fr">cjolif@ilog.fr</a> </dd>
-</dl>
+<p>Christophe Jolif
+:
+ <a href="mailto:cjolif@ilog.fr">cjolif@ilog.fr</a></p>
<p>Christophe Jolif is a Software Architect mainly working on the ILOG JViews Component Suite, the ILOG Java visualization framework. He has been working for ILOG since 1997, and is representing the company in the Scalable Vector Graphics (SVG) W3C Working Group since 1999. He has implemented SVG import and export features in ILOG JViews and is now also working on the SVG Batik project at Apache.</p>
-<dl>
-<dt>Thierry Kormann</dt>
-<dd><a href="mailto:tkormann@ilog.fr">tkormann@ilog.fr</a> </dd>
-</dl>
+<p>Thierry Kormann
+:
+ <a href="mailto:tkormann@ilog.fr">tkormann@ilog.fr</a></p>
<p>Thierry is a software engineer, at the Koala project of ILOG located at Sophia-Antipolis, France and a member of the SVG working group. Thierry has contributed to most of Koalaâs projects involving Java and XML. Since then, he co-founded the Apache Batik project. His daytime job is focused on Graphics and XML related technologies. Prior to joining ILOG, Thierry worked as a software engineer for Bull.</p>
-<dl>
-<dt>Nicolas Socheleau</dt>
-<dd><a href="mailto:nicolas.socheleau@bitflash.com">nicolas.socheleau@bitflash.com</a> </dd>
-</dl>
+<p>Nicolas Socheleau
+:
+ <a href="mailto:nicolas.socheleau@bitflash.com">nicolas.socheleau@bitflash.com</a></p>
<p>Nicolas Socheleau is a software engineer at BitFlash Inc, Ottawa, Canada where he worked on different SVG related projects. He joined the Batik team in June 2002. His interests include XML technologies and Graphics. He contributed some text functionality and SVG DOM interface implementations.</p>
-<dl>
-<dt>Emmanuel Tissandier</dt>
-<dd><a href="mailto:tissandi@ilog.fr">tissandi@ilog.fr</a> </dd>
-</dl>
+<p>Emmanuel Tissandier
+:
+ <a href="mailto:tissandi@ilog.fr">tissandi@ilog.fr</a></p>
<p>Emmanuel Tissandier has been working for 10 years as a software engineer in object oriented environments. He started with the development of CASE tools at Rank Xerox and joined the visualization R&D team of ILOG in 1995. Since 1997, he has been the R&D Project Manager for the ILOG JViews Component Suite, a product for delivering two-dimensional structured graphics, cartography, diagrams, and Gantt charts in Java.</p>
<p>Bella Robinson implemented the SVG font support in Batik:</p>
-<dl>
-<dt>Bella Robinson</dt>
-<dd><a href="mailto:bella.robinson@cmis.csiro.au">bella.robinson@cmis.csiro.au</a> </dd>
-</dl>
+<p>Bella Robinson
+:
+ <a href="mailto:bella.robinson@cmis.csiro.au">bella.robinson@cmis.csiro.au</a></p>
<p>Bella is a Software Engineer working for CSIRO Australia. She was one of the main developers of the CSIRO SVG Toolkit and has also been working on a Pocket SVG Viewer for handheld devices. Her interests include graphics and XML programming.</p>
-<p>In addition, <a href="mailto:James.Davidson@eng.sun.com">James Davidson</a> and <a href="mailto:stefano@apache.org">Stefano Mazzochi</a> , two Apache veterans who helped the Batik team start the project at Apache, also have commit access to the Subversion repository.</p>
+<p>In addition, <a href="mailto:James.Davidson@eng.sun.com">James Davidson</a> and <a href="mailto:stefano@apache.org">Stefano Mazzochi</a>, two Apache veterans who helped the Batik team start the project at Apache, also have commit access to the Subversion repository.</p>
<h2 id="batik-contributors-wzxhzdk2wzxhzdk3">Batik contributors <a id="contributors"></a></h2>
<p>The following people have contributed to Batik:</p>
<ul>
Modified: websites/staging/xmlgraphics/trunk/content/batik/demo.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/batik/demo.html (original)
+++ websites/staging/xmlgraphics/trunk/content/batik/demo.html Wed Dec 5 08:23:47 2012
@@ -203,7 +203,7 @@ function updateBar(name) {
}
}
</script>
-The applet ( <a href="demo/AppletDemo.java">view source</a> ) displays the <a href="http://svn.apache.org/repos/asf/xmlgraphics/batik/trunk/samples/barChart.svg">barChart.svg</a> sample from the Batik distribution using a <code>JSVGCanvas</code> . Script in the web page then interacts with the applet, by calling the <code>updateBar</code> method of the applet object when the <strong>Update chart</strong> button is pressed. This method modifies the SVG document being displayed to update the heights of the bars.</p></div>
+The applet ( <a href="demo/AppletDemo.java">view source</a> ) displays the <a href="http://svn.apache.org/repos/asf/xmlgraphics/batik/trunk/samples/barChart.svg">barChart.svg</a> sample from the Batik distribution using a <code>JSVGCanvas</code>. Script in the web page then interacts with the applet, by calling the <code>updateBar</code> method of the applet object when the <strong>Update chart</strong> button is pressed. This method modifies the SVG document being displayed to update the heights of the bars.</p></div>
</div>
<div class="clear"></div>
Modified: websites/staging/xmlgraphics/trunk/content/batik/dev/svg12.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/batik/dev/svg12.html (original)
+++ websites/staging/xmlgraphics/trunk/content/batik/dev/svg12.html Wed Dec 5 08:23:47 2012
@@ -167,9 +167,9 @@ $(document).ready(function () {
</div>
<!-- <div id="breadcrumb"><a href="/">Home</a> » <a href="/batik/">Batik</a> » <a href="/batik/dev/">Dev</a></div> -->
<div class="section-content"><h1 id="svg-12-support">SVG 1.2 support</h1>
-<p>This page details information atbout Batikâs implementation of features from SVG 1.2, <a href="http://www.w3.org/TR/SVGTiny12/">Tiny</a> and <a href="http://www.w3.org/TR/SVG12/">Full</a> . Note that the information on this page is based on the code in the Subversion repository trunk.</p>
+<p>This page details information atbout Batikâs implementation of features from SVG 1.2, <a href="http://www.w3.org/TR/SVGTiny12/">Tiny</a> and <a href="http://www.w3.org/TR/SVG12/">Full</a>. Note that the information on this page is based on the code in the Subversion repository trunk.</p>
<h2 id="dom-level-3-wzxhzdk2wzxhzdk3">DOM Level 3 <a id="dom3"></a></h2>
-<p>DOM Level 3 <a href="http://www.w3.org/TR/DOM-Level-3-Core/">Core</a> , <a href="http://www.w3.org/TR/DOM-Level-3-Events/">Events</a> and <a href="http://www.w3.org/TR/DOM-Level-3-XPath/">XPath</a> are all supported. These features are available regardless of whether the document has <code>version="1.1"</code> or <code>version="1.2"</code> set on the root <code>svg</code> element.</p>
+<p>DOM Level 3 <a href="http://www.w3.org/TR/DOM-Level-3-Core/">Core</a>, <a href="http://www.w3.org/TR/DOM-Level-3-Events/">Events</a> and <a href="http://www.w3.org/TR/DOM-Level-3-XPath/">XPath</a> are all supported. These features are available regardless of whether the document has <code>version="1.1"</code> or <code>version="1.2"</code> set on the root <code>svg</code> element.</p>
<p>There are a few issues with the DOM Level 3 Core implementation:</p>
<ol>
<li>
@@ -182,12 +182,12 @@ $(document).ready(function () {
<p>XML Schema information is never used. Batik does not implement XML Schema, so any methods or attributes that would utilise or expose schema information (such as the <code>schemaTypeInfo</code> attribute on the <code>Attr</code> and <code>Element</code> interfaces) do not do so.</p>
</li>
<li>
-<p><code>Document.normalizeDocument</code> ignores the <code>"entities"</code> parameter in the documentâs <code>DOMConfiguration</code> .</p>
+<p><code>Document.normalizeDocument</code> ignores the <code>"entities"</code> parameter in the documentâs <code>DOMConfiguration</code>.</p>
</li>
</ol>
<h3 id="using-dom-level-3-functionality-from-java-wzxhzdk4wzxhzdk5">Using DOM Level 3 functionality from Java <a id="dom3java"></a></h3>
<p>JREs before 1.5 include the DOM Level 2 interfaces and this can cause problems when trying to use the DOM Level 3 versions of these same interface files ( <code>org.w3c.dom.*</code> ). Though the concrete Batik DOM classes implement the DOM Level 3 functionality, you wonât be able to access those methods through the <code>org.w3c.dom</code> interfaces on these earlier JREs.</p>
-<p>There are two ways to overcome this problem. The first is to install the DOM Level 3 interfaces using the <a href="http://java.sun.com/j2se/1.4.2/docs/guide/standards/">Endorsed Standards Override Mechanism</a> . Copy the file <code>lib/xml-apis-ext.jar</code> into the endorsed standards override directory and the DOM Level 3 interfaces will be visible. You can then write code against them (for example, call <code>Document.renameNode</code> directly). However, this will mean that other people cannot run or compile your code unless they have JRE 1.5 or later, or they have also installed the <code>xml-apis-ext.jar</code> in the same way.</p>
+<p>There are two ways to overcome this problem. The first is to install the DOM Level 3 interfaces using the <a href="http://java.sun.com/j2se/1.4.2/docs/guide/standards/">Endorsed Standards Override Mechanism</a>. Copy the file <code>lib/xml-apis-ext.jar</code> into the endorsed standards override directory and the DOM Level 3 interfaces will be visible. You can then write code against them (for example, call <code>Document.renameNode</code> directly). However, this will mean that other people cannot run or compile your code unless they have JRE 1.5 or later, or they have also installed the <code>xml-apis-ext.jar</code> in the same way.</p>
<p>The second method, which requires less messing about with the JRE, is to cast your DOM objects to the concrete Batik DOM objects and call your DOM Level 3 methods directly on them. The Batik DOM classes are in the <code>org.apache.batik.dom</code> package. The classes named <code>Abstract*</code> implement the DOM interfaces, and also contain the DOM Level 3 methods. The advantage of this method is that for your code to compile and run in othersâ environments, they need not install any jars with the endorsed standards overrides.</p>
<p>Here is an example of using the second method to get access to DOM Level 3 specific methods:</p>
<div class="codehilite"><pre><span class="kn">import</span> <span class="nn">org.apache.batik.dom.AbstractDocument</span><span class="o">;</span>
@@ -254,10 +254,10 @@ $(document).ready(function () {
<p>Note that using these org.apache.batik.dom interfaces is only needed for the DOM Level 3 Core and Events interfaces. There were no earlier versions of the DOM XPath interfaces to conflict with, so these can be used directly ( <code>org.w3c.dom.xpath</code> ).</p>
<p>Of course, none of this matters if you are just using the DOM 3 functionality in ECMAScript, as the matter of interfaces is hidden from the scripting environment.</p>
<h2 id="xml-binding-language-for-svg-sxbl-wzxhzdk6wzxhzdk7">XML Binding Language for SVG (sXBL) <a id="sxbl"></a></h2>
-<p>sXBL is supported in documents with <code>version="1.2"</code> . However, the following issues exist:</p>
+<p>sXBL is supported in documents with <code>version="1.2"</code>. However, the following issues exist:</p>
<ol>
<li>
-<p>sXBL cannot be used for <a href="http://www.w3.org/TR/2004/WD-SVG12-20041027/binding.html#sXBL-bindings-for-svg">SVG resources</a> or <a href="http://www.w3.org/TR/2004/WD-SVG12-20041027/binding.html#sXBL-bindings-for-visual-effects">visual effects</a> .</p>
+<p>sXBL cannot be used for <a href="http://www.w3.org/TR/2004/WD-SVG12-20041027/binding.html#sXBL-bindings-for-svg">SVG resources</a> or <a href="http://www.w3.org/TR/2004/WD-SVG12-20041027/binding.html#sXBL-bindings-for-visual-effects">visual effects</a>.</p>
</li>
<li>
<p>The <code>traitDef</code> element is not implemented.</p>
@@ -266,10 +266,10 @@ $(document).ready(function () {
<p>The <a href="http://www.w3.org/TR/sXBL/#shadow0">handling of CSS</a> is probably not quite correct.</p>
</li>
</ol>
-<p>Two content selector languages are supported: XPath 1.0 Patterns and the drastically reduced XPath subset. XPath Patterns is the default language. To change the language used to the XPath subset, put an attribute <code>batik:selectorLanguage="XPathSubset"</code> on the <code>xbl:content</code> element or on the <code>svg</code> document element. (The <code>batik</code> extension namespace prefix should be declared with <code>xmlns:batik="http://xml.apache.org/batik/ext"</code> .)</p>
-<p>Note that sXBL is likely to be dropped in favor of <a href="http://www.w3.org/TR/xbl2">XBL 2.0</a> in <a href="http://www.w3.org/TR/SVG12/">SVG 1.2 Full</a> .</p>
+<p>Two content selector languages are supported: XPath 1.0 Patterns and the drastically reduced XPath subset. XPath Patterns is the default language. To change the language used to the XPath subset, put an attribute <code>batik:selectorLanguage="XPathSubset"</code> on the <code>xbl:content</code> element or on the <code>svg</code> document element. (The <code>batik</code> extension namespace prefix should be declared with <code>xmlns:batik="http://xml.apache.org/batik/ext"</code>.)</p>
+<p>Note that sXBL is likely to be dropped in favor of <a href="http://www.w3.org/TR/xbl2">XBL 2.0</a> in <a href="http://www.w3.org/TR/SVG12/">SVG 1.2 Full</a>.</p>
<h2 id="flowing-text-and-graphics-wzxhzdk8wzxhzdk9">Flowing text and graphics <a id="flowtext"></a></h2>
-<p>The <code>flowRoot</code> , <code>flowRegion</code> , <code>flowDiv</code> , <code>flowPara</code> , <code>flowSpan</code> , <code>flowRegionBreak</code> and <code>flowLine</code> elements from <a href="http://www.w3.org/TR/SVG12/">SVG 1.2 Full</a> âs <a href="http://www.w3.org/TR/2004/WD-SVG12-20041027/flow.html">Flowing Text and Graphics</a> chapter are supported in documents with <code>version="1.2"</code> .</p>
+<p>The <code>flowRoot</code>, <code>flowRegion</code>, <code>flowDiv</code>, <code>flowPara</code>, <code>flowSpan</code>, <code>flowRegionBreak</code> and <code>flowLine</code> elements from <a href="http://www.w3.org/TR/SVG12/">SVG 1.2 Full</a> âs <a href="http://www.w3.org/TR/2004/WD-SVG12-20041027/flow.html">Flowing Text and Graphics</a> chapter are supported in documents with <code>version="1.2"</code>.</p>
<p>The more recent <a href="http://www.w3.org/TR/SVGTiny12/">SVG 1.2 Tiny</a> draft specifies a different syntax for (a more restricted version of) flowing text, and the full flowing text syntax is therefore likely to change.</p>
<h2 id="other-svg-12-features-wzxhzdk10wzxhzdk11">Other SVG 1.2 features <a id="other"></a></h2>
<p>The following other features from SVG 1.2 are supported:</p>
@@ -278,13 +278,13 @@ $(document).ready(function () {
<p>the <a href="http://www.w3.org/TR/SVGTiny12/painting.html#SolidColorElement">paint server element,</a></p>
</li>
<li>
-<p>the <code>multiImage</code> , <code>subImageRef</code> and <code>subImage</code> elements for <a href="http://www.w3.org/TR/2004/WD-SVG12-20041027/media.html#multires">Alternate content based on display resolutions</a> ,</p>
+<p>the <code>multiImage</code>, <code>subImageRef</code> and <code>subImage</code> elements for <a href="http://www.w3.org/TR/2004/WD-SVG12-20041027/media.html#multires">Alternate content based on display resolutions</a>,</p>
</li>
<li>
-<p>the XML Events <a href="http://www.w3.org/TR/SVGTiny12/script.html#HandlerElement">element</a> ,</p>
+<p>the XML Events <a href="http://www.w3.org/TR/SVGTiny12/script.html#HandlerElement">element</a>,</p>
</li>
<li>
-<p>self-contained <a href="http://www.w3.org/TR/2004/WD-SVG12-20041027/nonvisual.html#external-references">resource documents</a> ,</p>
+<p>self-contained <a href="http://www.w3.org/TR/2004/WD-SVG12-20041027/nonvisual.html#external-references">resource documents</a>,</p>
</li>
<li>
<p>the mouse <a href="http://www.w3.org/TR/2004/WD-SVG12-20041027/dom.html#wheelevent">wheel event</a> (which is likely to be superseded by a similar event developed by the W3C WebAPI WG),</p>
@@ -293,7 +293,7 @@ $(document).ready(function () {
<p>the <a href="http://www.w3.org/TR/2004/WD-SVG12-20041027/dom.html#shapemod">ShapeChange and RenderedBBoxChange events</a> (though the <code>boundingBox</code> attribute of the RenderedBBoxChange event is not used), and</p>
</li>
<li>
-<p>the <code>startMouseCapture</code> and <code>stopMouseCapture</code> methods on the <a href="http://www.w3.org/TR/2004/WD-SVG12-20041027/api.html#GlobalObject">global object</a> .</p>
+<p>the <code>startMouseCapture</code> and <code>stopMouseCapture</code> methods on the <a href="http://www.w3.org/TR/2004/WD-SVG12-20041027/api.html#GlobalObject">global object</a>.</p>
</li>
</ul></div>
</div>
Modified: websites/staging/xmlgraphics/trunk/content/batik/dev/test.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/batik/dev/test.html (original)
+++ websites/staging/xmlgraphics/trunk/content/batik/dev/test.html Wed Dec 5 08:23:47 2012
@@ -186,7 +186,7 @@ $(document).ready(function () {
<p>The following are the high level interfaces in the infrastructure.</p>
<p><a href="../javadoc/org/apache/batik/test/Test.html">Test</a>
:
-A <code>Test</code> is performing whatever check is needed in its <code>run</code> method, and each run produces a <code>TestReport</code> .</p>
+A <code>Test</code> is performing whatever check is needed in its <code>run</code> method, and each run produces a <code>TestReport</code>.</p>
<p><a href="../javadoc/org/apache/batik/test/TestReport.html">TestReport</a>
:
A <code>TestReport</code> describes whether a <code>Test</code> run passed or failed and provides a description of the failure in terms of an error code (unique in the context of a given <code>Test</code> ) and a set of key/value pairs.</p>
@@ -195,7 +195,7 @@ A <code>TestReport</code> describes whet
A <code>TestSuite</code> is a test aggregation which can run a set of <code>Test</code> instances.</p>
<p><a href="../javadoc/org/apache/batik/test/TestReportProcessor.html">TestReportProcessor</a>
:
-A <code>TestReportProcessor</code> is used to analyze a <code>TestReport</code> . A specific implementation can choose to create graphs, send an email or write an HTML file.</p>
+A <code>TestReportProcessor</code> is used to analyze a <code>TestReport</code>. A specific implementation can choose to create graphs, send an email or write an HTML file.</p>
<h3 id="default-implementations-wzxhzdk11wzxhzdk12">Default implementations <a id="Default+implementations"></a></h3>
<p>The test infrastructure comes with a number of default implementations for the interfaces described above. Specifically:</p>
<p><a href="../javadoc/org/apache/batik/test/AbstractTest.html">AbstractTest</a>
@@ -215,7 +215,7 @@ This class is a sample <code>TestReportP
This is another implementation of the <code>TestReportProcessor</code> interface that emails a test report to a list of destination e-mail addresses.</p>
<h3 id="xml-implementations-wzxhzdk13wzxhzdk14">XML implementations <a id="XML+implementations"></a></h3>
<p>The test infrastructure is using XML-out (and XML-in too, see the <a href="#runningATestSuite">Running a test suite</a> section) as a favorite way to generate test reports. The <a href="../javadoc/org/apache/batik/test/XMLTestReportProcessor.html">XMLTestReportProcessor</a> implementation of the <code>TestReportProcessor</code> interface. It outputs reports in XML in a configurable directory.</p>
-<p>The <code>XMLTestReportProcessor</code> can notify an <a href="../javadoc/org/apache/batik/test/XMLReportConsumer.html">XMLReportConsumer</a> when it has created a new report. There is one implementation of that interface that can run an XSL stylesheet on the XML report (e.g., to generate an HTML report), called <a href="../javadoc/org/apache/batik/test/XSLXMLReportConsumer.html">XSLXMLReportConsumer</a> . This is used by the <code>regard</code> rule in the Batik build to produce an HTML report for the default regression test suite.</p>
+<p>The <code>XMLTestReportProcessor</code> can notify an <a href="../javadoc/org/apache/batik/test/XMLReportConsumer.html">XMLReportConsumer</a> when it has created a new report. There is one implementation of that interface that can run an XSL stylesheet on the XML report (e.g., to generate an HTML report), called <a href="../javadoc/org/apache/batik/test/XSLXMLReportConsumer.html">XSLXMLReportConsumer</a>. This is used by the <code>regard</code> rule in the Batik build to produce an HTML report for the default regression test suite.</p>
<h2 id="managing-test-suites-wzxhzdk15wzxhzdk16">Managing test suites <a id="managingATestSuite"></a></h2>
<p>The infrastructure is designed to make it easy to create, update and modify test suites. This section describes how to describe a set of tests to be run and how to actually run that test suite.</p>
<h3 id="describing-a-test-suite-wzxhzdk17wzxhzdk18">Describing a test suite <a id="Describing+a+test+suite"></a></h3>
@@ -314,7 +314,7 @@ This is another implementation of the <c
<p>and for Unix:</p>
<p>build.sh runtestsuite path/to/my/newly/created/testSuite.xml</p>
<p>In addition, the <code>regard</code> rule runs a specific set of tests by default, so that you do not need to pass any <em>testRun</em> file argument.</p>
-<p><strong> <code>regard</code> is the projectâs safeguard against regressions</strong> .</p>
+<p><strong> <code>regard</code> is the projectâs safeguard against regressions</strong>.</p>
<h2 id="regard-the-batik-regression-test-suite-wzxhzdk21wzxhzdk22">regard: the Batik regression test suite <a id="regard"></a></h2>
<p>The regard test suite contains all the regression tests for the Batik project. The <code>regard</code> tool is a specific test suite description, <code>regard.xml</code> (which you can find in the <code>test-resources/org/apache/batik/test</code> directory). That file contains a set of test suite files which sould be run.</p>
<p>The following describes how to use the regard tool and some of the most important tests in the regard test suite.</p>
@@ -329,7 +329,7 @@ This is another implementation of the <c
<p>build.sh regard unitTesting.ts batikFX.svg</p>
<p>will run all the tests with an ID containing <code>unitTesting.ts</code> (i.e., all the test selection unit testing, see <code>test-resources/org/apache/batik/gvt/unitTesting.xml</code> ) and the accuracy rendering test on <code>batikFX.svg</code> (because it is the only test with <code>batikFX.svg</code> in its ID).</p>
<h3 id="rendering-accuracy-tests-wzxhzdk25wzxhzdk26">Rendering accuracy tests <a id="Rendering+accuracy+tests"></a></h3>
-<p>There is a <code>Test</code> implementation, <a href="../javadoc/org/apache/batik/test/SVGRenderingAccuracyTest.html">SVGRenderingAccuracyTest</a> , which checks that Batikâs rendering of an SVG document stays accurate. It compares reference images with the rendering Batik produces and reports any discrepency.</p>
+<p>There is a <code>Test</code> implementation, <a href="../javadoc/org/apache/batik/test/SVGRenderingAccuracyTest.html">SVGRenderingAccuracyTest</a>, which checks that Batikâs rendering of an SVG document stays accurate. It compares reference images with the rendering Batik produces and reports any discrepency.</p>
<p>An <code>SVGRenderingAccuracyTest</code> âs constructor configuration is made of:</p>
<ul>
<li>
@@ -374,11 +374,11 @@ This is another implementation of the <c
<h4 id="daily-usage-wzxhzdk33wzxhzdk34">Daily usage ## <a id="Daily+usage"></a></h4>
<p>Once the intial set up has been done, you can use regard by simply updating your SVN copy, including the test-references. If no change occurs, your test will keep passing with your reference images. If a test fails (e.g., if someone checks in a new reference image from a platform different than the one you are using, you will have to check if it is because of system specific reasons or if there is a bigger problem.</p>
<h3 id="svg-generator-tests-wzxhzdk35wzxhzdk36">SVG generator tests <a id="SVG+generator+tests"></a></h3>
-<p>Regard contains over 100 tests for checking regressions on the SVG generator. If you use <code>svggen</code> as an argument to regard, all the SVG generator tests will be run (because <code>regard.xml</code> points to <code>test-resources/org/apache/batik/svggen/regsvggen.xml</code> , which is a test suite description for the SVG generator and that fileâs root <code>testSuite</code> element has the âsvggenâ ID).</p>
+<p>Regard contains over 100 tests for checking regressions on the SVG generator. If you use <code>svggen</code> as an argument to regard, all the SVG generator tests will be run (because <code>regard.xml</code> points to <code>test-resources/org/apache/batik/svggen/regsvggen.xml</code>, which is a test suite description for the SVG generator and that fileâs root <code>testSuite</code> element has the âsvggenâ ID).</p>
<h2 id="writing-new-tests-wzxhzdk37wzxhzdk38">Writing new tests <a id="writingNewTests"></a></h2>
<p>Writing a new test involves either configuring a new test or writing a new <code>Test</code> class. In both cases, you will need to add an entry to a test suiteâs XML description. This section uses two test suites as an example: the âregardâ test suite to show how to configure a new test and the âunitTestsâ test suite to show how to add a new <code>Test</code> implementation.</p>
<h3 id="adding-a-new-test-configuration-wzxhzdk39wzxhzdk40">Adding a new test configuration <a id="Adding+a+new+test+configuration"></a></h3>
-<p>Imagine that you add a cool new test case to the <code>samples</code> directory, such as <code>linking-viewBox.svg</code> . In order to check for regressions on that file you can add the following entry:</p>
+<p>Imagine that you add a cool new test case to the <code>samples</code> directory, such as <code>linking-viewBox.svg</code>. In order to check for regressions on that file you can add the following entry:</p>
<div class="codehilite"><pre><span class="nt"><test</span> <span class="na">id=</span><span class="s">"anne.svg"</span> <span class="na">class=</span><span class="s">"org.apache.batik.test.svg.SVGRenderingAccuracyTest"</span><span class="nt">></span>
<span class="nt"><arg</span> <span class="na">class=</span><span class="s">"java.net.URL"</span>
<span class="na">value=</span><span class="s">"file:samples/tests/linkingViewBox.svg"</span><span class="nt">/></span>
@@ -394,9 +394,9 @@ This is another implementation of the <c
</pre></div>
-<p>to the <code>test-resources/org/apache/batik/test/samplesRendering.xml</code> test suite description, the description of the regard test suite. If you have access to the build machine where the reference images are typically generated, you can check 0n the reference image in <code>test-references/samples/tests</code> . Otherwise (and this is OK), you can let the test fail the first time it is run on the build/test machine and that will be a reminder for whoever is responsible for that machine that a valid reference image should be checked in.</p>
+<p>to the <code>test-resources/org/apache/batik/test/samplesRendering.xml</code> test suite description, the description of the regard test suite. If you have access to the build machine where the reference images are typically generated, you can check 0n the reference image in <code>test-references/samples/tests</code>. Otherwise (and this is OK), you can let the test fail the first time it is run on the build/test machine and that will be a reminder for whoever is responsible for that machine that a valid reference image should be checked in.</p>
<h3 id="writing-a-new-test-wzxhzdk41wzxhzdk42">Writing a new test <a id="Writing+a+new+test"></a></h3>
-<p>Imagine you want to validate some aspect of your code, and let's take the bridge error handling as an example. You could create a new class in the <code>test-sources</code> directory, in <code>test-sources/org/apache/batik/bridge</code> in our example, and let's call it <code>ErrorHandlingTest</code> . To simplify the implementation of the <code>Test</code> interface, you can choose to derive from the <code>AbstractTest</code> class and generate a <code>DefaultTestReport</code> .</p>
+<p>Imagine you want to validate some aspect of your code, and let's take the bridge error handling as an example. You could create a new class in the <code>test-sources</code> directory, in <code>test-sources/org/apache/batik/bridge</code> in our example, and let's call it <code>ErrorHandlingTest</code>. To simplify the implementation of the <code>Test</code> interface, you can choose to derive from the <code>AbstractTest</code> class and generate a <code>DefaultTestReport</code>.</p>
<p>While writing the <code>Test</code> you may want to use your own XML file with just your test, for example:</p>
<div class="codehilite"><pre><span class="nt"><testReportProcessor</span> <span class="na">class=</span><span class="s">"org.apache.batik.test.SimpleTestReportProcessor"</span><span class="nt">/></span>
Modified: websites/staging/xmlgraphics/trunk/content/batik/download.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/batik/download.html (original)
+++ websites/staging/xmlgraphics/trunk/content/batik/download.html Wed Dec 5 08:23:47 2012
@@ -187,18 +187,17 @@ $(document).ready(function () {
<p>There are several ways to obtain a source distribution. Please note that they are listed from least current to most current:</p>
<ul>
<li>
-<p>Download a released version from a <a href="http://www.apache.org/dyn/closer.cgi/xmlgraphics/batik">Batik Distribution mirror</a> . Source distributions include "-src" in their names.</p>
+<p>Download a released version from a <a href="http://www.apache.org/dyn/closer.cgi/xmlgraphics/batik">Batik Distribution mirror</a>. Source distributions include "-src" in their names.</p>
</li>
<li>
-<p>Download directly from the SVN repository. Anyone can do this using the <a href="http://xmlgraphics.apache.org/repo.html">Anonymous SVN Server</a> . By default, the code in SVN is up-to-the-minute, the same code that the developers are modifying. See the <a href="dev/tools.html#svn">SVN section of Developer Tools</a> for more information on using SVN.</p>
+<p>Download directly from the SVN repository. Anyone can do this using the <a href="http://xmlgraphics.apache.org/repo.html">Anonymous SVN Server</a>. By default, the code in SVN is up-to-the-minute, the same code that the developers are modifying. See the <a href="dev/tools.html#svn">SVN section of Developer Tools</a> for more information on using SVN.</p>
</li>
</ul>
<h4 id="latest-stable-release">Latest Stable Release</h4>
<p><em>Repository URL</em> ~ <a href="http://svn.apache.org/repos/asf/xmlgraphics/batik/">http://svn.apache.org/repos/asf/xmlgraphics/batik/</a></p>
<p><em>Web View</em> ~ <a href="http://svn.apache.org/viewvc/xmlgraphics/batik/">http://svn.apache.org/viewvc/xmlgraphics/batik/</a></p>
<p><em>Repository URL</em> ~ TRUNK: <a href="http://svn.apache.org/repos/asf/xmlgraphics/batik/trunk/">http://svn.apache.org/repos/asf/xmlgraphics/batik/trunk/</a></p>
-<p><em>European Mirror</em> <a href="http://svn.eu.apache.org/repos/asf/xmlgraphics/batik/trunk/">http://svn.eu.apache.org/repos/asf/xmlgraphics/batik/trunk/</a><br />
-</p>
+<p><em>European Mirror</em> <a href="http://svn.eu.apache.org/repos/asf/xmlgraphics/batik/trunk/">http://svn.eu.apache.org/repos/asf/xmlgraphics/batik/trunk/</a></p>
<p><em>Web View</em> ~ TRUNK: <a href="http://svn.apache.org/viewvc/xmlgraphics/batik/trunk/">http://svn.apache.org/viewvc/xmlgraphics/batik/trunk/</a></p>
<p><em>European Mirror</em> <a href="http://svn.eu.apache.org/viewvc/xmlgraphics/batik/trunk/">http://svn.eu.apache.org/viewvc/xmlgraphics/batik/trunk/</a></p>
<p>With any source distribution, you will need to build FOP from the source files. For details please see the "Build" page on the documentation tab for the version you've downloaded.</p>
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: commits-help@xmlgraphics.apache.org