xmlgraphics-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r1052282 - in /websites/staging/xmlgraphics/trunk/content: ./ batik/ batik/dev/ batik/tools/ batik/using/scripting/
Date Sat, 02 Nov 2019 15:13:21 GMT
Author: buildbot
Date: Sat Nov  2 15:13:20 2019
New Revision: 1052282

Log:
Staging update by buildbot for xmlgraphics

Modified:
    websites/staging/xmlgraphics/trunk/content/   (props changed)
    websites/staging/xmlgraphics/trunk/content/batik/contributors.html
    websites/staging/xmlgraphics/trunk/content/batik/dev/test.html
    websites/staging/xmlgraphics/trunk/content/batik/status.html
    websites/staging/xmlgraphics/trunk/content/batik/tools/pretty-printer.html
    websites/staging/xmlgraphics/trunk/content/batik/tools/rasterizer.html
    websites/staging/xmlgraphics/trunk/content/batik/using/scripting/ecmascript.html
    websites/staging/xmlgraphics/trunk/content/batik/using/scripting/security.html

Propchange: websites/staging/xmlgraphics/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sat Nov  2 15:13:20 2019
@@ -1 +1 @@
-1866694
+1869296

Modified: websites/staging/xmlgraphics/trunk/content/batik/contributors.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/batik/contributors.html (original)
+++ websites/staging/xmlgraphics/trunk/content/batik/contributors.html Sat Nov  2 15:13:20
2019
@@ -209,7 +209,7 @@ h2:hover > .headerlink, h3:hover > .head
 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. </p>
+since 2013 have been done by FOP committers. </p>
 <p>This page contains information about the original (i.e. pre-2007) Batik developers
and the last features they
 worked on.</p>
 <h2 id="committers">Committers<a class="headerlink" href="#committers" title="Permanent
link">&para;</a></h2>

Modified: websites/staging/xmlgraphics/trunk/content/batik/dev/test.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/batik/dev/test.html (original)
+++ websites/staging/xmlgraphics/trunk/content/batik/dev/test.html Sat Nov  2 15:13:20 2019
@@ -218,7 +218,7 @@ h2:hover > .headerlink, h3:hover > .head
 </li>
 </ul>
 <p>The intent for the test infrastructure is that it grows along with Batik and keeps
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>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.</p>
 <h2 id="infrastructure">The test infrastructure<a class="headerlink" href="#infrastructure"
title="Permanent link">&para;</a></h2>
 <h3 id="High-level-interfaces">High-level interfaces<a class="headerlink" href="#High-level-interfaces"
title="Permanent link">&para;</a></h3>
 <p>The following are the high level interfaces in the infrastructure.</p>
@@ -385,7 +385,7 @@ This is another implementation of the <c
 
 <p>will run all the tests with an ID containing <code>unitTesting.ts</code>
(i.e., all the test selection unit testing, see <code>test-resources/org/apache/batik/gvt/unitTesting.xml</code>)
and the accuracy rendering test on <code>batikFX.svg</code> (because it is the
only test with <code>batikFX.svg</code> in its ID).</p>
 <h3 id="Rendering-accuracy-tests">Rendering accuracy tests<a class="headerlink"
href="#Rendering-accuracy-tests" title="Permanent link">&para;</a></h3>
-<p>There is a <code>Test</code> implementation, <a href="../javadoc/org/apache/batik/test/SVGRenderingAccuracyTest.html">SVGRenderingAccuracyTest</a>,
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.</p>
+<p>There is a <code>Test</code> implementation, <a href="../javadoc/org/apache/batik/test/SVGRenderingAccuracyTest.html">SVGRenderingAccuracyTest</a>,
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.</p>
 <p>An <code>SVGRenderingAccuracyTest</code> ’s constructor configuration
is made of:</p>
 <ul>
 <li>
@@ -450,7 +450,7 @@ This is another implementation of the <c
 </pre></div>
 
 
-<p>to the <code>test-resources/org/apache/batik/test/samplesRendering.xml</code>
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 <code>test-references/samples/tests</code>. 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.</p>
+<p>to the <code>test-resources/org/apache/batik/test/samplesRendering.xml</code>
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 <code>test-references/samples/tests</code>. 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.</p>
 <h3 id="Writing-a-new-test">Writing a new test<a class="headerlink" href="#Writing-a-new-test"
title="Permanent link">&para;</a></h3>
 <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>
directory, in <code>test-sources/org/apache/batik/bridge</code> in our example,
and let's call it <code>ErrorHandlingTest</code>. To simplify the implementation
of the <code>Test</code> interface, you can choose 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>

Modified: websites/staging/xmlgraphics/trunk/content/batik/status.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/batik/status.html (original)
+++ websites/staging/xmlgraphics/trunk/content/batik/status.html Sat Nov  2 15:13:20 2019
@@ -211,7 +211,7 @@ h2:hover > .headerlink, h3:hover > .head
 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.</p>
 <p>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.</p>
+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.</p>
 <p>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.</p>

Modified: websites/staging/xmlgraphics/trunk/content/batik/tools/pretty-printer.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/batik/tools/pretty-printer.html (original)
+++ websites/staging/xmlgraphics/trunk/content/batik/tools/pretty-printer.html Sat Nov  2
15:13:20 2019
@@ -267,7 +267,7 @@ Make sure that your <code>JAVA_HOME</cod
 <p>-
 Open a command line window and go to the <code>xml-batik</code> or <code>batik-</code><em><code>version</code></em>
directory where the Batik distribution was expanded.</p>
 <p>-
-For windows, type the following at the command prompt:</p>
+For Windows, type the following at the command prompt:</p>
 <div class="codehilite"><pre><span class="n">build</span> <span
class="n">svgpp</span>
 </pre></div>
 

Modified: websites/staging/xmlgraphics/trunk/content/batik/tools/rasterizer.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/batik/tools/rasterizer.html (original)
+++ websites/staging/xmlgraphics/trunk/content/batik/tools/rasterizer.html Sat Nov  2 15:13:20
2019
@@ -317,7 +317,7 @@ specifies a list of script types (i.e.,
 </li>
 </ul>
 <p>-
-For windows, type the following at the command prompt:</p>
+For Windows, type the following at the command prompt:</p>
 <div class="codehilite"><pre><span class="n">build</span> <span
class="n">svgrasterizer</span>
 </pre></div>
 

Modified: websites/staging/xmlgraphics/trunk/content/batik/using/scripting/ecmascript.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/batik/using/scripting/ecmascript.html (original)
+++ websites/staging/xmlgraphics/trunk/content/batik/using/scripting/ecmascript.html Sat Nov
 2 15:13:20 2019
@@ -268,7 +268,7 @@ h2:hover > .headerlink, h3:hover > .head
 
 <p>For more information on scripting Java classes from ECMAScript code, see Rhino's
<a href="http://www.mozilla.org/rhino/ScriptingJava.html">Scripting Java</a> document.</p>
 <h2 id="customizingRhino">Customizing the Rhino interpreter<a class="headerlink"
href="#customizingRhino" title="Permanent link">&para;</a></h2>
-<p>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 <code>print</code> 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.</p>
+<p>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 <code>print</code> 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.</p>
 <p>You should first subclass the default Batik ECMAScript interpreter to add the functionality
to it as below.</p>
 <div class="codehilite"><pre><span class="kn">import</span> <span
class="nn">org.apache.batik.script.rhino.RhinoInterpreter</span><span class="o">;</span>
 

Modified: websites/staging/xmlgraphics/trunk/content/batik/using/scripting/security.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/batik/using/scripting/security.html (original)
+++ websites/staging/xmlgraphics/trunk/content/batik/using/scripting/security.html Sat Nov
 2 15:13:20 2019
@@ -226,7 +226,7 @@ h2:hover > .headerlink, h3:hover > .head
 <p>The policy defined as described above is enforced unless the <code>java.security.policy</code>
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.</p>
 </li>
 </ul>
-<p><strong>Important note:</strong> The default policy files assume that
the applications use the Xerces parser and give appropriate permissions to its <code>lib/xerces-2_5_0.jar</code>
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:</p>
+<p><strong>Important note:</strong> The default policy files assume that
the applications use the Xerces parser and give appropriate permissions to its <code>lib/xerces-2_5_0.jar</code>
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:</p>
 <div class="codehilite"><pre>grant codeBase &quot;<span class="cp">${</span><span
class="n">app</span><span class="o">.</span><span class="n">dev</span><span
class="o">.</span><span class="n">base</span><span class="cp">}</span>/lib/xerces_2_5_0.jar&quot;
{
   permission java.security.AllPermission;
 };



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


Mime
View raw message