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/10/24 06:26:12 UTC
svn commit: r835978 [2/16] - 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/
Modified: websites/staging/xmlgraphics/trunk/content/batik/tools/rasterizer.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/batik/tools/rasterizer.html (original)
+++ websites/staging/xmlgraphics/trunk/content/batik/tools/rasterizer.html Wed Oct 24 04:26:06 2012
@@ -161,11 +161,11 @@ $(document).ready(function () {
<!-- <div id="breadcrumb"><a href="/">Home</a> » <a href="/batik/">Batik</a> » <a href="/batik/tools/">Tools</a></div> -->
<div class="section-content"><h1 id="svg-rasterizer">SVG Rasterizer</h1>
<p>This page describes the features of the SVG Rasterizer utility that comes with the Batik distribution. The SVG Rasterizer is a utility that can convert SVG files to a raster format. The tool can convert individual files or sets of files, making it easy to convert entire directories of SVG files. The provided formats are<abbr title="Joint Photography Expert Group">JPEG</abbr>,<abbr title="Portable Network Graphics">PNG</abbr>and<abbr title="Tagged Image File Format">TIFF</abbr>, however the design allows new formats to be added easily. In addition, the rasterizer can (despite its name) transcode to<abbr title="Portable Document Format">PDF</abbr>.</p>
-<h2 id="downloading-the-rasterizer-wzxhzdk9wzxhzdk10">Downloading the rasterizer <a id="downloading"></a></h2>
+<h2 id="downloading-the-rasterizer-wzxhzdk9wzxhzdk10">Downloading the rasterizer <a id="downloading"></a></h2>
<p>Refer to the <a href="../install.html">install page</a> and the <a href="../download.cgi">download area</a> to find out what to download and how to install it. Remember that you can get either the source or binary distribution.</p>
-<h2 id="rasterizing-one-or-several-svg-files-wzxhzdk11wzxhzdk12">Rasterizing one or several SVG files <a id="using"></a></h2>
+<h2 id="rasterizing-one-or-several-svg-files-wzxhzdk11wzxhzdk12">Rasterizing one or several SVG files <a id="using"></a></h2>
<p>The method for starting the rasterizer depends on the distribution of Batik that you chose to download. The following describes how to start the viewer for each distribution.</p>
-<h3 id="using-the-binary-distribution-wzxhzdk13wzxhzdk14">Using the binary distribution # <a id="using-binary"></a></h3>
+<h3 id="using-the-binary-distribution-wzxhzdk13wzxhzdk14">Using the binary distribution <a id="using-binary"></a></h3>
<p>If you downloaded the binary distribution of Batik, you should have a file called <code>batik-1.6.zip</code> (or similar), and, after expanding that file, a jar file called <code>batik-rasterizer.jar</code> . To start the rasterizer, open a console, go to the directory where you expanded the distribution (and where <code>batik-rasterizer.jar</code> is located) and simply type the following at the command prompt:
java -jar batik-rasterizer.jar FILES
For example, if you type:
@@ -225,7 +225,7 @@ where, as options:</p>
<p>For example:
java -jar batik-rasterizer.jar -d myDir -m image/jpeg samples/*.svg
will generate JPEG images for all the SVG files found in the samples directory.</p>
-<h3 id="using-the-source-distribution-wzxhzdk15wzxhzdk16">Using the source distribution # <a id="usingSource"></a></h3>
+<h3 id="using-the-source-distribution-wzxhzdk15wzxhzdk16">Using the source distribution <a id="usingSource"></a></h3>
<p>If you downloaded the source distribution of Batik, you got a zip or tar file that expanded into a directory called <code>xml-batik</code> or<code>batik- <em>version</em> </code>. In that directory, you can find build scripts for the platform you are running on. For example, there is a <code>build.bat</code> script for users of the Windows platform and there is a <code>build.sh</code> script for UNIX users.</p>
<p>To start the rasterizer you should:</p>
<ul>
@@ -248,17 +248,17 @@ build svgrasterizer [OPTIONS] FILES
and for Unix:
./build.sh svgrasterizer [OPTIONS] FILES
Refer to <a href="#using-binary">âUsing the binary distributionâ</a> for an explanation of the options.</p>
-<h2 id="rasterizer-ant-task-wzxhzdk19wzxhzdk20">Rasterizer Ant task <a id="task"></a></h2>
+<h2 id="rasterizer-ant-task-wzxhzdk19wzxhzdk20">Rasterizer Ant task <a id="task"></a></h2>
<p>The Rasterizer task is an <a href="http://ant.apache.org/">Ant</a> version of the rasterizer utility. It fulfills the same basic purpose as the utility but has a different syntax and a slightly different set of features.</p>
<p>The task is able to produce four raster formats:<abbr title="Portable Network Graphics">PNG</abbr>,<abbr title="Joint Photographic Expert Group">JPEG</abbr>,<abbr title="Tagged Image File Format">TIFF</abbr>and<abbr title="Portable Document Format">PDF</abbr>.</p>
-<h3 id="using-the-rasterizer-task-wzxhzdk29wzxhzdk30">Using the rasterizer task # <a id="initTask"></a></h3>
+<h3 id="using-the-rasterizer-task-wzxhzdk29wzxhzdk30">Using the rasterizer task <a id="initTask"></a></h3>
<p>The first thing to do is to compile rasterizer task classes. Download the source distribution of Batik and see the <code>README</code> file in the <code>contrib/rasterizertask</code> directory for more instructions. The build procedure works the same way as when building Batik itself.</p>
<p>After building, ensure that the generated <code>batik-rasterizer.jar</code> and the classes (or jar file) of the rasterizer task are in your <code>CLASSPATH</code> .</p>
<p>Next you have to define the task in your Ant project. To do this, add the following line either after the <code>project</code> start tag or after the <code>target</code> start tag in the target you are using the rasterizer task:
<taskdef name="rasterize"
classname="org.apache.tools.ant.taskdefs.optional.RasterizerTask"/>
Now you can use the rasterizer task in your project. See the <a href="#taskParameters">parameters section</a> for an explanation of the available parameters or the <a href="#taskExamples">examples section</a> to see few usage examples.</p>
-<h3 id="parameters-of-the-ant-task-wzxhzdk32wzxhzdk33">Parameters of the Ant task # <a id="taskParameters"></a></h3>
+<h3 id="parameters-of-the-ant-task-wzxhzdk32wzxhzdk33">Parameters of the Ant task <a id="taskParameters"></a></h3>
<p>The following table lists the attributes that may be specified on the <code>rasterize</code> task element.</p>
<table>
<thead>
@@ -352,7 +352,7 @@ Now you can use the rasterizer task in y
</tbody>
</table>
<p>You can use <code>fileset</code> elements to select input files and directories. See the <a href="http://ant.apache.org/">Ant</a> documentation to learn how to use <a href="http://ant.apache.org/manual/CoreTypes/fileset.html">filesets</a> .</p>
-<h3 id="examples-of-using-the-rasterizer-task-wzxhzdk34wzxhzdk35">Examples of using the rasterizer task # <a id="taskExamples"></a></h3>
+<h3 id="examples-of-using-the-rasterizer-task-wzxhzdk34wzxhzdk35">Examples of using the rasterizer task <a id="taskExamples"></a></h3>
<p>The following example is the complete Ant project that converts an SVG image (called <code>input.svg</code> ) to a PNG image (called <code>output.png</code> ):
<?xml version="1.0"?></p>
<project name="RasterizerExample" default="main" basedir=".">
Modified: websites/staging/xmlgraphics/trunk/content/batik/uses.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/batik/uses.html (original)
+++ websites/staging/xmlgraphics/trunk/content/batik/uses.html Wed Oct 24 04:26:06 2012
@@ -163,12 +163,12 @@ $(document).ready(function () {
<div class="toc">
<ul>
<li><a href="#projects-using-batik">Projects using Batik</a><ul>
-<li><a href="#examples-of-projects-and-products-using-batik-wzxhzdk0wzxhzdk1">Examples of projects and products using Batik <a id="Examples+of+projects+and+products+using+Batik"></a></a></li>
+<li><a href="#examples-of-projects-and-products-using-batik-wzxhzdk0wzxhzdk1">Examples of projects and products using Batik <a id="Examples+of+projects+and+products+using+Batik"></a></a></li>
</ul>
</li>
</ul>
</div>
-<h2 id="examples-of-projects-and-products-using-batik-wzxhzdk0wzxhzdk1">Examples of projects and products using Batik <a id="Examples+of+projects+and+products+using+Batik"></a></h2>
+<h2 id="examples-of-projects-and-products-using-batik-wzxhzdk0wzxhzdk1">Examples of projects and products using Batik <a id="Examples+of+projects+and+products+using+Batik"></a></h2>
<p>While it is hard to track projects and products which are using Batik, here are a few that are known of:</p>
<ul>
<li>
Modified: websites/staging/xmlgraphics/trunk/content/batik/using/architecture.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/batik/using/architecture.html (original)
+++ websites/staging/xmlgraphics/trunk/content/batik/using/architecture.html Wed Oct 24 04:26:06 2012
@@ -166,14 +166,14 @@ $(document).ready(function () {
<a href="#applicationComponents">Application modules</a> illustrate how to use the core modules and let users evaluate the Batik software by experimenting with its features.</p>
<p>The <a href="#coreComponents">Core modules</a> are the heart of Batik and the primary deliverables for the projects. These are the modules developers use to manipulate, generate, create, convert, render and view SVG content.</p>
<p>Finally, the <a href="#lowLevelComponents">Low level modules</a> are used internally by the core modules to accomplish their work. These modules are not typically used by developers directly.</p>
-<h2 id="application-modules-wzxhzdk2wzxhzdk3">Application modules <a id="applicationComponents"></a></h2>
+<h2 id="application-modules-wzxhzdk2wzxhzdk3">Application modules <a id="applicationComponents"></a></h2>
<p>As mentioned earlier, the application modules illustrate the functionality that Batik offers.</p>
<p>For example, the <a href="../tools/browser.html">SVG browser</a> is built using several Batik core modules (such as the <code>JSVGCanvas</code> GUI component and the <code>ImageTranscoder</code> s) and illustrates how Batik lets you not only view, zoom, pan and rotate SVG documents, but also search them and convert them to other formats (such as JPEG, TIFF or PNG).</p>
<p>The <a href="../tools/pretty-printer.html">SVG pretty printer</a> is another example that shows how Batik lets you manipulate and transform SVG content, here for the purposed of tidying up potentially disorganized SVG files.</p>
<p>The <a href="../tools/font-converter.html">SVG font converter</a> illustrates how Batik can help you embed SVG font definitions in an SVG file by providing an application that converts ranges of characters from a TrueType Font format to the SVG font format.</p>
<p>Finally, the <a href="../tools/rasterizer.html">SVG rasterizer</a> shows how to leverage the <a href="../using/transcoder.html">transcoder API</a> to convert to and from SVG content.</p>
<p>Note that even though the application modules are meant to be useful and fun to use, they are not the primary deliverables of the Batik project. Instead, they are illustrations of how the Batik core modules might be used and combined.</p>
-<h2 id="core-modules-wzxhzdk4wzxhzdk5">Core modules <a id="coreComponents"></a></h2>
+<h2 id="core-modules-wzxhzdk4wzxhzdk5">Core modules <a id="coreComponents"></a></h2>
<p>The Batik core modules are the heart of the Batik architecture. They can be used individually or in combination for various purposes, and the <a href="#applicationComponents">application modules</a> offer some usage examples.</p>
<ul>
<li>
@@ -192,7 +192,7 @@ $(document).ready(function () {
<p>The <a href="../using/transcoder.html">transcoder</a> is a module that provides a generic API for transcoding an input to an output. This module transcodes an input stream or a document into a particular ouput format, used for converting SVG documents to other types.</p>
</li>
</ul>
-<h2 id="low-level-modules-wzxhzdk6wzxhzdk7">Low level modules <a id="lowLevelComponents"></a></h2>
+<h2 id="low-level-modules-wzxhzdk6wzxhzdk7">Low level modules <a id="lowLevelComponents"></a></h2>
<p>The low level modules are not expected to be used directly by developers using the Batik API. Rather, they support the operation of the core modules. The low level modules include:</p>
<ul>
<li>
Modified: websites/staging/xmlgraphics/trunk/content/batik/using/dom-api.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/batik/using/dom-api.html (original)
+++ websites/staging/xmlgraphics/trunk/content/batik/using/dom-api.html Wed Oct 24 04:26:06 2012
@@ -161,14 +161,14 @@ $(document).ready(function () {
<!-- <div id="breadcrumb"><a href="/">Home</a> » <a href="/batik/">Batik</a> » <a href="/batik/using/">Using</a></div> -->
<div class="section-content"><h1 id="svg-dom-api">SVG DOM API</h1>
<p>The <a href="http://www.w3.org/dom/">Document Object Model</a> (DOM) is an API for XML documents. It defines the logical structure of documents and the way a document is accessed and manipulated. This page shows how to create an SVG document using the DOM API.</p>
-<h2 id="getting-started-wzxhzdk0wzxhzdk1">Getting started <a id="gettingStarted"></a></h2>
+<h2 id="getting-started-wzxhzdk0wzxhzdk1">Getting started <a id="gettingStarted"></a></h2>
<p>The DOM API defines an interface called <a href="http://java.sun.com/j2se/1.5.0/docs/api/org/w3c/dom/DOMImplementation.html">DOMImplementation</a> , which represents the bootstrap of any DOM implementation. The role of this class is to bootstrap a particular implementation of the DOM by providing a method to create a <a href="http://java.sun.com/j2se/1.5.0/docs/api/org/w3c/dom/Document.html">Document</a> . Then, the concrete <code>Document</code> represents an XML document and also acts like a factory for the various DOM objects such as <a href="http://java.sun.com/j2se/1.5.0/docs/api/org/w3c/dom/Element.html">Element</a> , <a href="http://java.sun.com/j2se/1.5.0/docs/api/org/w3c/dom/Attr.html">Attr</a> and <a href="http://java.sun.com/j2se/1.5.0/docs/api/org/w3c/dom/Text.html">Text</a> .</p>
<p>How to get an instance of the <code>DOMImplementation</code> interface depends on the DOM implementation you are using. In Batik, the DOM implementation is located in the package <code>org.apache.batik.dom.svg</code> and the class is named <a href="http://xmlgraphics.apache.org/batik/javadoc/org/apache/batik/dom/svg/SVGDOMImplementation.html">SVGDOMImplementation</a> . The following example shows how to get a concrete <code>DOMImplementation</code> object.
import org.w3c.dom.DOMImplementation;
import org.apache.batik.dom.svg.SVGDOMImplementation;</p>
<p>DOMImplementation impl = SVGDOMImplementation.getDOMImplementation();
Once you have an instance of a <code>DOMImplementation</code> , you are not relying on Batik-specific code any more and ready to use the DOM API.</p>
-<h2 id="creating-a-document-wzxhzdk2wzxhzdk3">Creating a Document <a id="creating"></a></h2>
+<h2 id="creating-a-document-wzxhzdk2wzxhzdk3">Creating a Document <a id="creating"></a></h2>
<p>Using the <code>DOMImplementation</code> , you are now able to create a <code>Document</code> . The following example illustrates how to create an SVG document. Note that the Batikâs DOM implementation can be used to represent either an SVG document fragment or any kind of XML document. Note that by choosing the namespace URI and the local name of the root element of SVG, we are creating an SVG document.
import org.apache.batik.dom.svg.SVGDOMImplementation;
import org.w3c.dom.Document;</p>
@@ -178,7 +178,7 @@ String svgNS = SVGDOMImplementation.SVG_
DOMImplementation impl = SVGDOMImplementation.getDOMImplementation();
Document doc = impl.createDocument(svgNS, "svg", null);
As we have created an SVG <code>Document</code> , we can cast this document to an <a href="../javadoc/org/w3c/dom/svg/SVGDocument.html">SVGDocument</a> (defined in the <code>org.w3c.dom.svg</code> package) if needed.</p>
-<h2 id="building-an-svg-document-wzxhzdk4wzxhzdk5">Building an SVG Document <a id="buildsvgdoc"></a></h2>
+<h2 id="building-an-svg-document-wzxhzdk4wzxhzdk5">Building an SVG Document <a id="buildsvgdoc"></a></h2>
<p>Finally, using the <code>Document</code> object, we are now able to construct SVG content. Note that the document created before supports both generic XML and SVG. Though the DOM implementation of Batik is an SVG DOM implementation, the SVG-specific methods that rely on the document having been rendered (particularly geometry related methods, such as <a href="../javadoc/org/w3c/dom/svg/SVGLocatable.html#getBBox()">SVGLocatable.getBBox</a> ) cannot be used at this point.</p>
<p>The document can be built using DOM Level 2 Core methods. The following example shows how to create a red rectangle located at (10, 20), with a size of (100, 50) placed in a (400, 450) SVG canvas:</p>
<p>import org.apache.batik.dom.svg.SVGDOMImplementation;
@@ -205,7 +205,7 @@ The example given constructs a document
<svg xmlns="http://www.w3.org/2000/svg" width="400" height="450">
<rect x="10" y="20" width="100" height="50" fill="red"/>
</svg></p>
-<h1 id="creating-a-document-from-an-svg-file-wzxhzdk9wzxhzdk10">Creating a Document from an SVG file <a id="createdocfromsvgfile"></a></h1>
+<h1 id="creating-a-document-from-an-svg-file-wzxhzdk9wzxhzdk10">Creating a Document from an SVG file <a id="createdocfromsvgfile"></a></h1>
<p>With Batik, you can also create an SVG DOM tree from a URI, an <a href="http://java.sun.com/j2se/1.5.0/docs/api/java/io/InputStream.html">InputStream</a> , or a <a href="http://java.sun.com/j2se/1.5.0/docs/api/java/io/Reader.html">Reader</a> , using the <a href="../javadoc/org/apache/batik/dom/util/SAXDocumentFactory.html">SAXSVGDocumentFactory</a> . The following example illustrates how to create an SVG document from a URI using the <code>SAXSVGDocumentFactory</code> class.
import java.io.IOException;</p>
<p>import org.apache.batik.dom.svg.SAXSVGDocumentFactory;
@@ -220,7 +220,7 @@ import org.apache.batik.util.XMLResource
// ...
}</p>
<p>As we have created an SVG <code>Document</code> , we can cast this document to an <code>SVGDocument</code> (defined in the <code>org.w3c.dom.svg</code> package) if needed.</p>
-<h2 id="rendering-an-svg-document-wzxhzdk11wzxhzdk12">Rendering an SVG Document <a id="rendering"></a></h2>
+<h2 id="rendering-an-svg-document-wzxhzdk11wzxhzdk12">Rendering an SVG Document <a id="rendering"></a></h2>
<p>Batik provides several ways to use an SVG DOM tree. Two modules can be immediately used to render your SVG document.</p>
<dl>
<dt>JSVGCanvas</dt>
Modified: websites/staging/xmlgraphics/trunk/content/batik/using/extending.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/batik/using/extending.html (original)
+++ websites/staging/xmlgraphics/trunk/content/batik/using/extending.html Wed Oct 24 04:26:06 2012
@@ -163,7 +163,7 @@ $(document).ready(function () {
<p>This page provides an overview of the built in extension mechanisms of Batik. As an open source project, people can of course make any extension they feel is interesting, however Batik has been designed with several forms of extension in mind.</p>
<p>In general, extensions are added through the Service Provider Interface mechanism as described in the <a href="http://java.sun.com/j2se/1.4/docs/guide/jar/jar.html#Service Provider">jar file documentation</a> . This allows for the extension of Batik simply by adding a new jar file(s) to the class path, and thus no modification of the Batik source is required!
If you feel that the Batik team has overlooked an important area for extension please let your feelings be known on the mailing lists.</p>
-<h1 id="custom-xml-elements-wzxhzdk0wzxhzdk1">Custom XML elements <a id="customXMLTags"></a></h1>
+<h1 id="custom-xml-elements-wzxhzdk0wzxhzdk1">Custom XML elements <a id="customXMLTags"></a></h1>
<p>First one must ask what it means to support custom XML elements? There are three basic options Batik considers:</p>
<dl>
<dt>Having your elements appear in the DOM tree</dt>
@@ -180,7 +180,7 @@ If you feel that the Batik team has over
<dd>Probably the most common reason to develop custom elements is to add new rendering primitives to the SVG language. In this case you must provide an <a href="#bridgeExtension">extension to the Batik bridge</a> . The bridge extension is resposible for constructing the class(es) that will handle the rendering of the new primitive in Batik.</dd>
</dl>
<p>In most cases it will also be necessary to write a DOM extension to make the element behave like other SVG elements (most notably for support of styling).</p>
-<h3 id="writing-a-batik-dom-extension-wzxhzdk2wzxhzdk3">Writing a Batik DOM extension # <a id="domExtension"></a></h3>
+<h3 id="writing-a-batik-dom-extension-wzxhzdk2wzxhzdk3">Writing a Batik DOM extension <a id="domExtension"></a></h3>
<p>The ability to extend the elements used in the SVG DOM tree allows users to provide implementations for nodes that can be used in place of Batikâs default implementation of a node. This may be done for a variety of reasons, but is most commonly done to extend the behavior of standard node calls (such as to include styling in attribute lookup), or to implement the DOM interface for an element.</p>
<p>The key class for building the DOM tree is <a href="../javadoc/org/apache/batik/dom/ExtensibleSVGDOMImplementation.html">org.apache.batik.dom.ExtensibleSVGDOMImplementation</a> . When an instance of this class is constructed it searches for instances of the <a href="../javadoc/org/apache/batik/dom/svg/DomExtension.html">org.apache.batik.dom.svg.DomExtension</a> Service Provider Interface. It then calls the <code>registerTags</code> method, passing itself as the only parameter. This method typically would typically call <code>registerCustomElementFactory</code> for each element that it wishes to handle.</p>
<p>With Batik the most likely reason to extend a node is to provide proper CSS styling of the node attributes. To this end Batik provides a class you can extend: <a href="../javadoc/org/apache/batik/extension/PrefixableStylableExtensionElement.html">org.apache.batik.extension.PrefixableStylableExtensionElement</a> . If you derive a new DOM class from this class you are only required to implement three methods: <code>getLocalName</code> , <code>getNamespaceURI</code> , and <code>newNode</code> (plus constructors). If all you want is proper style support (commonly the case) then you are done implementing your element at this point.</p>
@@ -204,7 +204,7 @@ If you feel that the Batik team has over
</ul>
<p>Included with these examples is <code>org.apache.batik.extension.svg.BatikDomExtension</code> , which is the required instance of <code>DomExtension</code> used to register the elements with the <code>ExtensibleSVGDOMImplementation</code> .</p>
<p>If your new element requires new âpresentation attributesâ (XML attributes that can be modified through CSS, or, depending on your viewpoint, the other way aroundâCSS properties that can be specified using XML attributes), you will also need to extend the CSS engine. This can be done by registering a custom CSS value factory. Both of the color examples do this (see <code>BatikDomExtension</code> ).</p>
-<h3 id="writing-a-batik-bridge-extension-wzxhzdk4wzxhzdk5">Writing a Batik bridge extension # <a id="bridgeExtension"></a></h3>
+<h3 id="writing-a-batik-bridge-extension-wzxhzdk4wzxhzdk5">Writing a Batik bridge extension <a id="bridgeExtension"></a></h3>
<p>Before you write a bridge extension it may be useful to understand what role the bridge package plays in Batik. The bridge package is responsible for creating and maintaining elements in the Graphics Vector Toolkit (GVT) tree based on the corresponding element in the SVG DOM. This is done because, for a variety of reasons, the SVG DOM is not well suited for rendering, thus the GVT tree is used for all rendering and transcoding operations.</p>
<p>The key class for managing this link is the <a href="../javadoc/org/apache/batik/bridge/BridgeContext.html">BridgeContext</a> . This class maintains an association between a element name with namespace and a particular bridge instance that will handle it. The work of constructing the proper entity or entities in the GVT tree is then deferred to the <a href="../javadoc/org/apache/batik/bridge/Bridge.html">Bridge</a> registered for a particular element. If no bridge is regiestered nothing is done.</p>
<p>New associations can be added by implementors of the <a href="../javadoc/org/apache/batik/bridge/BridgeExtension.html">BridgeExtension</a> Service Provider Interface. This interface has a number of methods that provide information about the particular extension being registered (including contact information, and the list of implemented extensions). It also has a <code>registerTags</code> method which is responsible for registering the bridge instances with a <code>BridgeContext</code> . All the built-in bridges are bundled together with a <code>BridgeExtension</code> (the <a href="../javadoc/org/apache/batik/bridge/SVGBridgeExtension.html">org.apache.batik.bridge.SVGBridgeExtension</a> class), as are the example extensions ( <a href="../javadoc/org/apache/batik/extension/svg/BatikBridgeExtension.html">org.apache.batik.extension.svg</a> ), so these are both good places to start.</p>
@@ -275,10 +275,10 @@ If you feel that the Batik team has over
<p>This is how gradients and patterns are implemented in Batik, so it is possible to construct rather complex paint effects through this mechanism.</p>
<p>For paints you are mostly on your own, because unlike the other cases there arenât any really generally useful base classes to derive off, the closest is the <a href="../javadoc/org/apache/batik/bridge/AbstractSVGGradientElementBridge.html">AbstractSVGGradientElementBridge</a> , which is used to handle most of the radial and linear gradient attributes.</p>
<p>The existing gradient paint implementations are in the <code>org.apache.batik.ext.awt</code> , and the pattern implementation is in <code>org.apache.batik.gvt</code> since it requires access to GVT internals.</p>
-<h2 id="new-image-file-formats-wzxhzdk12wzxhzdk13">New image file formats <a id="imageTagFormats"></a></h2>
+<h2 id="new-image-file-formats-wzxhzdk12wzxhzdk13">New image file formats <a id="imageTagFormats"></a></h2>
<p>When Batik encounters an <code>image</code> element and it determines the element does not reference an SVG file, it defers the loading of the referenced image to <a href="../javadoc/org/apache/batik/ext/awt/image/spi/ImageTagRegistry.html">org.apache.batik.ext.awt.image.spi.ImageTagRegistry</a> . This class maintains a list of <a href="../javadoc/org/apache/batik/ext/awt/image/spi/RegistryEntry.html">RegistryEntry</a> s, generally one for each format.</p>
<p>Since the formats supported natively by Batik are also implemented through this mechanism. The <a href="../javadoc/org/apache/batik/ext/awt/image/codec/jpeg/JPEGRegistryEntry.html">JPEGRegistryEntry</a> and <a href="../javadoc/org/apache/batik/ext/awt/image/codec/png/PNGRegistryEntry.html">PNGRegistryEntry</a> classes should be used as good references for extensions.</p>
-<h3 id="registryentry-wzxhzdk14wzxhzdk15">RegistryEntry # <a id="RegistryEntry"></a></h3>
+<h3 id="registryentry-wzxhzdk14wzxhzdk15">RegistryEntry <a id="RegistryEntry"></a></h3>
<p>There are currently two flavors of <code>RegistryEntry</code> :</p>
<dl>
<dt>URLRegistryEntry</dt>
@@ -286,7 +286,7 @@ If you feel that the Batik team has over
<dt>StreamRegistryEntry</dt>
<dd>A <a href="../javadoc/org/apache/batik/ext/awt/image/spi/StreamRegistryEntry.html">StreamRegistryEntry</a> works with a markable <a href="http://java.sun.com/j2se/1.5.0/docs/api/java/io/InputStream.html">InputStream</a> . This is the preferred form of registry entry as it generally avoids opening a potentially expensive connection multiple times, instead it opens the stream once and relies on mark and reset to allow entries to check the stream.</dd>
</dl>
-<h3 id="helper-classes-wzxhzdk16wzxhzdk17">Helper classes # <a id="Helper+classes"></a></h3>
+<h3 id="helper-classes-wzxhzdk16wzxhzdk17">Helper classes <a id="Helper+classes"></a></h3>
<p>There exists quite a number of classes to assist in implementing a <code>RegistryEntry</code> . It is strongly recommended that you review these classes and make use of them where appropriate. They will likely save you time and improve the integration with Batik.</p>
<dl>
<dt>MagicNumberRegistryEntry</dt>
@@ -300,12 +300,12 @@ If you feel that the Batik team has over
<dt>AbstractRed</dt>
<dd><a href="../javadoc/org/apache/batik/ext/awt/image/rendered/AbstractRed.html">AbstractRed</a> is an abstract base class that makes it relatively easy to implement the <a href="../javadoc/org/apache/batik/ext/awt/image/rendered/CacheableRed.html">CacheableRed</a> interface (Batik's subclass of <code>RenderedImage</code> ).</dd>
</dl>
-<h2 id="new-url-protocols-wzxhzdk18wzxhzdk19">New URL protocols <a id="urlProtocols"></a></h2>
+<h2 id="new-url-protocols-wzxhzdk18wzxhzdk19">New URL protocols <a id="urlProtocols"></a></h2>
<p>For a variety of reasons (not the least of which is the heavy use of the <code>data:</code> URL protocol in SVG), several parts of Batik use a <a href="../javadoc/org/apache/batik/util/ParsedURL.html">ParsedURL</a> instead of the JDKâs <a href="http://java.sun.com/j2se/1.5.0/docs/api/java/net/URL.html">java.net.URL</a> class.</p>
<p><code>ParsedURL</code> offers a few advantages over the JDKâs <code>URL</code> class. First, it is designed to make minimal use of exceptions, so it is possible to use it to parse a malformed URL and get âthe good partsâ. Second, it is extensible, so support for new URL protocols can be added, even those that change the normal parsing rules for URLs (such as our friend the <code>data:</code> protocol). Third, it can automatically check a when a stream can be opened for common compression types and decode them for you (this behavior can also be bypassed if needed).</p>
<p>The service class is <a href="../javadoc/org/apache/batik/util/ParsedURLProtocolHandler.html">org.apache.batik.util.ParsedURLProtocolHandler</a> . This interface consists of three methods: one returns the protocol to be handled, one is for parsing an absolute URL string and one is for parsing relative URL strings. Both the parsing methods return an object of type <a href="../javadoc/org/apache/batik/util/ParsedURLData.html">ParsedURLData</a> (the instance may of course be a subclass of <code>ParsedURLData</code> ).</p>
<p>The <code>ParsedURLData</code> class holds all the data and implements all the stream handling commands for the <code>ParsedURL</code> class. This allows <code>ParsedURLProtocolHandler</code> s to return custom subclasses for particular protocols.</p>
-<h2 id="additional-script-interpreters-wzxhzdk20wzxhzdk21">Additional script interpreters <a id="interpreters"></a></h2>
+<h2 id="additional-script-interpreters-wzxhzdk20wzxhzdk21">Additional script interpreters <a id="interpreters"></a></h2>
<p>While conforming SVG browsers need support only ECMAScript as a scripting language, Batik can support any scripting language given the right glue to connect it to the rest of the system.</p>
<p>Script interpreters are also handled via the Service Provider Interface, The interface that needs to be implemented to expose a new interpreter to Batik is <a href="../javadoc/org/apache/batik/script/InterpreterFactory.html">InterpreterFactory</a> . This class has two methods: <code>getMimeType</code> , which returns a string that specifies what script type this intepreter handles (specifically, what the <code>type</code> attribute of <code>script</code> elements must be for them to be handled by this intepreter), and <code>createInterpreter</code> , which creates an instance of the <a href="../javadoc/org/apache/batik/script/Interpreter.html">Interpreter</a> interface.</p>
<p>Batik comes with implementations of <code>Interpreter</code> and <code>IntepreterFactory</code> to support TCL and Python script in SVG documents, if the Jacl and Jython distributions are installed, respectively. See the classes in the <code>org.apache.batik.script.jacl</code> and <code>org.apache.batik.script.jython</code> packages to guidance on how to implement the interpreter interfaces, and the <a href="../install.html">installation notes</a> on what jar files are needed for TCL and Python support.</p></div>
Modified: websites/staging/xmlgraphics/trunk/content/batik/using/parsers.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/batik/using/parsers.html (original)
+++ websites/staging/xmlgraphics/trunk/content/batik/using/parsers.html Wed Oct 24 04:26:06 2012
@@ -161,7 +161,7 @@ $(document).ready(function () {
<!-- <div id="breadcrumb"><a href="/">Home</a> » <a href="/batik/">Batik</a> » <a href="/batik/using/">Using</a></div> -->
<div class="section-content"><h1 id="parser-module">Parser module</h1>
<p>SVG has a number of microsyntaxes that are used within attribute values, such as the <code>transform</code> attribute on <code>SVGTransformable</code> elements, and the path data <code>d</code> attribute on <code>path</code> elements. Since these are not trivial to parse, this functionality has been factored out into a separate package that can be used by other SVG-processing applications if needed.</p>
-<h2 id="parsers-handlers-and-producers-wzxhzdk2wzxhzdk3">Parsers, handlers and producers <a id="parsersHandlersAndProducers"></a></h2>
+<h2 id="parsers-handlers-and-producers-wzxhzdk2wzxhzdk3">Parsers, handlers and producers <a id="parsersHandlersAndProducers"></a></h2>
<p>In the parser module, each microsyntax is supported by a pair of classes: a parser and a handler. The parser is a class that implements the <a href="../javadoc/org/apache/batik/parser/Parser.html">Parser</a> interface, which has methods to parse values from a <a href="http://java.sun.com/j2se/1.5.0/docs/api/java/io/Reader.html">Reader</a> or a <a href="http://java.sun.com/j2se/1.5.0/docs/api/java/lang/String.html">String</a> . The handler is an interface specific to the microsyntax that will have its methods called whenever the corresponding element in the input is parsed. For those handler interfaces that have more than one method, adapter classes are provided (named <code>Default</code> *).</p>
<p>Parsers can also have an error handler associated with them, whose single method <code>error</code> will be called when there is a problem parsing the input. If an error handler is not associated with a parser, a <a href="../javadoc/org/apache/batik/parser/ParseException.html">ParseException</a> will be thrown if an error occurs.</p>
<p>The microsyntaxes supported by the parser module are:</p>
@@ -190,7 +190,7 @@ $(document).ready(function () {
<dd>Implemented by <a href="../javadoc/org/apache/batik/parser/TransformListParser.html">TransformListParser</a> , handled with <a href="../javadoc/org/apache/batik/parser/TransformListHandler.html">TransformListHandler</a> . This parser is used for parsing transform lists, as found in the <code>transform</code> attribute of any transformable element.</dd>
</dl>
<p>Some microsyntaxes also have a corresponding producer class, which is an implementation of the handler interface that generates an object while parsing.</p>
-<h2 id="examples-wzxhzdk4wzxhzdk5">Examples <a id="examples"></a></h2>
+<h2 id="examples-wzxhzdk4wzxhzdk5">Examples <a id="examples"></a></h2>
<p>The following example code demonstrates how to use the parser classes to parse a list of points:
import java.awt.geom.Point2D;
import java.util.LinkedList;
Modified: websites/staging/xmlgraphics/trunk/content/batik/using/scripting/ecmascript.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/batik/using/scripting/ecmascript.html (original)
+++ websites/staging/xmlgraphics/trunk/content/batik/using/scripting/ecmascript.html Wed Oct 24 04:26:06 2012
@@ -161,7 +161,7 @@ $(document).ready(function () {
<!-- <div id="breadcrumb"><a href="/">Home</a> » <a href="/batik/">Batik</a> » <a href="/batik/using/">Using</a> » <a href="/batik/using/scripting/">Scripting</a></div> -->
<div class="section-content"><h1 id="scripting-with-ecmascript">Scripting with ECMAScript</h1>
<p>This page is a brief introduction to scripting SVG documents with ECMAScript, and how Batikâs ECMAScript environment can be extended.</p>
-<h2 id="scripting-basics-wzxhzdk3wzxhzdk4">Scripting basics <a id="scriptingBasics"></a></h2>
+<h2 id="scripting-basics-wzxhzdk3wzxhzdk4">Scripting basics <a id="scriptingBasics"></a></h2>
<p>As the ECMAScript language (the standardised version of JavaScript) is one of the most popular scripting languages, and as the SVG specification states that an SVG conforming implementation must support it, SVG documents processed by Batik support scripting with ECMAScript using Mozillaâs ECMAScript interpreter, <a href="http://www.mozilla.org/rhino/">Rhino</a> .</p>
<p>There are two places in an SVG file where you can put scripts.</p>
<p>The first one is in the <code>script</code> element, where you can place any code, including function definitions, to be executed just before the document <code>SVGLoad</code> event is fired.
@@ -187,7 +187,7 @@ Note that inside the event attribute scr
<p>the <a href="http://www.ecma.ch/ecma1/stand/ecma-262.htm">ECMAScript specification</a> , for advanced information on the ECMAScript language.</p>
</li>
</ul>
-<h2 id="using-rhino-features-wzxhzdk13wzxhzdk14">Using Rhino features <a id="rhinoFeatures"></a></h2>
+<h2 id="using-rhino-features-wzxhzdk13wzxhzdk14">Using Rhino features <a id="rhinoFeatures"></a></h2>
<p>Rhino has a number of features beyond those supported by standard ECMAScript interpreters, and these can be used with Batik. One useful feature is that ECMAScript code can use Java classes and objects, and not just the standard ECMAScript primitive types and host objects exposed by Batik.</p>
<p>To create an instance of a Java class from ECMAScript, you first need to import the package in which it resides. This is done using the <code>importPackage</code> global function that Rhino provides. For example, to import the <code>javax.swing.JFrame</code> class, you use:
importPackage(Packages.javax.swing);
@@ -214,7 +214,7 @@ Note how an ECMAScript string value is p
<p></script>
</svg>
For more information on scripting Java classes from ECMAScript code, see Rhino's <a href="http://www.mozilla.org/rhino/ScriptingJava.html">Scripting Java</a> document.</p>
-<h2 id="customizing-the-rhino-interpreter-wzxhzdk20wzxhzdk21">Customizing the Rhino interpreter <a id="customizingRhino"></a></h2>
+<h2 id="customizing-the-rhino-interpreter-wzxhzdk20wzxhzdk21">Customizing the Rhino interpreter <a id="customizingRhino"></a></h2>
<p>A useful example of customization of the Rhino interpreter comes from the fact that the ECMAScript specification doesnât provide any predefined I/O facilities to interact with the console. However, it is very common for ECMAScript compatible languages to provide a function named <code>print</code> to output messages to the console. We will describe here an example of cutomization of the Batik Rhino interpreter to add such functionality to it.</p>
<p>You should first subclass the default Batik ECMAScript interpreter to add the functionality to it as below.
import org.apache.batik.script.rhino.RhinoInterpreter;</p>
Modified: websites/staging/xmlgraphics/trunk/content/batik/using/scripting/java.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/batik/using/scripting/java.html (original)
+++ websites/staging/xmlgraphics/trunk/content/batik/using/scripting/java.html Wed Oct 24 04:26:06 2012
@@ -161,7 +161,7 @@ $(document).ready(function () {
<!-- <div id="breadcrumb"><a href="/">Home</a> » <a href="/batik/">Batik</a> » <a href="/batik/using/">Using</a> » <a href="/batik/using/scripting/">Scripting</a></div> -->
<div class="section-content"><h1 id="scripting-with-java">Scripting With Java</h1>
<p>This page explains how to manipulate the DOM tree of an SVG document from a Java program.</p>
-<h2 id="how-to-manipulate-a-document-in-a-jsvgcanvas-wzxhzdk1wzxhzdk2">How to manipulate a document in a JSVGCanvas <a id="Swing"></a></h2>
+<h2 id="how-to-manipulate-a-document-in-a-jsvgcanvas-wzxhzdk1wzxhzdk2">How to manipulate a document in a JSVGCanvas <a id="Swing"></a></h2>
<p>The follow code template demonstrates how to manipulate an SVG document displayed in a <a href="../../javadoc/org/apache/batik/swing/JSVGCanvas.html">JSVGCanvas</a> directly from a Java program.
You donât have to worry about graphics updates; after each event listener invocation the canvas is updated if needed.import java.awt.event.WindowAdapter;
import java.awt.event.WindowEvent;</p>
@@ -270,7 +270,7 @@ import org.w3c.dom.events.EventTarget;</
<p>}</p>
-<h2 id="writing-thread-safe-code-wzxhzdk3wzxhzdk4">Writing thread-safe code <a id="Threads"></a></h2>
+<h2 id="writing-thread-safe-code-wzxhzdk3wzxhzdk4">Writing thread-safe code <a id="Threads"></a></h2>
<p>The DOM listeners registered on the SVG document are called from the canvas update thread. To avoid race conditions, do not manipulate the DOM tree from another thread.</p>
<p>The way to switch from an external thread to the canvas update thread is to use the following code:
// Returns immediately
@@ -290,7 +290,7 @@ canvas.getUpdateManager().getUpdateRunna
});
Like with event listeners, when a <a href="http://java.sun.com/j2se/1.5.0/docs/api/java/lang/Runnable.html">Runnable</a> is invoked from the update thread, the graphics are updated.
It is very dangerous to call <code>invokeAndWait</code> from the Swing event thread. This is the only thread that can be used to interact with Swing components. In some cases DOM calls may need to query the canvas for information (such as actual Swing component size, etc). If this happens you will get a thread deadlock. You should only make invokeAndWait calls from âthird partyâ threads.</p>
-<h1 id="using-the-svg-dom-wzxhzdk5wzxhzdk6">Using the SVG DOM <a id="SVGDOM"></a></h1>
+<h1 id="using-the-svg-dom-wzxhzdk5wzxhzdk6">Using the SVG DOM <a id="SVGDOM"></a></h1>
<p>Batik provides a fairly complete implementation of the SVG DOM. The SVG DOM provides all the functionality most applications require. In particular, the DOM implements DOM Events, including mutation and UI Events. As an example, DOM events allow you to get notified when the cursor moves over elements of interest:
// Element of Interest.
Element theElem = ...;
@@ -313,7 +313,7 @@ SVGPoint cPt = document.getRootElement
cPt.setX(uiEvt.getClientX());
cPt.setY(uiEvt.getClientY());
cPt = cPt.matrixTransform(imat);</p>
-<h1 id="referencing-java-code-from-a-document-wzxhzdk7wzxhzdk8">Referencing Java code from a document <a id="javaInDocument"></a></h1>
+<h1 id="referencing-java-code-from-a-document-wzxhzdk7wzxhzdk8">Referencing Java code from a document <a id="javaInDocument"></a></h1>
<p>Batik implements the Java bindings for SVG, and thus allows Java code to be referenced from <code>script</code> elements. This feature is available to any application of Batik that uses the bridge module (for example the Swing component and the transcoders).</p>
<p>In order to use this extension, the <code>type</code> attribute of a <code>script</code> element must be set to <code>application/java-archive</code> . In addition, the <code>xlink:href</code> attribute must be the URI of a jar file that contains the code to run.</p>
<p>The manifest of this jar file must contains an entry of the form:
Modified: websites/staging/xmlgraphics/trunk/content/batik/using/scripting/security.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/batik/using/scripting/security.html (original)
+++ websites/staging/xmlgraphics/trunk/content/batik/using/scripting/security.html Wed Oct 24 04:26:06 2012
@@ -162,13 +162,13 @@ $(document).ready(function () {
<div class="section-content"><h1 id="script-security">Script security</h1>
<p>With the addition of scripting support in Batik 1.5, security features have also been added to enable users of the Batik toolkit to run scripts in a secure manner.</p>
<p>If you are using script, please make sure you have reviewed the <a href="../../index.html#SecurityWarning">Script Security Warning</a> with regards to the Batik 1.5 release.</p>
-<h2 id="running-scripts-securely-wzxhzdk0wzxhzdk1">Running scripts securely <a id="sandbox"></a></h2>
+<h2 id="running-scripts-securely-wzxhzdk0wzxhzdk1">Running scripts securely <a id="sandbox"></a></h2>
<p>The Java platform offers a lot of options for running applications securely. Running an application securely requires that it runs in a so-called security sand-box which controls all the access the application makes to restricted resources (such as the file system).</p>
<p>The concept of Java security is an application-wide concept. As such, it has to be applied at the application level (and not at the framework level). In the Batik distribution, the sample applications (such as the <a href="../../tools/browser.html">Squiggle Browser</a> and the <a href="../../tools/rasterizer.html">SVG rasterizer</a> ) apply security (or disable it) but the framework does not apply it: it is security-aware (meaning that it is able to handle security exceptions).</p>
-<h3 id="enforcing-security-in-a-batik-application-wzxhzdk2wzxhzdk3">Enforcing security in a Batik application # <a id="enforcing"></a></h3>
+<h3 id="enforcing-security-in-a-batik-application-wzxhzdk2wzxhzdk3">Enforcing security in a Batik application <a id="enforcing"></a></h3>
<p>Enforcing security in a Batik application is done by setting a <a href="http://java.sun.com/j2se/1.5.0/docs/api/java/lang/SecurityManager.html">java.lang.SecurityManager</a> . This security manager will apply the security settings of the Java platform (as defined by the <em>jre-dir</em> <code>/lib/security/java.policy</code> and, optionally, by the policy file whose URL is defined in the <code>java.security.policy</code> system property).</p>
<p>The <a href="../../javadoc/org/apache/batik/util/ApplicationSecurityEnforcer.html">org.apache.batik.util.ApplicationSecurityEnforcer</a> helper class makes it easier for Batik application developers to add security support in their applications. That helper class is used by the sample Batik applications.</p>
-<h3 id="squiggle-security-wzxhzdk4wzxhzdk5">Squiggle security # <a id="squiggle"></a></h3>
+<h3 id="squiggle-security-wzxhzdk4wzxhzdk5">Squiggle security <a id="squiggle"></a></h3>
<p>The Squiggle browser lets the user decide whether or not scripts should be run securely (see the âBrowser Optionsâ in the preference dialog box). When scripts are run securely, Squiggle will enforce the security settings as follows:</p>
<ul>
<li>
@@ -191,7 +191,7 @@ grant codeBase "${app.dev.base}/lib/myXM
};
in the <code>resources/org/apache/batik/apps/svgbrowser/resources/svgbrowser.policy</code> file (for the source distribution) and do the same in <code>resources/org/apache/batik/apps/svgbrowser/resources/svgbrowser.bin.policy</code> (for the binary distribution which will then need to be rebuilt with the <code>build dist-zip</code> command.</p>
<p>Alternatively, you can write your own policy file and specify its URL through the <code>java.security.policy</code> system property (which you can specify through the <code>-Djava.security.policy=</code> <em>url</em> command line option).</p>
-<h2 id="controlling-access-to-external-resources-wzxhzdk6wzxhzdk7">Controlling access to external resources <a id="externalResources"></a></h2>
+<h2 id="controlling-access-to-external-resources-wzxhzdk6wzxhzdk7">Controlling access to external resources <a id="externalResources"></a></h2>
<p>SVG makes a very powerful use of external resources in many elements such as <code>image</code> , <code>use</code> , <code>font</code> , <code>script</code> and <code>radialGradient</code> . There are over fifteen SVG elements that may reference external resources that way.</p>
<p>In some environments, and typically for security reasons, it is important to control the resources referenced by an SVG document and be able to accept or reject these resources.</p>
<p>In the Batik toolkit, this flexibility is provided by the <a href="../../javadoc/org/apache/batik/bridge/UserAgent.html">org.apache.batik.bridge.UserAgent</a> interface which can define various strategies with regards to external resources. By providing a new implementation of the <code>UserAgent</code> interface, it is possible to apply the desired security strategy for scripts and external resources.</p>
Modified: websites/staging/xmlgraphics/trunk/content/batik/using/svg-generator.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/batik/using/svg-generator.html (original)
+++ websites/staging/xmlgraphics/trunk/content/batik/using/svg-generator.html Wed Oct 24 04:26:06 2012
@@ -163,7 +163,7 @@ $(document).ready(function () {
<div class="figure">  </div>
<p>As SVG is emerging as a promising graphics format for a wide range of domains and applications, bridging it with Java becomes important. This page explains how Batikâs <a href="../javadoc/org/apache/batik/svggen/SVGGraphics2D.html">SVGGraphics2D</a> , referred to as the SVG Generator, makes this possible.</p>
-<h2 id="the-svggraphics2d-class-wzxhzdk7wzxhzdk8">The SVGGraphics2D class <a id="whatIsIt"></a></h2>
+<h2 id="the-svggraphics2d-class-wzxhzdk7wzxhzdk8">The SVGGraphics2D class <a id="whatIsIt"></a></h2>
<p>On the Java platform, all rendering goes through the <a href="http://java.sun.com/j2se/1.5.0/docs/api/java/awt/Graphics2D.html">Graphics2D</a> abstract class, which offers methods such as <code>drawRect</code> , <code>fillRect</code> , and <code>drawString</code> . There are specialized implementations of this abstract class for each type of output, such as a screen or a printer. <code>SVGGraphics2D</code> is a new implementation of that interface that generates SVG content instead of drawing to a screen or a printer.</p>
<p><code>SVGGraphics2D</code> has the following features:</p>
<ul>
@@ -181,7 +181,7 @@ The above figure shows how the generator
</ul>
<p>The generator manages a tree of DOM objects that represent the SVG content corresponding to the rendering calls made on the <code>SVGGraphics2D</code> instance. In other words, every time a program invokes a rendering method, such as <code>fillRect</code> , on a <code>SVGGraphics2D</code> instance, a new DOM object, representing the SVG equivalent, is appended to the DOM tree. For example, a <code>rect</code> element will be appended after the <code>fillRect</code> method has been invoked).</p>
<p>The programmer, using this generator, can then access the DOM tree to further manipulate it or can directly write the content to an output stream, as we see in the following section.</p>
-<h2 id="how-to-use-svggraphics2d-wzxhzdk9wzxhzdk10">How to use SVGGraphics2D <a id="howToUse"></a></h2>
+<h2 id="how-to-use-svggraphics2d-wzxhzdk9wzxhzdk10">How to use SVGGraphics2D <a id="howToUse"></a></h2>
<p>From the figure in the previous section we can see that in order for an instance of <code>SVGGraphics2D</code> to build the SVG content (the DOM tree), an instance of a <code>Document</code> class is needed. The DOM tree is an in-memory representation of the SVG document, which can be further manipulated by the user using DOM API or be streamed out by a <a href="http://java.sun.com/j2se/1.5.0/docs/api/java/io/Writer.html">Writer</a> object.</p>
<p>The following example program demonstrates how to generate SVG content from Java graphics.
import java.awt.Rectangle;
@@ -260,10 +260,10 @@ We can see that generating SVG content f
</li>
</ol>
<p>SVG has <a href="http://www.w3.org/TR/SVG11/styling.html#AlternativesForStyling">two ways to specify styling properties</a> , such as the fill color: presentation attributes (one XML attribute per property) or the CSS <code>style</code> attribute (any number of properties in one CSS inline stylesheet). The <code>useCss</code> parameter allows the user to control that option.</p>
-<h2 id="svg-generator-customization-wzxhzdk11wzxhzdk12">SVG Generator customization <a id="custom"></a></h2>
+<h2 id="svg-generator-customization-wzxhzdk11wzxhzdk12">SVG Generator customization <a id="custom"></a></h2>
<p>In the previous section, we have just seen that the SVG generation process can be customized to output SVG styling properties as presentation attributes or CSS inline stylesheets. In this section we will talk about some examples of more advanced customizations.</p>
<p>Instead of creating the <code>SVGGraphics2D</code> just by using the <code>Document</code> that will be used as a factory for creating the SVG elements, we can use the constructor that uses an <a href="../javadoc/org/apache/batik/svggen/SVGGeneratorContext.html">SVGGeneratorContext</a> instance. By providing your own <code>SVGGeneratorContext</code> instance, you will be able to do advanced customization. You will find below several examples of possible customizations.</p>
-<h3 id="have-your-own-comment-in-the-generated-svg-file-wzxhzdk13wzxhzdk14">Have your own comment in the generated SVG file # <a id="Have+your+own+comment+in+the+generated+SVG+file"></a></h3>
+<h3 id="have-your-own-comment-in-the-generated-svg-file-wzxhzdk13wzxhzdk14">Have your own comment in the generated SVG file <a id="Have+your+own+comment+in+the+generated+SVG+file"></a></h3>
<p>We begin with the simplest possible example. If you integrate the Batik SVG generator in your own Java application, you may want to specialize the comment generated in the XML code.
DOMImplementation impl =
GenericDOMImplementation.getDOMImplementation();
@@ -272,7 +272,7 @@ Document myFactory = impl.createDocument
<p>SVGGeneratorContext ctx = SVGGeneratorContext.createDefault(myFactory);
ctx.setComment("Generated by FooApplication with Batik SVG Generator");
SVGGraphics2D g2d = new SVGGraphics2D(ctx, false);</p>
-<h2 id="use-embedded-svg-fonts-in-the-generated-svg-file-wzxhzdk15wzxhzdk16">Use embedded SVG Fonts in the generated SVG file # <a id="Use+embedded+SVG+Fonts+in+the+generated+SVG+file"></a></h2>
+<h2 id="use-embedded-svg-fonts-in-the-generated-svg-file-wzxhzdk15wzxhzdk16">Use embedded SVG Fonts in the generated SVG file <a id="Use+embedded+SVG+Fonts+in+the+generated+SVG+file"></a></h2>
<p>In order to have a self-contained SVG file that doesn't have to use system fonts to be displayed, you can embed the fonts you used for drawing strings in the SVG file through the SVG fonts facility.
DOMImplementation impl =
GenericDOMImplementation.getDOMImplementation();
@@ -281,7 +281,7 @@ Document myFactory = impl.createDocument
<p>SVGGeneratorContext ctx = SVGGeneratorContext.createDefault(myFactory);
ctx.setEmbeddedFontsOn(true);
SVGGraphics2D g2d = new SVGGraphics2D(ctx, true);</p>
-<h2 id="customizing-the-way-images-are-stored-wzxhzdk17wzxhzdk18">Customizing the way images are stored # <a id="Customizing+the+way+images+are+stored"></a></h2>
+<h2 id="customizing-the-way-images-are-stored-wzxhzdk17wzxhzdk18">Customizing the way images are stored <a id="Customizing+the+way+images+are+stored"></a></h2>
<p>Every time you call one of the <code>drawImage</code> methods provided by the <code>Graphics2D</code> interface, a default representation of your image is created in a location and put in a default file. For instance, a base64 encoding is created and embedded in the SVG file by default. Alternatively, you can choose to have your images written to separate files in a predefined directory, in one of the two raster formats required by the SVG specification: JPEG or PNG.</p>
<p>You can change the default behavior by explicitly providing the image handler to be used by the SVG generator. Once again, you use the <code>SVGGeneratorContext</code> for this. In the example below, all images are converted to PNG format and written to directory <code>res/images</code> .
DOMImplementation impl =
@@ -328,7 +328,7 @@ class MySVGGenerator {</p>
<p>}</p>
-<h2 id="customizing-the-generated-svg-style-wzxhzdk19wzxhzdk20">Customizing the generated SVG style # <a id="Customizing+the+generated+SVG+style"></a></h2>
+<h2 id="customizing-the-generated-svg-style-wzxhzdk19wzxhzdk20">Customizing the generated SVG style <a id="Customizing+the+generated+SVG+style"></a></h2>
<p>Your needs in matter of styling may be different from the two provided options (XML presentation attributes or CSS inline stylesheets). For example, you may want to put the CSS properties in a SVG <code>style</code> element section and reference them through the class attribute. In this case you will need to define a new <a href="../javadoc/org/apache/batik/svggen/StyleHandler.html">StyleHandler</a> as below.
public class StyleSheetStyleHandler implements StyleHandler {</p>
<div class="codehilite"><pre><span class="sr">//</span> <span class="n">The</span> <span class="n">CDATA</span> <span class="n">section</span> <span class="n">that</span> <span class="n">holds</span> <span class="n">the</span> <span class="n">CSS</span> <span class="n">stylesheet</span><span class="o">.</span>
@@ -380,7 +380,7 @@ style.appendChild(styleSheet);
defs.appendChild(style);</p>
<p>// Dump the root content to a given Writer myWriter.
g2d.stream(root, myWriter);</p>
-<h2 id="extending-paint-object-to-svg-element-translation-wzxhzdk21wzxhzdk22">Extending Paint object to SVG element translation # <a id="Extending+Paint+object+to+SVG+element+translation"></a></h2>
+<h2 id="extending-paint-object-to-svg-element-translation-wzxhzdk21wzxhzdk22">Extending Paint object to SVG element translation <a id="Extending+Paint+object+to+SVG+element+translation"></a></h2>
<p>The <code>SVGGraphics2D</code> is able to generate SVG elements for generic Java 2D objects, but you sometimes have your own classes such as implementations of the Java 2D <a href="http://java.sun.com/j2se/1.4.2/docs/api/java/awt/Paint.html">Paint</a> interface. In this case, you will need to write an <a href="../javadoc/org/apache/batik/svggen/ExtensionHandler.html">ExtensionHandler</a> that you will set on your <code>SVGGeneratorContext</code> .</p>
<p>In the following example we define the first draft of an <code>ExtensionHandler</code> allowing to translate a Batik implementation of the <code>Paint</code> interface named <a href="../javadoc/org/apache/batik/ext/awt/LinearGradientPaint.html">LinearGradientPaint</a> .
class MyExtensionHandler extends DefaultExtensionHandler {</p>
@@ -443,7 +443,7 @@ You should then set it on the <code>SVGG
SVGGeneratorContext ctx = SVGGeneratorContext.createDefault(myFactory);
ctx.setExtensionHandler(new MyExtensionHandler());
SVGGraphics2D g2d = new SVGGraphics2D(ctx, false);</p>
-<h1 id="how-to-view-the-generated-svg-document-wzxhzdk23wzxhzdk24">How to view the generated SVG document <a id="view"></a></h1>
+<h1 id="how-to-view-the-generated-svg-document-wzxhzdk23wzxhzdk24">How to view the generated SVG document <a id="view"></a></h1>
<p>The following code example illustrates how to view the SVG content generated by an <code>SVGGraphics2D</code> object.
import java.awt.<em>;
import java.awt.geom.</em>;</p>
Modified: websites/staging/xmlgraphics/trunk/content/batik/using/swing.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/batik/using/swing.html (original)
+++ websites/staging/xmlgraphics/trunk/content/batik/using/swing.html Wed Oct 24 04:26:06 2012
@@ -161,7 +161,7 @@ $(document).ready(function () {
<!-- <div id="breadcrumb"><a href="/">Home</a> » <a href="/batik/">Batik</a> » <a href="/batik/using/">Using</a></div> -->
<div class="section-content"><h1 id="batik-swing-components">Batik Swing components</h1>
<p>The goal of the Batik Swing component module is to provide a Swing component that can used to display SVG documents. With the <a href="../javadoc/org/apache/batik/swing/JSVGCanvas.html">JSVGCanvas</a> class, you can easily display an SVG document (from a URI or a DOM tree) and allow the user to manipulate it, such as rotating, zooming, panning, selecting text or activating hyperlinks. First this document explains how to create a <code>JSVGCanvas</code> and integrate it in to a Swing application. Then, it descibes some advanced features such as the listener mechanism used to track all events that occurred while displaying or manipulating an SVG document.</p>
-<h2 id="creating-a-jsvgcanvas-wzxhzdk1wzxhzdk2">Creating a JSVGCanvas <a id="creatingJSVGCanvas"></a></h2>
+<h2 id="creating-a-jsvgcanvas-wzxhzdk1wzxhzdk2">Creating a JSVGCanvas <a id="creatingJSVGCanvas"></a></h2>
<p>The following example illustrates how to create a <code>JSVGCanvas</code> , which is a Swing component that follows the Swing design rule. This means that the component is not thread safe and all operations on the component or the document it is displaying must be performed as described in <a href="http://java.sun.com/docs/books/tutorial/uiswing/overview/threads.html">the Swing tutorial</a> . The <code>JSVGCanvas</code> is also a <a href="http://java.sun.com/products/javabeans/">JavaBean</a> , so it can be used in visual application builders.
If you try this example, do not forget to set your <code>CLASSPATH</code> so that it contains the Batik classes and resources, as well as Xerces ( <code>lib/xerces_2_5_0.jar</code> ) and the XML APIs jars ( <code>lib/xml-apis.jar</code> and <code>lib/xml-apis-ext.jar</code> ).import java.awt.<em>;
import java.awt.event.</em>;
@@ -271,7 +271,7 @@ import org.apache.batik.swing.svg.GVTTre
<p>}<div class="figure"> <img alt="Screenshot of the example SVGApplication program" src="images/svgapplication.png" title="" /> </div></p>
-<h1 id="handling-events-wzxhzdk5wzxhzdk6">Handling events <a id="eventhandling"></a></h1>
+<h1 id="handling-events-wzxhzdk5wzxhzdk6">Handling events <a id="eventhandling"></a></h1>
<p>Each time you set a URI or an SVG DOM tree to be displayed in a <code>JSVGCanvas</code> (using the <code>setURI</code> or <code>setSVGDocument</code> method), the specified document is first parsed (in case of a URI), built, rendered and optionally updated. The proper way to be notified of these different phases is to implement a listener and attach it to the component. There are five types of listener:</p>
<dl>
<dt><code>SVGDocumentLoaderListener</code></dt>
@@ -295,7 +295,7 @@ import org.apache.batik.swing.svg.GVTTre
<p>These listeners give a complete description of the different steps of the five phases (including error states). Adapter classes are available to ease the creation of new listener implementationâ <a href="../javadoc/org/apache/batik/swing/svg/SVGDocumentLoaderAdapter.html">SVGDocumentLoaderAdapter</a> , <a href="../javadoc/org/apache/batik/swing/svg/GVTTreeBuilderListenerAdapter.html">GVTTreeBuilderListenerAdapter</a> , <a href="../javadoc/org/apache/batik/swing/svg/SVGLoadEventDispatcherAdapter.html">SVGLoadEventDispatcherAdapter</a> , <a href="../javadoc/org/apache/batik/swing/gvt/GVTTreeRendererAdapter.html">GVTTreeRendererAdapter</a> and <a href="../javadoc/org/apache/batik/bridge/UpdateManagerAdapter.html">UpdateManagerAdapter</a> ,</p>
<p>For static documents, you can assume that the JSVGCanvas has completed its job (parsing, building and rendering) when the <code>gvtRenderingCompleted</code> method call is called, following a <code>setURI</code> or a <code>setSVGDocument</code> method call.</p>
<p>In the case of dynamic documents, the end of the computation (parsing, building, SVGLoad dispatch, initial rendering and updates) is marked by a call to the <code>updateManagerStopped</code> method.</p>
-<h2 id="adding-an-interactor-wzxhzdk7wzxhzdk8">Adding an Interactor <a id="interactor"></a></h2>
+<h2 id="adding-an-interactor-wzxhzdk7wzxhzdk8">Adding an Interactor <a id="interactor"></a></h2>
<p>The <code>JSVGCanvas</code> provides a set of build-in interactors that let the users manipulate the displayed document, including ones for zooming, panning and rotating. Interactors catch user input to the <code>JSVGCanvas</code> component and translate them into behaviour. If you want to add new behaviors to the <code>JSVGCanvas</code> , you can implement the <a href="../javadoc/org/apache/batik/swing/gvt/Interactor.html">Interactor</a> interface. Then, you can register this new interactor to the component by adding an element to the <code>List</code> returned by the <code>getInteractors()</code> method of the canvas.</p></div>
</div>
Modified: websites/staging/xmlgraphics/trunk/content/batik/using/transcoder.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/batik/using/transcoder.html (original)
+++ websites/staging/xmlgraphics/trunk/content/batik/using/transcoder.html Wed Oct 24 04:26:06 2012
@@ -161,7 +161,7 @@ $(document).ready(function () {
<!-- <div id="breadcrumb"><a href="/">Home</a> » <a href="/batik/">Batik</a> » <a href="/batik/using/">Using</a></div> -->
<div class="section-content"><h1 id="transcoder-api">Transcoder API</h1>
<p>The goal of the transcoder API (package <code>org.apache.batik.transcoder</code> ) is to provide a generic API for transcoding an input to an output. First, this document explains the basic transcoder API that <a href="../javadoc/org/apache/batik/transcoder/Transcoder.html">Transcoder</a> , <a href="../javadoc/org/apache/batik/transcoder/TranscoderInput.html">TranscoderInput</a> and <a href="../javadoc/org/apache/batik/transcoder/TranscoderOutput.html">TranscoderOutput</a> define, and thus all transcoders have in common. Next, it describes how to use the image transcoder API (package <code>org.apache.batik.transcoder.image</code> ), which lets you rasterize an SVG document fragment to a raster image such as JPEG, PNG or TIFF.</p>
-<h2 id="the-transcoder-api-wzxhzdk3wzxhzdk4">The transcoder API <a id="transcoderAPI"></a></h2>
+<h2 id="the-transcoder-api-wzxhzdk3wzxhzdk4">The transcoder API <a id="transcoderAPI"></a></h2>
<p>The <code>org.apache.batik.transcoder</code> package defines 5 major classes:</p>
<dl>
<dt>Transcoder</dt>
@@ -175,9 +175,9 @@ $(document).ready(function () {
<dt>ErrorHandler</dt>
<dd>The <a href="../javadoc/org/apache/batik/transcoder/ErrorHandler.html">ErrorHandler</a> class provides a way to get any errors or warnings that might occur while transcoding. A default implementation is provided but you can, for example, implement your own handler that displays a dialog instead of stack trace.</dd>
</dl>
-<h2 id="how-to-use-the-image-transcoder-api-wzxhzdk5wzxhzdk6">How to use the image transcoder API <a id="howtousetranscoderAPI"></a></h2>
+<h2 id="how-to-use-the-image-transcoder-api-wzxhzdk5wzxhzdk6">How to use the image transcoder API <a id="howtousetranscoderAPI"></a></h2>
<p>The <code>org.apache.batik.transcoder.image</code> package provides an easy way to transcode an SVG document to a raster image such as JPEG, PNG or TIFF. Additional raster image formats can be added by subclassing the <code>ImageTranscoder</code> class and implementing the <code>writeImage</code> method. Although, in next sections, the examples will use the JPEG transcoder, the PNG transcoder works the same way.</p>
-<h3 id="creating-an-image-wzxhzdk7wzxhzdk8">Creating an image # <a id="createImage"></a></h3>
+<h3 id="creating-an-image-wzxhzdk7wzxhzdk8">Creating an image <a id="createImage"></a></h3>
<p>The following example, using the <code>JPEGTranscoder</code> , shows how to transform an SVG document to a JPEG image.
import java.io.*;</p>
<p>import org.apache.batik.transcoder.image.JPEGTranscoder;
@@ -231,11 +231,11 @@ java SaveAsJPEG filename.svg</p>
<p>Inspect the output file <code>out.jpg</code> .</p>
</li>
</ol>
-<h3 id="defining-the-size-of-the-image-wzxhzdk9wzxhzdk10">Defining the size of the image # <a id="defineSizeOfImage"></a></h3>
+<h3 id="defining-the-size-of-the-image-wzxhzdk9wzxhzdk10">Defining the size of the image <a id="defineSizeOfImage"></a></h3>
<p>By adding the following line of code to the previous example, you will specify the raster image size (in pixels). The transcoding hint <code>KEY_WIDTH</code> lets you specify the raster image width. If the raster image height is not provided (using the <code>KEY_HEIGHT</code> ), the transcoder will compute the raster image height by keeping the aspect ratio of the SVG document.
t.addTranscodingHint(JPEGTranscoder.KEY_WIDTH, new Float(100));
The transcoder will have the same behavior if you specify the <code>KEY_HEIGHT</code> without initializing the <code>KEY_WIDTH</code> . In all cases (even if both keys are provided), the transcoder will preserve the apsect ratio of the SVG document.</p>
-<h3 id="selecting-an-area-of-interest-wzxhzdk11wzxhzdk12">Selecting an area of interest # <a id="selectAreaOfIntrest"></a></h3>
+<h3 id="selecting-an-area-of-interest-wzxhzdk11wzxhzdk12">Selecting an area of interest <a id="selectAreaOfIntrest"></a></h3>
<p>The image transcoder lets you specify an area of interest (that is, a part of the SVG document). The key <code>KEY_AOI</code> allows you to select the region of the SVG document to render. The value of this key must be a <a href="http://java.sun.com/j2se/1.5.0/docs/api/java/awt/Rectangle.html">java.awt.Rectangle</a> specified in pixels, using the coordinate space of the SVG document. The following example shows how you can split an SVG document into 4 tiles.
import java.io.<em>;
import java.awt.</em>;</p>
@@ -310,7 +310,7 @@ java SaveAsJPEGTiles</p>
<p>Inspect the output files <code>tileTopRight.jpg</code> , <code>tileTopRight.jpg</code> , <code>tileBottomRight.jpg</code> and <code>tileBottomLeft.jpg</code> .</p>
</li>
</ol>
-<h3 id="other-transcoding-hints-wzxhzdk13wzxhzdk14">Other transcoding hints # <a id="otherTransHints"></a></h3>
+<h3 id="other-transcoding-hints-wzxhzdk13wzxhzdk14">Other transcoding hints <a id="otherTransHints"></a></h3>
<p>The <code>ImageTranscoder</code> provides additional <code>TranscodingHints</code> that let you customize the generated images.</p>
<dl>
<dt><code>ImageTranscoder.KEY_MEDIA</code></dt>
@@ -334,7 +334,7 @@ trans.addTranscodingHint(ImageTranscoder
<dd>This hint lets you choose a background color. For example:
trans.addTranscodingHint(ImageTranscoder.KEY_BACKGROUND_COLOR, Color.white);</dd>
</dl>
-<h2 id="generating-an-image-from-an-svg-dom-tree-wzxhzdk15wzxhzdk16">Generating an image from an SVG DOM tree # <a id="genImagefromSVGDOM"></a></h2>
+<h2 id="generating-an-image-from-an-svg-dom-tree-wzxhzdk15wzxhzdk16">Generating an image from an SVG DOM tree <a id="genImagefromSVGDOM"></a></h2>
<p>The following code creates and saves an SVG DOM tree to a raster image.
import java.io.*;</p>
<p>import org.apache.batik.transcoder.image.JPEGTranscoder;
Modified: websites/staging/xmlgraphics/trunk/content/commons/bugs.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/commons/bugs.html (original)
+++ websites/staging/xmlgraphics/trunk/content/commons/bugs.html Wed Oct 24 04:26:06 2012
@@ -131,7 +131,7 @@ $(document).ready(function () {
<div class="section-content"><h1 id="apachewzxhzdk0-xml-graphics-commons-bugs-and-other-trackable-issues">Apache™ XML Graphics Commons: Bugs and Other Trackable Issues</h1>
<p><version>$Revision: 911792 $</version></p>
<p>Information on this page applies to enhancement requests and other trackable issues as well as bugs.</p>
-<h2 id="reported-issues-wzxhzdk3wzxhzdk4">Reported Issues <a id="issues_existing"></a></h2>
+<h2 id="reported-issues-wzxhzdk3wzxhzdk4">Reported Issues <a id="issues_existing"></a></h2>
<p>A list of unresolved reported bugs can be found at <a href="http://issues.apache.org/bugzilla/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&bugidtype=include&bug_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&product=XMLGraphicsCommons&short_desc=&short_desc_type=allwordssubstr&long_desc=&long_desc_type=allwordssubstr&bug_file_loc=&bug_file_loc_type=allwordssubstr&keywords=&keywords_type=anywords&field0-0-0=noop&type0-0-0=noop&value0-0-0=">XML Graphics Commons Open Bugs (Bugzilla)</a> . If you have an interest in an issue already reported, please consider the following:</p>
<ul>
<li>
@@ -141,7 +141,7 @@ $(document).ready(function () {
<p>If you would like to track the status of the issue, consider adding your email address to the list of "CC" recipients, so that you will receive an email as changes are made to the issue.</p>
</li>
</ul>
-<h2 id="unreported-issues-reporting-new-issues-wzxhzdk5wzxhzdk6">Unreported Issues (Reporting New Issues) <a id="issues_new"></a></h2>
+<h2 id="unreported-issues-reporting-new-issues-wzxhzdk5wzxhzdk6">Unreported Issues (Reporting New Issues) <a id="issues_new"></a></h2>
<p>User reports of bugs and requests for enhancements are extremely important parts of XML Graphics Commons development, and we appreciate the time you take to help us track these issues down.</p>
<ul>
<li>
Modified: websites/staging/xmlgraphics/trunk/content/commons/changes.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/commons/changes.html (original)
+++ websites/staging/xmlgraphics/trunk/content/commons/changes.html Wed Oct 24 04:26:06 2012
@@ -130,10 +130,10 @@ $(document).ready(function () {
<!-- <div id="breadcrumb"><a href="/">Home</a> » <a href="/commons/">Commons</a></div> -->
<div class="section-content"><h1 id="history-of-changes">History of Changes</h1>
<p><a href="changes.rss"></a> </p>
-<h2 id="introduction-and-explanation-of-symbols-wzxhzdk0wzxhzdk1">Introduction and explanation of symbols <a id="introduction"></a></h2>
+<h2 id="introduction-and-explanation-of-symbols-wzxhzdk0wzxhzdk1">Introduction and explanation of symbols <a id="introduction"></a></h2>
<p>Changes are sorted by "type" and then chronologically with the most recent at the top. These symbols denote the various action types:<icon alt="add" src="images/add.jpg"></icon>=add,<icon alt="fix" src="images/fix.jpg"></icon>=fix,<icon alt="remove" src="images/remove.jpg"></icon>=remove,<icon alt="update" src="images/update.jpg"></icon>=update</p>
-<h2 id="version-trunk-na-wzxhzdk10wzxhzdk11">Version Trunk (n/a) <a id="version_Trunk"></a></h2>
-<h3 id="changes-to-the-code-base-wzxhzdk12wzxhzdk13">Changes to the Code Base # <a id="Code_Trunk"></a></h3>
+<h2 id="version-trunk-na-wzxhzdk10wzxhzdk11">Version Trunk (n/a) <a id="version_Trunk"></a></h2>
+<h3 id="changes-to-the-code-base-wzxhzdk12wzxhzdk13">Changes to the Code Base <a id="Code_Trunk"></a></h3>
<ul>
<li>
<p><icon alt="fix" src="images/fix.jpg"></icon>Support rdf:resource attributes in XMP. Committed by GA. Thanks to Brian Carlson. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=50497">50497</a> .</p>
@@ -169,12 +169,12 @@ $(document).ready(function () {
<p><icon alt="update" src="images/update.jpg"></icon>Various code style fixes Committed by JM. Thanks to Glenn Adams. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=49703">49703</a> .</p>
</li>
</ul>
-<h3 id="contributors-to-this-release-wzxhzdk14wzxhzdk15">Contributors to this release # <a id="contributors_Trunk"></a></h3>
+<h3 id="contributors-to-this-release-wzxhzdk14wzxhzdk15">Contributors to this release <a id="contributors_Trunk"></a></h3>
<p>We thank the following people for their contributions to this release.</p>
<p>This is a list of all people who participated as committers:<br></br>Glenn Adams (GA), Jeremias Märki (JM), (PH).</p>
<p>This is a list of other contributors:<br></br>Brian Carlson, Florian Barbera Vila Bollain, Glenn Adams, JM and Mehdi Houshmand, Joshua Marquart, Sebastian Bazley.</p>
-<h2 id="version-14-7-july-2010-wzxhzdk20wzxhzdk21">Version 1.4 (7 July 2010) <a id="version_1.4"></a></h2>
-<h3 id="changes-to-the-code-base-wzxhzdk22wzxhzdk23">Changes to the Code Base # <a id="Code_1.4"></a></h3>
+<h2 id="version-14-7-july-2010-wzxhzdk20wzxhzdk21">Version 1.4 (7 July 2010) <a id="version_1.4"></a></h2>
+<h3 id="changes-to-the-code-base-wzxhzdk22wzxhzdk23">Changes to the Code Base <a id="Code_1.4"></a></h3>
<ul>
<li>
<p><icon alt="add" src="images/add.jpg"></icon>Added getter and setter for enabling/disabling comments in PSGenerator. Committed by JM. Thanks to Julien Aymé. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=49250">49250</a> .</p>
@@ -264,12 +264,12 @@ $(document).ready(function () {
<p><icon alt="update" src="images/update.jpg"></icon>Moved method disableClipping from AbstractPSDocumentGraphics2D to PSGraphics2D. Committed by JM. Thanks to Julien Aymé. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=49337">49337</a> .</p>
</li>
</ul>
-<h3 id="contributors-to-this-release-wzxhzdk24wzxhzdk25">Contributors to this release # <a id="contributors_1.4"></a></h3>
+<h3 id="contributors-to-this-release-wzxhzdk24wzxhzdk25">Contributors to this release <a id="contributors_1.4"></a></h3>
<p>We thank the following people for their contributions to this release.</p>
<p>This is a list of all people who participated as committers:<br></br>Adrian Cumiskey (AC), Chris Bowditch (CB), Jeremias Märki (JM), Max Berger (MB), Vincent Hennebert (VH).</p>
<p>This is a list of other contributors:<br></br>Andrey Koltunov, Calixte Denizet, JiÅà Kunhart, Julien Aymé, Peter Hancock, Venkat Reddy.</p>
-<h2 id="version-131-11-june-2008-wzxhzdk30wzxhzdk31">Version 1.3.1 (11 June 2008) <a id="version_1.3.1"></a></h2>
-<h3 id="changes-to-the-code-base-wzxhzdk32wzxhzdk33">Changes to the Code Base # <a id="Code_1.3.1"></a></h3>
+<h2 id="version-131-11-june-2008-wzxhzdk30wzxhzdk31">Version 1.3.1 (11 June 2008) <a id="version_1.3.1"></a></h2>
+<h3 id="changes-to-the-code-base-wzxhzdk32wzxhzdk33">Changes to the Code Base <a id="Code_1.3.1"></a></h3>
<ul>
<li>
<p><icon alt="add" src="images/add.jpg"></icon>Added fallbacks for Type 1 fonts which don't have the normal "one", "two" etc. glyphs, but actually only provide "oneoldstyle", "twooldstyle" etc. Committed by JM.</p>
@@ -308,11 +308,11 @@ $(document).ready(function () {
<p><icon alt="fix" src="images/fix.jpg"></icon>Bugfix for EOFException when pre-loading very small PNG images (file size < 88 bytes). Committed by JM.</p>
</li>
</ul>
-<h3 id="contributors-to-this-release-wzxhzdk34wzxhzdk35">Contributors to this release # <a id="contributors_1.3.1"></a></h3>
+<h3 id="contributors-to-this-release-wzxhzdk34wzxhzdk35">Contributors to this release <a id="contributors_1.3.1"></a></h3>
<p>We thank the following people for their contributions to this release.</p>
<p>This is a list of all people who participated as committers:<br></br>Jeremias Märki (JM), Max Berger (MB).</p>
-<h2 id="version-13-07-feb-2008-wzxhzdk38wzxhzdk39">Version 1.3 (07 Feb 2008) <a id="version_1.3"></a></h2>
-<h3 id="changes-to-the-code-base-wzxhzdk40wzxhzdk41">Changes to the Code Base # <a id="Code_1.3"></a></h3>
+<h2 id="version-13-07-feb-2008-wzxhzdk38wzxhzdk39">Version 1.3 (07 Feb 2008) <a id="version_1.3"></a></h2>
+<h3 id="changes-to-the-code-base-wzxhzdk40wzxhzdk41">Changes to the Code Base <a id="Code_1.3"></a></h3>
<ul>
<li>
<p><icon alt="add" src="images/add.jpg"></icon>Image Loading: Support for passing in SAXSource instance. Committed by JM. Thanks to Adam Strzelecki. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=44466">44466</a> .</p>
@@ -354,12 +354,12 @@ $(document).ready(function () {
<p><icon alt="update" src="images/update.jpg"></icon>PostScript: Improved PSImageUtils by introducing the ImageEncoder interface and allowing for streams instead of byte arrays for data transfer which can lower memory consumption. Committed by JM.</p>
</li>
</ul>
-<h3 id="contributors-to-this-release-wzxhzdk42wzxhzdk43">Contributors to this release # <a id="contributors_1.3"></a></h3>
+<h3 id="contributors-to-this-release-wzxhzdk42wzxhzdk43">Contributors to this release <a id="contributors_1.3"></a></h3>
<p>We thank the following people for their contributions to this release.</p>
<p>This is a list of all people who participated as committers:<br></br>Chris Bowditch (CB), Jeremias Märki (JM).</p>
<p>This is a list of other contributors:<br></br>Adam Strzelecki, Adrian Cumiskey, Max Berger, Sergey Orlov.</p>
-<h2 id="version-12-21-july-2007-wzxhzdk48wzxhzdk49">Version 1.2 (21 July 2007) <a id="version_1.2"></a></h2>
-<h3 id="changes-to-the-code-base-wzxhzdk50wzxhzdk51">Changes to the Code Base # <a id="Code_1.2"></a></h3>
+<h2 id="version-12-21-july-2007-wzxhzdk48wzxhzdk49">Version 1.2 (21 July 2007) <a id="version_1.2"></a></h2>
+<h3 id="changes-to-the-code-base-wzxhzdk50wzxhzdk51">Changes to the Code Base <a id="Code_1.2"></a></h3>
<ul>
<li>
<p><icon alt="add" src="images/add.jpg"></icon>Added support for CMYK and GRAY color spaces for PSGenerator (moved there from PSGraphics2D). Committed by JM. Thanks to Adrian Cumiskey. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=42507">42507</a> .</p>
@@ -371,12 +371,12 @@ $(document).ready(function () {
<p><icon alt="fix" src="images/fix.jpg"></icon>Fixed the PDF/A namespace according to ISO-19005-1:2005/Cor.1:2007 and deprecated the use of the draft PDF/A namespace used by Adobe Acrobat 7.x. Committed by JM.</p>
</li>
</ul>
-<h3 id="contributors-to-this-release-wzxhzdk52wzxhzdk53">Contributors to this release # <a id="contributors_1.2"></a></h3>
+<h3 id="contributors-to-this-release-wzxhzdk52wzxhzdk53">Contributors to this release <a id="contributors_1.2"></a></h3>
<p>We thank the following people for their contributions to this release.</p>
<p>This is a list of all people who participated as committers:<br></br>Jeremias Märki (JM).</p>
<p>This is a list of other contributors:<br></br>Adrian Cumiskey.</p>
-<h2 id="version-11-22-dec-2006-wzxhzdk58wzxhzdk59">Version 1.1 (22 Dec 2006) <a id="version_1.1"></a></h2>
-<h3 id="changes-to-the-code-base-wzxhzdk60wzxhzdk61">Changes to the Code Base # <a id="Code_1.1"></a></h3>
+<h2 id="version-11-22-dec-2006-wzxhzdk58wzxhzdk59">Version 1.1 (22 Dec 2006) <a id="version_1.1"></a></h2>
+<h3 id="changes-to-the-code-base-wzxhzdk60wzxhzdk61">Changes to the Code Base <a id="Code_1.1"></a></h3>
<ul>
<li>
<p><icon alt="add" src="images/add.jpg"></icon>Added the start of an XMP metadata framework. Committed by JM.</p>
@@ -397,19 +397,19 @@ $(document).ready(function () {
<p><icon alt="fix" src="images/fix.jpg"></icon>Bugfix: The generation of the PostScript setdash command was assuming that only integer values can be used but that isn't the case. Committed by JM.</p>
</li>
</ul>
-<h3 id="contributors-to-this-release-wzxhzdk62wzxhzdk63">Contributors to this release # <a id="contributors_1.1"></a></h3>
+<h3 id="contributors-to-this-release-wzxhzdk62wzxhzdk63">Contributors to this release <a id="contributors_1.1"></a></h3>
<p>We thank the following people for their contributions to this release.</p>
<p>This is a list of all people who participated as committers:<br></br>Jeremias Märki (JM).</p>
<p>This is a list of other contributors:<br></br>Max Berger.</p>
-<h2 id="version-10-17-apr-2006-wzxhzdk68wzxhzdk69">Version 1.0 (17 Apr 2006) <a id="version_1.0"></a></h2>
-<h3 id="changes-to-the-code-base-wzxhzdk70wzxhzdk71">Changes to the Code Base # <a id="Code_1.0"></a></h3>
+<h2 id="version-10-17-apr-2006-wzxhzdk68wzxhzdk69">Version 1.0 (17 Apr 2006) <a id="version_1.0"></a></h2>
+<h3 id="changes-to-the-code-base-wzxhzdk70wzxhzdk71">Changes to the Code Base <a id="Code_1.0"></a></h3>
<ul>
<li><icon alt="add" src="images/add.jpg"></icon>Initial release with several components from Batik and FOP: Image codecs, Image writer abstraction, I/O classes, Java2D helpers, PostScript library with Graphics2D implementation. Committed by JM.</li>
</ul>
-<h3 id="contributors-to-this-release-wzxhzdk72wzxhzdk73">Contributors to this release # <a id="contributors_1.0"></a></h3>
+<h3 id="contributors-to-this-release-wzxhzdk72wzxhzdk73">Contributors to this release <a id="contributors_1.0"></a></h3>
<p>We thank the following people for their contributions to this release.</p>
<p>This is a list of all people who participated as committers:<br></br>Jeremias Märki (JM).</p>
-<h2 id="all-committers-wzxhzdk76wzxhzdk77">All Committers <a id="all-committers"></a></h2>
+<h2 id="all-committers-wzxhzdk76wzxhzdk77">All Committers <a id="all-committers"></a></h2>
<p>This is a list of all people who have ever participated as committers on this project.</p>
<ul>
<li>
Modified: websites/staging/xmlgraphics/trunk/content/commons/download.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/commons/download.html (original)
+++ websites/staging/xmlgraphics/trunk/content/commons/download.html Wed Oct 24 04:26:06 2012
@@ -129,9 +129,9 @@ $(document).ready(function () {
<div id="content" class="grid_16">
<!-- <div id="breadcrumb"><a href="/">Home</a> » <a href="/commons/">Commons</a></div> -->
<div class="section-content"><h1 id="download-apachewzxhzdk0-xml-graphics-commons">Download Apache™ XML Graphics Commons</h1>
-<h2 id="download-a-release-wzxhzdk1wzxhzdk2">Download a Release <a id="release"></a></h2>
+<h2 id="download-a-release-wzxhzdk1wzxhzdk2">Download a Release <a id="release"></a></h2>
<p>Source ("-src") and binary ("-bin") distributions can be downloaded from a <a href="http://www.apache.org/dyn/closer.cgi/xmlgraphics/commons">Apache™ XML Graphics Commons Distribution Mirror</a> .</p>
-<h2 id="download-from-subversion-wzxhzdk4wzxhzdk5">Download from Subversion <a id="svn"></a></h2>
+<h2 id="download-from-subversion-wzxhzdk4wzxhzdk5">Download from Subversion <a id="svn"></a></h2>
<p>The latest source code is available directly from the Subversion repository:</p>
<table>
<thead>
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: commits-help@xmlgraphics.apache.org