Noticed most of these while producing the manual as JavaHelp: especially the
nonportable character references do not render correctly in all browsers. A
simple dash suffices.
Cheers,
-Jesse
--
Jesse Glick <mailto:[EMAIL PROTECTED]>
NetBeans, Open APIs <http://www.netbeans.org/>
tel (+4202) 3300-9161 Sun Micro x49161 Praha CR
Index: docs/manual/develop.html
===================================================================
RCS file: /home/cvspublic/jakarta-ant/docs/manual/develop.html,v
retrieving revision 1.2
diff -u -r1.2 develop.html
--- docs/manual/develop.html 2001/02/13 12:31:48 1.2
+++ docs/manual/develop.html 2001/03/08 20:15:04
@@ -26,7 +26,7 @@
in the buildfile)
</li>
<li>
-boolean – your method will be passed the value
+boolean - your method will be passed the value
<i>true</i> if the value specified in the buildfile is one of
<code>true</code>,
<code>yes</code>, or <code>on</code>)
</li>
Index: docs/manual/dirtasks.html
===================================================================
RCS file: /home/cvspublic/jakarta-ant/docs/manual/dirtasks.html,v
retrieving revision 1.2
diff -u -r1.2 dirtasks.html
--- docs/manual/dirtasks.html 2001/02/13 12:31:48 1.2
+++ docs/manual/dirtasks.html 2001/03/08 20:15:04
@@ -62,7 +62,7 @@
<code>/test/**</code> matches all files/directories under <code>/test/</code>,
such as <code>/test/x.java</code>,
or <code>/test/foo/bar/xyz.html</code>, but not <code>/xyz.xml</code>.</p>
-<p>There is one "shorthand" – if a pattern ends
+<p>There is one "shorthand" - if a pattern ends
with <code>/</code>
or <code>\</code>, then <code>**</code>
is appended.
Index: docs/manual/install.html
===================================================================
RCS file: /home/cvspublic/jakarta-ant/docs/manual/install.html,v
retrieving revision 1.4
diff -u -r1.4 install.html
--- docs/manual/install.html 2001/03/07 17:13:53 1.4
+++ docs/manual/install.html 2001/03/08 20:15:05
@@ -222,7 +222,7 @@
Just pass <nobr><code>-DMYVAR=%MYVAR%</code></nobr> (Windows) or
<nobr><code>-DMYVAR=$MYVAR</code></nobr> (Unix)
-to Ant – you can then access
+to Ant - you can then access
these variables inside your buildfile as <code>${MYVAR}</code>.</p>
<p>Two more options are: <nobr><code>-quiet</code></nobr>,
@@ -301,7 +301,6 @@
install directory's <code>lib</code> directory if you are using the
indicated feature. Note that only one of the regexp libraries is
needed for use with the mappers.</p>
-<p/>
<table border="1" cellpadding="2" cellspacing="0">
<tr>
Index: docs/manual/intro.html
===================================================================
RCS file: /home/cvspublic/jakarta-ant/docs/manual/intro.html,v
retrieving revision 1.2
diff -u -r1.2 intro.html
--- docs/manual/intro.html 2001/02/13 12:31:49 1.2
+++ docs/manual/intro.html 2001/03/08 20:15:05
@@ -38,7 +38,7 @@
<p>Granted, this removes some of the expressive power that is inherent in being
able to construct a shell command such as
<nobr><code>`find . -name foo -exec rm {}`</code></nobr>, but it
-gives you the ability to be cross-platform – to work anywhere and
+gives you the ability to be cross-platform - to work anywhere and
everywhere. And
hey, if you really need to execute a shell command, Ant has an
<exec> task that
Index: docs/manual/using.html
===================================================================
RCS file: /home/cvspublic/jakarta-ant/docs/manual/using.html,v
retrieving revision 1.2
diff -u -r1.2 using.html
--- docs/manual/using.html 2001/02/13 12:31:49 1.2
+++ docs/manual/using.html 2001/03/08 20:15:05
@@ -54,7 +54,7 @@
distributable when you have compiled first, so the distribute target
<i>depends on</i> the compile target. Ant resolves these dependencies.</p>
<p>It should be noted, however, that Ant's <code>depends</code> attribute
-only specifies the <i>order</i> in which targets should be executed – it
+only specifies the <i>order</i> in which targets should be executed - 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>
@@ -265,7 +265,7 @@
is found in a file, but no
filter is associated with that token, no changes take place;
therefore, no escaping
-method is available – but as long as you choose appropriate names for your
+method is available - but as long as you choose appropriate names for your
tokens, this should not cause problems.</p>
<p><b>Warning:</b> If you copy binary files with filtering turned on, you can
corrupt the
files. This feature should be used with text files <em>only</em>.</p>
@@ -289,7 +289,7 @@
directory relative to the project's base directory (or an absolute
filename), while the <code>path</code> attribute accepts colon-
or semicolon-separated lists of locations. The <code>path</code>
-attribute is intended to be used with predefined paths – in any other
+attribute is intended to be used with predefined paths - in any other
case, multiple elements with <code>location</code> attributes should be
preferred.</p>
<p>As a shortcut, the <code><classpath></code> tag
@@ -323,7 +323,7 @@
<p>If you want to use the same path-like structure for several tasks,
you can define them with a <code><path></code> element at the
same level as <i>target</i>s, and reference them via their
-<i>id</i> attribute – see <a href="#references">References</a> for an
+<i>id</i> attribute - see <a href="#references">References</a> for an
example.</p>
<p>A path-like structure can include a reference to another path-like
structure via nested <code><path></code> elements:</p>
@@ -405,7 +405,7 @@
<h3><a name="references">References</a></h3>
<p>The <code>id</code> attribute of the buildfile's elements can be
used to refer to them. This can useful if you are going to replicate
-the same snippet of XML over and over again – using a
+the same snippet of XML over and over again - using a
<code><classpath></code> structure more than once for
example.</p>
<p>The following example:</p>
Index: docs/manual/CoreTasks/echo.html
===================================================================
RCS file: /home/cvspublic/jakarta-ant/docs/manual/CoreTasks/echo.html,v
retrieving revision 1.2
diff -u -r1.2 echo.html
--- docs/manual/CoreTasks/echo.html 2001/02/13 12:31:50 1.2
+++ docs/manual/CoreTasks/echo.html 2001/03/08 20:15:07
@@ -31,7 +31,7 @@
<tr>
<td valign="top">append</td>
<td valign="top">Append to an existing file?</td>
- <td valign="top" align="center">No – default is false.</td>
+ <td valign="top" align="center">No - default is false.</td>
</tr>
</table>
<h3>Examples</h3>
Index: docs/manual/CoreTasks/style.html
===================================================================
RCS file: /home/cvspublic/jakarta-ant/docs/manual/CoreTasks/style.html,v
retrieving revision 1.2
diff -u -r1.2 style.html
--- docs/manual/CoreTasks/style.html 2001/02/13 12:31:52 1.2
+++ docs/manual/CoreTasks/style.html 2001/03/08 20:15:07
@@ -25,7 +25,7 @@
attributes of <code><fileset></code> (<code>dir</code> becomes
<code>basedir</code>)
as well as the nested <code><include></code>,
<code><exclude></code>
and <code><patternset></code> elements.</p>
-<p>Style supports the use of a <param> element which is use to pass
values
+<p>Style supports the use of a <param> element which is used to pass
values
to an <xsl:param> declaration.</p>
<h3>Parameters</h3>
<table border="1" cellpadding="2" cellspacing="0">
@@ -41,7 +41,7 @@
</tr>
<tr>
<td valign="top">destdir</td>
- <td valign="top">directory where to store the results.</td>
+ <td valign="top">directory in which to store the results.</td>
<td align="center" valign="top">Yes</td>
</tr>
<tr>
Index: docs/manual/CoreTypes/fileset.html
===================================================================
RCS file: /home/cvspublic/jakarta-ant/docs/manual/CoreTypes/fileset.html,v
retrieving revision 1.2
diff -u -r1.2 fileset.html
--- docs/manual/CoreTypes/fileset.html 2001/02/13 12:31:54 1.2
+++ docs/manual/CoreTypes/fileset.html 2001/03/08 20:15:09
@@ -13,7 +13,7 @@
patterns taken from a number of <a
href="patternset.html">PatternSets</a>. FileSets can appear inside tasks
that support this feature or at the same level as <code>target</code>
-– i.e., as children of <code>project</code>.</p>
+- i.e., as children of <code>project</code>.</p>
<p>PatternSets can be specified as nested
<code><patternset></code>
elements. In addition, FileSet holds an implicit PatternSet and
Index: docs/manual/CoreTypes/mapper.html
===================================================================
RCS file: /home/cvspublic/jakarta-ant/docs/manual/CoreTypes/mapper.html,v
retrieving revision 1.2
diff -u -r1.2 mapper.html
--- docs/manual/CoreTypes/mapper.html 2001/02/13 12:31:54 1.2
+++ docs/manual/CoreTypes/mapper.html 2001/03/08 20:15:09
@@ -11,16 +11,16 @@
<p>Some tasks take source files and create target files. Depending on
the task, it may be quite obvious which name a target file will have
(using <a href="../CoreTasks/javac.html">javac</a>, you know there will be
-<code>.class</code> files for your <code>.java</code> files) – in
+<code>.class</code> files for your <code>.java</code> files) - in
other cases you may want to specify the target files, either to help
Ant or to get an extra bit of functionality.</p>
<p>While source files are usually specified as <a
-href="fileset.html">fileset</a>s, you don't specify target files directly
–
+href="fileset.html">fileset</a>s, you don't specify target files directly -
instead, you tell Ant how to find the target file(s) for one source file. An
instance of <code>org.apache.tools.ant.util.FileNameMapper</code> is
responsible for this. It constructs target file names based on rules
that can be parameterized with <code>from</code> and <code>to</code>
-attributes – the exact meaning of which is implementation-dependent.</p>
+attributes - the exact meaning of which is implementation-dependent.</p>
<p>These instances are defined in <code><mapper></code> elements
with the following attributes:</p>
<table border="1" cellpadding="2" cellspacing="0">
@@ -64,7 +64,7 @@
</tr>
</table>
<p>The classpath can be specified via a nested
-<code><classpath></code>, as well – that is,
+<code><classpath></code>, as well - that is,
a <a href="../using.html#path">path</a>-like structure.</p>
<p>The built-in mapper types are:</p>
<h4><a name="identity-mapper">identity</a></h4>
@@ -128,7 +128,7 @@
</table>
<h4><a name="merge-mapper">merge</a></h4>
<p>The target file name will always be the same, as defined by
-<code>to</code> – <code>from</code> will be ignored.</p>
+<code>to</code> - <code>from</code> will be ignored.</p>
<h5>Examples:</h5>
<blockquote><pre>
<mapper type="merge" to="archive.tar"/>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
