Batik is a Java(tm) technology based toolkit for applications or applets that want to use images in the Scalable Vector Graphics (SVG) format for various purposes, such as viewing, generation or manipulation.

It is the ambition of this project to give developers a set of core modules which can be used together or individually to support specific SVG solutions. Examples of modules are an SVG parser, an SVG generator and an SVG DOM implementations. Another ambition of the Batik project is to make it highly extensible (for example, Batik allows the developer to handle custom SVG tags). Even though the goal of the project is to provide a set of core modules, one of the deliveries is a full fledged SVG Browser implementation which validates the various modules and their inter-operability.

Batik provides building blocks that developers can assemble in various ways in their Java technology applications or applets to generate, parse, view or convert SVG contents. For example, Batik contains a Swing component that can add SVG viewing capability to all Java technology applications or applets. Batik can also be used to generate SVG on a client or on a server, and Batik can convert SVG content into other formats such as JPEG, PNG or Tiff or other formats ( transcoder API). Batik's goal is to make it easy for developers to handle SVG content for many purposes, client-side or server-side, as illustrated in the diagram.

SVG (Scalable Vector Graphics) is an open-standard language for describing two-dimensional (2D) graphics in XML. It is a Recommendation from the W3C. SVG lets you describe rich images with features such as gradients, transparency, filter effects and animation.

SVG has three types of graphic objects: shapes (e.g., paths consisting of straight lines and curves), images and text. Graphical objects can be grouped, styled, transformed and composited (e.g., drawn with transparency). SVG has a large set of static features which includes nested transformations, clipping paths, masking and filter effects.

In addition, SVG images can be dynamic and interactive. A rich set of event handlers such as 'onmouseover' and 'onclick' can be assigned to any SVG graphical object. These handlers can invoke scripts, which, in response to an event, can dynamically modify the SVG graphic through the SVG Document Object Model (DOM) API, allowing, for example scripts to change the color or location of graphical elements in reaction to events.

SVG graphical elements can be animated through scripting. Alternatively, animation sequences can be expressed directly in XML because SVG leverages the SMIL specification for multimedia, another W3C specification.

Batik contains several core modules which can be used independently or jointly to generate SVG content (see the SVG Generator, an SVG DOM implementation documentation) view SVG content (see the JSVGCanvas) or convert to and from the SVG format (see the SVG Transcoders tutorial).

In addition, Batik contains low level modules such as an object oriented Graphic Vector Toolkit (GVT), a set of low level parsers(SVG Parser) specific to the SVG syntax and a set of extensions to the Java 2D API (such as sophisticated fill types and filter effects).

Finally, Batik comes with packaged applications to help developers get familiar with the code and be quickly able to use the various modules: an SVG browser (in the org.apache.batik.apps.svgbrowser package) an SVG rasterizer (in the org.apache.batik.apps.rasterizer package), a Font converter (in the org.apache.batik.apps.ttf2svg package) and an SVG pretty printer (in the org.apache.batik.apps.svgpp package).

The Squiggle SVG browser (here) can display SVG documents and lets the user zoom, pan and rotate any SVG document, view the SVG source, link between SVG documents, view a tree representation of the SVG DOM and more. One important component of the SVG viewer is the org.apache.batik.swing.JSVGCanvas component which can be plugged in any Java application or applet to provide SVG viewing capability.

The SVG rasterizer (here) lets the user convert SVG files to raster formats such as JPEG, PNG or Tiff . It contains an extensible mechanism so that arbitrary raster formats can be added. For example, the rasterizer lets you create one SVG file with a special effect (e.g., shadows, gradients, etc...), turn it into an PNG image, then modify the SVG source (e.g., modify a piece of text or a color), and generate another PNG image from it. This way, you can easily generate a series of images sharing a common theme or look and feel to post on a web site (note that the rasterizer can also be used on a web server to do this conversion automatically).

The SVG Font Converter(here) lets the user easily create an SVG Font for a set of characters from a True Type Font file. That SVG Font definition can be embedded in a document using the characters. This allows users to create SVG documents that are self contained and do not rely on system fonts, and guarantees that the SVG file will be displayed exactly as it was authored on all platforms.

The SVG Pretty Printer(here) is a convenience tool to pretty print an SVG document, which means that you can reformat any existing SVG document to produce a properly formatted and highly legible version.

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).

The Squiggle SVG Browser and the rasterizer are examples of some of the types of applications Batik allows. Batik's architecture allows the modules to be used in many different ways so other applications are possible, such as using the transcoders (to other vector formats, such as PDF, for example). Furthermore, the Graphic Vector Toolkit could be used to render other graphic formats such as XHTML.

You can see an online demonstration of the Squiggle SVG browser on the demo page. Alternatively, you can download Batik or see screenshots of the Batik SVG viewer, images created from the rasterizer and an example of how to use the SVGGraphics2D generator.

Apache's mission is to allow the web to be an open environment and to remain an open environment. Batik as an open source implementation of a key format for today's and tomorrow's web fits well in this mission.

Batik is used in Cocoon for server side rasterization of SVG images. In addition, the Batik is used in the FOP project to convert SVG images to PDF format.

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:

• CSIRO
• ILOG
• Koala Team
• Eastman Kodak Company
• Sun Microsystems, Inc.

In addition, the Batik project is supported by IBM.

We encourage anyone to participate. As with all ASF project, 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.

The Batik Project is an open volunteer project in the spirit of the Apache Software Foundation (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.

The process for contributing to Batik is the same as for other Java projects at Apache. A formal description of that process can be found on the Jakarta web site.(Batik Commiters and Batik Contributors)

For direct participation, we suggest you to subscribe to the Batik mailing list (follow the link for information on how to subscribe and to access the mail list archives), and to checkout the latest code.

The SVG implementation is not complete (status), and there is more work to do to achieve a fully functional viewer.

Batik 1.1 supports all the static SVG features, linking and a limited support for scripting. Work has started on dynamic features. Scripting support with the 1.5 beta releases, and declarative animation (known as SMIL animation) will be supported in the 2.0 release.

The type of applications (e.g., transcoding applications) that can or will be added to Batik depends on contributions and feedback.

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.

You can get a list of tools exporting SVG from the SVG implementation section of the SVG Home page on the W3C web site. You can also imagine building a tool on top of Batik: feel free to contribute!

Authoring is one way of creating SVG content, and graphic authoring packages are useful for that purpose. However, there are many types of graphics which can be generated, such as stock quotes, statistical data, etc. For these types of graphics, there are many ways to generate SVG content. For example, if your data (say stock information) is contained in an XML document, you could use XSLT to transform your XML data into SVG. If your data comes from a database and you retrieve that data in a servlet on a Web server (e.g., using JDBC), you could use the Java binding for the DOM API to generate an SVG document from the data base data. You could also use Batik's SVG generator and use the Java 2D API to generate that graphic.

The following URLs will be useful to learn more about each of these solutions:

• Xalan for XSLT
• Xerces and Crimson for the DOM API
• SVG Generator

There are many companies supporting SVG and you will find a list of available implementations on the W3C's SVG implementation page

The SVG specification is available from the W3C Web site

The following status page shows how much of the SVG specification Batik implements by showing which of the tests in the SVG Basic Effectivity test suite Batik successfully passes.

Being an XML grammar means SVG can leverage work done around XML, and SVG actually leverages other grammars such as XLink, for linking and SMIL for the animation.

Beyond the use and mix with other XML syntaxes, being an XML grammar lets SVG benefit from the pletora of XML tools that make it so easy to manipulate, generate, search and edit SVG files.

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.

We think that Batik gracefully evokes Java, graphics and high-quality, terms that constitute the core of the toolkit.

The following page shows examples of what Batik textures look like.

Batik is written in the Java language and requires a version 1.3 implementation at this time.

You will need the JDK 1.3 to run Batik.

To install Batik you need to download the binary or source distribution and unzip it on your computer.

You can have a look at the installation instructions for more information.

You can submit bug fixes and patches to the Batik developers mailing list and you can enter bugs in Bugzilla.

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).

Batik can recognize the following scripting languages:

• ECMAScript thanks to the Mozilla Rhino JavaScript engine included in the distribution.
• Python for which you need to download the JPython engine.
• Tcl for which you need to download the Jacl engine.

To get more information on how to install optional scripting languages you can have a look at the installation instructions.

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/extbefore running any of the Batik's applications.

When running from the source distribution you automatically get the service provider entries for the Batik extension tags (regularPolygon, and star for example). We chose not to include these by default in the binary distribution for the Batik applications.

You can make the Batik extension tags available by putting the 'lib/batik-extensions.jar' file on the java class path.

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 add lib/batik-extensions.jar to your class path.

Both FOP and Batik use the org.w3c.xxx 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 w3c.jar file FOP uses. However, if the w3c.jar, file which 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 get a failure.

The solution is to either repackage the w3c.jar file with the classes in the Batik distribution (you will need the Batik source distrib to do that), or you will need to make sure the Batik jars are loaded before the w3c.jar, for example by putting them before the w3c.jar file in your classpath. If you are copying your jar files to ..jre/lib/ext, you can simply remove the FOP w3c.jar file from that directory.

You just have to follow the instructions posted on the XML Apache CVS page.

As of Mac OS X release 10.1.1 there still appear to be problems in the Apple implementation of the Java 2D API's. The true source of these problems and/or work arounds have yet to be identified (although the problems appear to be closely tied to a 'gstack underflow' error messages from the Apple JVM). We are interested in finding the source of these problems and reasonable work arounds, 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).

Other things to be aware of on Mac OS X, due to fixes for other problems with Java 2D under Mac OS X, you may find that some filtering operations take significantly more memory than on other platforms. This will be especially true for deeply nested filter trees (where the result of one filtering operation is filtered by another filtering operation).

Finally a few hints on avoiding problems under Mac OS X. The bugs seems to be triggered by filters (I've never seen a pure raster SVG document 'mess up'). The use of the 'filterRes' attribute on the 'filter' element seems especially problematic. The bug isn't 100% reproducible, so while some content has the problem a lot if you play with the document enough it will often 'fix' it's self for a while, then after a while it will go back to being broken (this makes me think the problem may be some sort of race condition in the JVM).

The Batik demo 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 execption thrown.

This is happening because the Java Web Start jar file (javaws.jar in /Applications/Utilities/Java Web Start/Content/MacOS) contains an older version of the DOM bindings.

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.