vhardy 01/11/09 03:56:34
Modified: xdocs svggen.xml
Log:
Fixed problem reported by Paul.
Revision Changes Path
1.11 +2 -2 xml-batik/xdocs/svggen.xml
Index: svggen.xml
===================================================================
RCS file: /home/cvs/xml-batik/xdocs/svggen.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- svggen.xml 2001/11/05 14:57:24 1.10
+++ svggen.xml 2001/11/09 11:56:34 1.11
@@ -12,7 +12,7 @@
<!-- ========================================================================= -->
<!-- author [EMAIL PROTECTED] -->
<!-- author [EMAIL PROTECTED] -->
-<!-- version $Id: svggen.xml,v 1.10 2001/11/05 14:57:24 vhardy Exp $ -->
+<!-- version $Id: svggen.xml,v 1.11 2001/11/09 11:56:34 vhardy Exp $ -->
<!-- ========================================================================= -->
<document>
<header>
@@ -258,7 +258,7 @@
<p>
With the caching image handlers, it is even possible to reuse the same copy
of your image data across
several different SVG documents. Just keep a reference to the image
handler, and pass it to the
- <code>CachedImageSVGGraphics2D</code> instance used for generating the SVG
DOM tree. The following
+ <code>SVGGraphics2D</code> instance used for generating the SVG DOM tree.
The following
simplified example shows how different SVG trees might be created by
separate SVG generators,
efficiently storing any common images just once.
</p>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
