Mercurial > emacs
changeset 52978:1a5c50faf357
Replace @sc{foo} with @acronym{FOO}.
| author | Eli Zaretskii <eliz@gnu.org> |
|---|---|
| date | Sun, 02 Nov 2003 06:29:59 +0000 |
| parents | 8af8c70252c1 |
| children | 3649390c0f91 |
| files | lispref/anti.texi lispref/backups.texi lispref/commands.texi lispref/customize.texi lispref/display.texi lispref/files.texi lispref/internals.texi lispref/keymaps.texi lispref/loading.texi lispref/modes.texi lispref/nonascii.texi lispref/numbers.texi lispref/objects.texi lispref/os.texi lispref/positions.texi lispref/processes.texi lispref/searching.texi lispref/sequences.texi lispref/streams.texi lispref/strings.texi lispref/syntax.texi lispref/text.texi |
| diffstat | 22 files changed, 165 insertions(+), 165 deletions(-) [+] |
line wrap: on
line diff
--- a/lispref/anti.texi Sat Nov 01 19:58:03 2003 +0000 +++ b/lispref/anti.texi Sun Nov 02 06:29:59 2003 +0000 @@ -100,7 +100,7 @@ the scroll bars. @item -For simplicity, all @sc{ascii} characters now have the same height and width. +For simplicity, all @acronym{ASCII} characters now have the same height and width. (Certain characters, such as Chinese characters, always have twice the standard width.) All characters are created equal.
--- a/lispref/backups.texi Sat Nov 01 19:58:03 2003 +0000 +++ b/lispref/backups.texi Sun Nov 02 06:29:59 2003 +0000 @@ -633,7 +633,7 @@ this file to find them. The default name for this file specifies your home directory and starts -with @samp{.saves-}. It also contains the Emacs process @sc{id} and the +with @samp{.saves-}. It also contains the Emacs process @acronym{ID} and the host name. @end defvar
--- a/lispref/commands.texi Sat Nov 01 19:58:03 2003 +0000 +++ b/lispref/commands.texi Sun Nov 02 06:29:59 2003 +0000 @@ -340,7 +340,7 @@ specification. If the key sequence that invoked the command has @var{n} events that are lists, the @var{n}th @samp{e} provides the @var{n}th such event. Events that are not lists, such as function keys -and @sc{ascii} characters, do not count where @samp{e} is concerned. +and @acronym{ASCII} characters, do not count where @samp{e} is concerned. @item f A file name of an existing file (@pxref{File Names}). The default @@ -797,7 +797,7 @@ @end example @noindent -The value is 5 because that is the @sc{ascii} code for @kbd{C-e}. +The value is 5 because that is the @acronym{ASCII} code for @kbd{C-e}. The alias @code{last-command-char} exists for compatibility with Emacs version 18. @@ -916,14 +916,14 @@ @ifnottex 2**26 @end ifnottex -bit in the character code indicates a non-@sc{ascii} +bit in the character code indicates a non-@acronym{ASCII} control character. @sc{ascii} control characters such as @kbd{C-a} have special basic codes of their own, so Emacs needs no special bit to indicate them. Thus, the code for @kbd{C-a} is just 1. -But if you type a control combination not in @sc{ascii}, such as +But if you type a control combination not in @acronym{ASCII}, such as @kbd{%} with the control key, the numeric value you get is the code for @kbd{%} plus @tex @@ -932,7 +932,7 @@ @ifnottex 2**26 @end ifnottex -(assuming the terminal supports non-@sc{ascii} +(assuming the terminal supports non-@acronym{ASCII} control characters). @item shift @@ -943,13 +943,13 @@ @ifnottex 2**25 @end ifnottex -bit in the character code indicates an @sc{ascii} control +bit in the character code indicates an @acronym{ASCII} control character typed with the shift key held down. For letters, the basic code itself indicates upper versus lower case; for digits and punctuation, the shift key selects an entirely different character with a different basic code. In order to keep within the -@sc{ascii} character set whenever possible, Emacs avoids using the +@acronym{ASCII} character set whenever possible, Emacs avoids using the @tex @math{2^{25}} @end tex @@ -958,7 +958,7 @@ @end ifnottex bit for those characters. -However, @sc{ascii} provides no way to distinguish @kbd{C-A} from +However, @acronym{ASCII} provides no way to distinguish @kbd{C-A} from @kbd{C-a}, so Emacs uses the @tex @math{2^{25}} @@ -1032,10 +1032,10 @@ @table @asis @item @code{backspace}, @code{tab}, @code{newline}, @code{return}, @code{delete} -These keys correspond to common @sc{ascii} control characters that have +These keys correspond to common @acronym{ASCII} control characters that have special keys on most keyboards. -In @sc{ascii}, @kbd{C-i} and @key{TAB} are the same character. If the +In @acronym{ASCII}, @kbd{C-i} and @key{TAB} are the same character. If the terminal can distinguish between them, Emacs conveys the distinction to Lisp programs by representing the former as the integer 9, and the latter as the symbol @code{tab}. @@ -1047,7 +1047,7 @@ symbols in this group. The function @code{read-char} likewise converts these events into characters. -In @sc{ascii}, @key{BS} is really @kbd{C-h}. But @code{backspace} +In @acronym{ASCII}, @key{BS} is really @kbd{C-h}. But @code{backspace} converts into the character code 127 (@key{DEL}), not into code 8 (@key{BS}). This is what most users prefer. @@ -1096,7 +1096,7 @@ Emacs supports four kinds of mouse events: click events, drag events, button-down events, and motion events. All mouse events are represented -as lists. The @sc{car} of the list is the event type; this says which +as lists. The @acronym{CAR} of the list is the event type; this says which mouse button was involved, and which modifier keys were used with it. The event type can also distinguish double or triple button presses (@pxref{Repeat Events}). The rest of the list elements give position @@ -1521,7 +1521,7 @@ key binding purposes. For a keyboard event, the event type equals the event value; thus, the event type for a character is the character, and the event type for a function key symbol is the symbol itself. For -events that are lists, the event type is the symbol in the @sc{car} of +events that are lists, the event type is the symbol in the @acronym{CAR} of the list. Thus, the event type is always a symbol or a character. Two events of the same type are equivalent where key bindings are @@ -1810,7 +1810,7 @@ can include these codes. @item -Non-@sc{ascii} characters above 256 can be included in a multibyte string. +Non-@acronym{ASCII} characters above 256 can be included in a multibyte string. @item Other keyboard character events cannot fit in a string. This includes @@ -1979,7 +1979,7 @@ If @var{inherit-input-method} is non-@code{nil}, then the current input method (if any) is employed to make it possible to enter a -non-@sc{ascii} character. Otherwise, input method handling is disabled +non-@acronym{ASCII} character. Otherwise, input method handling is disabled for reading this event. If @code{cursor-in-echo-area} is non-@code{nil}, then @code{read-event} @@ -2009,7 +2009,7 @@ function key event), @code{read-char} signals an error. The arguments work as in @code{read-event}. -In the first example, the user types the character @kbd{1} (@sc{ascii} +In the first example, the user types the character @kbd{1} (@acronym{ASCII} code 49). The second example shows a keyboard macro definition that calls @code{read-char} from the minibuffer using @code{eval-expression}. @code{read-char} reads the keyboard macro's very next character, which @@ -2189,7 +2189,7 @@ as part of a command or explicitly by a Lisp program. In the example below, the Lisp program reads the character @kbd{1}, -@sc{ascii} code 49. It becomes the value of @code{last-input-event}, +@acronym{ASCII} code 49. It becomes the value of @code{last-input-event}, while @kbd{C-e} (we assume @kbd{C-x C-e} command is used to evaluate this expression) remains the value of @code{last-command-event}. @@ -2513,7 +2513,7 @@ value, @var{arg}. The argument may be a symbol, a number, or a list. If it is @code{nil}, the value 1 is returned; if it is @code{-}, the value @minus{}1 is returned; if it is a number, that number is returned; -if it is a list, the @sc{car} of that list (which should be a number) is +if it is a list, the @acronym{CAR} of that list (which should be a number) is returned. @end defun
--- a/lispref/customize.texi Sat Nov 01 19:58:03 2003 +0000 +++ b/lispref/customize.texi Sun Nov 02 06:29:59 2003 +0000 @@ -62,7 +62,7 @@ in the customization buffer with the Info node name. @item (url-link @var{url}) -Link to a web page; @var{url} is a string which specifies the @sc{url}. +Link to a web page; @var{url} is a string which specifies the @acronym{URL}. The link appears in the customization buffer as @var{url}. @item (emacs-commentary-link @var{library})
--- a/lispref/display.texi Sat Nov 01 19:58:03 2003 +0000 +++ b/lispref/display.texi Sun Nov 02 06:29:59 2003 +0000 @@ -2414,7 +2414,7 @@ For the remaining character sets, those that you don't specify explicitly, Emacs chooses a font based on @var{fontpattern}: it replaces @samp{fontset-@var{alias}} with a value that names one character set. -For the @sc{ascii} character set, @samp{fontset-@var{alias}} is replaced +For the @acronym{ASCII} character set, @samp{fontset-@var{alias}} is replaced with @samp{ISO8859-1}. In addition, when several consecutive fields are wildcards, Emacs @@ -2430,7 +2430,7 @@ @end example @noindent -the font specification for @sc{ascii} characters would be this: +the font specification for @acronym{ASCII} characters would be this: @example -*-fixed-medium-r-normal-*-24-*-ISO8859-1 @@ -3476,19 +3476,19 @@ All other codes in the range 0 through 31, and code 127, display in one of two ways according to the value of @code{ctl-arrow}. If it is non-@code{nil}, these codes map to sequences of two glyphs, where the -first glyph is the @sc{ascii} code for @samp{^}. (A display table can +first glyph is the @acronym{ASCII} code for @samp{^}. (A display table can specify a glyph to use instead of @samp{^}.) Otherwise, these codes map just like the codes in the range 128 to 255. On MS-DOS terminals, Emacs arranges by default for the character code 127 to be mapped to the glyph code 127, which normally displays as an -empty polygon. This glyph is used to display non-@sc{ascii} characters +empty polygon. This glyph is used to display non-@acronym{ASCII} characters that the MS-DOS terminal doesn't support. @xref{MS-DOS and MULE,,, emacs, The GNU Emacs Manual}. @item Character codes 128 through 255 map to sequences of four glyphs, where -the first glyph is the @sc{ascii} code for @samp{\}, and the others are +the first glyph is the @acronym{ASCII} code for @samp{\}, and the others are digit characters representing the character code in octal. (A display table can specify a glyph to use instead of @samp{\}.) @@ -3551,7 +3551,7 @@ @cindex display table You can use the @dfn{display table} feature to control how all possible character codes display on the screen. This is useful for displaying -European languages that have letters not in the @sc{ascii} character +European languages that have letters not in the @acronym{ASCII} character set. The display table maps each character code into a sequence of
--- a/lispref/files.texi Sat Nov 01 19:58:03 2003 +0000 +++ b/lispref/files.texi Sun Nov 02 06:29:59 2003 +0000 @@ -993,7 +993,7 @@ is 1, then the file is writable by all users, etc. The highest value returnable is 4095 (7777 octal), meaning that -everyone has read, write, and execute permission, that the @sc{suid} bit +everyone has read, write, and execute permission, that the @acronym{SUID} bit is set for both others and group, and that the sticky bit is set. @example @@ -1066,10 +1066,10 @@ (@pxref{Changing Files}). @item -The file's @sc{uid}. +The file's @acronym{UID}. @item -The file's @sc{gid}. +The file's @acronym{GID}. @item The time of last access, as a list of two integers. @@ -1092,7 +1092,7 @@ as in @samp{ls -l}. @item -@code{t} if the file's @sc{gid} would change if file were +@code{t} if the file's @acronym{GID} would change if file were deleted and recreated; @code{nil} otherwise. @item @@ -1136,10 +1136,10 @@ directory). @item 2235 -is owned by the user with @sc{uid} 2235. +is owned by the user with @acronym{UID} 2235. @item 75 -is in the group with @sc{gid} 75. +is in the group with @acronym{GID} 75. @item (8489 20284) was last accessed on Aug 19 00:09. @@ -1158,7 +1158,7 @@ has a mode of read and write access for the owner, group, and world. @item nil -would retain the same @sc{gid} if it were recreated. +would retain the same @acronym{GID} if it were recreated. @item 129500 has an inode number of 129500.
--- a/lispref/internals.texi Sat Nov 01 19:58:03 2003 +0000 +++ b/lispref/internals.texi Sun Nov 02 06:29:59 2003 +0000 @@ -1388,7 +1388,7 @@ The associated buffer of the process. @item pid -An integer, the Unix process @sc{id}. +An integer, the Unix process @acronym{ID}. @item childp A flag, non-@code{nil} if this is really a child process. @@ -1418,7 +1418,7 @@ message in the process buffer. @item pty_flag -Non-@code{nil} if communication with the subprocess uses a @sc{pty}; +Non-@code{nil} if communication with the subprocess uses a @acronym{PTY}; @code{nil} if it uses a pipe. @item infd
--- a/lispref/keymaps.texi Sat Nov 01 19:58:03 2003 +0000 +++ b/lispref/keymaps.texi Sun Nov 02 06:29:59 2003 +0000 @@ -231,9 +231,9 @@ @defun make-keymap &optional prompt This function creates and returns a new full keymap. That keymap contains a char-table (@pxref{Char-Tables}) with 384 slots: the first -128 slots are for defining all the @sc{ascii} characters, the next 128 +128 slots are for defining all the @acronym{ASCII} characters, the next 128 slots are for 8-bit European characters, and each one of the final 128 -slots is for one character set of non-@sc{ascii} characters supported by +slots is for one character set of non-@acronym{ASCII} characters supported by Emacs. The new keymap initially binds all these characters to @code{nil}, and does not bind any other kind of event. @@ -593,7 +593,7 @@ This function returns the current buffer's local keymap, or @code{nil} if it has none. In the following example, the keymap for the @samp{*scratch*} buffer (using Lisp Interaction mode) is a sparse keymap -in which the entry for @key{ESC}, @sc{ascii} code 27, is another sparse +in which the entry for @key{ESC}, @acronym{ASCII} code 27, is another sparse keymap. @example @@ -999,7 +999,7 @@ translating a meta character to a two-character sequence so it can be looked up in a keymap. For useful results, the value should be a prefix event (@pxref{Prefix Keys}). The default value is 27, which is the -@sc{ascii} code for @key{ESC}. +@acronym{ASCII} code for @key{ESC}. As long as the value of @code{meta-prefix-char} remains 27, key lookup translates @kbd{M-b} into @kbd{@key{ESC} b}, which is normally defined @@ -1361,8 +1361,8 @@ redefines the first (leftmost) mouse button, typed with the Meta key, to set point where you click. -@cindex non-@sc{ascii} text in keybindings - Be careful when using non-@sc{ascii} text characters in Lisp +@cindex non-@acronym{ASCII} text in keybindings + Be careful when using non-@acronym{ASCII} text characters in Lisp specifications of keys to bind. If these are read as multibyte text, as they usually will be in a Lisp file (@pxref{Loading Non-ASCII}), you must type the keys as multibyte too. For instance, if you use this: @@ -1576,7 +1576,7 @@ string representing the first key sequence found, rather than a list of all possible key sequences. If @var{firstonly} is @code{t}, then the value is the first key sequence, except that key sequences consisting -entirely of @sc{ascii} characters (or meta variants of @sc{ascii} +entirely of @acronym{ASCII} characters (or meta variants of @acronym{ASCII} characters) are preferred to all other key sequences. If @var{noindirect} is non-@code{nil}, @code{where-is-internal} doesn't @@ -1609,13 +1609,13 @@ The listing describes meta characters as @key{ESC} followed by the corresponding non-meta character. -When several characters with consecutive @sc{ascii} codes have the +When several characters with consecutive @acronym{ASCII} codes have the same definition, they are shown together, as @samp{@var{firstchar}..@var{lastchar}}. In this instance, you need to -know the @sc{ascii} codes to understand which characters this means. +know the @acronym{ASCII} codes to understand which characters this means. For example, in the default global map, the characters @samp{@key{SPC} -..@: ~} are described by a single line. @key{SPC} is @sc{ascii} 32, -@kbd{~} is @sc{ascii} 126, and the characters between them include all +..@: ~} are described by a single line. @key{SPC} is @acronym{ASCII} 32, +@kbd{~} is @acronym{ASCII} 126, and the characters between them include all the normal printing characters, (e.g., letters, digits, punctuation, etc.@:); all these characters are bound to @code{self-insert-command}. @end deffn @@ -1695,7 +1695,7 @@ The @sc{car}, @var{item-string}, is the string to be displayed in the menu. It should be short---preferably one to three words. It should describe the action of the command it corresponds to. Note that it is -not generally possible to display non-ASCII text in menus. It will +not generally possible to display non-@acronym{ASCII} text in menus. It will work for keyboard menus and will work to a large extent when Emacs is built with Gtk+ support.@footnote{In this case, the text is first encoded using the @code{utf-8} coding system and then rendered by the
--- a/lispref/loading.texi Sat Nov 01 19:58:03 2003 +0000 +++ b/lispref/loading.texi Sun Nov 02 06:29:59 2003 +0000 @@ -37,7 +37,7 @@ @menu * How Programs Do Loading:: The @code{load} function and others. * Library Search:: Finding a library to load. -* Loading Non-ASCII:: Non-@sc{ascii} characters in Emacs Lisp files. +* Loading Non-ASCII:: Non-@acronym{ASCII} characters in Emacs Lisp files. * Autoload:: Setting up a function to autoload. * Repeated Loading:: Precautions about loading a file twice. * Named Features:: Loading a library if it isn't already loaded. @@ -293,9 +293,9 @@ @end defvar @node Loading Non-ASCII -@section Loading Non-@sc{ascii} Characters +@section Loading Non-@acronym{ASCII} Characters - When Emacs Lisp programs contain string constants with non-@sc{ascii} + When Emacs Lisp programs contain string constants with non-@acronym{ASCII} characters, these can be represented within Emacs either as unibyte strings or as multibyte strings (@pxref{Text Representations}). Which representation is used depends on how the file is read into Emacs. If @@ -309,7 +309,7 @@ To make the results more predictable, Emacs always performs decoding into the multibyte representation when loading Lisp files, even if it was started with the @samp{--unibyte} option. This means that string -constants with non-@sc{ascii} characters translate into multibyte +constants with non-@acronym{ASCII} characters translate into multibyte strings. The only exception is when a particular file specifies no decoding. @@ -321,7 +321,7 @@ @code{default-enable-multibyte-characters}, and convert representations appropriately. - In most Emacs Lisp programs, the fact that non-@sc{ascii} strings are + In most Emacs Lisp programs, the fact that non-@acronym{ASCII} strings are multibyte strings should not be noticeable, since inserting them in unibyte buffers converts them to unibyte automatically. However, if this does make a difference, you can force a particular Lisp file to be @@ -329,7 +329,7 @@ comment on the file's first line. With that designator, the file will unconditionally be interpreted as unibyte, even in an ordinary multibyte Emacs session. This can matter when making keybindings to -non-@sc{ascii} characters written as @code{?v@var{literal}}. +non-@acronym{ASCII} characters written as @code{?v@var{literal}}. @node Autoload @section Autoload
--- a/lispref/modes.texi Sat Nov 01 19:58:03 2003 +0000 +++ b/lispref/modes.texi Sun Nov 02 06:29:59 2003 +0000 @@ -423,7 +423,7 @@ @group ;; @r{Set syntax of chars up to 0 to class of chars that are} ;; @r{part of symbol names but not words.} - ;; @r{(The number 0 is @code{48} in the @sc{ascii} character set.)} + ;; @r{(The number 0 is @code{48} in the @acronym{ASCII} character set.)} (while (< i ?0) (modify-syntax-entry i "_ " emacs-lisp-mode-syntax-table) (setq i (1+ i)))
--- a/lispref/nonascii.texi Sat Nov 01 19:58:03 2003 +0000 +++ b/lispref/nonascii.texi Sun Nov 02 06:29:59 2003 +0000 @@ -4,11 +4,11 @@ @c See the file elisp.texi for copying conditions. @setfilename ../info/characters @node Non-ASCII Characters, Searching and Matching, Text, Top -@chapter Non-@sc{ascii} Characters +@chapter Non-@acronym{ASCII} Characters @cindex multibyte characters -@cindex non-@sc{ascii} characters +@cindex non-@acronym{ASCII} characters - This chapter covers the special issues relating to non-@sc{ascii} + This chapter covers the special issues relating to non-@acronym{ASCII} characters and how they are stored in strings and buffers. @menu @@ -44,8 +44,8 @@ @cindex unibyte text In unibyte representation, each character occupies one byte and therefore the possible character codes range from 0 to 255. Codes 0 -through 127 are @sc{ascii} characters; the codes from 128 through 255 -are used for one non-@sc{ascii} character set (you can choose which +through 127 are @acronym{ASCII} characters; the codes from 128 through 255 +are used for one non-@acronym{ASCII} character set (you can choose which character set by setting the variable @code{nonascii-insert-offset}). @cindex leading code @@ -134,14 +134,14 @@ acceptable because the buffer's representation is a choice made by the user that cannot be overridden automatically. - Converting unibyte text to multibyte text leaves @sc{ascii} characters + Converting unibyte text to multibyte text leaves @acronym{ASCII} characters unchanged, and likewise character codes 128 through 159. It converts -the non-@sc{ascii} codes 160 through 255 by adding the value +the non-@acronym{ASCII} codes 160 through 255 by adding the value @code{nonascii-insert-offset} to each character code. By setting this variable, you specify which character set the unibyte characters correspond to (@pxref{Character Sets}). For example, if @code{nonascii-insert-offset} is 2048, which is @code{(- (make-char -'latin-iso8859-1) 128)}, then the unibyte non-@sc{ascii} characters +'latin-iso8859-1) 128)}, then the unibyte non-@acronym{ASCII} characters correspond to Latin 1. If it is 2688, which is @code{(- (make-char 'greek-iso8859-7) 128)}, then they correspond to Greek letters. @@ -153,10 +153,10 @@ text. @defvar nonascii-insert-offset -This variable specifies the amount to add to a non-@sc{ascii} character +This variable specifies the amount to add to a non-@acronym{ASCII} character when converting unibyte text to multibyte. It also applies when @code{self-insert-command} inserts a character in the unibyte -non-@sc{ascii} range, 128 through 255. However, the functions +non-@acronym{ASCII} range, 128 through 255. However, the functions @code{insert} and @code{insert-char} do not perform this conversion. The right value to use to select character set @var{cs} is @code{(- @@ -263,7 +263,7 @@ values in that range are valid. The values 128 through 255 are not entirely proper in multibyte text, but they can occur if you do explicit encoding and decoding (@pxref{Explicit Encoding}). Some other character -codes cannot occur at all in multibyte text. Only the @sc{ascii} codes +codes cannot occur at all in multibyte text. Only the @acronym{ASCII} codes 0 through 127 are completely legitimate in both representations. @defun char-valid-p charcode &optional genericp @@ -301,8 +301,8 @@ characters, generally known as Big 5, is divided into two Emacs character sets, @code{chinese-big5-1} and @code{chinese-big5-2}. - @sc{ascii} characters are in character set @code{ascii}. The -non-@sc{ascii} characters 128 through 159 are in character set + @acronym{ASCII} characters are in character set @code{ascii}. The +non-@acronym{ASCII} characters 128 through 159 are in character set @code{eight-bit-control}, and codes 160 through 255 are in character set @code{eight-bit-graphic}. @@ -336,8 +336,8 @@ @cindex dimension (of character set) In multibyte representation, each character occupies one or more bytes. Each character set has an @dfn{introduction sequence}, which is -normally one or two bytes long. (Exception: the @sc{ascii} character -set and the @sc{eight-bit-graphic} character set have a zero-length +normally one or two bytes long. (Exception: the @code{ascii} character +set and the @code{eight-bit-graphic} character set have a zero-length introduction sequence.) The introduction sequence is the beginning of the byte sequence for any character in the character set. The rest of the character's bytes distinguish it from the other characters in the @@ -426,8 +426,8 @@ @result{} (latin-iso8859-1 0) @end example -The character sets @sc{ascii}, @sc{eight-bit-control}, and -@sc{eight-bit-graphic} don't have corresponding generic characters. If +The character sets @code{ascii}, @code{eight-bit-control}, and +@code{eight-bit-graphic} don't have corresponding generic characters. If @var{charset} is one of them and you don't supply @var{code1}, @code{make-char} returns the character code corresponding to the smallest code in @var{charset}. @@ -744,7 +744,7 @@ return value is just one coding system, the one that is highest in priority. -If the region contains only @sc{ascii} characters, the value +If the region contains only @acronym{ASCII} characters, the value is @code{undecided} or @code{(undecided)}. @end defun @@ -846,12 +846,12 @@ expression that matches certain file names. The element applies to file names that match @var{pattern}. -The @sc{cdr} of the element, @var{coding}, should be either a coding +The @acronym{CDR} of the element, @var{coding}, should be either a coding system, a cons cell containing two coding systems, or a function name (a symbol with a function definition). If @var{coding} is a coding system, that coding system is used for both reading the file and writing it. If -@var{coding} is a cons cell containing two coding systems, its @sc{car} -specifies the coding system for decoding, and its @sc{cdr} specifies the +@var{coding} is a cons cell containing two coding systems, its @acronym{CAR} +specifies the coding system for decoding, and its @acronym{cdr} specifies the coding system for encoding. If @var{coding} is a function name, the function must return a coding @@ -975,7 +975,7 @@ @example ;; @r{Read the file with no character code conversion.} -;; @r{Assume @sc{crlf} represents end-of-line.} +;; @r{Assume @acronym{crlf} represents end-of-line.} (let ((coding-system-for-write 'emacs-mule-dos)) (insert-file-contents filename)) @end example @@ -1175,9 +1175,9 @@ @section Input Methods @cindex input methods - @dfn{Input methods} provide convenient ways of entering non-@sc{ascii} + @dfn{Input methods} provide convenient ways of entering non-@acronym{ASCII} characters from the keyboard. Unlike coding systems, which translate -non-@sc{ascii} characters to and from encodings meant to be read by +non-@acronym{ASCII} characters to and from encodings meant to be read by programs, input methods provide human-friendly commands. (@xref{Input Methods,,, emacs, The GNU Emacs Manual}, for information on how users use input methods to enter text.) How to define input methods is not
--- a/lispref/numbers.texi Sat Nov 01 19:58:03 2003 +0000 +++ b/lispref/numbers.texi Sun Nov 02 06:29:59 2003 +0000 @@ -163,12 +163,12 @@ value is 1500. They are all equivalent. You can also use a minus sign to write negative floating point numbers, as in @samp{-1.0}. -@cindex IEEE floating point +@cindex @acronym{IEEE} floating point @cindex positive infinity @cindex negative infinity @cindex infinity @cindex NaN - Most modern computers support the IEEE floating point standard, which + Most modern computers support the @acronym{IEEE} floating point standard, which provides for positive infinity and negative infinity as floating point values. It also provides for a class of values called NaN or ``not-a-number''; numerical functions return such values in cases where @@ -189,7 +189,7 @@ @end table In addition, the value @code{-0.0} is distinguishable from ordinary -zero in IEEE floating point (although @code{equal} and @code{=} consider +zero in @acronym{IEEE} floating point (although @code{equal} and @code{=} consider them equal values). You can use @code{logb} to extract the binary exponent of a floating @@ -565,7 +565,7 @@ @cindex @code{arith-error} in division If you divide an integer by 0, an @code{arith-error} error is signaled. (@xref{Errors}.) Floating point division by zero returns either -infinity or a NaN if your machine supports IEEE floating point; +infinity or a NaN if your machine supports @acronym{IEEE} floating point; otherwise, it signals an @code{arith-error} error. @example @@ -1166,7 +1166,7 @@ If you want random numbers that don't always come out the same, execute @code{(random t)}. This chooses a new seed based on the current time of -day and on Emacs's process @sc{id} number. +day and on Emacs's process @acronym{ID} number. @defun random &optional limit This function returns a pseudo-random integer. Repeated calls return a @@ -1176,7 +1176,7 @@ nonnegative and less than @var{limit}. If @var{limit} is @code{t}, it means to choose a new seed based on the -current time of day and on Emacs's process @sc{id} number. +current time of day and on Emacs's process @acronym{ID} number. @c "Emacs'" is incorrect usage! On some machines, any integer representable in Lisp may be the result
--- a/lispref/objects.texi Sat Nov 01 19:58:03 2003 +0000 +++ b/lispref/objects.texi Sun Nov 02 06:29:59 2003 +0000 @@ -216,7 +216,7 @@ @node Character Type @subsection Character Type -@cindex @sc{ascii} character codes +@cindex @acronym{ASCII} character codes A @dfn{character} in Emacs Lisp is nothing more than an integer. In other words, characters are represented by their character codes. For @@ -228,8 +228,8 @@ Characters in strings, buffers, and files are currently limited to the range of 0 to 524287---nineteen bits. But not all values in that range -are valid character codes. Codes 0 through 127 are @sc{ascii} codes; the -rest are non-@sc{ascii} (@pxref{Non-ASCII Characters}). Characters that represent +are valid character codes. Codes 0 through 127 are @acronym{ASCII} codes; the +rest are non-@acronym{ASCII} (@pxref{Non-ASCII Characters}). Characters that represent keyboard input have a much wider range, to encode modifier keys such as Control, Meta and Shift. @@ -323,9 +323,9 @@ @end example In strings and buffers, the only control characters allowed are those -that exist in @sc{ascii}; but for keyboard input purposes, you can turn +that exist in @acronym{ASCII}; but for keyboard input purposes, you can turn any character into a control character with @samp{C-}. The character -codes for these non-@sc{ascii} control characters include the +codes for these non-@acronym{ASCII} control characters include the @tex @math{2^{26}} @end tex @@ -333,7 +333,7 @@ 2**26 @end ifnottex bit as well as the code for the corresponding non-control -character. Ordinary terminals have no way of generating non-@sc{ascii} +character. Ordinary terminals have no way of generating non-@acronym{ASCII} control characters, but you can generate them straightforwardly using X and other window systems. @@ -375,9 +375,9 @@ @ifnottex 2**7 @end ifnottex -bit attached to an @sc{ascii} character indicates a meta character; thus, the +bit attached to an @acronym{ASCII} character indicates a meta character; thus, the meta characters that can fit in a string have codes in the range from -128 to 255, and are the meta versions of the ordinary @sc{ascii} +128 to 255, and are the meta versions of the ordinary @acronym{ASCII} characters. (In Emacs versions 18 and older, this convention was used for characters outside of strings as well.) @@ -389,8 +389,8 @@ @samp{?\M-\C-b}, @samp{?\C-\M-b}, or @samp{?\M-\002}. The case of a graphic character is indicated by its character code; -for example, @sc{ascii} distinguishes between the characters @samp{a} -and @samp{A}. But @sc{ascii} has no way to represent whether a control +for example, @acronym{ASCII} distinguishes between the characters @samp{a} +and @samp{A}. But @acronym{ASCII} has no way to represent whether a control character is upper case or lower case. Emacs uses the @tex @math{2^{25}} @@ -432,9 +432,9 @@ mark followed by a backslash and the octal character code (up to three octal digits); thus, @samp{?\101} for the character @kbd{A}, @samp{?\001} for the character @kbd{C-a}, and @code{?\002} for the -character @kbd{C-b}. Although this syntax can represent any @sc{ascii} +character @kbd{C-b}. Although this syntax can represent any @acronym{ASCII} character, it is preferred only when the precise octal value is more -important than the @sc{ascii} representation. +important than the @acronym{ASCII} representation. @example @group @@ -915,11 +915,11 @@ @end example @node Non-ASCII in Strings -@subsubsection Non-@sc{ascii} Characters in Strings +@subsubsection Non-@acronym{ASCII} Characters in Strings - You can include a non-@sc{ascii} international character in a string + You can include a non-@acronym{ASCII} international character in a string constant by writing it literally. There are two text representations -for non-@sc{ascii} characters in Emacs strings (and in buffers): unibyte +for non-@acronym{ASCII} characters in Emacs strings (and in buffers): unibyte and multibyte. If the string constant is read from a multibyte source, such as a multibyte buffer or string, or a file that would be visited as multibyte, then the character is read as a multibyte character, and that @@ -927,9 +927,9 @@ unibyte source, then the character is read as unibyte and that makes the string unibyte. - You can also represent a multibyte non-@sc{ascii} character with its + You can also represent a multibyte non-@acronym{ASCII} character with its character code: use a hex escape, @samp{\x@var{nnnnnnn}}, with as many -digits as necessary. (Multibyte non-@sc{ascii} character codes are all +digits as necessary. (Multibyte non-@acronym{ASCII} character codes are all greater than 256.) Any character which is not a valid hex digit terminates this construct. If the next character in the string could be interpreted as a hex digit, write @w{@samp{\ }} (backslash and space) to @@ -939,7 +939,7 @@ character to the string, but it does terminate the preceding hex escape. Using a multibyte hex escape forces the string to multibyte. You can -represent a unibyte non-@sc{ascii} character with its character code, +represent a unibyte non-@acronym{ASCII} character with its character code, which must be in the range from 128 (0200 octal) to 255 (0377 octal). This forces a unibyte string. @@ -958,12 +958,12 @@ However, not all of the characters you can write with backslash escape-sequences are valid in strings. The only control characters that -a string can hold are the @sc{ascii} control characters. Strings do not -distinguish case in @sc{ascii} control characters. +a string can hold are the @acronym{ASCII} control characters. Strings do not +distinguish case in @acronym{ASCII} control characters. Properly speaking, strings cannot hold meta characters; but when a string is to be used as a key sequence, there is a special convention -that provides a way to represent meta versions of @sc{ascii} characters in a +that provides a way to represent meta versions of @acronym{ASCII} characters in a string. If you use the @samp{\M-} syntax to indicate a meta character in a string constant, this sets the @tex @@ -1877,7 +1877,7 @@ Comparison of strings is case-sensitive, but does not take account of text properties---it compares only the characters in the strings. A unibyte string never equals a multibyte string unless the -contents are entirely @sc{ascii} (@pxref{Text Representations}). +contents are entirely @acronym{ASCII} (@pxref{Text Representations}). @example @group
--- a/lispref/os.texi Sat Nov 01 19:58:03 2003 +0000 +++ b/lispref/os.texi Sun Nov 02 06:29:59 2003 +0000 @@ -590,7 +590,7 @@ Emacs provides access to variables in the operating system environment through various functions. These variables include the name of the -system, the user's @sc{uid}, and so on. +system, the user's @acronym{UID}, and so on. @defvar system-configuration This variable holds the GNU configuration name for the hardware/software @@ -820,7 +820,7 @@ @end defun @defun emacs-pid -This function returns the process @sc{id} of the Emacs process. +This function returns the process @acronym{ID} of the Emacs process. @end defun @defvar tty-erase-char @@ -870,7 +870,7 @@ which the user is logged in. If the environment variable @code{LOGNAME} is set, that value is used. Otherwise, if the environment variable @code{USER} is set, that value is used. Otherwise, the value is based -on the effective @sc{uid}, not the real @sc{uid}. +on the effective @acronym{UID}, not the real @acronym{UID}. If you specify @var{uid}, the value is the user name that corresponds to @var{uid} (which should be an integer). @@ -885,7 +885,7 @@ @defun user-real-login-name This function returns the user name corresponding to Emacs's real -@sc{uid}. This ignores the effective @sc{uid} and ignores the +@acronym{UID}. This ignores the effective @acronym{UID} and ignores the environment variables @code{LOGNAME} and @code{USER}. @end defun @@ -921,7 +921,7 @@ Titles}). @defun user-real-uid -This function returns the real @sc{uid} of the user. +This function returns the real @acronym{UID} of the user. The value may be a floating point number. @example @@ -933,7 +933,7 @@ @end defun @defun user-uid -This function returns the effective @sc{uid} of the user. +This function returns the effective @acronym{UID} of the user. The value may be a floating point number. @end defun @@ -1935,7 +1935,7 @@ @code{C-s} and @kbd{C-q} for flow control. Therefore, the choice of @kbd{C-s} and @kbd{C-q} as command characters for searching and quoting was natural and uncontroversial. With so many commands needing key -assignments, of course we assigned meanings to nearly all @sc{ascii} +assignments, of course we assigned meanings to nearly all @acronym{ASCII} control characters. Later, some terminals were introduced which required these characters
--- a/lispref/positions.texi Sat Nov 01 19:58:03 2003 +0000 +++ b/lispref/positions.texi Sun Nov 02 06:29:59 2003 +0000 @@ -787,7 +787,7 @@ Note that char classes are not currently supported in @var{character-set}; they will be treated as literals. Thus you cannot use @code{"[:alpha:]"} instead of @code{"a-zA-Z"} to include -non-ASCII letters. A way to skip forward over all letters is: +non-@acronym{ASCII} letters. A way to skip forward over all letters is: @example (re-search-forward "\\=[[:alpha:]]*" nil t)
--- a/lispref/processes.texi Sat Nov 01 19:58:03 2003 +0000 +++ b/lispref/processes.texi Sun Nov 02 06:29:59 2003 +0000 @@ -265,7 +265,7 @@ the buffer as output is inserted. (However, if the coding system chosen for decoding output is @code{undecided}, meaning deduce the encoding from the actual data, then redisplay sometimes cannot continue once -non-@sc{ascii} characters are encountered. There are fundamental +non-@acronym{ASCII} characters are encountered. There are fundamental reasons why it is hard to fix this; see @ref{Output from Processes}.) Otherwise the function @code{call-process} does no redisplay, and the @@ -468,17 +468,17 @@ @defvar process-connection-type @cindex pipes -@cindex @sc{pty}s +@cindex @acronym{PTY}s This variable controls the type of device used to communicate with -asynchronous subprocesses. If it is non-@code{nil}, then @sc{pty}s are +asynchronous subprocesses. If it is non-@code{nil}, then @acronym{PTY}s are used, when available. Otherwise, pipes are used. -@sc{pty}s are usually preferable for processes visible to the user, as +@acronym{PTY}s are usually preferable for processes visible to the user, as in Shell mode, because they allow job control (@kbd{C-c}, @kbd{C-z}, etc.) to work between the process and its children, whereas pipes do not. For subprocesses used for internal purposes by programs, it is often better to use a pipe, because they are more efficient. In -addition, the total number of @sc{pty}s is limited on many systems and +addition, the total number of @acronym{PTY}s is limited on many systems and it is good not to waste them. The value of @code{process-connection-type} takes effect when @@ -494,7 +494,7 @@ @end smallexample To determine whether a given subprocess actually got a pipe or a -@sc{pty}, use the function @code{process-tty-name} (@pxref{Process +@acronym{PTY}, use the function @code{process-tty-name} (@pxref{Process Information}). @end defvar @@ -597,10 +597,10 @@ @end defun @defun process-id process -This function returns the @sc{pid} of @var{process}. This is an +This function returns the @acronym{PID} of @var{process}. This is an integer that distinguishes the process @var{process} from all other processes running on the same computer at the current time. The -@sc{pid} of a process is chosen by the operating system kernel when the +@acronym{PID} of a process is chosen by the operating system kernel when the process is started and remains constant as long as the process exists. @end defun @@ -724,9 +724,9 @@ data appears on the ``standard input'' of the subprocess. Some operating systems have limited space for buffered input in a -@sc{pty}. On these systems, Emacs sends an @sc{eof} periodically amidst +@acronym{PTY}. On these systems, Emacs sends an @acronym{EOF} periodically amidst the other characters, to force them through. For most programs, -these @sc{eof}s do no harm. +these @acronym{EOF}s do no harm. Subprocess input is normally encoded using a coding system before the subprocess receives it, much like text written into a file. You can use @@ -782,10 +782,10 @@ @defun process-send-eof &optional process-name This function makes @var{process-name} see an end-of-file in its -input. The @sc{eof} comes after any text already sent to it. +input. The @acronym{EOF} comes after any text already sent to it. If @var{process-name} is not supplied, or if it is @code{nil}, then -this function sends the @sc{eof} to the current buffer's process. An +this function sends the @acronym{EOF} to the current buffer's process. An error is signaled if the current buffer has no process. The function returns @var{process-name}. @@ -898,7 +898,7 @@ This function sends a signal to process @var{process}. The argument @var{signal} specifies which signal to send; it should be an integer. -You can specify the target process by its process @sc{id}; that allows +You can specify the target process by its process @acronym{ID}; that allows you to send signals to processes that are not children of Emacs. @end defun @@ -1480,7 +1480,7 @@ A network connection is handled by Lisp much like a subprocess, and is represented by a process object. However, the process you are communicating with is not a child of the Emacs process, so it has no -process @sc{id}, and you can't kill it or send it signals. All you +process @acronym{ID}, and you can't kill it or send it signals. All you can do is send and receive data. @code{delete-process} closes the connection, but does not kill the program at the other end; that program must decide what to do about closure of the connection.
--- a/lispref/searching.texi Sat Nov 01 19:58:03 2003 +0000 +++ b/lispref/searching.texi Sun Nov 02 06:29:59 2003 +0000 @@ -293,9 +293,9 @@ You can also include character ranges in a character alternative, by writing the starting and ending characters with a @samp{-} between them. -Thus, @samp{[a-z]} matches any lower-case @sc{ascii} letter. Ranges may be +Thus, @samp{[a-z]} matches any lower-case @acronym{ASCII} letter. Ranges may be intermixed freely with individual characters, as in @samp{[a-z$%.]}, -which matches any lower case @sc{ascii} letter or @samp{$}, @samp{%} or +which matches any lower case @acronym{ASCII} letter or @samp{$}, @samp{%} or period. Note that the usual regexp special characters are not special inside a @@ -326,14 +326,14 @@ @var{c1} is the first character of the charset to which @var{c2} belongs. -You cannot always match all non-@sc{ascii} characters with the regular +You cannot always match all non-@acronym{ASCII} characters with the regular expression @code{"[\200-\377]"}. This works when searching a unibyte buffer or string (@pxref{Text Representations}), but not in a multibyte -buffer or string, because many non-@sc{ascii} characters have codes +buffer or string, because many non-@acronym{ASCII} characters have codes above octal 0377. However, the regular expression @code{"[^\000-\177]"} -does match all non-@sc{ascii} characters (see below regarding @samp{^}), +does match all non-@acronym{ASCII} characters (see below regarding @samp{^}), in both multibyte and unibyte representations, because only the -@sc{ascii} characters are excluded. +@acronym{ASCII} characters are excluded. Starting in Emacs 21, a character alternative can also specify named character classes (@pxref{Char Classes}). This is a POSIX feature whose @@ -415,7 +415,7 @@ @table @samp @item [:ascii:] -This matches any @sc{ascii} (unibyte) character. +This matches any @acronym{ASCII} (unibyte) character. @item [:alnum:] This matches any letter or digit. (At present, for multibyte characters, it matches anything that has word syntax.) @@ -425,20 +425,20 @@ @item [:blank:] This matches space and tab only. @item [:cntrl:] -This matches any @sc{ascii} control character. +This matches any @acronym{ASCII} control character. @item [:digit:] This matches @samp{0} through @samp{9}. Thus, @samp{[-+[:digit:]]} matches any digit, as well as @samp{+} and @samp{-}. @item [:graph:] -This matches graphic characters---everything except @sc{ascii} control +This matches graphic characters---everything except @acronym{ASCII} control characters, space, and the delete character. @item [:lower:] This matches any lower-case letter, as determined by the current case table (@pxref{Case Tables}). @item [:nonascii:] -This matches any non-@sc{ascii} (multibyte) character. +This matches any non-@acronym{ASCII} (multibyte) character. @item [:print:] -This matches printing characters---everything except @sc{ascii} control +This matches printing characters---everything except @acronym{ASCII} control characters and the delete character. @item [:punct:] This matches any punctuation character. (At present, for multibyte
--- a/lispref/sequences.texi Sat Nov 01 19:58:03 2003 +0000 +++ b/lispref/sequences.texi Sun Nov 02 06:29:59 2003 +0000 @@ -322,7 +322,7 @@ @end group @group (aref "abcdefg" 1) - @result{} 98 ; @r{@samp{b} is @sc{ascii} code 98.} + @result{} 98 ; @r{@samp{b} is @acronym{ASCII} code 98.} @end group @end example
--- a/lispref/streams.texi Sat Nov 01 19:58:03 2003 +0000 +++ b/lispref/streams.texi Sun Nov 02 06:29:59 2003 +0000 @@ -721,24 +721,24 @@ @end defvar @defvar print-escape-nonascii -If this variable is non-@code{nil}, then unibyte non-@sc{ascii} +If this variable is non-@code{nil}, then unibyte non-@acronym{ASCII} characters in strings are unconditionally printed as backslash sequences by the print functions @code{prin1} and @code{print} that print with quoting. -Those functions also use backslash sequences for unibyte non-@sc{ascii} +Those functions also use backslash sequences for unibyte non-@acronym{ASCII} characters, regardless of the value of this variable, when the output stream is a multibyte buffer or a marker pointing into one. @end defvar @defvar print-escape-multibyte -If this variable is non-@code{nil}, then multibyte non-@sc{ascii} +If this variable is non-@code{nil}, then multibyte non-@acronym{ASCII} characters in strings are unconditionally printed as backslash sequences by the print functions @code{prin1} and @code{print} that print with quoting. Those functions also use backslash sequences for multibyte -non-@sc{ascii} characters, regardless of the value of this variable, +non-@acronym{ASCII} characters, regardless of the value of this variable, when the output stream is a unibyte buffer or a marker pointing into one. @end defvar
--- a/lispref/strings.texi Sat Nov 01 19:58:03 2003 +0000 +++ b/lispref/strings.texi Sun Nov 02 06:29:59 2003 +0000 @@ -44,7 +44,7 @@ The length of a string (like any array) is fixed, and cannot be altered once the string exists. Strings in Lisp are @emph{not} terminated by a distinguished character code. (By contrast, strings in -C are terminated by a character with @sc{ascii} code 0.) +C are terminated by a character with @acronym{ASCII} code 0.) Since strings are arrays, and therefore sequences as well, you can operate on them with the general array and sequence functions. @@ -52,10 +52,10 @@ change individual characters in a string using the functions @code{aref} and @code{aset} (@pxref{Array Functions}). - There are two text representations for non-@sc{ascii} characters in + There are two text representations for non-@acronym{ASCII} characters in Emacs strings (and in buffers): unibyte and multibyte (@pxref{Text -Representations}). An @sc{ascii} character always occupies one byte in a -string; in fact, when a string is all @sc{ascii}, there is no real +Representations}). An @acronym{ASCII} character always occupies one byte in a +string; in fact, when a string is all @acronym{ASCII}, there is no real difference between the unibyte and multibyte representations. For most Lisp programming, you don't need to be concerned with these two representations. @@ -66,8 +66,8 @@ codes in the range 128 to 255. Strings cannot hold characters that have the hyper, super or alt -modifiers; they can hold @sc{ascii} control characters, but no other -control characters. They do not distinguish case in @sc{ascii} control +modifiers; they can hold @acronym{ASCII} control characters, but no other +control characters. They do not distinguish case in @acronym{ASCII} control characters. If you want to store such characters in a sequence, such as a key sequence, you must use a vector instead of a string. @xref{Character Type}, for more information about the representation of meta @@ -417,7 +417,7 @@ strings. When @code{equal} (@pxref{Equality Predicates}) compares two strings, it uses @code{string=}. -If the strings contain non-@sc{ascii} characters, and one is unibyte +If the strings contain non-@acronym{ASCII} characters, and one is unibyte while the other is multibyte, then they cannot be equal. @xref{Text Representations}. @end defun @@ -439,11 +439,11 @@ Pairs of characters are compared according to their character codes. Keep in mind that lower case letters have higher numeric values in the -@sc{ascii} character set than their upper case counterparts; digits and +@acronym{ASCII} character set than their upper case counterparts; digits and many punctuation characters have a lower numeric value than upper case -letters. An @sc{ascii} character is less than any non-@sc{ascii} -character; a unibyte non-@sc{ascii} character is always less than any -multibyte non-@sc{ascii} character (@pxref{Text Representations}). +letters. An @acronym{ASCII} character is less than any non-@acronym{ASCII} +character; a unibyte non-@acronym{ASCII} character is always less than any +multibyte non-@acronym{ASCII} character (@pxref{Text Representations}). @example @group @@ -551,7 +551,7 @@ @cindex string to character This function returns the first character in @var{string}. If the string is empty, the function returns 0. The value is also 0 when the -first character of @var{string} is the null character, @sc{ascii} code +first character of @var{string} is the null character, @acronym{ASCII} code 0. @example @@ -846,7 +846,7 @@ The character case functions change the case of single characters or of the contents of strings. The functions normally convert only alphabetic characters (the letters @samp{A} through @samp{Z} and -@samp{a} through @samp{z}, as well as non-@sc{ascii} letters); other +@samp{a} through @samp{z}, as well as non-@acronym{ASCII} letters); other characters are not altered. You can specify a different case conversion mapping by specifying a case table (@pxref{Case Tables}). @@ -854,7 +854,7 @@ arguments. The examples below use the characters @samp{X} and @samp{x} which have -@sc{ascii} codes 88 and 120 respectively. +@acronym{ASCII} codes 88 and 120 respectively. @defun downcase string-or-char This function converts a character or a string to lower case. @@ -1001,7 +1001,7 @@ The extra table @var{equivalences} is a map that cyclicly permutes each equivalence class (of characters with the same canonical -equivalent). (For ordinary @sc{ascii}, this would map @samp{a} into +equivalent). (For ordinary @acronym{ASCII}, this would map @samp{a} into @samp{A} and @samp{A} into @samp{a}, and likewise for each set of equivalent characters.) @@ -1038,7 +1038,7 @@ @end defun The following three functions are convenient subroutines for packages -that define non-@sc{ascii} character sets. They modify the specified +that define non-@acronym{ASCII} character sets. They modify the specified case table @var{case-table}; they also modify the standard syntax table. @xref{Syntax Tables}. Normally you would use these functions to change the standard case table.
--- a/lispref/syntax.texi Sat Nov 01 19:58:03 2003 +0000 +++ b/lispref/syntax.texi Sun Nov 02 06:29:59 2003 +0000 @@ -752,7 +752,7 @@ @defvar multibyte-syntax-as-symbol @tindex multibyte-syntax-as-symbol If this variable is non-@code{nil}, @code{scan-sexps} treats all -non-@sc{ascii} characters as symbol constituents regardless +non-@acronym{ASCII} characters as symbol constituents regardless of what the syntax table says about them. (However, text properties can still override the syntax.) @end defvar @@ -946,7 +946,7 @@ initialized by copying from the standard categories table, so that the standard categories are available in all modes. - Each category has a name, which is an @sc{ascii} printing character in + Each category has a name, which is an @acronym{ASCII} printing character in the range @w{@samp{ }} to @samp{~}. You specify the name of a category when you define it with @code{define-category}.
--- a/lispref/text.texi Sat Nov 01 19:58:03 2003 +0000 +++ b/lispref/text.texi Sun Nov 02 06:29:59 2003 +0000 @@ -3520,7 +3520,7 @@ A register is a sort of variable used in Emacs editing that can hold a variety of different kinds of values. Each register is named by a -single character. All @sc{ascii} characters and their meta variants +single character. All @acronym{ASCII} characters and their meta variants (but with the exception of @kbd{C-g}) can be used to name registers. Thus, there are 255 possible registers. A register is designated in Emacs Lisp by the character that is its name. @@ -3688,7 +3688,7 @@ @cindex base 64 encoding Base 64 code is used in email to encode a sequence of 8-bit bytes as -a longer sequence of @sc{ascii} graphic characters. It is defined in +a longer sequence of @acronym{ASCII} graphic characters. It is defined in Internet RFC@footnote{ An RFC, an acronym for @dfn{Request for Comments}, is a numbered Internet informational document describing a standard. RFCs are