From: Akim Demaille <akim@epita.fr>
Date: Fri, 30 Mar 2001 12:50:29 +0000 (+0000)
Subject: * doc/autoconf.texi: Use "invalid" instead of "illegal," as
X-Git-Tag: autoconf-2.50~74
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=a50e90e712ef4c74112bf301cf7f631fd6555137;p=thirdparty%2Fautoconf.git

* doc/autoconf.texi: Use "invalid" instead of "illegal," as
suggested by the GNU coding standards.
---

diff --git a/ChangeLog b/ChangeLog
index 8db3564d6..a4a2ea6d5 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,8 @@
+2001-03-30  Steven G. Johnson  <stevenj@alum.mit.edu>
+
+	* doc/autoconf.texi: Use "invalid" instead of "illegal," as
+	suggested by the GNU coding standards.
+
 2001-03-30  Tim Van Holder <tim.van.holder@pandora.be>
 
 	* m4sh.m4 (AS_BASENAME): New.
diff --git a/doc/autoconf.texi b/doc/autoconf.texi
index 1fb62fa11..ee70fc9fa 100644
--- a/doc/autoconf.texi
+++ b/doc/autoconf.texi
@@ -5329,22 +5329,24 @@ the directory, @command{make install} will do nothing (unless the
 @item The 8+3 limit (@sc{sfn})
 Because the @sc{dos} file system only stores the first 8 characters of
 the filename and the first 3 of the extension, those must be unique.
-That means that @samp{foobar-part1.c}, @samp{foobar-part2.c} and
-@samp{foobar-prettybird.c} all resolve to the same filename
-(@samp{FOOBAR-P.C}).  The same goes for @samp{foo.bar} and
-@samp{foo.bartender}.
+That means that @file{foobar-part1.c}, @file{foobar-part2.c} and
+@file{foobar-prettybird.c} all resolve to the same filename
+(@file{FOOBAR-P.C}).  The same goes for @file{foo.bar} and
+@file{foo.bartender}.
+
 Note: This is not usually a problem under Windows, as it uses numeric
-tails in the short version of filenames to make them unique.  However,
-a registry setting can turn this behaviour off.  While this makes it
+tails in the short version of filenames to make them unique.  However, a
+registry setting can turn this behaviour off.  While this makes it
 possible to share file trees containing long file names between @sc{sfn}
 and @sc{lfn} environments, it also means the above problem applies there
 as well.
 
-@item Illegal characters
-Some characters are illegal in @sc{dos} filenames, and should therefore
-be avoided. In a @sc{lfn} environment, these are '/', '\', '?', '*', ':',
-'<', '>', '|' and '"'.  In a @sc{sfn} environment, other characters are
-also illegal.  These include '+', ',', '[' and ']'.
+@item Invalid characters
+Some characters are invalid in @sc{dos} filenames, and should therefore
+be avoided. In a @sc{lfn} environment, these are @samp{/}, @samp{\},
+@samp{?}, @samp{*}, @samp{:}, @samp{<}, @samp{>}, @samp{|} and @samp{"}.
+In a @sc{sfn} environment, other characters are also invalid.  These
+include @samp{+}, @samp{,}, @samp{[} and @samp{]}.
 @end table
 
 @node Shell Substitutions, Assignments, File System Conventions, Portable Shell