You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@xmlgraphics.apache.org by ps...@apache.org on 2012/12/05 09:19:31 UTC

svn commit: r1417307 [2/14] - in /xmlgraphics/site/trunk/content: ./ batik/ batik/dev/ batik/tools/ batik/using/ batik/using/scripting/ commons/ fop/ fop/0.95/ fop/1.0/ fop/1.1/ fop/dev/ fop/dev/design/ fop/trunk/

Modified: xmlgraphics/site/trunk/content/batik/status.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/batik/status.mdtext?rev=1417307&r1=1417306&r2=1417307&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/batik/status.mdtext (original)
+++ xmlgraphics/site/trunk/content/batik/status.mdtext Wed Dec  5 08:19:09 2012
@@ -8,17 +8,17 @@ This page details information about Bati
 
 
 Not supported
-:    
+:
 If a feature is<span class="no">not</span>supported, this means that Batik performs no useful processing for it. This feature could be silently ignored or an exception might be thrown when trying to use it.
 
 
 Partially supported
-:    
+:
 If a feature is<span class="partial">partially</span>suppored, this means that Batik performs some processing for it, but there are known bugs with this processing.
 
 
 Fully supported
-:    
+:
 If a feature is<span class="yes">fully</span>supported, this means that Batik performs the correct processing for it, as detailed in the relevant specification.
 
 Note that the information on this page is based on the code in the Subversion repository trunk.
@@ -65,7 +65,7 @@ Note that all presentation attributes ar
 |-------|
 | systemLanguage | yes |  |
 |----------------|
-| target | no | While `target` is not supported, new windows can be opened with `xlink:show="new"` . |
+| target | no | While `target` is not supported, new windows can be opened with `xlink:show="new"`. |
 |--------|
 | transform | yes |  |
 |-----------|
@@ -3269,7 +3269,7 @@ Note that all presentation attributes ar
 |--------------|
 |  | <a name="svg:style"></a>svg:style |  |  |
 |-----------|--|--|
-|  |  | <notes>The `:hover` , `:link` , `:visited` , `:active` and `:focus` pseudo-classes are not supported in selectors.</notes> |
+|  |  | <notes>The `:hover`, `:link`, `:visited`, `:active` and `:focus` pseudo-classes are not supported in selectors.</notes> |
 | Attributes |
 |------------|
 | id | yes |  |
@@ -5446,7 +5446,7 @@ The table below lists the SVG DOM interf
 |---|
 | Operations |
 |------------|
-| matrixTransform | partial | Not implemented for any `SVGPoint` in an `SVGPointList` . |
+| matrixTransform | partial | Not implemented for any `SVGPoint` in an `SVGPointList`. |
 |-----------------|
 |  | <a name="SVGPointList"></a>SVGPointList |  |  |
 |--------------|--|--|
@@ -5879,21 +5879,21 @@ The current SVG document.
 </div><div class="object-property-header">event</div><div class="object-property-desc">
 The most recently dispatched event object.
 </div><div class="object-property-header">evt</div><div class="object-property-desc">
-An alias for `event` .
+An alias for `event`.
 </div><div class="object-property-header">location</div><div class="object-property-desc">
 Implementation of the [Location](http://www.w3.org/TR/SVGTiny12/svgudom.html#dom__Location) interface. Methods `assign` and `reload` are available.
 This interface is available since version 1.8.</div><div class="object-property-header">window</div><div class="object-property-desc">
 The global object (a self-reference).
 </div><div class="object-section-header">Function properties</div><div class="object-property-header">alert<span class="object-property-func-params">(message)</span></div><div class="object-property-desc">
-Displays an alert dialog with the specified `message` .
+Displays an alert dialog with the specified `message`.
 </div><div class="object-property-header">clearInterval<span class="object-property-func-params">(intervalID)</span></div><div class="object-property-desc">
-Cancels an interval that was set by a call to `setInterval` . The `intervalID` must be an object that has been returned by a previous `setInterval` call.
+Cancels an interval that was set by a call to `setInterval`. The `intervalID` must be an object that has been returned by a previous `setInterval` call.
 </div><div class="object-property-header">clearTimeout<span class="object-property-func-params">(timeoutID)</span></div><div class="object-property-desc">
-Cancels a timeout that was set by a call to `setTimeout` . The `timeoutID` must be an object that has been returned by a previous `clearTimeout` call.
+Cancels a timeout that was set by a call to `setTimeout`. The `timeoutID` must be an object that has been returned by a previous `clearTimeout` call.
 </div><div class="object-property-header">confirm<span class="object-property-func-params">(message)</span></div><div class="object-property-desc">
-Displays a confirmation dialog with the specified `message` . The window has an OK and a Cancel button. The function returns `true` if the user clicks on the OK button, and `false` otherwise.
+Displays a confirmation dialog with the specified `message`. The window has an OK and a Cancel button. The function returns `true` if the user clicks on the OK button, and `false` otherwise.
 </div><div class="object-property-header">getURL<span class="object-property-func-params">(uri, function[, encoding])</span></div><div class="object-property-desc">
-Gets data from the given `uri` . This method returns immediately and the given `function` is called when the data is fully downloaded. The optional `encoding` argument is the encoding to assume the data is in, defaulting to UTF-8. The argument passed to the function is an object with three properties:
+Gets data from the given `uri`. This method returns immediately and the given `function` is called when the data is fully downloaded. The optional `encoding` argument is the encoding to assume the data is in, defaulting to UTF-8. The argument passed to the function is an object with three properties:
 
 
 
@@ -5907,7 +5907,7 @@ content
 :    A string holding the data.</div><div class="object-property-header">parseXML<span class="object-property-func-params">(text, document)</span></div><div class="object-property-desc">
 Parses and returns a `DocumentFragment` object. `text` is the string that is to be parsed as XML data, and `document` is a `Document` that will be used for creating new DOM objects.
 </div><div class="object-property-header">postURL<span class="object-property-func-params">(uri, content, function[, type, encoding])</span></div><div class="object-property-desc">
-Sends data to the given `uri` . This method returns immediately and the given `function` is called when the data is fully downloaded. The optional `type` argument will specify the `Content-Type` HTTP header to use, defaulting to `text/plain` . The optional `encoding` argument is the encoding to assume the data is in, defaulting to UTF-8. The argument passed to the function is an object with three properties:
+Sends data to the given `uri`. This method returns immediately and the given `function` is called when the data is fully downloaded. The optional `type` argument will specify the `Content-Type` HTTP header to use, defaulting to `text/plain`. The optional `encoding` argument is the encoding to assume the data is in, defaulting to UTF-8. The argument passed to the function is an object with three properties:
 
 
 
@@ -5921,7 +5921,7 @@ content
 :    A string holding the data.</div><div class="object-property-header">printNode<span class="object-property-func-params">(node)</span></div><div class="object-property-desc">
 Returns a string that is the serialization of the given DOM node.
 </div><div class="object-property-header">prompt<span class="object-property-func-params">(message[, defaultValue])</span></div><div class="object-property-desc">
-Displays an input dialog with the specified `message` . The `defaultValue` parameter specifies the initial contents of the text box in the window. The function returns the string entered by the user, or null if the window was cancelled.
+Displays an input dialog with the specified `message`. The `defaultValue` parameter specifies the initial contents of the text box in the window. The function returns the string entered by the user, or null if the window was cancelled.
 </div><div class="object-property-header">setInterval<span class="object-property-func-params">(script, interval)</span></div><div class="object-property-desc">
 Evaluates the given `script` repeatedly after the specified amount of time. The value for `script` must be either a string, which is evaluated by `eval` every interval, or an ECMAScript function object, which is called every interval. This method does not stall the script: the evaluation is scheduled and the script continues its execution. The function returns an object that can be passed to the `clearInterval` function.
 </div><div class="object-property-header">setTimeout<span class="object-property-func-params">(script, timeout)</span></div><div class="object-property-desc">
@@ -6411,7 +6411,7 @@ The table below lists the test cases fro
 |------------------|
 |  [styling-css-05-b](http://www.w3.org/Graphics/SVG/Test/20061213/svg/styling-css-05-b.svg)  | yes |  |
 |------------------|
-|  [styling-css-06-b](http://www.w3.org/Graphics/SVG/Test/20061213/svg/styling-css-06-b.svg)  | no | The `:hover` , `:link` , `:visited` , `:active` and `:focus` pseudo-classes are not supported in selectors. |
+|  [styling-css-06-b](http://www.w3.org/Graphics/SVG/Test/20061213/svg/styling-css-06-b.svg)  | no | The `:hover`, `:link`, `:visited`, `:active` and `:focus` pseudo-classes are not supported in selectors. |
 |------------------|
 |  [styling-inherit-01-b](http://www.w3.org/Graphics/SVG/Test/20061213/svg/styling-inherit-01-b.svg)  | yes |  |
 |----------------------|

Modified: xmlgraphics/site/trunk/content/batik/tools/browser.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/batik/tools/browser.mdtext?rev=1417307&r1=1417306&r2=1417307&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/batik/tools/browser.mdtext (original)
+++ xmlgraphics/site/trunk/content/batik/tools/browser.mdtext Wed Dec  5 08:19:09 2012
@@ -24,13 +24,13 @@ where:
 
 
 
- **-font-size**  *font-size* 
-:    
+ **-font-size**  *font-size*
+:
 specifies the font size to use in windows and menus, and
 
 
- *[URIs]* 
-:    
+ *[URIs]*
+:
 specifies the URIs for the SVG documents the browser should open when it starts.
 
 For example:
@@ -52,7 +52,7 @@ To start the browser you should:
 
 - Open a command line window and change to the `xml-batik` or <code>batik- *version*</code> directory where the Batik distribution was expanded
 
-- 
+-
 For Windows, type the following at the command prompt:
 build squiggle
 and for Unix and Mac OS X:
@@ -79,15 +79,15 @@ The following image shows the result of 
 The browser has several features to view and browse SVG documents:
 
 
--  [Opening a local SVG file](#localFile) 
+-  [Opening a local SVG file](#localFile)
 
--  [Opening an SVG file from the web](#urlFile) 
+-  [Opening an SVG file from the web](#urlFile)
 
--  [Using the location text field to view an SVG file](#locationBar) 
+-  [Using the location text field to view an SVG file](#locationBar)
 
--  [Browsing SVG files](#browsing) 
+-  [Browsing SVG files](#browsing)
 
--  [Viewing multiple SVG files](#viewingMultiple) 
+-  [Viewing multiple SVG files](#viewingMultiple)
 
 ### Opening a local SVG file <a id="localFile"></a>
 
@@ -106,24 +106,24 @@ When you know the URL of the document yo
 
 ## Browsing SVG files <a id="browsing"></a>
 
-As with HTML content, it is common to navigate back and forth between SVG files (remember that SVG files contain hyperlinks, just like HTML does) and, as described later in this document, it is possible to [zoom](#zoomInOut) into SVG documents, [pan](#panning) and [rotate](#rotating) .
+As with HTML content, it is common to navigate back and forth between SVG files (remember that SVG files contain hyperlinks, just like HTML does) and, as described later in this document, it is possible to [zoom](#zoomInOut) into SVG documents, [pan](#panning) and [rotate](#rotating).
 <div class="figure"> ![Screnshot of Squiggle showing the 'Go' menu](images/svgviewerBrowsing.png "") </div>
 Squiggle offers multiple features to help you browse SVG files:
 
 
 
 Navigating between files
-:    
+:
 The **Go→Back** menu item (or the **Ctrl-left arrow** keyboard accelerator) and the **Go→Forward** menu item (or the **Ctrl-right arrow** keyboard accelerator) let you move to the previous and next visited SVG documents.
 
 
 History
-:    
+:
 The **Go** menu also contains a list of previously viewed SVG documents, which gives you a way to randomly access any document you have already visited.
 
 
 Navigating between views
-:    
+:
 The **View→Previous Transform** menu item ( **Ctrl-K** ) and the **View→Next Transform** menu item ( **Ctrl-L** ) let you go to the previous or next view of the document. This is useful when, for example, you [pan](#panning) or [rotate](#rotating) the document and want to go back to the previous view you had of the document (i.e., before you panned or rotated it).
 
 ### Viewing multiple SVG files <a id="viewingMultiple"></a>
@@ -142,7 +142,7 @@ The **File→Export As** menu item of
 
 ## Inspecting the SVG source <a id="inspecting"></a>
 
-The browser offers two ways to inspect the source of an SVG document: [viewing the plain source](#viewingSource) or [viewing the document tree](#viewingTree) . Both are explained below.
+The browser offers two ways to inspect the source of an SVG document: [viewing the plain source](#viewingSource) or [viewing the document tree](#viewingTree). Both are explained below.
 
 ### Viewing the source <a id="viewingSource"></a>
 
@@ -163,7 +163,7 @@ This dialog contains several types of op
 
 
 General panel
-:    
+:
 This panel lets you choose some optional behavior:
 
 
@@ -187,12 +187,12 @@ Use a validating XML parser
 :    When on, the XML parser used to load documents will be in validating mode. This means that the document will be validated against the DTD when it is loaded, and external DTD subsets will be fetched.
 
 Security panel
-:    
+:
 This panel has options relating to the script and resource access in documents.
 
 
 Language panel
-:    
+:
 This is the panel shown in the above figure. That panel lets you select your languages. The user language can be used in SVG documents to choose between alternate contents. For example, open the `samples/moonPhases.svg` example. Then, change the user language to French and [reload](#reloading) the document ( **Ctrl-R** ). You will see that the text is now displayed in French. You can do the same with Japanese and the text will be shown in Japanese.
 
 
@@ -200,7 +200,7 @@ Stylesheet panel
 :    This panel lets you specify a user stylesheet which can override some of the default settings in viewed SVG documents. This might be useful if you want, for example, to override the font size used in text elements.
 
 Network panel
-:    
+:
 This panel lets you configure the proxy server to use if you are working from behind a firewall.
 
 ## Navigating SVG documents: zooming, panning, rotating, transform and thumbnail <a id="zooming"></a>
@@ -208,15 +208,15 @@ This panel lets you configure the proxy 
 The Batik browser offers multiple way to navigate SVG documents:
 
 
--  [Zooming in and out](#zoomInOut) 
+-  [Zooming in and out](#zoomInOut)
 
--  [Panning](#panning) 
+-  [Panning](#panning)
 
--  [Rotating](#rotating) 
+-  [Rotating](#rotating)
 
--  [Arbitrary transforms](#transform) 
+-  [Arbitrary transforms](#transform)
 
--  [Thumbnail](#thumbnail) 
+-  [Thumbnail](#thumbnail)
 
 ### Zooming in and out <a id="zoomInOut"></a>
 
@@ -250,7 +250,7 @@ It is sometimes useful to be able to rot
 
 ### Using the Transform dialog <a id="transform"></a>
 
-While the mouse and keyboard interactions give interactive way to navigate an SVG document, it is sometimes desirable to be able to define precisely the amount of [zoom](#zoomInOut) , [pan](#panning) or [rotation](#rotating) desired. The Transform dialog, available through the **View→Transform** menu ( **Ctrl-E** ) offers that feature.
+While the mouse and keyboard interactions give interactive way to navigate an SVG document, it is sometimes desirable to be able to define precisely the amount of [zoom](#zoomInOut), [pan](#panning) or [rotation](#rotating) desired. The Transform dialog, available through the **View→Transform** menu ( **Ctrl-E** ) offers that feature.
 
 ### Thumbnail <a id="thumbnail"></a>
 

Modified: xmlgraphics/site/trunk/content/batik/tools/font-converter.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/batik/tools/font-converter.mdtext?rev=1417307&r1=1417306&r2=1417307&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/batik/tools/font-converter.mdtext (original)
+++ xmlgraphics/site/trunk/content/batik/tools/font-converter.mdtext Wed Dec  5 08:19:09 2012
@@ -17,43 +17,43 @@ where:
 
 
 
- *ttf-path* 
-:    
+ *ttf-path*
+:
 specifies the TrueType Font file containing the characters to be converted,
 
 
- **-l**  *range-begin*  **-h**  *range-end* 
-:    
+ **-l**  *range-begin*  **-h**  *range-end*
+:
 specifies the range of characters (by codepoint, in decimal) to be converted,
 
 
- **-autorange** 
-:    
+ **-autorange**
+:
 automatically determines the available character range, instead of using the default, ASCII printable characters (ranging from 32 to 126),
 
 
- **-ascii** 
-:    
+ **-ascii**
+:
 forces usage of the ASCII character map in the font, instead of the Unicode character map,
 
 
- **-id**  *id* 
-:    
+ **-id**  *id*
+:
 specifies the value for the `id` attribute of the generated `font` element,
 
 
- **-o**  *output-path* 
-:    
+ **-o**  *output-path*
+:
 specifies the pathname of the output SVG document containing the generated SVG font, and
 
 
- **-testcard** 
-:    
+ **-testcard**
+:
 specifies that a sequence of SVG `text` elements should be appended to the output SVG file to test the characters in the SVG font, providing an easy way to validate that generated SVG font visually.
 
 For example:
 java -jar batik-ttf2svg.jar /usr/home/myFont.ttf -l 48 -h 57 -id MySVGFont -o mySVGFont.svg -testcard
-will convert characters 48 to 57, i.e., `'0'` to `'9'` , in the `myFont.ttf` file into their SVG equivalent in the `mySVGFont.svg` file, appending a test card so that the font can be visualized.
+will convert characters 48 to 57, i.e., `'0'` to `'9'`, in the `myFont.ttf` file into their SVG equivalent in the `mySVGFont.svg` file, appending a test card so that the font can be visualized.
 
 
 # Use cases <a id="use-cases"></a>

Modified: xmlgraphics/site/trunk/content/batik/tools/pretty-printer.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/batik/tools/pretty-printer.mdtext?rev=1417307&r1=1417306&r2=1417307&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/batik/tools/pretty-printer.mdtext (original)
+++ xmlgraphics/site/trunk/content/batik/tools/pretty-printer.mdtext Wed Dec  5 08:19:09 2012
@@ -15,11 +15,11 @@ The method for starting the pretty-print
 
 ### Using the binary distribution <a id="using-binary"></a>
 
-If you downloaded the binary distribution of Batik, you should have a file called `batik-1.6.zip` (or similar), and, after expanding that file, a jar file called `batik-svgpp.jar` . To start the pretty printer, open a console, change to the directory where you expanded the distribution (and where `batik-svgpp.jar` is located) and simply type the following at the command prompt:
+If you downloaded the binary distribution of Batik, you should have a file called `batik-1.6.zip` (or similar), and, after expanding that file, a jar file called `batik-svgpp.jar`. To start the pretty printer, open a console, change to the directory where you expanded the distribution (and where `batik-svgpp.jar` is located) and simply type the following at the command prompt:
 java -jar batik-svgpp.jar [OPTIONS] FILES
 For example, if you type:
 
- `java -jar batik-svgpp.jar samples/batikFX.svg` 
+ `java -jar batik-svgpp.jar samples/batikFX.svg`
 
 you will see the indented document written to standard output.
 
@@ -27,43 +27,43 @@ For the options:
 
 
 
- **-newline cr**  *|*  **cr-lf**  *|*  **lf** 
-:    
+ **-newline cr**  *|*  **cr-lf**  *|*  **lf**
+:
 specifies the newline character(s) generated in the printed document, the default being `lf` (Unix-style newlines),
 
 
- **-tab-width**  *number* 
-:    
+ **-tab-width**  *number*
+:
 specifies the tabulation width, the default being 4,
 
 
- **-doc-width**  *number* 
-:    
+ **-doc-width**  *number*
+:
 specifies the maximum number of columns for the whole document, the default being 80,
 
 
- **-no-format** 
-:    
+ **-no-format**
+:
 specifies that the current indentation should be preserved, useful for performing doctype or newline substitutions,
 
 
- **-xml-decl**  *string* 
-:    
+ **-xml-decl**  *string*
+:
 specifies the XML declaration,
 
 
- **-doctype change**  *|*  **remove** 
-:    
+ **-doctype change**  *|*  **remove**
+:
 specifies whether the doctype should be changed or removed,
 
 
- **-publid-id**  *string* 
-:    
+ **-publid-id**  *string*
+:
 specifies the public ID to in the doctype declaration, when `-doctype change` is specified, and
 
 
- **-system-id**  *string* 
-:    
+ **-system-id**  *string*
+:
 specifies the system ID to in the doctype declaration, when `-doctype change` is specified.
 
 For example:
@@ -80,15 +80,15 @@ If you downloaded the source distributio
 To start the pretty printer you should:
 
 
-- 
+-
 Make sure that your `JAVA_HOME` environment variable is set to your JDK installation directory.
 
 
-- 
+-
 Open a command line window and go to the `xml-batik` or<code>batik- *version* </code>directory where the Batik distribution was expanded.
 
 
-- 
+-
 For windows, type the following at the command prompt:
 build svgpp
 and for Unix:

Modified: xmlgraphics/site/trunk/content/batik/tools/rasterizer.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/batik/tools/rasterizer.mdtext?rev=1417307&r1=1417306&r2=1417307&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/batik/tools/rasterizer.mdtext (original)
+++ xmlgraphics/site/trunk/content/batik/tools/rasterizer.mdtext Wed Dec  5 08:19:09 2012
@@ -15,7 +15,7 @@ The method for starting the rasterizer d
 
 ### Using the binary distribution <a id="using-binary"></a>
 
-If you downloaded the binary distribution of Batik, you should have a file called `batik-1.6.zip` (or similar), and, after expanding that file, a jar file called `batik-rasterizer.jar` . To start the rasterizer, open a console, go to the directory where you expanded the distribution (and where `batik-rasterizer.jar` is located) and simply type the following at the command prompt:
+If you downloaded the binary distribution of Batik, you should have a file called `batik-1.6.zip` (or similar), and, after expanding that file, a jar file called `batik-rasterizer.jar`. To start the rasterizer, open a console, go to the directory where you expanded the distribution (and where `batik-rasterizer.jar` is located) and simply type the following at the command prompt:
 
 java -jar batik-rasterizer.jar FILES
 
@@ -42,7 +42,7 @@ specifies the output directory, or the o
 
  **-m**  *mime-type*
 :
-specifies the output MIME type, which should be one of `image/png` , `image/jpeg` , `image/tiff` or `application/pdf` ,
+specifies the output MIME type, which should be one of `image/png`, `image/jpeg`, `image/tiff` or `application/pdf`,
 
 
  **-w**  *width*
@@ -152,7 +152,7 @@ will generate JPEG images for all the SV
 
 ### Using the source distribution <a id="usingSource"></a>
 
-If you downloaded the source distribution of Batik, you got a zip or tar file that expanded into a directory called `xml-batik` or <code>batik- *version*</code> . In that directory, you can find build scripts for the platform you are running on. For example, there is a `build.bat` script for users of the Windows platform and there is a `build.sh` script for UNIX users.
+If you downloaded the source distribution of Batik, you got a zip or tar file that expanded into a directory called `xml-batik` or `batik- *version*`. In that directory, you can find build scripts for the platform you are running on. For example, there is a `build.bat` script for users of the Windows platform and there is a `build.sh` script for UNIX users.
 
 To start the rasterizer you should:
 
@@ -193,7 +193,7 @@ The task is able to produce four raster 
 
 The first thing to do is to compile rasterizer task classes. Download the source distribution of Batik and see the `README` file in the `contrib/rasterizertask` directory for more instructions. The build procedure works the same way as when building Batik itself.
 
-After building, ensure that the generated `batik-rasterizer.jar` and the classes (or jar file) of the rasterizer task are in your `CLASSPATH` .
+After building, ensure that the generated `batik-rasterizer.jar` and the classes (or jar file) of the rasterizer task are in your `CLASSPATH`.
 
 Next you have to define the task in your Ant project. To do this, add the following line either after the `project` start tag or after the `target` start tag in the target you are using the rasterizer task:
 
@@ -209,24 +209,24 @@ The following table lists the attributes
 
 | Attribute | Description | Required |
 |-----------|-------------|----------|
-| result | Sets the type of the result image. Only one of the following values must be used: `image/png` , `image/jpeg` , `image/tiff` and `application/pdf` . The value must be in lowercase letters. | Yes |
+| result | Sets the type of the result image. Only one of the following values must be used: `image/png`, `image/jpeg`, `image/tiff` and `application/pdf`. The value must be in lowercase letters. | Yes |
 | height | Sets the height of the result image in pixels. The task calculates the height from the SVG file if this parameter has not been set. The rasterizer keeps the aspect ratio of the SVG file even if the both `height` and `width` have been set. | No |
 | width | Sets the width of the result image in pixels. The task calculates the width from the SVG file if this parameter has not been set. The rasterizer keeps the aspect ratio of the SVG file even if the both `height` and `width` have been set. | No |
 | maxheight | Sets the maximum height of the result image in pixels. The image won’t be higher than defined in this parameter, regardless of the size set in the image itself or in other parameters. This is a floating point value. | No |
 | maxwidth | Sets the maximum width of the result image in pixels. The image won’t be wider than defined in this parameter, regardless of the size set in the image itself or in other parameters. This is a floating point value. | No |
 | quality | Sets the quality of the produced image. The value must be greater than 0 but smaller than 1, larger numbers meaning higher quality. The quality value is used only with JPEG images. The default quality value is 0.99. | No |
-| area | Defines the area in the SVG file which will be rasterized. Parts outside this area are discarded and don’t show in the result image. The area attribute value has four integers separated by commas. The first two integers set the x and y coordinates of the upper left corner of the area, respectively. The last two integers set the width and height of the area, respectively. For example, `10, 20, 100, 200` sets the rectangular area from point `10, 10` to point `110, 220` . The specified area is applied to all images if more than one file is rasterized during one task. | No |
+| area | Defines the area in the SVG file which will be rasterized. Parts outside this area are discarded and don’t show in the result image. The area attribute value has four integers separated by commas. The first two integers set the x and y coordinates of the upper left corner of the area, respectively. The last two integers set the width and height of the area, respectively. For example, `10, 20, 100, 200` sets the rectangular area from point `10, 10` to point `110, 220`. The specified area is applied to all images if more than one file is rasterized during one task. | No |
 | bg | Sets the background color of the result image. The `bg` attribute value is either three or four integers separated with commas. The four values are alpha channel, red, green, and blue, respectively. If only three values are given, then the values are red, green, and blue and the alpha channel is automatically set to 255 (opaque). All values have to between 0 and 255. The default value is none which means that background is transparent and not filled with any color. | No |
-| media | CSS media type that is used to select a CSS stylesheet. The selected stylesheet is then used to rasterize the SVG files. Only the visual media group is supported (see the [CSS2 specification](http://www.w3.org/TR/REC-CSS2/) for more information about media groups). The default value is `screen` . | No |
+| media | CSS media type that is used to select a CSS stylesheet. The selected stylesheet is then used to rasterize the SVG files. Only the visual media group is supported (see the [CSS2 specification](http://www.w3.org/TR/REC-CSS2/) for more information about media groups). The default value is `screen`. | No |
 | dpi | Resolution for the result image. The attribute value is used to compute the “pixel to millimeter” ratio used when processing SVG files. The default value is 96. | No |
-| lang | Language which is used select language specific areas from the SVG file during the rasterizing process. The valid values are defined in [RFC3066](http://www.faqs.org/rfcs/rfc3066.html) . The default value is `en` . | No |
+| lang | Language which is used select language specific areas from the SVG file during the rasterizing process. The valid values are defined in [RFC3066](http://www.faqs.org/rfcs/rfc3066.html). The default value is `en`. | No |
 | src | Name of a one input file. Use this parameter to convert just one file whose name and location are known. The `dest` parameter must also be given. | One of the following is required: `src` attribute, `srcdir` attribute or `fileset` element(s). |
 | dest | Name of a one output file. Used this with `src` parameter only. The output directory is created if it doesn’t exist. | Required if `src` is used. |
-| srcdir | Name of the input directory. `srcdir` and `fileset` elements can be combined and `srcdir` can be omitted if there is at least one `fileset` child element. `srcdir` file selection can be controlled with `include` , `exclude` , etc. child elements. Note that without control parameters the task tries to rasterize *all* files in the given directory. | One of the following is required: `src` attribute, `srcdir` attribute or `fileset` element(s). |
+| srcdir | Name of the input directory. `srcdir` and `fileset` elements can be combined and `srcdir` can be omitted if there is at least one `fileset` child element. `srcdir` file selection can be controlled with `include`, `exclude`, etc. child elements. Note that without control parameters the task tries to rasterize *all* files in the given directory. | One of the following is required: `src` attribute, `srcdir` attribute or `fileset` element(s). |
 | destdir | Name of an output directory. Use this with the `srcdir` attribute or `fileset` elements. The task generates the names of the output images by changing the suffix of the input file names to correspond the result image type. A suffix is added if the input file doesn’t have one. Output directories are created if they don’t exist. | Required if `srcdir` attribute or `fileset` elements are used. |
-| classname | Class name of the XML parser used to parse SVG images. The value can be either the complete classname with package information included or the special name `jaxp` , which means any available parser in the `CLASSPATH` that supports JAXP. See the Batik code for the default value. | No |
+| classname | Class name of the XML parser used to parse SVG images. The value can be either the complete classname with package information included or the special name `jaxp`, which means any available parser in the `CLASSPATH` that supports JAXP. See the Batik code for the default value. | No |
 
-You can use `fileset` elements to select input files and directories. See the [Ant](http://ant.apache.org/) documentation to learn how to use [filesets](http://ant.apache.org/manual/CoreTypes/fileset.html) .
+You can use `fileset` elements to select input files and directories. See the [Ant](http://ant.apache.org/) documentation to learn how to use [filesets](http://ant.apache.org/manual/CoreTypes/fileset.html).
 
 ### Examples of using the rasterizer task <a id="taskExamples"></a>
 

Modified: xmlgraphics/site/trunk/content/batik/uses.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/batik/uses.mdtext?rev=1417307&r1=1417306&r2=1417307&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/batik/uses.mdtext (original)
+++ xmlgraphics/site/trunk/content/batik/uses.mdtext Wed Dec  5 08:19:09 2012
@@ -14,34 +14,34 @@ While it is hard to track projects and p
 
 -  [The Apache FOP project](http://xmlgraphics.apache.org/fop/) uses Batik to handle SVG images. It uses the SVG rasterizer and extends the Batik transcoder architecture to offer SVG to PDF conversion.
 
--  [eDoc Studio](http://www.exurbi.com/) , a page layout package, uses the Batik SVG generator to export pages to SVG.
+-  [eDoc Studio](http://www.exurbi.com/), a page layout package, uses the Batik SVG generator to export pages to SVG.
 
 -  [ElixirTech’s ElixirReport](http://www.elixirtech.com/ElixirReport) uses Batik for charting and for its SVG component.
 
 -  [GLIPS Graffiti](http://glipssvgeditor.sourceforge.net/) is an Open Source Extensible Full Feature Native SVG Editor.
 
--  [ILOG Discovery Preview](http://www2.ilog.com/preview/Discovery/) , a free visual data analysis tool letting you visualize and edit data sets in a very wide variety of views (2D graphs and charts, various kinds of treemaps, parallel coordinates, parallel histograms and much more), uses the Batik SVG export module.
+-  [ILOG Discovery Preview](http://www2.ilog.com/preview/Discovery/), a free visual data analysis tool letting you visualize and edit data sets in a very wide variety of views (2D graphs and charts, various kinds of treemaps, parallel coordinates, parallel histograms and much more), uses the Batik SVG export module.
 
--  [ILOG JViews Component Suite](http://www.ilog.com/products/jviews) , a product for advanced visualization, uses and extends the Batik SVG export module.
+-  [ILOG JViews Component Suite](http://www.ilog.com/products/jviews), a product for advanced visualization, uses and extends the Batik SVG export module.
 
 -  [The JFreeChart Project](http://www.object-refinery.com/jfreechart/index.html) uses Batik to export charts in the SVG format.
 
--  [Lagoon](http://lagoon.sourceforge.net/) , an XML-based framework for web site maintenance, uses the Batik SVG Rasterizer to render SVG as bitmap graphics for web publishing.
+-  [Lagoon](http://lagoon.sourceforge.net/), an XML-based framework for web site maintenance, uses the Batik SVG Rasterizer to render SVG as bitmap graphics for web publishing.
 
 -  [Lords Map](http://www.throneworld.com/lords/gms/dev.html) is a program to allow players and visitors to view the current map of various campaigns. Lords Map uses Batik’s SVG DOM and SVG Generator.
 
--  [Luxor XUL](http://luxor-xul.sourceforge.net/index.html) is a free, open-source XML User Interface Language (XUL) toolkit in Java released under the GNU GPL that supports hand-picked Mozilla XUL goodies and also includes a ultra-lightweight, multi-threaded web server, a portal engine, a scripting engine, a template engine and much more. Gerard Bauer, the Luxor project lead, has written an extensive [SVG presentation](http://luxor-xul.sourceforge.net/talk/jug-nov-2002/slides.html) .
+-  [Luxor XUL](http://luxor-xul.sourceforge.net/index.html) is a free, open-source XML User Interface Language (XUL) toolkit in Java released under the GNU GPL that supports hand-picked Mozilla XUL goodies and also includes a ultra-lightweight, multi-threaded web server, a portal engine, a scripting engine, a template engine and much more. Gerard Bauer, the Luxor project lead, has written an extensive [SVG presentation](http://luxor-xul.sourceforge.net/talk/jug-nov-2002/slides.html).
 
--  [OptimalJ](http://www.optimalj.com) , a UML Class Diagram Editor for NetBeans, uses Batik to export SVG.
+-  [OptimalJ](http://www.optimalj.com), a UML Class Diagram Editor for NetBeans, uses Batik to export SVG.
 
 -  [Oracle Corp.’s JDeveloper10i](http://otn.oracle.com/products/jdev/content.html) uses Batik to export class diagrams in SVG. It uses the SVG export module.
 
 -  [Sketsa](http://www.kiyut.com/) is a vector drawing application based on Batik. With Sketsa, you can create vector graphics that can be scaled and printed at any resolution, without losing detail or clarity.
 
--  [Svolgo](http://dannyayers.com/2005/10/18/svolgo-redux/) , a Graph Visualisation/Transformation Framework for the Semantic Web Cross-model transformation, node and arc diagrams, representation in SVG. This project uses Batik’s SVG DOM implementation.
+-  [Svolgo](http://dannyayers.com/2005/10/18/svolgo-redux/), a Graph Visualisation/Transformation Framework for the Semantic Web Cross-model transformation, node and arc diagrams, representation in SVG. This project uses Batik’s SVG DOM implementation.
 
--  [Volity](http://volity.net/) is an open platform for Internet-based multiplayer casual gaming. Its official client, [Gamut](http://volity.org/projects/gamut/) , uses Batik, allowing developers to create game UI files that use ECMAScript-driven SVG.
+-  [Volity](http://volity.net/) is an open platform for Internet-based multiplayer casual gaming. Its official client, [Gamut](http://volity.org/projects/gamut/), uses Batik, allowing developers to create game UI files that use ECMAScript-driven SVG.
 
 -  [XML_svg2image](http://pear.php.net/package/XML_svg2image) is a PHP class which translates SVG files to PNG or JPEG using Batik.
 
--  [XWeb](http://xweb.sf.net) , a tool to create websites automatically out of XML input. Uses the Batik SVG Rasterizer.
+-  [XWeb](http://xweb.sf.net), a tool to create websites automatically out of XML input. Uses the Batik SVG Rasterizer.

Modified: xmlgraphics/site/trunk/content/batik/using/architecture.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/batik/using/architecture.mdtext?rev=1417307&r1=1417306&r2=1417307&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/batik/using/architecture.mdtext (original)
+++ xmlgraphics/site/trunk/content/batik/using/architecture.mdtext Wed Dec  5 08:19:09 2012
@@ -3,7 +3,7 @@ Title: Architecture overview
 #Architecture overview
 
 
-This document briefly describes the Batik architecture and the role of each of its modules. For detailed module design, you can refer to the Batik UML diagrams [Object by Design](http://opensource.objectsbydesign.com/batik/index.html) or [yWorks](http://www.yworks.com/products/yDoc/showcase/batik-1.5/) .
+This document briefly describes the Batik architecture and the role of each of its modules. For detailed module design, you can refer to the Batik UML diagrams [Object by Design](http://opensource.objectsbydesign.com/batik/index.html) or [yWorks](http://www.yworks.com/products/yDoc/showcase/batik-1.5/).
 
 The Batik modules are of one of three types: application modules, core modules and low level modules. The following figure illustrates these three module types.
 <div class="figure"> ![Batik Architecture](images/HighLevelArchitecture.png "") </div>

Modified: xmlgraphics/site/trunk/content/batik/using/dom-api.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/batik/using/dom-api.mdtext?rev=1417307&r1=1417306&r2=1417307&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/batik/using/dom-api.mdtext (original)
+++ xmlgraphics/site/trunk/content/batik/using/dom-api.mdtext Wed Dec  5 08:19:09 2012
@@ -7,9 +7,9 @@ The [Document Object Model](http://www.w
 
 ## Getting started <a id="gettingStarted"></a>
 
-The DOM API defines an interface called [DOMImplementation](http://java.sun.com/j2se/1.5.0/docs/api/org/w3c/dom/DOMImplementation.html) , 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 [Document](http://java.sun.com/j2se/1.5.0/docs/api/org/w3c/dom/Document.html) . Then, the concrete `Document` represents an XML document and also acts like a factory for the various DOM objects such as [Element](http://java.sun.com/j2se/1.5.0/docs/api/org/w3c/dom/Element.html) , [Attr](http://java.sun.com/j2se/1.5.0/docs/api/org/w3c/dom/Attr.html) and [Text](http://java.sun.com/j2se/1.5.0/docs/api/org/w3c/dom/Text.html) .
+The DOM API defines an interface called [DOMImplementation](http://java.sun.com/j2se/1.5.0/docs/api/org/w3c/dom/DOMImplementation.html), 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 [Document](http://java.sun.com/j2se/1.5.0/docs/api/org/w3c/dom/Document.html). Then, the concrete `Document` represents an XML document and also acts like a factory for the various DOM objects such as [Element](http://java.sun.com/j2se/1.5.0/docs/api/org/w3c/dom/Element.html), [Attr](http://java.sun.com/j2se/1.5.0/docs/api/org/w3c/dom/Attr.html) and [Text](http://java.sun.com/j2se/1.5.0/docs/api/org/w3c/dom/Text.html).
 
-How to get an instance of the `DOMImplementation` interface depends on the DOM implementation you are using. In Batik, the DOM implementation is located in the package `org.apache.batik.dom.svg` and the class is named [SVGDOMImplementation](http://xmlgraphics.apache.org/batik/javadoc/org/apache/batik/dom/svg/SVGDOMImplementation.html) . The following example shows how to get a concrete `DOMImplementation` object.
+How to get an instance of the `DOMImplementation` interface depends on the DOM implementation you are using. In Batik, the DOM implementation is located in the package `org.apache.batik.dom.svg` and the class is named [SVGDOMImplementation](http://xmlgraphics.apache.org/batik/javadoc/org/apache/batik/dom/svg/SVGDOMImplementation.html). The following example shows how to get a concrete `DOMImplementation` object.
 
     :::java
     import org.w3c.dom.DOMImplementation;
@@ -17,11 +17,11 @@ How to get an instance of the `DOMImplem
 
     DOMImplementation impl = SVGDOMImplementation.getDOMImplementation();
 
-Once you have an instance of a `DOMImplementation` , you are not relying on Batik-specific code any more and ready to use the DOM API.
+Once you have an instance of a `DOMImplementation`, you are not relying on Batik-specific code any more and ready to use the DOM API.
 
 ## Creating a Document <a id="creating"></a>
 
-Using the `DOMImplementation` , you are now able to create a `Document` . 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.
+Using the `DOMImplementation`, you are now able to create a `Document`. 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.
 
     :::java
     import org.apache.batik.dom.svg.SVGDOMImplementation;
@@ -33,7 +33,7 @@ Using the `DOMImplementation` , you are 
     DOMImplementation impl = SVGDOMImplementation.getDOMImplementation();
     Document doc = impl.createDocument(svgNS, "svg", null);
 
-As we have created an SVG `Document` , we can cast this document to an [SVGDocument](../javadoc/org/w3c/dom/svg/SVGDocument.html) (defined in the `org.w3c.dom.svg` package) if needed.
+As we have created an SVG `Document`, we can cast this document to an [SVGDocument](../javadoc/org/w3c/dom/svg/SVGDocument.html) (defined in the `org.w3c.dom.svg` package) if needed.
 
 ## Building an SVG Document <a id="buildsvgdoc"></a>
 
@@ -77,7 +77,7 @@ The example given constructs a document 
 
 # Creating a Document from an SVG file <a id="createdocfromsvgfile"></a>
 
-With Batik, you can also create an SVG DOM tree from a URI, an [InputStream](http://java.sun.com/j2se/1.5.0/docs/api/java/io/InputStream.html) , or a [Reader](http://java.sun.com/j2se/1.5.0/docs/api/java/io/Reader.html) , using the [SAXSVGDocumentFactory](../javadoc/org/apache/batik/dom/util/SAXDocumentFactory.html) . The following example illustrates how to create an SVG document from a URI using the `SAXSVGDocumentFactory` class.
+With Batik, you can also create an SVG DOM tree from a URI, an [InputStream](http://java.sun.com/j2se/1.5.0/docs/api/java/io/InputStream.html), or a [Reader](http://java.sun.com/j2se/1.5.0/docs/api/java/io/Reader.html), using the [SAXSVGDocumentFactory](../javadoc/org/apache/batik/dom/util/SAXDocumentFactory.html). The following example illustrates how to create an SVG document from a URI using the `SAXSVGDocumentFactory` class.
 
     :::java
     import java.io.IOException;
@@ -96,7 +96,7 @@ With Batik, you can also create an SVG D
         // ...
     }
 
-As we have created an SVG `Document` , we can cast this document to an `SVGDocument` (defined in the `org.w3c.dom.svg` package) if needed.
+As we have created an SVG `Document`, we can cast this document to an `SVGDocument` (defined in the `org.w3c.dom.svg` package) if needed.
 
 ## Rendering an SVG Document <a id="rendering"></a>
 
@@ -106,8 +106,8 @@ Batik provides several ways to use an SV
 
 JSVGCanvas
 :
-The [JSVGCanvas](../javadoc/org/apache/batik/swing/JSVGCanvas.html) is a Swing component that can display SVG document. A SVG document can be specified using a URI or an SVG DOM tree (using the [setSVGDocument](../javadoc/org/apache/batik/swing/JSVGCanvas.html#setSVGDocument(Document)) method). For futher information about the `JSVGCanvas` , see the [Swing components module documentation](../using/swing.html) .
+The [JSVGCanvas](../javadoc/org/apache/batik/swing/JSVGCanvas.html) is a Swing component that can display SVG document. A SVG document can be specified using a URI or an SVG DOM tree (using the [setSVGDocument](../javadoc/org/apache/batik/swing/JSVGCanvas.html#setSVGDocument(Document)) method). For futher information about the `JSVGCanvas`, see the [Swing components module documentation](../using/swing.html).
 
 
 ImageTranscoder
-:    The [ImageTranscoder](../javadoc/org/apache/batik/transcoder/image/ImageTranscoder.html) is a transcoder that can take a URI, an `InputStream` or an SVG DOM tree and produces a raster image (such JPEG, PNG or TIFF). By creating a [TranscoderInput](../javadoc/org/apache/batik/transcoder/TranscoderInput.html) object with the SVG DOM tree, you will be able to transform your SVG content to a raster image. For futher information, see the [transcoder module documentation](../using/transcoder.html) .
\ No newline at end of file
+:    The [ImageTranscoder](../javadoc/org/apache/batik/transcoder/image/ImageTranscoder.html) is a transcoder that can take a URI, an `InputStream` or an SVG DOM tree and produces a raster image (such JPEG, PNG or TIFF). By creating a [TranscoderInput](../javadoc/org/apache/batik/transcoder/TranscoderInput.html) object with the SVG DOM tree, you will be able to transform your SVG content to a raster image. For futher information, see the [transcoder module documentation](../using/transcoder.html).
\ No newline at end of file

Modified: xmlgraphics/site/trunk/content/batik/using/extending.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/batik/using/extending.mdtext?rev=1417307&r1=1417306&r2=1417307&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/batik/using/extending.mdtext (original)
+++ xmlgraphics/site/trunk/content/batik/using/extending.mdtext Wed Dec  5 08:19:09 2012
@@ -5,7 +5,7 @@ Title: Extending Batik
 
 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.
 
-In general, extensions are added through the Service Provider Interface mechanism as described in the [jar file documentation](http://java.sun.com/j2se/1.4/docs/guide/jar/jar.html#Service Provider) . 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!
+In general, extensions are added through the Service Provider Interface mechanism as described in the [jar file documentation](http://java.sun.com/j2se/1.4/docs/guide/jar/jar.html#Service Provider). 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.
 # Custom XML elements <a id="customXMLTags"></a>
 
@@ -14,22 +14,22 @@ First one must ask what it means to supp
 
 
 Having your elements appear in the DOM tree
-:    
+:
 As long as your custom elements are well formed XML they will appear in the SVG DOM tree. When rendering Batik will skip branches of the tree that use elements it doesn’t know about (so even if standard SVG elements are child nodes they will not be displayed). Note that you must make use of XML namespaces for your personal elements even if you are not planning on validating the XML.
 
 This can be useful if you want to add extra pieces of data into the standard SVG drawing. These might be annotations, or other application specific data. In general this wouldn’t be particularly useful with squiggle (the SVG browser) or the rasterizer, but might be very useful if you were writing a custom browser, rasterizer, or pre/post processing tools.
 
 
 Adding functionality to your custom element DOM objects
-:    
-If you need your elements to use a custom element subclass in the DOM tree (for behavioral or performance reasons) then you need to provide an [extension to the Batik DOM](#domExtension) .
+:
+If you need your elements to use a custom element subclass in the DOM tree (for behavioral or performance reasons) then you need to provide an [extension to the Batik DOM](#domExtension).
 
 Doing this gives you the opportunity to override the standard methods on DOM elements, or to provide additional methods to your DOM elements. For example, you may wish to add specialized get and set methods for attributes on your custom elements, so that they can be manipulated more easily than just using the string-based `getAttribute` and `setAttribute` methods provided by DOM Core.
 
 
 Having your custom elements be rendered
-:    
-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 [extension to the Batik bridge](#bridgeExtension) . The bridge extension is resposible for constructing the class(es) that will handle the rendering of the new primitive in Batik.
+:
+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 [extension to the Batik bridge](#bridgeExtension). The bridge extension is resposible for constructing the class(es) that will handle the rendering of the new primitive in Batik.
 
 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).
 
@@ -37,24 +37,24 @@ In most cases it will also be necessary 
 
 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.
 
-The key class for building the DOM tree is [org.apache.batik.dom.ExtensibleSVGDOMImplementation](../javadoc/org/apache/batik/dom/ExtensibleSVGDOMImplementation.html) . When an instance of this class is constructed it searches for instances of the [org.apache.batik.dom.svg.DomExtension](../javadoc/org/apache/batik/dom/svg/DomExtension.html) Service Provider Interface. It then calls the `registerTags` method, passing itself as the only parameter. This method typically would typically call `registerCustomElementFactory` for each element that it wishes to handle.
+The key class for building the DOM tree is [org.apache.batik.dom.ExtensibleSVGDOMImplementation](../javadoc/org/apache/batik/dom/ExtensibleSVGDOMImplementation.html). When an instance of this class is constructed it searches for instances of the [org.apache.batik.dom.svg.DomExtension](../javadoc/org/apache/batik/dom/svg/DomExtension.html) Service Provider Interface. It then calls the `registerTags` method, passing itself as the only parameter. This method typically would typically call `registerCustomElementFactory` for each element that it wishes to handle.
 
-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: [org.apache.batik.extension.PrefixableStylableExtensionElement](../javadoc/org/apache/batik/extension/PrefixableStylableExtensionElement.html) . If you derive a new DOM class from this class you are only required to implement three methods: `getLocalName` , `getNamespaceURI` , and `newNode` (plus constructors). If all you want is proper style support (commonly the case) then you are done implementing your element at this point.
+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: [org.apache.batik.extension.PrefixableStylableExtensionElement](../javadoc/org/apache/batik/extension/PrefixableStylableExtensionElement.html). If you derive a new DOM class from this class you are only required to implement three methods: `getLocalName`, `getNamespaceURI`, and `newNode` (plus constructors). If all you want is proper style support (commonly the case) then you are done implementing your element at this point.
 
 The distribution comes with a number of examples:
 
 
--  `org.apache.batik.extension.svg.BatikStarElement` 
+-  `org.apache.batik.extension.svg.BatikStarElement`
 
--  `org.apache.batik.extension.svg.BatikRegularPolygonElement` 
+-  `org.apache.batik.extension.svg.BatikRegularPolygonElement`
 
--  `org.apache.batik.extension.svg.BatikHistogramNormalizationElement` 
+-  `org.apache.batik.extension.svg.BatikHistogramNormalizationElement`
 
--  `org.apache.batik.extension.svg.SolidColorElement` 
+-  `org.apache.batik.extension.svg.SolidColorElement`
 
--  `org.apache.batik.extension.svg.ColorSwitchElement` 
+-  `org.apache.batik.extension.svg.ColorSwitchElement`
 
-Included with these examples is `org.apache.batik.extension.svg.BatikDomExtension` , which is the required instance of `DomExtension` used to register the elements with the `ExtensibleSVGDOMImplementation` .
+Included with these examples is `org.apache.batik.extension.svg.BatikDomExtension`, which is the required instance of `DomExtension` used to register the elements with the `ExtensibleSVGDOMImplementation`.
 
 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 `BatikDomExtension` ).
 
@@ -62,69 +62,69 @@ If your new element requires new “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.
 
-The key class for managing this link is the [BridgeContext](../javadoc/org/apache/batik/bridge/BridgeContext.html) . 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 [Bridge](../javadoc/org/apache/batik/bridge/Bridge.html) registered for a particular element. If no bridge is regiestered nothing is done.
+The key class for managing this link is the [BridgeContext](../javadoc/org/apache/batik/bridge/BridgeContext.html). 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 [Bridge](../javadoc/org/apache/batik/bridge/Bridge.html) registered for a particular element. If no bridge is regiestered nothing is done.
 
-New associations can be added by implementors of the [BridgeExtension](../javadoc/org/apache/batik/bridge/BridgeExtension.html) 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 `registerTags` method which is responsible for registering the bridge instances with a `BridgeContext` . All the built-in bridges are bundled together with a `BridgeExtension` (the [org.apache.batik.bridge.SVGBridgeExtension](../javadoc/org/apache/batik/bridge/SVGBridgeExtension.html) class), as are the example extensions ( [org.apache.batik.extension.svg](../javadoc/org/apache/batik/extension/svg/BatikBridgeExtension.html) ), so these are both good places to start.
+New associations can be added by implementors of the [BridgeExtension](../javadoc/org/apache/batik/bridge/BridgeExtension.html) 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 `registerTags` method which is responsible for registering the bridge instances with a `BridgeContext`. All the built-in bridges are bundled together with a `BridgeExtension` (the [org.apache.batik.bridge.SVGBridgeExtension](../javadoc/org/apache/batik/bridge/SVGBridgeExtension.html) class), as are the example extensions ( [org.apache.batik.extension.svg](../javadoc/org/apache/batik/extension/svg/BatikBridgeExtension.html) ), so these are both good places to start.
 
 The `Bridge` interface itself is very simple. It only includes methods to get the namespace and local name of the element the bridge is responsible for. This interface is then extended for each of the major concepts present in SVG:
 
 
 
- [GraphicsNodeBridge](#graphicsNodeBridge) 
-:    
+ [GraphicsNodeBridge](#graphicsNodeBridge)
+:
 These are probably the most common SVG elements, as they represent graphic elements in the “visible” SVG tree. These are the elements most other bridges modify in some way (by clipping, masking, filtering, etc).
 
- *Example SVG elements:*  `svg` , `g` , `path` , `rect` .
+ *Example SVG elements:*  `svg`, `g`, `path`, `rect`.
 
- *Example extension bridges:*  `BatikRegularPolygonElementBridge` , `BatikStarElementBridge` .
+ *Example extension bridges:*  `BatikRegularPolygonElementBridge`, `BatikStarElementBridge`.
 
 
 FilterBridge
-:    
+:
 This handles the SVG `filter` element. If you wanted to implement a new element that could be referenced from the `filter` attribute on an SVG graphics node then you would need to subclass this bridge. However, adding new types of filters to the existing SVG `filter` element is accomplished via the FilterPrimitiveBridge.
 
- *Example SVG element:*  `filter` 
+ *Example SVG element:*  `filter`
 
 
- [FilterPrimitiveBridge](#filterPrimitiveBridge) 
-:    
+ [FilterPrimitiveBridge](#filterPrimitiveBridge)
+:
 This constructs an element in the filter chain applied to an SVG graphics node.
 
- *Example SVG elements:*  `feBlend` , `feCompose` , `feGaussianBlur` .
+ *Example SVG elements:*  `feBlend`, `feCompose`, `feGaussianBlur`.
 
- *Example extension bridge:*  `BatikHistogramNormalizationElementBridge` 
+ *Example extension bridge:*  `BatikHistogramNormalizationElementBridge`
 
 
- [PaintBridge](#paintBridge) 
-:    
+ [PaintBridge](#paintBridge)
+:
 This constructs a Java [Paint](http://java.sun.com/j2se/1.5.0/docs/api/java/awt/Paint.html) object to be used in filling or stroking graphic elements.
 
- *Example SVG elements:*  `gradient` , `pattern` .
+ *Example SVG elements:*  `gradient`, `pattern`.
 
- *Example extension bridge:*  `ColorSwitchBridge` .
+ *Example extension bridge:*  `ColorSwitchBridge`.
 
 
 ClipBridge
-:    
+:
 This constructs a [ClipRable](../javadoc/org/apache/batik/ext/awt/image/renderable/ClipRable.html) to apply to a graphics node. This provides a path that data is clipped to.
 
- *Example SVG element:*  `clipPath` .
+ *Example SVG element:*  `clipPath`.
 
 
 MarkerBridge
-:    
+:
 This constructs a [Marker](../javadoc/org/apache/batik/gvt/Marker.html) for annotating the path of a graphics node.
 
- *Example SVG element:*  `marker` .
+ *Example SVG element:*  `marker`.
 
 
 MaskBridge
-:    
+:
 This constructs a mask filter to apply to a graphics node. Mask filters typically modify the alpha channel of the graphics node output to make portions fully or partially transparent that wouldn’t be otherwise.
 
- *Example SVG element:*  `mask` .
+ *Example SVG element:*  `mask`.
 
-Extension writers are free to work with any of the above bridges, however the three most common are likely to be the `GraphicsNodeBridge` , the `FilterPrimitiveBridge` , and the `PaintBridge` (each of which has example extensions available for inspection). Each of these interfaces has several very useful subclasses that handle much of the common behavior among elements.
+Extension writers are free to work with any of the above bridges, however the three most common are likely to be the `GraphicsNodeBridge`, the `FilterPrimitiveBridge`, and the `PaintBridge` (each of which has example extensions available for inspection). Each of these interfaces has several very useful subclasses that handle much of the common behavior among elements.
 
 In some simple cases it is possible to provide only an extension to the bridge and achieve your desired effect, however in most cases you will find that for your element to behave like a normal SVG element (for example, to support styling) you will need to provide a DOM extension as well.
 
@@ -132,22 +132,22 @@ In some simple cases it is possible to p
 
 The graphics node bridge is oriented around constructing a new [GraphicsNode](../javadoc/org/apache/batik/gvt/GraphicsNode.html) in the GVT tree. The `GraphicsNode` is the basic object that makes up the GVT tree. Each `GraphicsNode` has a `paint` method that is responsible for painting the object (including considering clipping, masking, filtering, and opacity for the node).
 
-If you want to you can implement the [GraphicsNodeBridge](../javadoc/org/apache/batik/bridge/GraphicsNodeBridge.html) interface directly, or you can subclass the [AbstractGraphicsNodeBridge](../javadoc/org/apache/batik/bridge/AbstractGraphicsNodeBridge.html) class. This gives you the most flexibility since you can construct your new subclass of `GraphicsNode` , where you can implement the paint method to do essentially anything you want. This is quite involved, however, and the steps necessary to create a full `GraphicsNodeBridge` are not detailed here.
+If you want to you can implement the [GraphicsNodeBridge](../javadoc/org/apache/batik/bridge/GraphicsNodeBridge.html) interface directly, or you can subclass the [AbstractGraphicsNodeBridge](../javadoc/org/apache/batik/bridge/AbstractGraphicsNodeBridge.html) class. This gives you the most flexibility since you can construct your new subclass of `GraphicsNode`, where you can implement the paint method to do essentially anything you want. This is quite involved, however, and the steps necessary to create a full `GraphicsNodeBridge` are not detailed here.
 
 However, if you just want to generate a custom filled or stroked shape the easiest way is to subclass one of the following two classes. In this case you are essentially only responsible for constructing a standard Java [Shape](http://java.sun.com/j2se/1.5.0/docs/api/java/awt/Shape.html) object to describe the desired area to operate on:
 
 
 
 SVGShapeElementBridge
-:    
-Subclasses of this class only need to implement `buildShape` , `getNamespaceURI` , and `getLocalName` . `buildShape` generally constructs a `Shape` object and sets it on the provided `shapeNode` object, however it may adjust other features of the given shape node.
+:
+Subclasses of this class only need to implement `buildShape`, `getNamespaceURI`, and `getLocalName`. `buildShape` generally constructs a `Shape` object and sets it on the provided `shapeNode` object, however it may adjust other features of the given shape node.
 
 
 SVGDecoratedShapeElementBridge
-:    
-This is very similar to `SVGShapeElementBridge` , except that it also handles the standard marker properties. Markers will be placed at the end of each segment of the path that describes the shape.
+:
+This is very similar to `SVGShapeElementBridge`, except that it also handles the standard marker properties. Markers will be placed at the end of each segment of the path that describes the shape.
 
-If you decide that you need to implement a new subclass of `GraphicsNode` it is strongly suggested that you extend [AbstractGraphicsNode](../javadoc/org/apache/batik/gvt/AbstractGraphicsNode.html) , as this class does much of the work to behave like other rendered elements in SVG (like clipping, filtering and masking). In this case you implement the `primitivePaint` method instead of the `paint` method.
+If you decide that you need to implement a new subclass of `GraphicsNode` it is strongly suggested that you extend [AbstractGraphicsNode](../javadoc/org/apache/batik/gvt/AbstractGraphicsNode.html), as this class does much of the work to behave like other rendered elements in SVG (like clipping, filtering and masking). In this case you implement the `primitivePaint` method instead of the `paint` method.
 
 #### FilterPrimitiveBridge ## <a id="filterPrimitiveBridge"></a>
 
@@ -159,11 +159,11 @@ The `org.apache.batik.ext.awt.image` pac
 
 Note that the `FilterPrimitiveBridge` is invoked once for each reference to the `filter` element that the filter primitive is part of. So if a filter effect is used a half dozen times the `createFilter` method will be called a half dozen times, even though the element may only appear once in the file. This means that it is safe for the filters returned to be “fixed” for a particular `GraphicsNode` being filtered.
 
-You will notice that Batik uses extended versions of the standard `RenderableImage` and `RenderedImage` interfaces to provide additional information about surrounding requirements for operations as well as a few convenience methods. These interfaces are called: [org.apache.batik.ext.awt.image.renderable.Filter](../javadoc/org/apache/batik/ext/awt/image/renderable/Filter.html) and [org.apache.batik.ext.awt.image.rendered.CacheableRed](../javadoc/org/apache/batik/ext/awt/image/rendered/CacheableRed.html) . Batik contains simple wrapper classes that can take the default JDK `RenderableImage` and `RenderedImage` interfaces. Within the codebase the naming convention “Red” for classes implementing `RenderedImage` and “Rable” for classes implementing `RenderableImage` is commonly used (“Red” is to be pronounced like the color, and “Rable” is to be pronounced like “horrible” with a silent “h”).
+You will notice that Batik uses extended versions of the standard `RenderableImage` and `RenderedImage` interfaces to provide additional information about surrounding requirements for operations as well as a few convenience methods. These interfaces are called: [org.apache.batik.ext.awt.image.renderable.Filter](../javadoc/org/apache/batik/ext/awt/image/renderable/Filter.html) and [org.apache.batik.ext.awt.image.rendered.CacheableRed](../javadoc/org/apache/batik/ext/awt/image/rendered/CacheableRed.html). Batik contains simple wrapper classes that can take the default JDK `RenderableImage` and `RenderedImage` interfaces. Within the codebase the naming convention “Red” for classes implementing `RenderedImage` and “Rable” for classes implementing `RenderableImage` is commonly used (“Red” is to be pronounced like the color, and “Rable” is to be pronounced like “horrible” with a silent “h”).
 
-The `FilterPrimitiveBridge` has only one method, `createFilter` , that must construct an instance of `Filter` to perform the required operation. This is still a fairly complex task given the general need to support accessing the various standard sources of image data. To this end there is a provided subclass, [AbstractSVGFilterPrimitiveElementBridge](../javadoc/org/apache/batik/bridge/AbstractSVGFilterPrimitiveElementBridge.html) , that provides convenience methods to handle many common tasks.
+The `FilterPrimitiveBridge` has only one method, `createFilter`, that must construct an instance of `Filter` to perform the required operation. This is still a fairly complex task given the general need to support accessing the various standard sources of image data. To this end there is a provided subclass, [AbstractSVGFilterPrimitiveElementBridge](../javadoc/org/apache/batik/bridge/AbstractSVGFilterPrimitiveElementBridge.html), that provides convenience methods to handle many common tasks.
 
-Generally the bulk of the work in writing a filter extension is the writing of the concrete `Filter` class, not tying it into the GVT tree. Batik does contain several base classes that make this processes a bit easier: [org.apache.batik.ext.awt.image.renderable.AbstractRable](../javadoc/org/apache/batik/ext/awt/image/renderable/AbstractRable.html) , [org.apache.batik.ext.awt.image.rendered.AbstractRed](../javadoc/org/apache/batik/ext/awt/image/rendered/AbstractRed.html) , and [org.apache.batik.ext.awt.image.rendered.AbstractTiledRed](../javadoc/org/apache/batik/ext/awt/image/rendered/AbstractTiledRed.html) , [TiledRed](../javadoc/org/apache/batik/ext/awt/image/rendered/TiledRed.html) ties into the Batik tile cache (use this with caution as it is a complex area of the Batik code).
+Generally the bulk of the work in writing a filter extension is the writing of the concrete `Filter` class, not tying it into the GVT tree. Batik does contain several base classes that make this processes a bit easier: [org.apache.batik.ext.awt.image.renderable.AbstractRable](../javadoc/org/apache/batik/ext/awt/image/renderable/AbstractRable.html), [org.apache.batik.ext.awt.image.rendered.AbstractRed](../javadoc/org/apache/batik/ext/awt/image/rendered/AbstractRed.html), and [org.apache.batik.ext.awt.image.rendered.AbstractTiledRed](../javadoc/org/apache/batik/ext/awt/image/rendered/AbstractTiledRed.html), [TiledRed](../javadoc/org/apache/batik/ext/awt/image/rendered/TiledRed.html) ties into the Batik tile cache (use this with caution as it is a complex area of the Batik code).
 
 The `org.apache.batik.ext.awt.image.rendered` and `org.apache.batik.ext.awt.image.renderable` packages contain quite a number of fairly general examples covering most common cases, please refer to them for more detail.
 
@@ -175,59 +175,59 @@ Like the filter primitive bridge, the `P
 
 This is how gradients and patterns are implemented in Batik, so it is possible to construct rather complex paint effects through this mechanism.
 
-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 [AbstractSVGGradientElementBridge](../javadoc/org/apache/batik/bridge/AbstractSVGGradientElementBridge.html) , which is used to handle most of the radial and linear gradient attributes.
+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 [AbstractSVGGradientElementBridge](../javadoc/org/apache/batik/bridge/AbstractSVGGradientElementBridge.html), which is used to handle most of the radial and linear gradient attributes.
 
-The existing gradient paint implementations are in the `org.apache.batik.ext.awt` , and the pattern implementation is in `org.apache.batik.gvt` since it requires access to GVT internals.
+The existing gradient paint implementations are in the `org.apache.batik.ext.awt`, and the pattern implementation is in `org.apache.batik.gvt` since it requires access to GVT internals.
 
 ## New image file formats <a id="imageTagFormats"></a>
 
-When Batik encounters an `image` element and it determines the element does not reference an SVG file, it defers the loading of the referenced image to [org.apache.batik.ext.awt.image.spi.ImageTagRegistry](../javadoc/org/apache/batik/ext/awt/image/spi/ImageTagRegistry.html) . This class maintains a list of [RegistryEntry](../javadoc/org/apache/batik/ext/awt/image/spi/RegistryEntry.html) s, generally one for each format.
+When Batik encounters an `image` element and it determines the element does not reference an SVG file, it defers the loading of the referenced image to [org.apache.batik.ext.awt.image.spi.ImageTagRegistry](../javadoc/org/apache/batik/ext/awt/image/spi/ImageTagRegistry.html). This class maintains a list of [RegistryEntry](../javadoc/org/apache/batik/ext/awt/image/spi/RegistryEntry.html) s, generally one for each format.
 
 Since the formats supported natively by Batik are also implemented through this mechanism. The [JPEGRegistryEntry](../javadoc/org/apache/batik/ext/awt/image/codec/jpeg/JPEGRegistryEntry.html) and [PNGRegistryEntry](../javadoc/org/apache/batik/ext/awt/image/codec/png/PNGRegistryEntry.html) classes should be used as good references for extensions.
 
 ### RegistryEntry <a id="RegistryEntry"></a>
 
-There are currently two flavors of `RegistryEntry` :
+There are currently two flavors of `RegistryEntry`:
 
 
 
 URLRegistryEntry
-:    
+:
 A [URLRegistryEntry](../javadoc/org/apache/batik/ext/awt/image/spi/URLRegistryEntry.html) takes a [ParsedURL](../javadoc/org/apache/batik/util/ParsedURL.html) and tries to decide if the URL is intended for it. This group of entries is mostly intended to handle alternate network protocols. It can also be useful for interfacing with libraries that want a URL instead of a stream.
 
 
 StreamRegistryEntry
-:    
-A [StreamRegistryEntry](../javadoc/org/apache/batik/ext/awt/image/spi/StreamRegistryEntry.html) works with a markable [InputStream](http://java.sun.com/j2se/1.5.0/docs/api/java/io/InputStream.html) . 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.
+:
+A [StreamRegistryEntry](../javadoc/org/apache/batik/ext/awt/image/spi/StreamRegistryEntry.html) works with a markable [InputStream](http://java.sun.com/j2se/1.5.0/docs/api/java/io/InputStream.html). 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.
 
 ### Helper classes <a id="Helper+classes"></a>
 
-There exists quite a number of classes to assist in implementing a `RegistryEntry` . 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.
+There exists quite a number of classes to assist in implementing a `RegistryEntry`. 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.
 
 
 
 MagicNumberRegistryEntry
-:    
+:
  [MagicNumberRegistryEntry](../javadoc/org/apache/batik/ext/awt/image/spi/MagicNumberRegistryEntry.html) is an abstract class that can handle the `isCompatibleStream` method for formats that make use of “magic numbers.” Magic numbers are a well known sequence of bytes at a well known offset in the file, that are commonly used to identify image file formats.
 
 
 RedRable
-:    
+:
  [RedRable](../javadoc/org/apache/batik/ext/awt/image/renderable/RedRable.html) takes any `java.awt.image.RenderedImage` and wraps it into a `Filter` (Batik’s subinterface of `RenderableImage` ). This is very useful for *single resolution* file formats.
 
 
 DeferRable
-:    
+:
  [DeferRable](../javadoc/org/apache/batik/ext/awt/image/renderable/DeferRable.html) allows one to load the image in a background thread, rather than hold up the construction of the GVT tree while reading the image (useful since reading the image is generally I/O bound, so it makes a good background task). This is used by most of the current image readers.
 
 
 AbstractRable
-:    
+:
  [AbstractRable](../javadoc/org/apache/batik/ext/awt/image/renderable/AbstractRable.html) is an abstract base class that makes it relatively easy to implement the Filter interface.
 
 
 AbstractRed
-:    
+:
  [AbstractRed](../javadoc/org/apache/batik/ext/awt/image/rendered/AbstractRed.html) is an abstract base class that makes it relatively easy to implement the [CacheableRed](../javadoc/org/apache/batik/ext/awt/image/rendered/CacheableRed.html) interface (Batik's subclass of `RenderedImage` ).
 
 ## New URL protocols <a id="urlProtocols"></a>
@@ -236,7 +236,7 @@ For a variety of reasons (not the least 
 
  `ParsedURL` offers a few advantages over the JDK’s `URL` 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 `data:` 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).
 
-The service class is [org.apache.batik.util.ParsedURLProtocolHandler](../javadoc/org/apache/batik/util/ParsedURLProtocolHandler.html) . 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 [ParsedURLData](../javadoc/org/apache/batik/util/ParsedURLData.html) (the instance may of course be a subclass of `ParsedURLData` ).
+The service class is [org.apache.batik.util.ParsedURLProtocolHandler](../javadoc/org/apache/batik/util/ParsedURLProtocolHandler.html). 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 [ParsedURLData](../javadoc/org/apache/batik/util/ParsedURLData.html) (the instance may of course be a subclass of `ParsedURLData` ).
 
 The `ParsedURLData` class holds all the data and implements all the stream handling commands for the `ParsedURL` class. This allows `ParsedURLProtocolHandler` s to return custom subclasses for particular protocols.
 
@@ -244,6 +244,6 @@ The `ParsedURLData` class holds all the 
 
 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.
 
-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 [InterpreterFactory](../javadoc/org/apache/batik/script/InterpreterFactory.html) . This class has two methods: `getMimeType` , which returns a string that specifies what script type this intepreter handles (specifically, what the `type` attribute of `script` elements must be for them to be handled by this intepreter), and `createInterpreter` , which creates an instance of the [Interpreter](../javadoc/org/apache/batik/script/Interpreter.html) interface.
+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 [InterpreterFactory](../javadoc/org/apache/batik/script/InterpreterFactory.html). This class has two methods: `getMimeType`, which returns a string that specifies what script type this intepreter handles (specifically, what the `type` attribute of `script` elements must be for them to be handled by this intepreter), and `createInterpreter`, which creates an instance of the [Interpreter](../javadoc/org/apache/batik/script/Interpreter.html) interface.
 
 Batik comes with implementations of `Interpreter` and `IntepreterFactory` to support TCL and Python script in SVG documents, if the Jacl and Jython distributions are installed, respectively. See the classes in the `org.apache.batik.script.jacl` and `org.apache.batik.script.jython` packages to guidance on how to implement the interpreter interfaces, and the [installation notes](../install.html) on what jar files are needed for TCL and Python support.

Modified: xmlgraphics/site/trunk/content/batik/using/index.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/batik/using/index.mdtext?rev=1417307&r1=1417306&r2=1417307&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/batik/using/index.mdtext (original)
+++ xmlgraphics/site/trunk/content/batik/using/index.mdtext Wed Dec  5 08:19:09 2012
@@ -8,45 +8,45 @@ The Batik toolkit has a number of module
 
 
 Architecture
-:    
+:
 The [architecture](../using/architecture.html) page gives an overview of how the various modules in Batik fit together.
 
 
 Javadoc APIs
-:    
+:
 The [Javadoc APIs](../using/../javadoc/) document all of the classes packaged with Batik.
 
 
 DOM API
-:    
+:
 The [DOM API](../using/dom-api.html) page explains how to use the DOM interfaces to create and render SVG documents.
 
 
 Parsers
-:    
+:
 The [Parsers](../using/parsers.html) page describes the parser classes that can be used for parsing the microsyntaxes of SVG (such as path data and transform lists).
 
 
 Scripting
-:    
-The scripting pages ( [Scriping with ECMAScript](../using/scripting/ecmascript.html) , [Scripting with Java](../using/scripting/java.html) and [Security](../using/scripting/security.html) ) document how to programmatically manipulate SVG documents, and how script interpreters can be used and extended in Batik.
+:
+The scripting pages ( [Scriping with ECMAScript](../using/scripting/ecmascript.html), [Scripting with Java](../using/scripting/java.html) and [Security](../using/scripting/security.html) ) document how to programmatically manipulate SVG documents, and how script interpreters can be used and extended in Batik.
 
 
 SVG generator
-:    
+:
 The [SVG Generator](../using/svg-generator.html) page documents the `SVGGraphics2D` class, which can be used to construct SVG documents from Java2D drawing commands.
 
 
 Swing components
-:    
+:
 The [Swing components](../using/swing.html) page describes the SVG canvas component, the primary method for displaying SVG content in Swing applications.
 
 
 Transcoder API
-:    
+:
 The [Transcoder API](../using/transcoder.html) page explains how to use the transcoder classes to convert SVG content to other formats (raster or vector).
 
 
 Extending Batik
-:    
+:
 The [Extending Batik](../using/extending.html) page lists the parts of the Batik API that are extensible and explains how to add functionality to the existing modules.



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