From 4c9deafd613dec315ae5103d3a23937ce8822b9b Mon Sep 17 00:00:00 2001 From: Stefan Bodewig Date: Fri, 9 Mar 2001 08:54:35 +0000 Subject: [PATCH] Replace some entity references to – with a simple (and more portable) dash. Submitted by: Jesse Glick git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@268781 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/CoreTasks/echo.html | 2 +- docs/manual/CoreTasks/style.html | 4 ++-- docs/manual/CoreTypes/fileset.html | 2 +- docs/manual/CoreTypes/mapper.html | 10 +++++----- docs/manual/develop.html | 2 +- docs/manual/dirtasks.html | 2 +- docs/manual/install.html | 3 +-- docs/manual/intro.html | 2 +- docs/manual/using.html | 10 +++++----- 9 files changed, 18 insertions(+), 19 deletions(-) diff --git a/docs/manual/CoreTasks/echo.html b/docs/manual/CoreTasks/echo.html index 49510f768..f1e0aaae0 100644 --- a/docs/manual/CoreTasks/echo.html +++ b/docs/manual/CoreTasks/echo.html @@ -31,7 +31,7 @@ append Append to an existing file? - No – default is false. + No - default is false.

Examples

diff --git a/docs/manual/CoreTasks/style.html b/docs/manual/CoreTasks/style.html index 8dab1e6c6..ac8c4a979 100644 --- a/docs/manual/CoreTasks/style.html +++ b/docs/manual/CoreTasks/style.html @@ -25,7 +25,7 @@ inclusion/exclusion of files works, and how to write patterns.

attributes of <fileset> (dir becomes basedir) as well as the nested <include>, <exclude> and <patternset> elements.

-

Style supports the use of a <param> element which is use to pass values +

Style supports the use of a <param> element which is used to pass values to an <xsl:param> declaration.

Parameters

@@ -41,7 +41,7 @@ inclusion/exclusion of files works, and how to write patterns.

- + diff --git a/docs/manual/CoreTypes/fileset.html b/docs/manual/CoreTypes/fileset.html index 531615fdb..934c088b3 100644 --- a/docs/manual/CoreTypes/fileset.html +++ b/docs/manual/CoreTypes/fileset.html @@ -13,7 +13,7 @@ directory tree starting in a base directory and are matched by patterns taken from a number of PatternSets. FileSets can appear inside tasks that support this feature or at the same level as target -– i.e., as children of project.

+- i.e., as children of project.

PatternSets can be specified as nested <patternset> elements. In addition, FileSet holds an implicit PatternSet and diff --git a/docs/manual/CoreTypes/mapper.html b/docs/manual/CoreTypes/mapper.html index f00223401..909522eb5 100644 --- a/docs/manual/CoreTypes/mapper.html +++ b/docs/manual/CoreTypes/mapper.html @@ -11,16 +11,16 @@

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 javac, you know there will be -.class files for your .java files) – in +.class files for your .java files) - in other cases you may want to specify the target files, either to help Ant or to get an extra bit of functionality.

While source files are usually specified as filesets, you don't specify target files directly – +href="fileset.html">filesets, 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 org.apache.tools.ant.util.FileNameMapper is responsible for this. It constructs target file names based on rules that can be parameterized with from and to -attributes – the exact meaning of which is implementation-dependent.

+attributes - the exact meaning of which is implementation-dependent.

These instances are defined in <mapper> elements with the following attributes:

destdirdirectory where to store the results.directory in which to store the results. Yes
@@ -64,7 +64,7 @@ with the following attributes:

The classpath can be specified via a nested -<classpath>, as well – that is, +<classpath>, as well - that is, a path-like structure.

The built-in mapper types are:

identity

@@ -128,7 +128,7 @@ leading directory information stripped off. Both to and

merge

The target file name will always be the same, as defined by -to – from will be ignored.

+to - from will be ignored.

Examples:
 <mapper type="merge" to="archive.tar"/>
diff --git a/docs/manual/develop.html b/docs/manual/develop.html
index d767fa113..8b6d327dd 100644
--- a/docs/manual/develop.html
+++ b/docs/manual/develop.html
@@ -26,7 +26,7 @@ any primitive type (they are converted for you from their String-representation
 in the buildfile)
 
 
  • 
-boolean – your method will be passed the value 
+boolean - your method will be passed the value 
 true if the value specified in the buildfile is one of true,
 yes, or on)
 
    • 
diff --git a/docs/manual/dirtasks.html b/docs/manual/dirtasks.html
index 83cc0ce77..1609a3553 100644
--- a/docs/manual/dirtasks.html
+++ b/docs/manual/dirtasks.html
@@ -62,7 +62,7 @@ For example:
 /test/** matches all files/directories under /test/,
 such as /test/x.java,
 or /test/foo/bar/xyz.html, but not /xyz.xml.
    
-
    There is one "shorthand" – if a pattern ends
+
    There is one "shorthand" - if a pattern ends
 with /
 or \, then **
 is appended.
diff --git a/docs/manual/install.html b/docs/manual/install.html
index 2f6a899f6..84bd50bb5 100644
--- a/docs/manual/install.html
+++ b/docs/manual/install.html
@@ -222,7 +222,7 @@ property task.
 
 Just pass -DMYVAR=%MYVAR% (Windows) or
 -DMYVAR=$MYVAR (Unix)
-to Ant – you can then access
+to Ant - you can then access
 these variables inside your buildfile as ${MYVAR}.
    
 
 
    Two more options are: -quiet,
@@ -301,7 +301,6 @@ command. This example assumes you have set your classpath to include:
    
 install directory's lib directory if you are using the
 indicated feature. Note that only one of the regexp libraries is
 needed for use with the mappers.
    
-
    
 
 
diff --git a/docs/manual/intro.html b/docs/manual/intro.html
index 859a8f270..45f997a33 100644
--- a/docs/manual/intro.html
+++ b/docs/manual/intro.html
@@ -38,7 +38,7 @@ Task interface.
    Granted, this removes some of the expressive power that is inherent in being
 able to construct a shell command such as
 `find . -name foo -exec rm {}`, 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
diff --git a/docs/manual/using.html b/docs/manual/using.html
index bc74fc4be..58d6b83e5 100644
--- a/docs/manual/using.html
+++ b/docs/manual/using.html
@@ -54,7 +54,7 @@ for example, and a target for creating a distributable. You can only build a
 distributable when you have compiled first, so the distribute target
 depends on the compile target. Ant resolves these dependencies.
    It should be noted, however, that Ant's depends attribute
-only specifies the order in which targets should be executed – it
+only specifies the order 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.
 
    
@@ -265,7 +265,7 @@ programming and scripting languages, as well as with documentation systems.
    
 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.
    Warning: If you copy binary files with filtering turned on, you can corrupt the
 files. This feature should be used with text files only.
    
@@ -289,7 +289,7 @@ be used. This takes the general form of:
    
 directory relative to the project's base directory (or an absolute
 filename), while the path attribute accepts colon-
 or semicolon-separated lists of locations. The path
-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 location attributes should be
 preferred.
    As a shortcut, the <classpath> tag
@@ -323,7 +323,7 @@ by the classes directory.
    If you want to use the same path-like structure for several tasks,
 you can define them with a <path> element at the
 same level as targets, and reference them via their
-id attribute – see References for an
+id attribute - see References for an
 example.
    A path-like structure can include a reference to another path-like
 structure via nested <path> elements:
    
@@ -405,7 +405,7 @@ that contain space characters, nested arg elements can be used.
    References
    The id 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
 <classpath> structure more than once for
 example.
    The following example: