You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@xmlgraphics.apache.org by vh...@apache.org on 2014/07/24 18:21:24 UTC
svn commit: r1613173 [1/15] - in /xmlgraphics/site/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: vhennebert
Date: Thu Jul 24 16:21:20 2014
New Revision: 1613173
URL: http://svn.apache.org/r1613173
Log:
Batch replacement of {#id} syntax for headers with { #id} to avoid parser error from Dotiac::DTL
Modified:
xmlgraphics/site/trunk/content/batik/contributors.mdtext
xmlgraphics/site/trunk/content/batik/dev/svg12.mdtext
xmlgraphics/site/trunk/content/batik/dev/test.mdtext
xmlgraphics/site/trunk/content/batik/download.mdtext
xmlgraphics/site/trunk/content/batik/faq.mdtext
xmlgraphics/site/trunk/content/batik/index.mdtext
xmlgraphics/site/trunk/content/batik/install.mdtext
xmlgraphics/site/trunk/content/batik/mailing-lists.mdtext
xmlgraphics/site/trunk/content/batik/status.mdtext
xmlgraphics/site/trunk/content/batik/tools/browser.mdtext
xmlgraphics/site/trunk/content/batik/tools/font-converter.mdtext
xmlgraphics/site/trunk/content/batik/tools/pretty-printer.mdtext
xmlgraphics/site/trunk/content/batik/tools/rasterizer.mdtext
xmlgraphics/site/trunk/content/batik/uses.mdtext
xmlgraphics/site/trunk/content/batik/using/architecture.mdtext
xmlgraphics/site/trunk/content/batik/using/dom-api.mdtext
xmlgraphics/site/trunk/content/batik/using/extending.mdtext
xmlgraphics/site/trunk/content/batik/using/parsers.mdtext
xmlgraphics/site/trunk/content/batik/using/scripting/ecmascript.mdtext
xmlgraphics/site/trunk/content/batik/using/scripting/java.mdtext
xmlgraphics/site/trunk/content/batik/using/scripting/security.mdtext
xmlgraphics/site/trunk/content/batik/using/svg-generator.mdtext
xmlgraphics/site/trunk/content/batik/using/swing.mdtext
xmlgraphics/site/trunk/content/batik/using/transcoder.mdtext
xmlgraphics/site/trunk/content/commons/bugs.mdtext
xmlgraphics/site/trunk/content/commons/changes.mdtext
xmlgraphics/site/trunk/content/commons/download.mdtext
xmlgraphics/site/trunk/content/commons/image-loader.mdtext
xmlgraphics/site/trunk/content/commons/index.mdtext
xmlgraphics/site/trunk/content/commons/postscript.mdtext
xmlgraphics/site/trunk/content/fop/0.95/anttask.mdtext
xmlgraphics/site/trunk/content/fop/0.95/changes_0.95.mdtext
xmlgraphics/site/trunk/content/fop/0.95/changes_0.95beta.mdtext
xmlgraphics/site/trunk/content/fop/0.95/compiling.mdtext
xmlgraphics/site/trunk/content/fop/0.95/configuration.mdtext
xmlgraphics/site/trunk/content/fop/0.95/embedding.mdtext
xmlgraphics/site/trunk/content/fop/0.95/extensions.mdtext
xmlgraphics/site/trunk/content/fop/0.95/fonts.mdtext
xmlgraphics/site/trunk/content/fop/0.95/graphics.mdtext
xmlgraphics/site/trunk/content/fop/0.95/hyphenation.mdtext
xmlgraphics/site/trunk/content/fop/0.95/index.mdtext
xmlgraphics/site/trunk/content/fop/0.95/intermediate.mdtext
xmlgraphics/site/trunk/content/fop/0.95/knownissues_overview.mdtext
xmlgraphics/site/trunk/content/fop/0.95/metadata.mdtext
xmlgraphics/site/trunk/content/fop/0.95/output.mdtext
xmlgraphics/site/trunk/content/fop/0.95/pdfa.mdtext
xmlgraphics/site/trunk/content/fop/0.95/pdfencryption.mdtext
xmlgraphics/site/trunk/content/fop/0.95/pdfx.mdtext
xmlgraphics/site/trunk/content/fop/0.95/releaseNotes_0.95.mdtext
xmlgraphics/site/trunk/content/fop/0.95/running.mdtext
xmlgraphics/site/trunk/content/fop/0.95/servlets.mdtext
xmlgraphics/site/trunk/content/fop/0.95/upgrading.mdtext
xmlgraphics/site/trunk/content/fop/1.0/accessibility.mdtext
xmlgraphics/site/trunk/content/fop/1.0/anttask.mdtext
xmlgraphics/site/trunk/content/fop/1.0/changes_1.0.mdtext
xmlgraphics/site/trunk/content/fop/1.0/compiling.mdtext
xmlgraphics/site/trunk/content/fop/1.0/configuration.mdtext
xmlgraphics/site/trunk/content/fop/1.0/embedding.mdtext
xmlgraphics/site/trunk/content/fop/1.0/events.mdtext
xmlgraphics/site/trunk/content/fop/1.0/extensions.mdtext
xmlgraphics/site/trunk/content/fop/1.0/fonts.mdtext
xmlgraphics/site/trunk/content/fop/1.0/graphics.mdtext
xmlgraphics/site/trunk/content/fop/1.0/hyphenation.mdtext
xmlgraphics/site/trunk/content/fop/1.0/index.mdtext
xmlgraphics/site/trunk/content/fop/1.0/intermediate.mdtext
xmlgraphics/site/trunk/content/fop/1.0/knownissues_overview.mdtext
xmlgraphics/site/trunk/content/fop/1.0/metadata.mdtext
xmlgraphics/site/trunk/content/fop/1.0/output.mdtext
xmlgraphics/site/trunk/content/fop/1.0/pdfa.mdtext
xmlgraphics/site/trunk/content/fop/1.0/pdfencryption.mdtext
xmlgraphics/site/trunk/content/fop/1.0/pdfx.mdtext
xmlgraphics/site/trunk/content/fop/1.0/releaseNotes_1.0.mdtext
xmlgraphics/site/trunk/content/fop/1.0/running.mdtext
xmlgraphics/site/trunk/content/fop/1.0/servlets.mdtext
xmlgraphics/site/trunk/content/fop/1.0/upgrading.mdtext
xmlgraphics/site/trunk/content/fop/1.1/accessibility.mdtext
xmlgraphics/site/trunk/content/fop/1.1/anttask.mdtext
xmlgraphics/site/trunk/content/fop/1.1/changes_1.1.mdtext
xmlgraphics/site/trunk/content/fop/1.1/compiling.mdtext
xmlgraphics/site/trunk/content/fop/1.1/complexscripts.mdtext
xmlgraphics/site/trunk/content/fop/1.1/configuration.mdtext
xmlgraphics/site/trunk/content/fop/1.1/embedding.mdtext
xmlgraphics/site/trunk/content/fop/1.1/events.mdtext
xmlgraphics/site/trunk/content/fop/1.1/extensions.mdtext
xmlgraphics/site/trunk/content/fop/1.1/fonts.mdtext
xmlgraphics/site/trunk/content/fop/1.1/graphics.mdtext
xmlgraphics/site/trunk/content/fop/1.1/hyphenation.mdtext
xmlgraphics/site/trunk/content/fop/1.1/index.mdtext
xmlgraphics/site/trunk/content/fop/1.1/intermediate.mdtext
xmlgraphics/site/trunk/content/fop/1.1/knownissues_overview.mdtext
xmlgraphics/site/trunk/content/fop/1.1/metadata.mdtext
xmlgraphics/site/trunk/content/fop/1.1/output.mdtext
xmlgraphics/site/trunk/content/fop/1.1/pdfa.mdtext
xmlgraphics/site/trunk/content/fop/1.1/pdfencryption.mdtext
xmlgraphics/site/trunk/content/fop/1.1/pdfx.mdtext
xmlgraphics/site/trunk/content/fop/1.1/releaseNotes_1.1.mdtext
xmlgraphics/site/trunk/content/fop/1.1/running.mdtext
xmlgraphics/site/trunk/content/fop/1.1/servlets.mdtext
xmlgraphics/site/trunk/content/fop/1.1/upgrading.mdtext
xmlgraphics/site/trunk/content/fop/bugs.mdtext
xmlgraphics/site/trunk/content/fop/changes.mdtext
xmlgraphics/site/trunk/content/fop/compliance.mdtext
xmlgraphics/site/trunk/content/fop/dev/conventions.mdtext
xmlgraphics/site/trunk/content/fop/dev/design/areas.mdtext
xmlgraphics/site/trunk/content/fop/dev/design/breakpos.mdtext
xmlgraphics/site/trunk/content/fop/dev/design/embedding.mdtext
xmlgraphics/site/trunk/content/fop/dev/design/extending.mdtext
xmlgraphics/site/trunk/content/fop/dev/design/fotree.mdtext
xmlgraphics/site/trunk/content/fop/dev/design/images.mdtext
xmlgraphics/site/trunk/content/fop/dev/design/index.mdtext
xmlgraphics/site/trunk/content/fop/dev/design/layout.mdtext
xmlgraphics/site/trunk/content/fop/dev/design/optimise.mdtext
xmlgraphics/site/trunk/content/fop/dev/design/parsing.mdtext
xmlgraphics/site/trunk/content/fop/dev/design/pdf-library.mdtext
xmlgraphics/site/trunk/content/fop/dev/design/properties.mdtext
xmlgraphics/site/trunk/content/fop/dev/design/renderers.mdtext
xmlgraphics/site/trunk/content/fop/dev/design/startup.mdtext
xmlgraphics/site/trunk/content/fop/dev/design/svg.mdtext
xmlgraphics/site/trunk/content/fop/dev/design/useragent.mdtext
xmlgraphics/site/trunk/content/fop/dev/doc.mdtext
xmlgraphics/site/trunk/content/fop/dev/extensions.mdtext
xmlgraphics/site/trunk/content/fop/dev/faq.mdtext
xmlgraphics/site/trunk/content/fop/dev/implement.mdtext
xmlgraphics/site/trunk/content/fop/dev/index.mdtext
xmlgraphics/site/trunk/content/fop/dev/release.mdtext
xmlgraphics/site/trunk/content/fop/dev/rtflib.mdtext
xmlgraphics/site/trunk/content/fop/dev/svg.mdtext
xmlgraphics/site/trunk/content/fop/dev/testing.mdtext
xmlgraphics/site/trunk/content/fop/dev/tools.mdtext
xmlgraphics/site/trunk/content/fop/download.mdtext
xmlgraphics/site/trunk/content/fop/examples.mdtext
xmlgraphics/site/trunk/content/fop/faq.mdtext
xmlgraphics/site/trunk/content/fop/fo.mdtext
xmlgraphics/site/trunk/content/fop/fop-pdf-images.mdtext
xmlgraphics/site/trunk/content/fop/gethelp.mdtext
xmlgraphics/site/trunk/content/fop/index.mdtext
xmlgraphics/site/trunk/content/fop/knownissues.mdtext
xmlgraphics/site/trunk/content/fop/license.mdtext
xmlgraphics/site/trunk/content/fop/maillist.mdtext
xmlgraphics/site/trunk/content/fop/news.mdtext
xmlgraphics/site/trunk/content/fop/quickstartguide.mdtext
xmlgraphics/site/trunk/content/fop/resources.mdtext
xmlgraphics/site/trunk/content/fop/status.mdtext
xmlgraphics/site/trunk/content/fop/team.mdtext
xmlgraphics/site/trunk/content/fop/trunk/accessibility.mdtext
xmlgraphics/site/trunk/content/fop/trunk/anttask.mdtext
xmlgraphics/site/trunk/content/fop/trunk/compiling.mdtext
xmlgraphics/site/trunk/content/fop/trunk/complexscripts.mdtext
xmlgraphics/site/trunk/content/fop/trunk/configuration.mdtext
xmlgraphics/site/trunk/content/fop/trunk/embedding.mdtext
xmlgraphics/site/trunk/content/fop/trunk/events.mdtext
xmlgraphics/site/trunk/content/fop/trunk/extensions.mdtext
xmlgraphics/site/trunk/content/fop/trunk/fonts.mdtext
xmlgraphics/site/trunk/content/fop/trunk/graphics.mdtext
xmlgraphics/site/trunk/content/fop/trunk/hyphenation.mdtext
xmlgraphics/site/trunk/content/fop/trunk/index.mdtext
xmlgraphics/site/trunk/content/fop/trunk/intermediate.mdtext
xmlgraphics/site/trunk/content/fop/trunk/metadata.mdtext
xmlgraphics/site/trunk/content/fop/trunk/output.mdtext
xmlgraphics/site/trunk/content/fop/trunk/pdfa.mdtext
xmlgraphics/site/trunk/content/fop/trunk/pdfencryption.mdtext
xmlgraphics/site/trunk/content/fop/trunk/pdfx.mdtext
xmlgraphics/site/trunk/content/fop/trunk/running.mdtext
xmlgraphics/site/trunk/content/fop/trunk/servlets.mdtext
xmlgraphics/site/trunk/content/fop/trunk/upgrading.mdtext
xmlgraphics/site/trunk/content/fop/trunk/whitespacemanagement.mdtext
xmlgraphics/site/trunk/content/legal.mdtext
xmlgraphics/site/trunk/content/mail.mdtext
xmlgraphics/site/trunk/content/repo.mdtext
xmlgraphics/site/trunk/content/team.mdtext
Modified: xmlgraphics/site/trunk/content/batik/contributors.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/batik/contributors.mdtext?rev=1613173&r1=1613172&r2=1613173&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/batik/contributors.mdtext (original)
+++ xmlgraphics/site/trunk/content/batik/contributors.mdtext Thu Jul 24 16:21:20 2014
@@ -5,7 +5,7 @@ Title: Batik contributors
This page contains information about the current Batik developers and the features they are working on at the moment.
-## Committers {#committers}
+## Committers { #committers}
This section lists all developers with commit access to the Batik subversion repository.
@@ -109,7 +109,7 @@ Bella is a Software Engineer working for
In addition, [James Davidson](mailto:James.Davidson@eng.sun.com) and [Stefano Mazzochi](mailto:stefano@apache.org), two Apache veterans who helped the Batik team start the project at Apache, also have commit access to the Subversion repository.
-## Batik contributors {#contributors}
+## Batik contributors { #contributors}
The following people have contributed to Batik:
@@ -158,7 +158,7 @@ The following people have contributed to
- [Andres Toussaint](mailto:andres@onemileup.com) âContributed SVGAnimatedPathData functionality.
-## Areas of expertise {#expertise}
+## Areas of expertise { #expertise}
The following table summarizes the areas of expertise of each active committer. It allows better coordination of both internal and external development efforts.
<div class="expertise">
Modified: xmlgraphics/site/trunk/content/batik/dev/svg12.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/batik/dev/svg12.mdtext?rev=1613173&r1=1613172&r2=1613173&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/batik/dev/svg12.mdtext (original)
+++ xmlgraphics/site/trunk/content/batik/dev/svg12.mdtext Thu Jul 24 16:21:20 2014
@@ -5,7 +5,7 @@ Title: SVG 1.2 support
This page details information atbout Batikâs implementation of features from SVG 1.2, [Tiny](http://www.w3.org/TR/SVGTiny12/) and [Full](http://www.w3.org/TR/SVG12/). Note that the information on this page is based on the code in the Subversion repository trunk.
-## DOM Level 3 {#dom3}
+## DOM Level 3 { #dom3}
DOM Level 3 [Core](http://www.w3.org/TR/DOM-Level-3-Core/), [Events](http://www.w3.org/TR/DOM-Level-3-Events/) and [XPath](http://www.w3.org/TR/DOM-Level-3-XPath/) are all supported. These features are available regardless of whether the document has `version="1.1"` or `version="1.2"` set on the root `svg` element.
@@ -20,7 +20,7 @@ There are a few issues with the DOM Leve
1. `Document.normalizeDocument` ignores the `"entities"` parameter in the documentâs `DOMConfiguration`.
-### Using DOM Level 3 functionality from Java {#dom3java}
+### Using DOM Level 3 functionality from Java { #dom3java}
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 (`org.w3c.dom.*`). Though the concrete Batik DOM classes implement the DOM Level 3 functionality, you wonât be able to access those methods through the `org.w3c.dom` interfaces on these earlier JREs.
@@ -94,7 +94,7 @@ Note that using these org.apache.batik.d
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.
-## XML Binding Language for SVG (sXBL) {#sxbl}
+## XML Binding Language for SVG (sXBL) { #sxbl}
sXBL is supported in documents with `version="1.2"`. However, the following issues exist:
@@ -109,13 +109,13 @@ Two content selector languages are suppo
Note that sXBL is likely to be dropped in favor of [XBL 2.0](http://www.w3.org/TR/xbl2) in [SVG 1.2 Full](http://www.w3.org/TR/SVG12/).
-## Flowing text and graphics {#flowtext}
+## Flowing text and graphics { #flowtext}
The `flowRoot`, `flowRegion`, `flowDiv`, `flowPara`, `flowSpan`, `flowRegionBreak` and `flowLine` elements from [SVG 1.2 Full](http://www.w3.org/TR/SVG12/) âs [Flowing Text and Graphics](http://www.w3.org/TR/2004/WD-SVG12-20041027/flow.html) chapter are supported in documents with `version="1.2"`.
The more recent [SVG 1.2 Tiny](http://www.w3.org/TR/SVGTiny12/) draft specifies a different syntax for (a more restricted version of) flowing text, and the full flowing text syntax is therefore likely to change.
-## Other SVG 1.2 features {#other}
+## Other SVG 1.2 features { #other}
The following other features from SVG 1.2 are supported:
Modified: xmlgraphics/site/trunk/content/batik/dev/test.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/batik/dev/test.mdtext?rev=1613173&r1=1613172&r2=1613173&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/batik/dev/test.mdtext (original)
+++ xmlgraphics/site/trunk/content/batik/dev/test.mdtext Thu Jul 24 16:21:20 2014
@@ -16,9 +16,9 @@ The intent for the test infrastructure i
While the test suites in the infrastructure will be run every day by build/test machines, they are also intended to help the commiters and developers get confident that their code modifications did not introduce regressions.
-## The test infrastructure {#infrastructure}
+## The test infrastructure { #infrastructure}
-### High-level interfaces {#High-level-interfaces}
+### High-level interfaces { #High-level-interfaces}
The following are the high level interfaces in the infrastructure.
@@ -43,7 +43,7 @@ A `TestSuite` is a test aggregation whic
:
A `TestReportProcessor` is used to analyze a `TestReport`. A specific implementation can choose to create graphs, send an email or write an HTML file.
-### Default implementations {#Default-implementations}
+### Default implementations { #Default-implementations}
The test infrastructure comes with a number of default implementations for the interfaces described above. Specifically:
@@ -73,17 +73,17 @@ This class is a sample `TestReportProces
:
This is another implementation of the `TestReportProcessor` interface that emails a test report to a list of destination e-mail addresses.
-### XML implementations {#XML-implementations}
+### XML implementations { #XML-implementations}
The test infrastructure is using XML-out (and XML-in too, see the [Running a test suite](#runningATestSuite) section) as a favorite way to generate test reports. The [XMLTestReportProcessor](../javadoc/org/apache/batik/test/XMLTestReportProcessor.html) implementation of the `TestReportProcessor` interface. It outputs reports in XML in a configurable directory.
The `XMLTestReportProcessor` can notify an [XMLReportConsumer](../javadoc/org/apache/batik/test/XMLReportConsumer.html) 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 [XSLXMLReportConsumer](../javadoc/org/apache/batik/test/XSLXMLReportConsumer.html). This is used by the `regard` rule in the Batik build to produce an HTML report for the default regression test suite.
-## Managing test suites {#managingATestSuite}
+## Managing test suites { #managingATestSuite}
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.
-### Describing a test suite {#Describing-a-test-suite}
+### Describing a test suite { #Describing-a-test-suite}
Test suites can be described in XML (XML-in refered to earlier in this document). The general format for describing a test suite is:
@@ -127,7 +127,7 @@ The following example shows a test suite
</testSuite>
-## Running a test suite {#runningATestSuite}
+## Running a test suite { #runningATestSuite}
Yet another XML file describes which test to run and how to process the generated test reports. The general syntax is something like:
@@ -191,13 +191,13 @@ In addition, the `regard` rule runs a sp
** `regard` is the projectâs safeguard against regressions**.
-## regard: the Batik regression test suite {#regard}
+## regard: the Batik regression test suite { #regard}
The regard test suite contains all the regression tests for the Batik project. The `regard` tool is a specific test suite description, `regard.xml` (which you can find in the `test-resources/org/apache/batik/test` directory). That file contains a set of test suite files which sould be run.
The following describes how to use the regard tool and some of the most important tests in the regard test suite.
-### Running regard {#Running-regard}
+### Running regard { #Running-regard}
The regard tool lets you run either all the tests or any specific test you want in the test suite. To run all the tests in the regard test suite, type the following at the command line, for Windows:
@@ -217,7 +217,7 @@ For example:
will run all the tests with an ID containing `unitTesting.ts` (i.e., all the test selection unit testing, see `test-resources/org/apache/batik/gvt/unitTesting.xml`) and the accuracy rendering test on `batikFX.svg` (because it is the only test with `batikFX.svg` in its ID).
-### Rendering accuracy tests {#Rendering-accuracy-tests}
+### Rendering accuracy tests { #Rendering-accuracy-tests}
There is a `Test` implementation, [SVGRenderingAccuracyTest](../javadoc/org/apache/batik/test/SVGRenderingAccuracyTest.html), 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.
@@ -239,9 +239,9 @@ In addition to this default behavior, th
Finally, to ease the process of creating âacceptedâ variation images, `SVGRenderingAccuracyTest` can take an optional file name (called `saveVariation`) describing where the variation between the rasterized SVG and the reference image will be stored in case the rasterized SVG is different from the reference image and the difference is not equal to the variation image, if any was defined. That way, it becomes possible to run a test, and if that test fails, the developer can review the `saveVariation` image and decide whether it is an acceptable variation or not and use it in subsequent test run as the âacceptedâ variation image, which will allow the test to pass if that exact same variation remains constant.
-### Day to day use of regard {#Day-to-day-use-of-regard}
+### Day to day use of regard { #Day-to-day-use-of-regard}
-#### Initial set up ## {#Initial-set-up}
+#### Initial set up ## { #Initial-set-up}
To set up the test environment the first time, you need to:
@@ -263,19 +263,19 @@ build regard
Check the newly generated HTML report in the `test-reports/html` directory: there should no longer be any test failure.
-#### Daily usage ## {#Daily-usage}
+#### Daily usage ## { #Daily-usage}
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.
-### SVG generator tests {#SVG-generator-tests}
+### SVG generator tests { #SVG-generator-tests}
Regard contains over 100 tests for checking regressions on the SVG generator. If you use `svggen` as an argument to regard, all the SVG generator tests will be run (because `regard.xml` points to `test-resources/org/apache/batik/svggen/regsvggen.xml`, which is a test suite description for the SVG generator and that fileâs root `testSuite` element has the âsvggenâ ID).
-## Writing new tests {#writingNewTests}
+## Writing new tests { #writingNewTests}
Writing a new test involves either configuring a new test or writing a new `Test` 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 `Test` implementation.
-### Adding a new test configuration {#Adding-a-new-test-configuration}
+### Adding a new test configuration { #Adding-a-new-test-configuration}
Imagine that you add a cool new test case to the `samples` directory, such as `linking-viewBox.svg`. In order to check for regressions on that file you can add the following entry:
@@ -295,7 +295,7 @@ Imagine that you add a cool new test cas
to the `test-resources/org/apache/batik/test/samplesRendering.xml` 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 `test-references/samples/tests`. 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.
-### Writing a new test {#Writing-a-new-test}
+### Writing a new test { #Writing-a-new-test}
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 `test-sources` directory, in `test-sources/org/apache/batik/bridge` in our example, and let's call it `ErrorHandlingTest`. To simplify the implementation of the `Test` interface, you can choose to derive from the `AbstractTest` class and generate a `DefaultTestReport`.
Modified: xmlgraphics/site/trunk/content/batik/download.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/batik/download.mdtext?rev=1613173&r1=1613172&r2=1613173&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/batik/download.mdtext (original)
+++ xmlgraphics/site/trunk/content/batik/download.mdtext Thu Jul 24 16:21:20 2014
@@ -3,7 +3,7 @@ Title: Apache(tm) Batik: Downloading A D
#Apache™ Batik: Downloading A Distribution
## Apache™ Batik: Downloading A Distribution
-### Binary or Source? {#dist-type}
+### Binary or Source? { #dist-type}
Most Apache™ Batik users will want to download the latest binary distribution, which is ready to run "out of the box." However, a source distribution will be preferable if you fall into one of the following categories:
@@ -14,11 +14,11 @@ Most Apache™ Batik users will want
- You wish to build a local copy of the API documentation (javadocs).
-### Binary Download {#binary}
+### Binary Download { #binary}
Binary distributions include "-bin" in their names, and can be downloaded from a [Batik Distribution mirror](http://www.apache.org/dyn/closer.cgi/xmlgraphics/batik).
-### Source Download {#source}
+### Source Download { #source}
There are several ways to obtain a source distribution. Please note that they are listed from least current to most current:
@@ -44,6 +44,6 @@ There are several ways to obtain a sourc
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.
-### Archive Download {#archives}
+### Archive Download { #archives}
Batik Archive distributions are linked from the upper portion of the Apache Batik Download Mirror Page and can be downloaded from the Batik Archives [binaries](http://archive.apache.org/dist/xmlgraphics/batik/) links.
Modified: xmlgraphics/site/trunk/content/batik/faq.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/batik/faq.mdtext?rev=1613173&r1=1613172&r2=1613173&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/batik/faq.mdtext (original)
+++ xmlgraphics/site/trunk/content/batik/faq.mdtext Thu Jul 24 16:21:20 2014
@@ -3,15 +3,15 @@ Title: Frequently Asked Questions
#Frequently Asked Questions
-## Questions {#Questions}
+## Questions { #Questions}
-### 1. General questions {#part-general}
+### 1. General questions { #part-general}
-#### 1.1. What is Batik? ## {#what-is-batik}
+#### 1.1. What is Batik? ## { #what-is-batik}
Batik is a Java-based toolkit for applications or applets that want to use images in the [Scalable Vector Graphics (SVG)](http://www.w3.org/TR/SVG11/) format for various purposes, such as display, generation or manipulation.
-#### 1.2. What is SVG? ## {#what-is-svg}
+#### 1.2. What is SVG? ## { #what-is-svg}
[SVG](http://www.w3.org/TR/SVG11/) (Scalable Vector Graphics) is an open-standard language for describing two-dimensional (2D) graphics in XML. It is a Recommendation from the [W3C](http://www.w3.org/). SVG lets you describe rich images with features such as gradients, transparency, filter effects and animation.
@@ -21,7 +21,7 @@ In addition, SVG images can be dynamic a
SVG graphical elements can be animated through scripting. Alternatively, animation sequences can be expressed directly in XML because SVG leverages the [SMIL Animation](http://www.w3.org/TR/smil-animation) specification for multimedia, another [W3C](http://www.w3.org/) specification.
-#### 1.3. What can I do with Batik? ## {#what-can-i-do}
+#### 1.3. What can I do with Batik? ## { #what-can-i-do}
Batik contains several [core modules](using/architecture.html) which can be used independently or jointly to **generate SVG content** (see the [SVG Generator](using/svg-generator.html) and [SVG DOM](using/dom-api.html) implementation documentation) **view SVG content** (see the [JSVGCanvas](using/swing.html)) or **convert to and from the SVG format** (see the [SVG Transcoder](using/transcoder.html) page).
@@ -39,15 +39,15 @@ The [SVG Pretty Printer](tools/pretty-pr
These applications show that Batik can be used client side (the browser can be used on any client machine) and server side (the rasterizer can be used to serve SVG images to client machines that do not have SVG support).
-#### 1.4. Why do we have such a project at Apache? ## {#why-at-apache}
+#### 1.4. Why do we have such a project at Apache? ## { #why-at-apache}
The [mission of the Apache XML Graphics Project](http://xmlgraphics.apache.org/charter.html) is to promote the use of XML-based graphics by âproviding robust, full-featured, commercial-quality, and freely available software packages for the conversion of XML to graphical output and for related componentsâ. Batik as an open source implementation of a key format for todayâs and tomorrowâs web fits well in this mission.
-#### 1.5. How does Batik relate to other Apache projects? ## {#how-does-batik-relate}
+#### 1.5. How does Batik relate to other Apache projects? ## { #how-does-batik-relate}
Batik is used in [Cocoon](http://cocoon.apache.org/) for server side rasterization of SVG images. In addition, the Batik is used in the [FOP](http://xmlgraphics.apache.org/fop/) project to convert SVG images to PDF format.
-#### 1.6. How did it start? ## {#how-did-it-start}
+#### 1.6. How did it start? ## { #how-did-it-start}
Batik started out because several teams doing SVG related projects decided to join efforts with the idea that the whole will be greater than the sum of the parts. The following companies or institutions are part of the team that contributed and/or created the initial Batik project, during the fall of 2000:
@@ -66,7 +66,7 @@ In addition, the Batik project is suppor
We encourage anyone to participate. As with all ASF projects, all efforts are volunteer-based. We are looking for individuals to work with us on fulfilling our goals for Batik in the spirit of collaborative open-source software development.
-#### 1.7. Where is Batik going? What is next? ## {#what-is-next}
+#### 1.7. Where is Batik going? What is next? ## { #what-is-next}
The SVG implementation is not complete (see the current [status](status.html)), and there is more work to do to achieve a fully functional viewer.
@@ -74,7 +74,7 @@ Batik 1.1 supports all static SVG featur
The type of applications (e.g., transcoding applications) that can or will be added to Batik depends on contributions and feedback.
-#### 1.8. How can I create and author SVG content? ## {#how-can-i-create-svg}
+#### 1.8. How can I create and author SVG content? ## { #how-can-i-create-svg}
Well, you can always use a plain text editor such as vi or xemacs, but there are many graphic authoring packages that can export SVG documents and that will let you author SVG content visually.
@@ -91,25 +91,25 @@ The following URLs will be useful to lea
- [SVG Generator](using/svg-generator.html)
-#### 1.9. What other SVG products are out there? ## {#what-other-svg-products-exist}
+#### 1.9. What other SVG products are out there? ## { #what-other-svg-products-exist}
There are many companies supporting SVG and you will find a list of available implementations on the [W3Câs SVG implementation page](http://www.w3.org/Graphics/SVG/SVG-Implementations).
-#### 1.10. Where can I find the SVG specification? ## {#svg-spec}
+#### 1.10. Where can I find the SVG specification? ## { #svg-spec}
The [SVG specification](http://www.w3.org/TR/SVG11/) is available from the [W3C web site](http://www.w3.org/).
-#### 1.11. How much of SVG does Batik implement? ## {#how-much-does-batik-implement}
+#### 1.11. How much of SVG does Batik implement? ## { #how-much-does-batik-implement}
The [status page](status.html) shows how much of the SVG specification Batik implements by showing which of the tests in the [SVG Basic Effectivity test suite](status.html#beSuiteStatus) Batik successfully passes.
-#### 1.12. What are the benefits of SVG being an XML grammar? ## {#benefits-of-svg-being-xml}
+#### 1.12. What are the benefits of SVG being an XML grammar? ## { #benefits-of-svg-being-xml}
Being an XML grammar means SVG can leverage work done around XML, and SVG actually leverages other grammars such as [XLink](http://www.w3.org/TR/2001/REC-xlink-20010627/), for linking and [SMIL](http://www.w3.org/TR/2001/REC-smil-animation-20010904/#AnimationFramework) for the animation.
Beyond the use and mix with other XML syntaxes, being an XML grammar lets SVG benefit from the plethora of XML tools that make it so easy to manipulate, generate, search and edit XML files.
-#### 1.13. Where does the name come from? ## {#what-is-in-a-name}
+#### 1.13. Where does the name come from? ## { #what-is-in-a-name}
Batik is a highly evolved art tradition that developed in Java (one of the islands comprising what is now called Indonesia). Batik is generally thought of as the quintessentially Indonesian textile. Motifs of flowers, twining plants, leaves, buds, birds, butterflies, fish, insects and geometric forms are rich in symbolic association and variety; there are about three thousand recorded batik patterns.
@@ -117,13 +117,13 @@ We think that Batik gracefully evokes Ja
[This page](http://www.expat.or.id/info/batik.html) shows examples of what Batik textures look like.
-### 2. Getting started with Apache Batik/SVG {#batik-help}
+### 2. Getting started with Apache Batik/SVG { #batik-help}
-#### 2.1. What are the system requirements to run Batik? ## {#system-requirements}
+#### 2.1. What are the system requirements to run Batik? ## { #system-requirements}
Batik is written in the Java language and requires a version 1.4 implementation at this time.
-#### 2.2. How do I install Batik? ## {#how-to-install}
+#### 2.2. How do I install Batik? ## { #how-to-install}
You will need a [JRE/JDK](http://java.sun.com/) version 1.4 or above to run Batik.
@@ -131,11 +131,11 @@ To install Batik you need to [download](
You can have a look at the [installation instructions](install.html) for more information.
-#### 2.3. How can I see a demo? ## {#how-can-i-see-demo}
+#### 2.3. How can I see a demo? ## { #how-can-i-see-demo}
You can see an online demonstration of Squiggle the SVG browser on the [demo page](demo.html). Alternatively, you can [download](/batik/download.html) Batik or see [screenshots](tools/browser.html) of the Batik SVG viewer, images created from the [rasterizer](tools/rasterizer.html) and an [example](using/svg-generator.html) of how to use the `SVGGraphics2D` generator.
-#### 2.4. What scripting languages can I use in my SVG files? ## {#what-scripting-languages-batik-supports}
+#### 2.4. What scripting languages can I use in my SVG files? ## { #what-scripting-languages-batik-supports}
A limited support of scripting in SVG files is provided with the current version of Batik (script are executed but dynamic update is not supported).
@@ -150,13 +150,13 @@ Batik can recognize the following script
To get more information on how to install optional scripting languages you can have a look at the [installation instructions](install.html).
-### 3. Troubleshooting Apache Batik {#batik-error}
+### 3. Troubleshooting Apache Batik { #batik-error}
-#### 3.1. When I try to run Batik it results in a NoSuchMethodException. What is the problem? ## {#NoSuchMethodException}
+#### 3.1. When I try to run Batik it results in a NoSuchMethodException. What is the problem? ## { #NoSuchMethodException}
There is certainly something wrong with your classpath. Clear your `CLASSPATH` environment variable and be sure to remove all the libraries which use the W3Câs DOM bindings from `jre/lib/ext` before running any of the Batikâs applications.
-#### 3.2. When I change the document in Java it doesnât update the display, even if I call repaint? ## {#display-does-not-update}
+#### 3.2. When I change the document in Java it doesnât update the display, even if I call repaint? ## { #display-does-not-update}
There are two common causes for this. The first is that the [JSVGCanvas](javadoc/org/apache/batik/swing/JSVGCanvas.html) doesnât know itâs a dynamic document. Normally Batik detects this by looking for script elements but when you modify the document from Java it canât tell. So call
myJSVGCanvas.setDocumentState(JSVGCanvas.ALWAYS_DYNAMIC);
@@ -167,11 +167,11 @@ UpdateManager um = JSVGCanvas.getUpdateM
um.getUpdateRunnableQueue().invokeLater(Runnable);
**NOTE:** The update manager only becomes available after the first rendering completes. You can be notified when this happens by registering a `GVTTreeRendererListener`.
-#### 3.3. When I change the document in Java it only updates if I move the mouse over the canvas? ## {#must-mouseover-to-change}
+#### 3.3. When I change the document in Java it only updates if I move the mouse over the canvas? ## { #must-mouseover-to-change}
The most common causes for this, is that the changes are not made in the `UpdateManager` âs thread. See previous FAQ for example code to run code in the Update Managerâs thread. Moving the mouse works because it delivers the mouse move events in the update thread, and after a runnable completes in the `UpdateManager` âs thread it checks if the canvas needs repainting.
-#### 3.4. When I create new SVG elements or modify some SVG attributes through the DOM API, from ECMAScript, nothing happens, the changes are not rendered. Why not? ## {#changes-are-not-rendered}
+#### 3.4. When I create new SVG elements or modify some SVG attributes through the DOM API, from ECMAScript, nothing happens, the changes are not rendered. Why not? ## { #changes-are-not-rendered}
A common problem is that script contain the wrong DOM calls to create elements or modify attributes.
@@ -193,29 +193,29 @@ where `xlinkNS` is equal to `"http://www
For more information on common authoring pitfalls, see Jonathan Wattâs [SVG Authoring Guidelines](http://jwatt.org/svg/authoring/).
-#### 3.5. When I get the UpdateManager from the canvas sometimes it is null, why? ## {#null-updatemanager}
+#### 3.5. When I get the UpdateManager from the canvas sometimes it is null, why? ## { #null-updatemanager}
The `JSVGCanvas` is highly asynchronous so when you call `setURI`, `setDocument` or `setSVGDocument` they return essentially immediately. Behind the scenes, the canvas creates the rendering tree and does a first rendering after dispatching the document `SVGLoad` event. Only after this first rendering does the `UpdateManger` become available.
-#### 3.6. Why do I have to go through the UpdateManager to run my code? Canât you just synchronize the DOM? ## {#why-updatemanager}
+#### 3.6. Why do I have to go through the UpdateManager to run my code? Canât you just synchronize the DOM? ## { #why-updatemanager}
It would be possible to synchronize individual calls to the DOM, however in general this is almost useless for the way DOM works. For example creating a single rectangle element takes approximately 6 individual DOM calls. So higher level synchronization is needed.
The use of a [Runnable](http://java.sun.com/j2se/1.5.0/docs/api/java/lang/Runnable.html) is a common way of accomplishing synchronization for a block of code. This is essentially the approach that Swing takes (all Swing modification should take place in the Swing thread). It was considered to use the Swing event thread, but this would lock the user interface while scripts were working.
-#### 3.7. I can use the Batik extension tags with the source distribution but not with the binary distribution. What am I missing? ## {#extension-tags-work-with-source-not-binary}
+#### 3.7. I can use the Batik extension tags with the source distribution but not with the binary distribution. What am I missing? ## { #extension-tags-work-with-source-not-binary}
When running from the source distribution you automatically get the service provider entries for the Batik extension elements (such as `regularPolygon` and `star`). We chose not to include these by default in the binary distribution for the Batik applications.
There is a subdirectory called `extensions` that has jar files that enable the extended elements from Batik.
-#### 3.8. Why do I get red circles when I view the samples/extensions files? ## {#red-circles}
+#### 3.8. Why do I get red circles when I view the samples/extensions files? ## { #red-circles}
You are using the binary distribution. This distribution does not include support for our example extensions (they are just examples and other people can do more sophisticated things).
If you want to view these examples you need to use the extension enabled versions of the applications in the `extensions` subdirectory.
-#### 3.9. I am modifying the DOM after displaying it in the JSVGCanvas, but my changes arenât shown (even if I call repaint). ## {#dom-modifications-do-not-display}
+#### 3.9. I am modifying the DOM after displaying it in the JSVGCanvas, but my changes arenât shown (even if I call repaint). ## { #dom-modifications-do-not-display}
For efficiency, if Batik loads a static document it doesnât set up any dynamic support. Batik normally decides whether a document is dynamic by checking if it contains any `script` elements or event handler attributes. However, if your Java application is modifying the DOM directly there may be no script elements. In this case you need to tell Batik to set up dynamic support regardless.
@@ -226,17 +226,17 @@ You can inform the `JSVGCanvas` that a d
myCanvas.setDocumentState(JSVGCanvas.ALWAYS_DYNAMIC);
myCanvas.setURI("myFile.svg");
-### 3.10. I am trying to use Batik and FOP together but Batik does not work and fails on the org.w3c.* packages. What is happening? ## {#batik-fails-with-fop-on-org.w3c.xxx}
+### 3.10. I am trying to use Batik and FOP together but Batik does not work and fails on the org.w3c.* packages. What is happening? ## { #batik-fails-with-fop-on-org.w3c.xxx}
Both FOP and Batik use the `org.w3c.` * packages. Depending on the version of FOP and Batik, Batik has been using a version of these packages which is more recent than the one in the `xml-apis.jar` file FOP uses. However, if the `xml-apis.jar` file that comes with the FOP distribution is loaded before the Batik jar files, then the version coming with FOP takes precedence (i.e., that is the version the Java Virtual Machine loads). Because that version is incompatible with Batik, you encounter this problem.
The solution is to either repackage the `xml-apis.jar` file with the classes in the Batik distribution (you will need the Batik source distribution to do that), or you will need to make sure the Batik jars are loaded before FOPâs `xml-apis.jar`, for example by putting Batikâs jar file before FOPâs in your classpath. If you are copying your jar files to `.../jre/lib/ext`, you can simply remove the FOP `xml-apis.jar` file from that directory.
-#### 3.11. How do I checkout the latest SVN version of Batik? ## {#how-to-checkout-latest-batik-via-svn}
+#### 3.11. How do I checkout the latest SVN version of Batik? ## { #how-to-checkout-latest-batik-via-svn}
You just have to follow the instructions on the [download page](/batik/download.html).
-#### 3.12. Iâm using Mac OS X, and some of the SVG files I view are messed up (things appear clipped or out of place). What do I need to do to fix this? ## {#mac-os-x-messed-up-svg-files}
+#### 3.12. Iâm using Mac OS X, and some of the SVG files I view are messed up (things appear clipped or out of place). What do I need to do to fix this? ## { #mac-os-x-messed-up-svg-files}
As of Mac OS X release 10.1.1 there still appears to be problems in the Apple implementation of the Java 2D APIs. The true source of these problems and/or workarounds have yet to be identified (although the problems appear to be closely tied to a âgstack underflowâ error message from the Apple JVM). We are interested in finding the source of these problems and reasonable workarounds, so if you know what causes these errors the Batik team would be very interested in hearing from you (either directly or through the user/developer mailing lists).
@@ -244,7 +244,7 @@ Other things to be aware of on Mac OS X,
Finally a few hints on avoiding problems under Mac OS X. The bugs seems to be triggered by filters, and pure raster SVG documents have not been found to cause problems. The use of the `filterRes` attribute on the `filter` element seems especially problematic. The bug isnât 100% reproducible, so while some content exhibits the problem, if you play with the document enough it will often âfixâ itself for a while, then later it will go back to being broken (which indicates that the problem may be some sort of race condition in the JVM).
-#### 3.13. I cannot run the Batik demo on Mac OS X (10.1.1). The Batik splash screen hangs. What is happening? ## {#mac-os-x-batik-demo-crash}
+#### 3.13. I cannot run the Batik demo on Mac OS X (10.1.1). The Batik splash screen hangs. What is happening? ## { #mac-os-x-batik-demo-crash}
The Batik [demo](demo.html) uses Java Web Start. Java Web Start (under the `Applications/Utilities` folder), lets you start a Java application from a web browser. You can see the debug traces by enabling the Java console for Java Web Start. If you do, you will see that there is a `java.lang.NoSuchMethodError` exception thrown.
@@ -253,9 +253,9 @@ This is happening because the Java Web S
One work around is to manually patch the `javaws.jar` file to remove the DOM bindings so that they do not take precedence over the Batik ones.
-### 4. How do I contribute to Batik Development? {#batik-dev}
+### 4. How do I contribute to Batik Development? { #batik-dev}
-#### 4.1. How can I contribute to Apache Batik development? ## {#how-can-i-contribute}
+#### 4.1. How can I contribute to Apache Batik development? ## { #how-can-i-contribute}
The Batik Project is an open volunteer project in the spirit of the [Apache Software Foundation](http://www.apache.org) (ASF). This means that there are many ways to contribute to the project, either with direct participation (coding, documenting, answering questions, proposing ideas, reporting bugs, suggesting bug-fixes, etc.) or by resource donation (publicity, hardware, software, conference presentations, speeches, etc.). Applications that use the Batik modules, such as tools or extensions, are of special interest to the project.
@@ -263,6 +263,6 @@ The process for contributing to Batik is
For direct participation, we suggest that you subscribe to the [Batik mailing lists](mailing-lists.html) and to checkout the [latest code](http://svn.apache.org/viewcvs.cgi/xmlgraphics/batik/).
-#### 4.2. How do I submit patches or bug fixes? ## {#submit-patches}
+#### 4.2. How do I submit patches or bug fixes? ## { #submit-patches}
You can submit bug fixes and patches to the [Batik developers](mailto:batik-dev@xmlgraphics.apache.org) mailing list and you can enter bugs in [Bugzilla](http://issues.apache.org/bugzilla/buglist.cgi?query_format=specific&bug_status=__open__&product=Batik).
\ No newline at end of file
Modified: xmlgraphics/site/trunk/content/batik/index.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/batik/index.mdtext?rev=1613173&r1=1613172&r2=1613173&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/batik/index.mdtext (original)
+++ xmlgraphics/site/trunk/content/batik/index.mdtext Thu Jul 24 16:21:20 2014
@@ -3,13 +3,13 @@ Title: Apache(tm) Batik SVG Toolkit - a
#Apache™ Batik SVG Toolkit
-## Overview {#overview}
+## Overview { #overview}
Batik is a Java-based toolkit for applications or applets that want to use images in the [Scalable Vector Graphics (SVG)](http://www.w3.org/TR/SVG11/) format for various purposes, such as display, generation or manipulation.
The projectâs ambition is to give developers a set of [core modules](using/architecture.html#coreComponents) that can be used together or individually to support specific SVG solutions. Examples of [modules](using/index.html) are the [SVG Parser](using/parsers.html), the [SVG Generator](using/svg-generator.html) and the [SVG DOM](using/dom-api.html). Another ambition for the Batik project is to make it highly [extensible](using/extending.html) âfor example, Batik allows the developer to handle custom SVG elements. Even though the goal of the project is to provide a set of core modules, one of the deliverables is a full fledged [SVG browser](tools/browser.html) implementation which validates the various modules and their inter-operability.
-## What Batik can be used for {#uses}
+## What Batik can be used for { #uses}
@@ -47,7 +47,7 @@ The Batik toolkit includes the following
See [examples of projects and products using Batik](uses.html) for real-life example of how Batik is already integrated in projects and products.
-## The SVG specification {#spec}
+## The SVG specification { #spec}
Scalable Vector Graphics, SVG, is a [W3C](http://www.w3.org/) Recommendation. It defines an XML grammar for rich 2D graphics which includes features such as transparency, arbitrary geometry, filter effects (shadows, lighting effects, etc.), scripting and animation.
@@ -57,13 +57,13 @@ This specification defines the features
SVG documents can be interactive and dynamic. Animations can be defined and triggered either declaratively (i.e., by embedding SVG animation elements in SVG content) or via scripting.
-## Implementation status {#status}
+## Implementation status { #status}
The latest revision of Batik, release 1.7, is a conformant [static SVG implementation](http://www.w3.org/TR/SVG11/conform.html#ConformingSVGViewers) and supports [interactivity](http://www.w3.org/TR/SVG11/interact.html), [linking](http://www.w3.org/TR/SVG11/linking.html) and [scripting](http://www.w3.org/TR/SVG11/script.html) features of the SVG specification. This release supports a nearly complete implementation of declarative [animation](http://www.w3.org/TR/SVG11/animate.html), too.
See the [status](status.html) page for a detailed description of the set of SVG features Batik supports.
-## Download Batik {#download}
+## Download Batik { #download}
You can get the Batik distribution, source and binary, from the [download page](download.cgi).
All other libraries needed by Batik are included in the distribution. As a consequence the Batik archive is quite big, but after you have downloaded it, you will not need anything else.<warning id="SecurityWarning" label="Security warning">
Modified: xmlgraphics/site/trunk/content/batik/install.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/batik/install.mdtext?rev=1613173&r1=1613172&r2=1613173&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/batik/install.mdtext (original)
+++ xmlgraphics/site/trunk/content/batik/install.mdtext Thu Jul 24 16:21:20 2014
@@ -3,7 +3,7 @@ Title: Installing Batik
#Installing Batik
-## System requirements {#systemRequirements}
+## System requirements { #systemRequirements}
Batik requires the following to be already installed in your system:
@@ -13,7 +13,7 @@ Java Runtime Environment
:
A Java 1.4 or above compatible runtime environment must be present.
-## Choosing a distribution to download {#distributions}
+## Choosing a distribution to download { #distributions}
To install Batik, you will need to go to the [download page](/batik/download.html) and download one or more ZIP file containing the distribution of your choice. It is good practice to [verify the integrity](#verify) of the distribution files, especially if you are using one of our mirror sites. Here are the various components you will find in the download area and their intended use:
@@ -85,7 +85,7 @@ After running this script, a Finder wind
- Now you can follow the instructions specific to the application you want to use. For example, see the [SVG Browser](tools/browser.html) page or the [SVG Rasterizer](tools/rasterizer.html) page for an explanation on how to use these tools.
-## Optional components {#optionalComponents}
+## Optional components { #optionalComponents}
By default, the Batik source distribution comes with the [Mozilla Rhino](http://www.mozilla.org/rhino/) JavaScript Engine (`js.jar`).
@@ -98,7 +98,7 @@ To enable other scripting languages supp
Conversely, you can remove the `js.jar` of the Batik `lib` directory to remove JavaScript support and have a smaller distribution.
-## Jar file dependency graph {#dependencyGraph}
+## Jar file dependency graph { #dependencyGraph}
<warning label="Out of date">
Note that the dependency graph in this section is out of date, and needs to be updated.
</warning>
@@ -110,7 +110,7 @@ When boxes touch, the box on top depends
<div class="figure">  </div>Some jar file names are shortened for clarity. All `batik` package references are short for `org.apache.batik`.
It is worth pointing out that a determined/clever programmer may be able to pare down some of these dependencies. For example the `batik-dom.jar` depends on `xerces.jar` because of the `SAXDocumentFactory` class in `org.apache.batik.dom.util`. If you didnât need to parse XML it would be possible to ignore or break this dependency and still use the `batik-dom.jar` file for its DOM implementation.
-## Verify releases {#verify}
+## Verify releases { #verify}
It is essential that you verify the integrity of the downloaded files using the PGP or MD5 signatures.
Modified: xmlgraphics/site/trunk/content/batik/mailing-lists.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/batik/mailing-lists.mdtext?rev=1613173&r1=1613172&r2=1613173&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/batik/mailing-lists.mdtext (original)
+++ xmlgraphics/site/trunk/content/batik/mailing-lists.mdtext Thu Jul 24 16:21:20 2014
@@ -12,7 +12,7 @@ Before posting a question or problem to
1. Batik development list archive (check links below)
-## Batik users list {#batik-users}
+## Batik users list { #batik-users}
`batik-users@xmlgraphics.apache.org`
@@ -29,7 +29,7 @@ This is the general Batik list, for prob
**Important:** If you are posting about a problem you are having (as most people do), please provide details about the system configuration (operating system, JDK version, window manager, etc.), and detailed information about the problem such as any available stack trace or, ideally, a test case that isolates the problem. This will help get a quick resolution.
-## Batik development list {#batik-dev}
+## Batik development list { #batik-dev}
`batik-dev@xmlgraphics.apache.org`
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: commits-help@xmlgraphics.apache.org