Repository: ant
Updated Branches:
  refs/heads/master 69c85b931 -> b453e8b5d

Another typo and more highlighting


Branch: refs/heads/master
Commit: b453e8b5d667ba03b6ab802ef9cf63b617a6706e
Parents: 69c85b9
Author: Gintas Grigelionis <>
Authored: Sun Mar 11 11:32:21 2018 +0100
Committer: Gintas Grigelionis <>
Committed: Sun Mar 11 11:32:21 2018 +0100

 manual/Tasks/pvcstask.html  |  2 +-
 manual/Types/selectors.html |  8 ++++----
 manual/install.html         | 12 ++++++------
 manual/listeners.html       |  2 +-
 manual/properties.html      |  2 +-
 manual/using.html           | 15 ++++++++-------
 6 files changed, 21 insertions(+), 20 deletions(-)
diff --git a/manual/Tasks/pvcstask.html b/manual/Tasks/pvcstask.html
index 5db446e..73594df 100644
--- a/manual/Tasks/pvcstask.html
+++ b/manual/Tasks/pvcstask.html
@@ -25,7 +25,7 @@
 <h1>Apache Ant Pvcs Task User Manual</h1>
 <p><strong>Note</strong>: Before using this task, the user running Ant must 
have access to the
-commands of PVCS (<code>get</code> and <code>pcli</code>) and must have access 
to the
+commands of PVCS (<kbd>get</kbd> and <kbd>pcli</kbd>) and must have access to 
 repository. Note that the way to specify the repository is platform dependent 
so use property to
 specify location of repository.</p>
diff --git a/manual/Types/selectors.html b/manual/Types/selectors.html
index f8a2631..6f3836f 100644
--- a/manual/Types/selectors.html
+++ b/manual/Types/selectors.html
@@ -852,7 +852,7 @@
     cache implementation</p>
     <h4 id="ModSelNote">Note on RuleBasedCollator</h4>
-    <p>The RuleBasedCollator needs a format for its work, but its needed while 
instantiation. There
+    <p>The RuleBasedCollator needs a format for its work, but its needed while 
instantiating. There
     is a problem in the initialization algorithm for this case. Therefore you 
should not use this
     (or tell me the workaround :-).</p>
@@ -980,9 +980,9 @@
     the <a href="../Tasks/script.html">script</a> task on how to use this 
     <p>If no <var>src</var> attribute is supplied, the script must be nested 
inside the selector
-    <p>The embedded script is invoked for every test, with the bean 
<code>self</code> is bound to
-    the selector. It has an attribute <var>selected</var> which can be set
-    using <code>setSelected(boolean)</code> to select a file.</p>
+    <p>The embedded script is invoked for every test, with the bean <code 
+    is bound to the selector. It has an attribute <var>selected</var> which 
can be set
+    using <code class="code">setSelected(boolean)</code> to select a file.</p>
     <p>The following beans are configured for every script, alongside the 
classic set of project,
     properties, and targets.</p>
diff --git a/manual/install.html b/manual/install.html
index abff025..38df65a 100644
--- a/manual/install.html
+++ b/manual/install.html
@@ -97,7 +97,7 @@ IDEs can invariably be pointed at different Ant 
installations. This lets develop
 eliminate inconsistencies between command-line and IDE Ant.
-<h3>Bundled in Java applications</h3>
+<h3>Bundled in Java Applications</h3>
 Many Java applications, most particularly application servers, ship with a 
version of Ant. These are primarily for
@@ -293,7 +293,7 @@ as <code>ANT_HOME</code>.
 <h3 id="setup">Setup</h3>
 Before you can run Ant there is some additional setup you will need to do 
unless you are installing
-the <a href="#jpackage">RPM version from</a>:
+the <a href="#jpackage">RPM Version from</a>:
 <li>Add the <samp>bin</samp> directory to your path.</li>
@@ -328,7 +328,7 @@ security restrictions on the classes which may be loaded by 
an extension.
 You can check the basic installation with opening a new shell and typing 
<kbd>ant</kbd>. You should get a message like
+<pre class="output">
 Buildfile: build.xml does not exist!
 Build failed
@@ -336,7 +336,7 @@ Build failed
 So Ant works. This message is there because you need to write a buildfile for 
your project. With a <kbd>ant
 -version</kbd> you should get an output like
+<pre class="output">
 Apache Ant(TM) version 1.9.2 compiled on July 8 2013
@@ -454,7 +454,7 @@ IDEs have different ways of adding external JAR files and 
third-party tasks to A
 configuration dialog. Sometimes JAR files added to a project are automatically 
added to Ant's classpath.
-<h3 id="classpath">The <code>CLASSPATH</code> environment variable</h3>
+<h3 id="classpath">The <code>CLASSPATH</code> Environment Variable</h3>
 The <code>CLASSPATH</code> environment variable is a source of many Ant 
support queries. As the round trip time for
 diagnosis on the Ant user mailing list can be slow, and because filing bug 
reports complaining about 'ant.bat' not
@@ -976,7 +976,7 @@ an Ant option. This can be added to a diagnostics target in 
a build file to see
 what the XML parser and classpath is, etc.
-<h3 id="ant-user">user mailing list</h3>
+<h3 id="ant-user">User Mailing List</h3>
 If you cannot get Ant installed or working, the Ant user mailing list is the 
best place to start with any
diff --git a/manual/listeners.html b/manual/listeners.html
index 346e205..f9ac1ea 100644
--- a/manual/listeners.html
+++ b/manual/listeners.html
@@ -281,7 +281,7 @@ like <code>cat</code>, <code>more</code>, etc.</p>
 <p>This is designed to work on terminals that support ANSI color codes.  It 
works on XTerm, ETerm,
 Win9x Console (with <code>ANSI.SYS</code> loaded.), etc.</p>
 <p><strong>Note</strong>: It doesn't work on WinNT and successors, even when
-a <code>COMMAND.COM</code> console loaded with <code>ANSI.SYS<</code> is 
+a <code>COMMAND.COM</code> console loaded with <code>ANSI.SYS</code> is 
 <p>If the user wishes to override the default colors with custom ones, a file 
containing zero or
 more of the custom color key-value pairs must be created.  The recognized keys 
and their default
 values are shown below:</p>
diff --git a/manual/properties.html b/manual/properties.html
index 8dc459e..83437ad 100644
--- a/manual/properties.html
+++ b/manual/properties.html
@@ -213,7 +213,7 @@ public class ToStringEvaluator implements 
PropertyHelper.PropertyEvaluator {
   <p>which will echo this message:</p>
+<pre class="output">${builddir}=build/classes</pre>
   <p>if the property <code>builddir</code> has the value 
diff --git a/manual/using.html b/manual/using.html
index 0f357fa..97eeaec 100644
--- a/manual/using.html
+++ b/manual/using.html
@@ -69,8 +69,8 @@ project's <var>default</var> is used.</p>
 <h3 id="targets">Targets</h3>
 <p>A target can depend on other targets. You might have a target for 
compiling, for example, and a target for creating a
-distributable. You can only build a distributable when you have compiled 
first, so the distribute target
-<em>depends on</em> the compile target. Ant resolves these dependencies.</p>
+distributable. You can only build a distributable when you have compiled 
first, so the <q>distribute</q>
+target <em>depends on</em> the <q>compile</q> target. Ant resolves these 
 <p>It should be noted, however, that Ant's <var>depends</var> attribute only 
specifies the <em>order</em> in which
 targets should be executed&mdash;it does not affect whether the target that 
specifies the dependency(s) gets executed if
 the dependent target(s) did not (need to) run.</p>
@@ -104,7 +104,7 @@ scripts you could do:</p>
 <p>to set the <code>foo</code> attribute of this particular task instance.  In 
another task (written in Java), you can
-access the instance via <code>project.getReference("task1")</code>.</p>
+access the instance via <code 
 <p>Note 1: If <q>task1</q> has not been run yet, then it has not been 
configured (ie., no attributes have been set), and
 if it is going to be configured later, anything you've done to the instance 
may be overwritten.</p>
 <p>Note 2: Future versions of Ant will most likely <em>not</em> be 
backward-compatible with this behaviour, since there
@@ -433,20 +433,21 @@ errors. Use Ant's own <a 
href="install.html#optionalTasks">mechanisms</a> for ad
   <li>declare a single task per using instruction using
     <code>&lt;<a href="Tasks/taskdef.html">taskdef</a> 
-    <code>&lt;taskdef name=&quot;for&quot; 
classname=&quot;net.sf.antcontrib.logic.For&quot;/&gt; &lt;for
+    <code class="code">&lt;taskdef name=&quot;for&quot; 
classname=&quot;net.sf.antcontrib.logic.For&quot;/&gt; &lt;for
       ... /&gt;</code>
   <li>declare a bundle of tasks using a <samp>properties</samp> file holding 
these taskname&ndash;ImplementationClass
     pairs and <code>&lt;taskdef&gt;</code><br/>
-    <code>&lt;taskdef 
resource=&quot;net/sf/antcontrib/;/&gt; &lt;for ... 
+    <code class="code">&lt;taskdef 
resource=&quot;net/sf/antcontrib/;/&gt; &lt;for
+    ... /&gt;</code>
   <li>declare a bundle of tasks using an <a href="Types/antlib.html">xml 
file</a> holding these
     taskname-ImplementationClass-pairs and <code>&lt;taskdef&gt;</code><br/>
-    <code>&lt;taskdef resource=&quot;net/sf/antcontrib/antlib.xml&quot;/&gt; 
&lt;for ... /&gt;</code>
+    <code class="code">&lt;taskdef 
resource=&quot;net/sf/antcontrib/antlib.xml&quot;/&gt; &lt;for ... /&gt;</code>
   <li>declare a bundle of tasks using an xml file named 
<samp>antlib.xml</samp>, XML namespace
     and <a href="Types/antlib.html#antlibnamespace"><code>antlib:</code> 
protocol handler</a><br/>
-    <code>&lt;project xmlns:ac=&quot;antlib:net.sf.antcontrib&quot;/&gt; 
&lt;ac:for ... /&gt;</code>
+    <code class="code">&lt;project 
xmlns:ac=&quot;antlib:net.sf.antcontrib&quot;/&gt; &lt;ac:for ... /&gt;</code>

Reply via email to