Use lower case characters in sc{} context.

Reported by Eli Zaretskii.

1 files changed, 26 insertions, 26 deletions

diff --git a/doc/textutils.texi b/doc/textutils.texi
index cafd2af54..1687d39d6 100644
--- a/doc/textutils.texi
+++ b/doc/textutils.texi
@@ -21,7 +21,7 @@
 START-INFO-DIR-ENTRY
 * Text utilities: (textutils).          GNU text utilities.
 * cat: (textutils)cat invocation.               Concatenate and write files.
-* cksum: (textutils)cksum invocation.           Print @sc{POSIX} CRC checksum.
+* cksum: (textutils)cksum invocation.           Print @sc{posix} CRC checksum.
 * comm: (textutils)comm invocation.             Compare sorted files by line.
 * csplit: (textutils)csplit invocation.         Split by context.
 * cut: (textutils)cut invocation.               Print selected parts of lines.
@@ -220,7 +220,7 @@ involved in improving this manual.  The entire GNU community will
 benefit.
 
 @cindex POSIX.2
-The GNU text utilities are mostly compatible with the @sc{POSIX.2} standard.
+The GNU text utilities are mostly compatible with the @sc{posix.2} standard.
 
 @c This paragraph appears in all of fileutils.texi, textutils.texi, and
 @c sh-utils.texi too -- so be sure to keep them consistent.
@@ -672,7 +672,7 @@ Output at most @var{bytes} bytes of the input.  Prefixes and suffixes on
 @opindex --strings
 @cindex string constants, outputting
 Instead of the normal output, output only @dfn{string constants}: at
-least @var{n} (3 by default) consecutive @sc{ASCII} graphic characters,
+least @var{n} (3 by default) consecutive @sc{ascii} graphic characters,
 followed by a null (zero) byte.
 
 @item -t @var{type}
@@ -687,14 +687,14 @@ of each output line using each of the data types that you specified,
 in the order that you specified.
 
 Adding a trailing ``z'' to any type specification appends a display
-of the @sc{ASCII} character representation of the printable characters
+of the @sc{ascii} character representation of the printable characters
 to the output line generated by the type specification.
 
 @table @samp
 @item a
 named character,
 @item c
-@sc{ASCII} character or backslash escape,
+@sc{ascii} character or backslash escape,
 @item d
 signed decimal,
 @item f
@@ -762,8 +762,8 @@ is not given at all, the default is 16.
 
 @end table
 
-The next several options map the old, pre-@sc{POSIX} format specification
-options to the corresponding @sc{POSIX} format specs.  GNU @code{od} accepts
+The next several options map the old, pre-@sc{posix} format specification
+options to the corresponding @sc{posix} format specs.  GNU @code{od} accepts
 any combination of old- and new-style options.  Format specification
 options accumulate.
 
@@ -779,7 +779,7 @@ Output as octal bytes.  Equivalent to @samp{-toC}.
 
 @item -c
 @opindex -c
-Output as @sc{ASCII} characters or backslash escapes.  Equivalent to
+Output as @sc{ascii} characters or backslash escapes.  Equivalent to
 @samp{-tc}.
 
 @item -d
@@ -1884,7 +1884,7 @@ by comparing the @code{cksum} output for the received files with the
 @code{cksum} output for the original files (typically given in the
 distribution).
 
-The CRC algorithm is specified by the @sc{POSIX.2} standard.  It is not
+The CRC algorithm is specified by the @sc{posix.2} standard.  It is not
 compatible with the BSD or System V @code{sum} algorithms (see the
 previous section); it is more robust.
 
@@ -2068,8 +2068,8 @@ input line length or restrictions on bytes allowed within lines.  In
 addition, if the final byte of an input file is not a newline, GNU
 @code{sort} silently supplies one.  A line's trailing newline is part of
 the line for comparison purposes; for example, with no options in an
-@sc{ASCII} locale, a line starting with a tab sorts before an empty line
-because tab precedes newline in the @sc{ASCII} collating sequence.
+@sc{ascii} locale, a line starting with a tab sorts before an empty line
+because tab precedes newline in the @sc{ascii} collating sequence.
 
 Upon any error, @code{sort} exits with a status of @samp{2}.
 
@@ -2216,7 +2216,7 @@ check that no pair of consecutive lines compares equal.
 @item -k @var{pos1}[,@var{pos2}]
 @opindex -k
 @cindex sort field
-The recommended, @sc{POSIX}, option for specifying a sort field.  The field
+The recommended, @sc{posix}, option for specifying a sort field.  The field
 consists of the part of the line between @var{pos1} and @var{pos2} (or the
 end of the line, if @var{pos2} is omitted), @emph{inclusive}.
 Fields and character positions are numbered starting with 1.
@@ -2226,8 +2226,8 @@ See below for more examples.
 @item -z
 @opindex -z
 @cindex sort zero-terminated lines
-Treat the input as a set of lines, each terminated by a zero byte (@sc{ASCII}
-@sc{NUL} (Null) character) instead of an @sc{ASCII} @sc{LF} (Line Feed).
+Treat the input as a set of lines, each terminated by a zero byte (@sc{ascii}
+@sc{nul} (Null) character) instead of an @sc{ascii} @sc{lf} (Line Feed).
 This option can be useful in conjunction with @samp{perl -0} or
 @samp{find -print0} and @samp{xargs -0} which do the same in order to
 reliably handle arbitrary pathnames (even those which contain Line Feed
@@ -2247,9 +2247,9 @@ options}.
 
 Historical (BSD and System V) implementations of @code{sort} have
 differed in their interpretation of some options, particularly
-@samp{-b}, @samp{-f}, and @samp{-n}.  GNU sort follows the @sc{POSIX}
+@samp{-b}, @samp{-f}, and @samp{-n}.  GNU sort follows the @sc{posix}
 behavior, which is usually (but not always!) like the System V behavior.
-According to @sc{POSIX}, @samp{-n} no longer implies @samp{-b}.  For
+According to @sc{posix}, @samp{-n} no longer implies @samp{-b}.  For
 consistency, @samp{-M} has been changed in the same way.  This may
 affect the meaning of character positions in field specifications in
 obscure cases.  The only fix is to add an explicit @samp{-b}.
@@ -2274,7 +2274,7 @@ from the global options it will be attached to both.
 Keys may span multiple fields.
 
 Here are some examples to illustrate various combinations of options.
-In them, the @sc{POSIX} @samp{-k} option is used to specify sort keys rather
+In them, the @sc{posix} @samp{-k} option is used to specify sort keys rather
 than the obsolete @samp{+@var{pos1}-@var{pos2}} syntax.
 
 @itemize @bullet
@@ -2646,7 +2646,7 @@ As it is setup now, the program assumes that the input file is coded
 using 8-bit ISO 8859-1 code, also known as Latin-1 character set,
 @emph{unless} if it is compiled for MS-DOS, in which case it uses the
 character set of the IBM-PC.  (GNU @code{ptx} is not known to work on
-smaller MS-DOS machines anymore.)  Compared to 7-bit @sc{ASCII}, the set of
+smaller MS-DOS machines anymore.)  Compared to 7-bit @sc{ascii}, the set of
 characters which are letters is then different, this fact alters the
 behaviour of regular expression matching.  Thus, the default regular
 expression for a keyword allows foreign or diacriticized letters.
@@ -2935,7 +2935,7 @@ sequence @code{^\@{ @}} and @code{~\@{ @}} respectively.  Other
 diacriticized characters of the underlying character set produce an
 appropriate @TeX{} sequence as far as possible.  The other non-graphical
 characters, like newline and tab, and all others characters which are
-not part of @sc{ASCII}, are merely changed to exactly one space, with no
+not part of @sc{ascii}, are merely changed to exactly one space, with no
 special attempt to compress consecutive spaces.  Let me know how to
 improve this special character processing for @TeX{}.
 
@@ -3217,7 +3217,7 @@ to the join field.  However, when printing unpairable lines
 (using either of the @samp{-a} or @samp{-v} options), there is no way
 to specify the join field using @var{m.n} in @var{field-list}
 if there are unpairable lines in both files.
-To give @code{join} that functionality, @sc{POSIX} invented the @samp{0}
+To give @code{join} that functionality, @sc{posix} invented the @samp{0}
 field specification notation.
 
 The elements in @var{field-list}
@@ -3460,7 +3460,7 @@ typically have the same length.  If @var{set1} is shorter than
 @var{set2}, the extra characters at the end of @var{set2} are ignored.
 
 On the other hand, making @var{set1} longer than @var{set2} is not
-portable; @sc{POSIX.2} says that the result is undefined.  In this situation,
+portable; @sc{posix.2} says that the result is undefined.  In this situation,
 BSD @code{tr} pads @var{set2} to the length of @var{set1} by repeating
 the last character of @var{set2} as many times as necessary.  System V
 @code{tr} truncates @var{set1} to the length of @var{set2}.
@@ -3558,7 +3558,7 @@ cat "$@@" \
 @vindex POSIXLY_CORRECT
 Setting the environment variable @env{POSIXLY_CORRECT} turns off the
 following warning and error messages, for strict compliance with
-@sc{POSIX.2}.  Otherwise, the following diagnostics are issued:
+@sc{posix.2}.  Otherwise, the following diagnostics are issued:
 
 @enumerate
 
@@ -3566,7 +3566,7 @@ following warning and error messages, for strict compliance with
 When the @samp{--delete} option is given but @samp{--squeeze-repeats}
 is not, and @var{set2} is given, GNU @code{tr} by default prints
 a usage message and exits, because @var{set2} would not be used.
-The @sc{POSIX} specification says that @var{set2} must be ignored in
+The @sc{posix} specification says that @var{set2} must be ignored in
 this case. Silently ignoring arguments is a bad idea.
 
 @item
@@ -3577,7 +3577,7 @@ value 400 octal does not fit into a single byte.
 @end enumerate
 
 GNU @code{tr} does not provide complete BSD or System V compatibility.
-For example, it is impossible to disable interpretation of the @sc{POSIX}
+For example, it is impossible to disable interpretation of the @sc{posix}
 constructs @samp{[:alpha:]}, @samp{[=c=]}, and @samp{[c*10]}.  Also, GNU
 @code{tr} does not delete zero bytes automatically, unlike traditional
 Unix versions, which provide no way to preserve zero bytes.
@@ -3795,7 +3795,7 @@ redirected standard output of your program away from your screen.
 For filter programs to work together, the format of the data has to be
 agreed upon.  The most straightforward and easiest format to use is simply
 lines of text.  Unix data files are generally just streams of bytes, with
-lines delimited by the @sc{ASCII} @sc{LF} (Line Feed) character,
+lines delimited by the @sc{ascii} @sc{lf} (Line Feed) character,
 conventionally called a ``newline'' in the Unix literature. (This is
 @code{'\n'} if you're a C programmer.)  This is the format used by all
 the traditional filtering programs.  (Many earlier operating systems
@@ -4047,7 +4047,7 @@ $ tr '[A-Z]' '[a-z]' < whats.gnu | tr -cd '[A-Za-z0-9_ \012]' | ...
 The second @code{tr} command operates on the complement of the listed
 characters, which are all the letters, the digits, the underscore, and
 the blank.  The @samp{\012} represents the newline character; it has to
-be left alone.  (The @sc{ASCII} tab character should also be included for
+be left alone.  (The @sc{ascii} tab character should also be included for
 good measure in a production script.)
 
 At this point, we have data consisting of words separated by blank space.