You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@xmlgraphics.apache.org by he...@apache.org on 2019/11/02 15:12:58 UTC
svn commit: r1869296 - in /xmlgraphics/site/trunk/content/batik:
contributors.mdtext dev/test.mdtext status.mdtext
tools/pretty-printer.mdtext tools/rasterizer.mdtext
using/scripting/ecmascript.mdtext using/scripting/security.mdtext
Author: helder
Date: Sat Nov 2 15:12:57 2019
New Revision: 1869296
URL: http://svn.apache.org/viewvc?rev=1869296&view=rev
Log:
General:
Re-did fixes made for xdocs in r1859293
(and added a couple more).
Modified:
xmlgraphics/site/trunk/content/batik/contributors.mdtext
xmlgraphics/site/trunk/content/batik/dev/test.mdtext
xmlgraphics/site/trunk/content/batik/status.mdtext
xmlgraphics/site/trunk/content/batik/tools/pretty-printer.mdtext
xmlgraphics/site/trunk/content/batik/tools/rasterizer.mdtext
xmlgraphics/site/trunk/content/batik/using/scripting/ecmascript.mdtext
xmlgraphics/site/trunk/content/batik/using/scripting/security.mdtext
Modified: xmlgraphics/site/trunk/content/batik/contributors.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/batik/contributors.mdtext?rev=1869296&r1=1869295&r2=1869296&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/batik/contributors.mdtext (original)
+++ xmlgraphics/site/trunk/content/batik/contributors.mdtext Sat Nov 2 15:12:57 2019
@@ -6,7 +6,7 @@ The Batik project had been mostly inacti
PMC agreed to give committership rights to all PMC members to all projects. This was done so that fixes
needed by the FOP project could be committed to Batik by FOP committers that belong to the PMC (similarly,
Batik committers that belong to the PMC also have committership rights to FOP). Most of the commits to Batik
-since 2013 have been done FOP committers.
+since 2013 have been done by FOP committers.
This page contains information about the original (i.e. pre-2007) Batik developers and the last features they
worked on.
Modified: xmlgraphics/site/trunk/content/batik/dev/test.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/batik/dev/test.mdtext?rev=1869296&r1=1869295&r2=1869296&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/batik/dev/test.mdtext (original)
+++ xmlgraphics/site/trunk/content/batik/dev/test.mdtext Sat Nov 2 15:12:57 2019
@@ -14,7 +14,7 @@ This document describes the Batik test i
The intent for the test infrastructure is that it grows along with Batik and keeps monitoring the health of the code base.
-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.
+While the test suites in the infrastructure will be run every day by build/test machines, they are also intended to help the committers and developers get confident that their code modifications did not introduce regressions.
## The test infrastructure { #infrastructure}
@@ -219,7 +219,7 @@ will run all the tests with an ID contai
### Rendering accuracy tests { #Rendering-accuracy-tests}
-There is a `Test` implementation, [SVGRenderingAccuracyTest](../javadoc/org/apache/batik/test/SVGRenderingAccuracyTest.html), which checks that Batikâs rendering of an SVG document stays accurate. It compares reference images with the rendering Batik produces and reports any discrepency.
+There is a `Test` implementation, [SVGRenderingAccuracyTest](../javadoc/org/apache/batik/test/SVGRenderingAccuracyTest.html), which checks that Batikâs rendering of an SVG document stays accurate. It compares reference images with the rendering Batik produces and reports any discrepancy.
An `SVGRenderingAccuracyTest` âs constructor configuration is made of:
@@ -293,7 +293,7 @@ Imagine that you add a cool new test cas
value="test-references/samples/tests/variation-candidate/linkingViewBox.png"/>
</test>
-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 0n 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 should be checked in.
+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 on 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 should be checked in.
### Writing a new test { #Writing-a-new-test}
Modified: xmlgraphics/site/trunk/content/batik/status.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/batik/status.mdtext?rev=1869296&r1=1869295&r2=1869296&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/batik/status.mdtext (original)
+++ xmlgraphics/site/trunk/content/batik/status.mdtext Sat Nov 2 15:12:57 2019
@@ -14,7 +14,7 @@ If a feature is <span class="no">not</sp
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.
+If a feature is <span class="partial">partially</span> supported, this means that Batik performs some processing for it, but there are known bugs with this processing.
Fully supported
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=1869296&r1=1869295&r2=1869296&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/batik/tools/pretty-printer.mdtext (original)
+++ xmlgraphics/site/trunk/content/batik/tools/pretty-printer.mdtext Sat Nov 2 15:12:57 2019
@@ -95,7 +95,7 @@ Open a command line window and go to the
-
-For windows, type the following at the command prompt:
+For Windows, type the following at the command prompt:
build svgpp
Modified: xmlgraphics/site/trunk/content/batik/tools/rasterizer.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/batik/tools/rasterizer.mdtext?rev=1869296&r1=1869295&r2=1869296&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/batik/tools/rasterizer.mdtext (original)
+++ xmlgraphics/site/trunk/content/batik/tools/rasterizer.mdtext Sat Nov 2 15:12:57 2019
@@ -164,7 +164,7 @@ To start the rasterizer you should:
- Open a command line window and go to the `xml-batik` or `batik-`*`version`* directory where the Batik distribution was expanded.
-
-For windows, type the following at the command prompt:
+For Windows, type the following at the command prompt:
build svgrasterizer
Modified: xmlgraphics/site/trunk/content/batik/using/scripting/ecmascript.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/batik/using/scripting/ecmascript.mdtext?rev=1869296&r1=1869295&r2=1869296&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/batik/using/scripting/ecmascript.mdtext (original)
+++ xmlgraphics/site/trunk/content/batik/using/scripting/ecmascript.mdtext Sat Nov 2 15:12:57 2019
@@ -79,7 +79,7 @@ For more information on scripting Java c
## Customizing the Rhino interpreter { #customizingRhino}
-A useful example of customization of the Rhino interpreter comes from the fact that the ECMAScript specification doesnât provide any predefined I/O facilities to interact with the console. However, it is very common for ECMAScript compatible languages to provide a function named `print` to output messages to the console. We will describe here an example of cutomization of the Batik Rhino interpreter to add such functionality to it.
+A useful example of customization of the Rhino interpreter comes from the fact that the ECMAScript specification doesnât provide any predefined I/O facilities to interact with the console. However, it is very common for ECMAScript compatible languages to provide a function named `print` to output messages to the console. We will describe here an example of customization of the Batik Rhino interpreter to add such functionality to it.
You should first subclass the default Batik ECMAScript interpreter to add the functionality to it as below.
Modified: xmlgraphics/site/trunk/content/batik/using/scripting/security.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/batik/using/scripting/security.mdtext?rev=1869296&r1=1869295&r2=1869296&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/batik/using/scripting/security.mdtext (original)
+++ xmlgraphics/site/trunk/content/batik/using/scripting/security.mdtext Sat Nov 2 15:12:57 2019
@@ -30,7 +30,7 @@ The Squiggle browser lets the user decid
- The policy defined as described above is enforced unless the `java.security.policy` system property is defined. In that case, the policy defined by the system property takes precedence and the policy file generated from the Squiggle preferences is ignored.
- **Important note:** The default policy files assume that the applications use the Xerces parser and give appropriate permissions to its `lib/xerces-2_5_0.jar` jar file. If you are using a different XML parser, you need to modify the policy files to grant the propser permissions to your XML parser instead of Xerces. You will have to replace:
+ **Important note:** The default policy files assume that the applications use the Xerces parser and give appropriate permissions to its `lib/xerces-2_5_0.jar` jar file. If you are using a different XML parser, you need to modify the policy files to grant the proper permissions to your XML parser instead of Xerces. You will have to replace:
grant codeBase "${app.dev.base}/lib/xerces_2_5_0.jar" {
permission java.security.AllPermission;
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: commits-help@xmlgraphics.apache.org