You are viewing a plain text version of this content. The canonical link for it is here.
Posted to batik-dev@xmlgraphics.apache.org by vh...@apache.org on 2001/04/30 07:03:39 UTC
cvs commit: xml-batik/xdocs/images 1_0beta2splash.png
vhardy 01/04/29 22:03:38
Modified: xdocs index.xml site-book.xml
Added: xdocs extendingBatik.xml jsvgcanvas.xml
testInfrastructure.xml ttf2svg.xml
xdocs/images 1_0beta2splash.png
Log:
Skeleton for 1.0 release documentation.
Revision Changes Path
1.18 +6 -1 xml-batik/xdocs/index.xml
Index: index.xml
===================================================================
RCS file: /home/cvs/xml-batik/xdocs/index.xml,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- index.xml 2000/12/02 00:26:19 1.17
+++ index.xml 2001/04/30 05:03:35 1.18
@@ -11,7 +11,7 @@
<!-- ========================================================================= -->
<!-- author vincent.hardy@eng.sun.com -->
-<!-- version $Id: index.xml,v 1.17 2000/12/02 00:26:19 vhardy Exp $ -->
+<!-- version $Id: index.xml,v 1.18 2001/04/30 05:03:35 vhardy Exp $ -->
<!-- ========================================================================= -->
<document>
<header>
@@ -26,7 +26,12 @@
<body>
<s1 title="Batik Overview">
+ <figure src="images/1_0beta2splash.png" alt="1.0 beta2" />
+ <p><strong>
+ This is a staging area for the next revision of the Batik web site that will
+ come on-line when Batik 1.0 becomes available around May 14th.
+ </strong></p>
<p>
<img src="images/logo.gif" alt="Batik Logo"/> Batik is a Java
based toolkit for applications that want to use images in the
1.19 +39 -33 xml-batik/xdocs/site-book.xml
Index: site-book.xml
===================================================================
RCS file: /home/cvs/xml-batik/xdocs/site-book.xml,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- site-book.xml 2001/02/05 10:15:15 1.18
+++ site-book.xml 2001/04/30 05:03:36 1.19
@@ -12,65 +12,71 @@
<!-- author stephane@hillion.org -->
<!-- author tkormann@apache.org -->
<!-- author vincent.hardy@eng.sun.com -->
-<!-- version $Id: site-book.xml,v 1.18 2001/02/05 10:15:15 cjolif Exp $ -->
+<!-- version $Id: site-book.xml,v 1.19 2001/04/30 05:03:36 vhardy Exp $ -->
<!-- ========================================================================= -->
<book title="Apache Batik documentation" copyright="2000-2001 The Apache Software Foundation">
<!-- ======================= -->
<!-- Home -->
<!-- ======================= -->
- <external label="Home" href="http://xml.apache.org/"/>
+ <external label="Home" href="http://xml.apache.org/"/>
<separator/>
<!-- ======================= -->
<!-- Top Level -->
<!-- ======================= -->
- <page id="index" label="Overview" source="index.xml"/>
- <faqs id="faqs" label="FAQ" source="faq.xml"/>
- <page id="demo" label="Tools and Apps" source="demo.xml" />
- <page id="license" label="License" source="license.xml"/>
- <external href="dist" label="Download"/>
- <page id="install" label="Install" source="installing.xml"/>
- <page id="pr" label="In the news" source="pr.xml" />
+ <page id="index" label="Overview" source="index.xml"/>
+ <faqs id="faqs" label="FAQ" source="faq.xml"/>
+ <page id="license" label="License" source="license.xml"/>
+ <external href="dist" label="Download"/>
+ <page id="install" label="Install" source="installing.xml"/>
+ <page id="pr" label="In the news" source="pr.xml" />
<separator/>
- <!-- ======================= -->
- <!-- Demos -->
- <!-- ======================= -->
- <page id="svgviewer" label="Viewer" source="svgviewer.xml"/>
- <page id="svgrasterizer" label="Rasterizer" source="svgrasterizer.xml" />
- <page id="svgpp" label="Pretty-printer" source="svgpp.xml" />
- <!-- <page id="svgapplet" label="SVG Applet" source="svgapplet.xml" />-->
- <page id="svggen" label="Generator" source="svggen.xml" />
+ <!-- ================================= -->
+ <!-- Sample Applications Documentation -->
+ <!-- ================================= -->
+ <page id="toolsAndApps" label="Tools and Apps" source="demo.xml" />
+ <page id="svgrasterizer" label="Rasterizer" source="svgrasterizer.xml" />
+ <page id="svgviewer" label="Viewer" source="svgviewer.xml"/>
+ <page id="ttf2svg" label="Font Converter" source="ttf2svg.xml"/>
+ <page id="svgpp" label="Pretty-printer" source="svgpp.xml" />
+
+ <!--<page id="svgapplet" label="SVG Applet" source="svgapplet.xml" />-->
<separator />
- <!-- ======================= -->
- <!-- Tutorials -->
- <!-- ======================= -->
- <page id="rasterizerTutorial" label="Transcoder API" source="rasterizerTutorial.xml"/>
+ <!-- ==================================== -->
+ <!-- Developer's Guides and Tutorials -->
+ <!-- ==================================== -->
+ <page id="architecture" label="Architecture" source="architecture.xml"/>
+ <page id="svggen" label="Generator" source="svggen.xml" />
+ <page id="domapi" label="DOM API" source="domTutorial.xml" />
+ <page id="scripting" label="Scripting" source="scriptIntro.xml" />
+ <page id="svgcanvas" label="SVG Bean" source="jsvgcanvas.xml" />
+ <page id="rasterizerTutorial" label="Transcoder API" source="rasterizerTutorial.xml"/>
+ <page id="extendingBatik" label="Extentions" source="extendingBatik.xml" />
+ <page id="test" label="Testing" source="testInfrastructure.xml"/>
<separator />
<!-- ======================= -->
<!-- Status / Admin -->
<!-- ======================= -->
- <page id="whoAreWe" label="Who we are" source="whoAreWe.xml" />
- <page id="status" label="Status" source="status.xml" />
- <changes id="changes" label="Changes" source="changes.xml"/>
- <!-- <todo id="todo" label="Todo" source="todo.xml"/> -->
- <external label="CVS Repository" href="http://xml.apache.org/websrc/index.cgi/xml-batik/"/>
+ <page id="whoAreWe" label="Who we are" source="whoAreWe.xml" />
+ <page id="status" label="Status" source="status.xml" />
+ <external label="CVS Repository" href="http://xml.apache.org/websrc/index.cgi/xml-batik/"/>
+ <page id="mailList" label="Mail Lists" source="mail-lists.xml"/>
+ <external label="Bug Database" href="http://xml.apache.org/bugs/"/>
+
+ <!-- <external label="Mail Archive" href="http://mail-archives.apache.org/"/> -->
<!-- <external label="Snapshots" href="http://xml.apache.org/from-cvs/xml-batik/"/> -->
- <page id="mailList" label="Mail Lists" source="mail-lists.xml"/>
- <external label="Mail Archive" href="http://mail-archives.apache.org/"/>
- <external label="Bug Database" href="http://xml.apache.org/bugs/"/>
+ <!-- <changes id="changes" label="Changes" source="changes.xml"/> -->
+ <!-- <todo id="todo" label="Todo" source="todo.xml"/> -->
<separator/>
<!-- ======================= -->
<!-- Documentation -->
<!-- ======================= -->
- <page id="glossary" label="Glossary" source="glossary.xml" />
- <page id="regard" label="Regression tool" source="regardIntro.xml" />
- <!-- <external label="API (Javadoc)" href="javadoc/index.html"/> -->
+ <page id="glossary" label="Glossary" source="glossary.xml" />
<separator />
-
</book>
1.1 xml-batik/xdocs/extendingBatik.xml
Index: extendingBatik.xml
===================================================================
<?xml version="1.0"?>
<!DOCTYPE document SYSTEM "./dtd/document-v10.dtd">
<!-- ========================================================================= -->
<!-- Copyright (C) The Apache Software Foundation. All rights reserved. -->
<!-- -->
<!-- This software is published under the terms of the Apache Software License -->
<!-- version 1.1, a copy of which has been included with this distribution in -->
<!-- the LICENSE file. -->
<!-- ========================================================================= -->
<!-- ========================================================================= -->
<!-- author vincent.hardy@eng.sun.com -->
<!-- version $Id: extendingBatik.xml,v 1.1 2001/04/30 05:03:35 vhardy Exp $ -->
<!-- ========================================================================= -->
<document>
<header>
<title>Extending Batik</title>
<subtitle>Possible extensions</subtitle>
<authors>
<person name="Vincent Hardy" email="vincent.hardy@eng.sun.com"/>
</authors>
</header>
<body>
<s1 title="Introduction">
<p>TO BE WRITTEN (VH)</p>
</s1>
</body>
</document>
1.1 xml-batik/xdocs/jsvgcanvas.xml
Index: jsvgcanvas.xml
===================================================================
<?xml version="1.0"?>
<!DOCTYPE document SYSTEM "./dtd/document-v10.dtd">
<!-- ========================================================================= -->
<!-- Copyright (C) The Apache Software Foundation. All rights reserved. -->
<!-- -->
<!-- This software is published under the terms of the Apache Software License -->
<!-- version 1.1, a copy of which has been included with this distribution in -->
<!-- the LICENSE file. -->
<!-- ========================================================================= -->
<!-- ========================================================================= -->
<!-- author vincent.hardy@eng.sun.com -->
<!-- version $Id: jsvgcanvas.xml,v 1.1 2001/04/30 05:03:35 vhardy Exp $ -->
<!-- ========================================================================= -->
<document>
<header>
<title>Batik - Architecture</title>
<subtitle>Batik's modules explained</subtitle>
<authors>
<person name="Thierry Kormann" email="tkormann@apache.org"/>
</authors>
</header>
<body>
<s1 title="Introduction">
<p>TO BE WRITTEN (TK)</p>
</s1>
</body>
</document>
1.1 xml-batik/xdocs/testInfrastructure.xml
Index: testInfrastructure.xml
===================================================================
<?xml version="1.0"?>
<!DOCTYPE document SYSTEM "./dtd/document-v10.dtd">
<!-- ========================================================================= -->
<!-- Copyright (C) The Apache Software Foundation. All rights reserved. -->
<!-- -->
<!-- This software is published under the terms of the Apache Software License -->
<!-- version 1.1, a copy of which has been included with this distribution in -->
<!-- the LICENSE file. -->
<!-- ========================================================================= -->
<!-- ========================================================================= -->
<!-- author vincent.hardy@eng.sun.com -->
<!-- version $Id: testInfrastructure.xml,v 1.1 2001/04/30 05:03:36 vhardy Exp $ -->
<!-- ========================================================================= -->
<document>
<header>
<title>Batik - Test Infrastructure</title>
<subtitle>How testing is done in Batik</subtitle>
<authors>
<person name="Vincent Hardy" email="vincent.hardy@eng.sun.com"/>
</authors>
</header>
<body>
<s1 title="Introduction">
<p>This document describes the current state of the test
infrastructure for Batik. The goals for the infrastructure
are to:</p>
<ul>
<li>Make it easy to detect regressions</li>
<li>Make it easy to run test suites</li>
<li>Make it easy to write new test and add them
to an existing test suite</li>
</ul>
<p>The intention of the test infrastructure is to grow
along with Batik and to keep monitoring the health of
the code base. </p>
<p>While the test suites in the infrastructure will be
run every day by build/test machines, they are also
intended to help the commiters and developers get confident
that their code modifications did not introduce regressions.</p>
<p>This document describes:</p>
<ul>
<li><link href="#infrastructure">Test infrastructure</link>This may be a little
dry, but it helps understanding the format of the files used to run
the test suites</li>
<li><link href="#managingATestSuite">How to describe and run a test suite</link></li>
<li><link href="#regardReplacement">The 'regard' replacement</link></li>
<li><link href="#regsvggenReplacement">The 'regsvggen' replacement</link></li>
<li><link href="#writingNewTests">Writing new Tests</link></li>
<li><link href="#limitations">Limitations</link></li>
</ul>
</s1>
<anchor id="infrastructure" />
<s1 title="The Test infrastructure">
<s2 title="High-Level Interfaces">
<p>The following are the high level
interfaces in the infrastructure</p>
<!-- <figure src="images/testHighLevel.jpg" alt="Batik Viewer"/> -->
<ul>
<li>A <code>Test</code> is performing whatever check
is needed in its <code>run</code> method, and each
run produces a <code>TestReport</code></li>
<li>A <code>TestReport</code> describes whether
a <code>Test</code> run passed or failed and provides a
description of the failure in terms of an error
code (unique in the context of a given <code>Test</code>)
and a set of key/value pairs</li>
<li>A <code>TestSuite</code> is a <code>Test</code>
aggregation which can run a set of <code>Test</code>. </li>
<li>A <code>TestReportProcessor</code> is used to
analyze a <code>TestReport</code>. A specific implementation
can chose to create graphs, send an email or write
an HTML file</li>
</ul>
</s2>
<s2 title="Default Implementations">
<p>The test infrastructure comes with a number of default
implementations for the interfaces described above.
Specifically:</p>
<ul>
<li><code>AbstractTest</code>. This implementation of
the <code>Test</code> interface is intended to make it
easier to write a 'safe' <code>Test</code> implementation.
See "Writing New Tests" for a description of how to
use that class.</li>
<li><code>DefaultTestReport</code> provides a simple
implementation of the <code>TestReport</code> interface
that most <code>Test</code> implementation will be able to
use. See "Writing New Tests" for more details.</li>
<li><code>DefaultTestSuite</code> provides an implementation
of the <code>TestSuite</code> interface and makes it
easy to aggregate <code>Test</code> instances.</li>
<li><code>SimpleTestReportProcessor</code> is a sample
<code>TestReportProcessor</code> implementation that
simply traces the content of a <code>TestReport</code> to
an output stream</li>
<li><code>TestReportMailer</code> is another implementation
of the <code>TestReportProcessor</code> interface that
emails a test report to a list of destination emails.</li>
</ul>
</s2>
<s2 title="XML Implementations">
<p>The test infrastructure is using XML-out (and XML-in
too, see "Running a test suite") as a favorite way to
generate test reports. The <code>XMLTestReportProcessor</code>
implementation of the <code>TestReportProcessor</code> interface.
outputs reports in XML in a configurable directory.</p>
<p>The <code>XMLTestReportProcessor</code> can notify a
<code>XMLReportConsumer</code> when it has created a new
report. There is one implementation of that interface
by default that can run an XSL stylesheet on the
XML report (e.g., to generate an HTML report) and that
is done by the <code>XSLXMLReportConsumer</code></p>
</s2>
</s1>
<anchor id="managingATestSuite" />
<s1 title="Managing Test Suites">
<p>The infrastructure tries to make it easy to create, update and
modify test suites. This section describes how to describe a set
of tests to be run and how to actually run that test suite</p>
<s2 title="Describing a Test Suite">
<p>Test suites can be described in XML (XML-in refered to earlier
in this document). The general format for describing a test suite is:</p>
<source>
<testSuite name="MyFavoriteTestSuite">
<!-- =================================== -->
<!-- Descriptions of processors that -->
<!-- will process the results of the -->
<!-- test suite -->
<!-- =================================== -->
<testReportProcessor class="myFavoriteReportProcessorA" />
<testReportProcessor class="myFavoriteReportProcessorB" />
<!-- =================================== -->
<!-- Set of tests to be run -->
<!-- =================================== -->
<test class="myFavoriteTestClassA" />
<test class="myFavoriteTestClassB" />
<test class="myFavoriteTestClassC" />
</testSuite>
</source>
<p>In a nutshell, you can specify a set of <code>TestReportProcessor</code> which
should process the <code>TestReport</code> generated by the <code>TestSuite</code> built
from the list of <code>Test</code> instances described in the file</p>
<p><code>TestReportProcessors</code> and <code>Test</code> classes
can be configured with either construction parameters or with
properties. For example: </p>
<source>
<testSuite name="SAMPLE TEST SUITE">
<testReportProcessor class="org.apache.batik.test.TestReportMailer">
<arg class="java.lang.String" value="someone@somewhere.com" />
<arg class="java.lang.String" value="someoneElse@somewhereElse.com" />
<arg class="java.lang.String" value="mailServer@myprovider.com" />
</testReportProcessor>
<testReportProcessor class="org.apache.batik.test.xml.XMLTestReportProcessor" >
<arg class="org.apache.batik.test.xml.XSLXMLReportConsumer">
<!-- Stylesheet -->
<arg class="java.lang.String" value="file:test-resources/org/apache/batik/test/svg/HTMLReport.xsl" />
<!-- Ouput Directory -->
<arg class="java.lang.String" value="test-reports/html" />
<!-- Output file prefix -->
<arg class="java.lang.String" value="SVGRenderingAccuracyTestReport" />
<!-- Output file suffix -->
<arg class="java.lang.String" value=".html" />
</arg>
</testReportProcessor>
<!-- ========================================================================== -->
<!-- Validates that the SVGRenderingAccuracyTest class is operating as expected -->
<!-- ========================================================================== -->
<test class="org.apache.batik.test.svg.SVGRenderingAccuracyTestValidator" />
<!-- ========================================================================== -->
<!-- Rendering regression tests -->
<!-- ========================================================================== -->
<test class="org.apache.batik.test.svg.SVGRenderingAccuracyTest">
<arg class="java.net.URL"
value="file:samples/anne.svg" />
<arg class="java.net.URL"
value="file:test-references/samples/solaris/anne.png" />
<property name="VariationURL"
class="java.net.URL"
value="file:test-references/samples/variation/anne.png" />
<property name="SaveVariation"
class="java.io.File"
value="test-references/samples/variation-candidate/anne.png" />
</test>
</testSuite>
</source>
</s2>
<s2 title="Running a Test Suite">
<p>There is now a rule in our <code>build.xml</code> to run a test suite defined in
an XML file as the one above. At the command line, type the following:</p>
<p><code>build runtestsuite -Dargs="path/to/my/newly/created/testSuite.xml"</code></p>
</s2>
</s1>
<anchor id="regardReplacement" />
<s1 title="The 'regard' replacement">
<p>'regard' is the tool we have used so far to deted regressions in how we render SVG images</p>
<p>There is a <code>Test</code> implementation, <code>SVGRenderingAccuracyTest</code> which takes over
the responsibility that regard has and then goes beyond.</p>
<s2 title="The SVGRenderingAccuracyTest configuration">
<p>An <code>SVGRenderingAccuracyTest</code>'s constructor configuration is made of</p>
<ul>
<li>The URL to the SVG it should render</li>
<li>The URL to a reference PNG file</li>
</ul>
<p>The default behavior for the test is to render the SVG into a PNG file and compare with
the reference image. If there is not difference, the test passes. Otherwise, it fails.</p>
<p>In addition to this default behavior, the <code>SVGRenderingAccuracyTest</code> can
take an optional configuration parameter, an image URL defined as an 'accepted' variation
around the reference image. If such a variation image is specified, then the test will pass if:</p>
<ul>
<li>The rasterized SVG is equal to the reference image</li>
<li>Or, the difference between the rasterized SVG and the reference image is
exactly the same as the accepted variation image</li>
</ul>
<p>Finally, to ease the process of creating 'accepted' variation images, <code>
SVGRenderingAccuracyTest</code> can take an optional file name (called 'saveVariation')
describing where the variation between
the rasterized SVG and the reference image will be stored in case the rasterized SVG
is different from the reference image and the difference is not equal to the variation
image, if any was defined. That way, it becomes possible to run a test. It that test fails,
the developer can review the saveVariation image and decide whether it is an acceptable
variation or not and use it in subsequent test run as the 'accepted' variation image, which
will allow the test to pass if that exact same variation remains constant.</p>
</s2>
<s2 title="Day to day use of regard replacement">
<p>Concretely, regard is replaced by a specific test suite description, regard.xml. That
file contains a set of test files (the ones in the samples and samples/test directories)
for which rendering regressions should be checked.</p>
<p><em>Initial set up</em></p>
<p>
To set up the test environment the first time, you need to:</p>
<ul>
<li>Check-out the latest version of the code, including the test-xx directories
(sources, resources and references) and the build.xml file</li>
<li>Run the regard test suite once:<code>build regard</code></li>
</ul>
<p>This will generate an HTML test report in the <code>test-reports/html</code> directory.
Depending on how much different text rendering is between your work environment and the
environment used to create the reference images, you will get more or less test that will fail,
because of differences in the way text is rendered on various platforms and because of
fonts not being available on some platforms. For example, a running the test on a Windows 2000
laptop against images generated on the Solaris platform caused 16 tests out of 71 to fail.</p>
<p>Review the HTML report to make sure that the differences are really due to text variations.
This will usually be the case and you can make sure by clicking on the diff images contained
in the report to see them at full scale. You can you can then turn the 'candidate' variations generated by
the test into 'accepted' variations by moving files from one directory to another:</p>
<p><code>mv test-references/samples/candidate-variations/*.png test-references/samples/accepted-variations/*.png</code></p>
<p><code>mv test-references/samples/tests/candidate-variations/*.png test-references/samples/tests/accepted-variations/*.png</code></p>
<p />
<p>You can now run the test again:</p>
<p><code>build regard</code></p>
<p>Check the newly generated HTML report in the test-reports/html directory: there should not
longer be any test failure</p>
<p />
<p><em>Daily usage</em></p>
<p />
<p>Once the intial set-up has been done, you can use regard by simply updating your
CVS copy, including the test-references. If no change occurs, your test will keep passing
with your reference images. If a test fails (e.g., if someone checks in a new reference
image from a platform different than the one you are using, you will have to check if it is
because of system specific reasons or if there is a bigger problem.</p>
</s2>
</s1>
<anchor id="regsvggenReplacement" />
<s1 title="The 'regsvggen' replacement">
<p>TO BE DONE</p>
</s1>
<anchor id="writingNewTests" />
<s1 title="Writing new Tests">
<p>Writing a new Test involves either configuring a new test or writing a new <code>Test</code> class. In
both cases, you will need to add an entry to a test suite's XML description. This section uses two
test suites as an example: the 'regard' test suite to show how to configure a new test and the
'unitTests' test suite to show how to add a new <code>Test</code> implementation.</p>
<s2 title="Adding a new test configuration">
<p>Imagine that you add a cool new test case to the samples directory, such as <em>linking-viewBox.svg</em>.
In order to check for regressions on that file you can add the following entry:</p>
<source>
<test class="org.apache.batik.test.svg.SVGRenderingAccuracyTest">
<arg class="java.net.URL"
value="file:samples/tests/linkingViewBox.svg" />
<arg class="java.net.URL"
value="file:test-references/samples/tests/solaris/linkingViewBox.png" />
<property name="VariationURL"
class="java.net.URL"
value="file:test-references/samples/tests/variation/linkingViewBox.png" />
<property name="SaveVariation"
class="java.io.File"
value="test-references/samples/tests/variation-candidate/linkingViewBox.png" />
</test>
</source>
<p>to the test-resources/org/apache/batik/test/samplesRendering.xml test suite description, the
description of the regard test suite. If you have access to the build machine where the
reference images are typically generated, you can check-in the reference image in
test-references/samples/tests. Otherwise (and this is ok), you can let the test fail the
first time it is run on the build/test machine and that will be a reminder for whoever
is responsible for that machine that a valid reference image shoudl be checked in.</p>
</s2>
<s2 title="Writing a new test">
<p>Imagine you want to validate some aspect of your code, and let's take the bridge error
handling as an example. You could create a new class in the <code>test-sources</code>
area, in the org/apache/batik/bridge in our example, and let's call it <code>ErrorHandlingTest</code>.
To simplify the implementation of the <code>Test</code> interface, you can chose
to derive from the <code>AbstractTest</code> class and generate a <code>DefaultTestReport</code>.</p>
<p>While writing the <code>Test</code> you may want to use your own XML file with just
your test, for example:</p>
<source>
<testReportProcessor class="org.apache.batik.test.SimpleTestReportProcessor" />
<test class="org.apache.batik.bridge.ErrorHandlingTest">
<!-- Expected error code -->
<arg class="java.lang.String" value="expected.error.code" />
<!-- Input SVG that this test manipulates to generate error conditions -->
<arg class="java.net.URL" value="file:test-resources/org/apache/batik/bridge/ErrorHandlingBase.svg" />
<!-- Id of the element to test -->
<arg class="java.lang.String value="rectangle6" />
<!-- Attribute to test -->
<arg class="java.lang.String value="x" />
<!-- Value to test on the attribute -->
<arg class="java.lang.String value="abcd" />
</test>
</source>
<p>This is just an example and does not pretend to be the right way to go about implementing
or specifying this specific type of test. Once done with tuning the test, one or multiple
configurations for the test can be added to the relevant test suite's XML description. In
some cases, it will be interesting to create a separate test suite.</p>
</s2>
</s1>
<anchor id="limitations" />
<s1 title="Known limitations and issues">
<ul>
<li>Need to add the ability to nest test suite descriptions</li>
<li>Need to modify test report generation to still list tests that succeed</li>
<li>Need to enhance HTML report to start with a ratio of success and failures</li>
<li>More</li>
</ul>
</s1>
</body>
</document>
1.1 xml-batik/xdocs/ttf2svg.xml
Index: ttf2svg.xml
===================================================================
<?xml version="1.0"?>
<!DOCTYPE document SYSTEM "./dtd/document-v10.dtd">
<!-- ========================================================================= -->
<!-- Copyright (C) The Apache Software Foundation. All rights reserved. -->
<!-- -->
<!-- This software is published under the terms of the Apache Software License -->
<!-- version 1.1, a copy of which has been included with this distribution in -->
<!-- the LICENSE file. -->
<!-- ========================================================================= -->
<!-- ========================================================================= -->
<!-- author vincent.hardy@eng.sun.com -->
<!-- version $Id: ttf2svg.xml,v 1.1 2001/04/30 05:03:36 vhardy Exp $ -->
<!-- ========================================================================= -->
<document>
<header>
<title>Font Converter Utility</title>
<subtitle>Creating SVG fonts</subtitle>
<authors>
<person name="Vincent Hardy" email="vincent.hardy@eng.sun.com"/>
</authors>
</header>
<body>
<s1 title="Introduction">
<p>TO BE WRITTEN (VH)</p>
</s1>
</body>
</document>
1.1 xml-batik/xdocs/images/1_0beta2splash.png
<<Binary file>>
---------------------------------------------------------------------
To unsubscribe, e-mail: batik-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: batik-dev-help@xml.apache.org