C programs according to preprocessor conditionals.
@item
-Tomas Abrahamsson wrote @file{artist.el}, a package for producing ASCII
+Tomas Abrahamsson wrote @file{artist.el}, a package for producing @acronym{ASCII}
art with a mouse or with keyboard keys.
@item
@item
Michael Gschwind wrote @file{iso-cvt.el}, a package to convert between
-the ISO 8859-1 character set and the notations for non-ASCII
+the ISO 8859-1 character set and the notations for non-@acronym{ASCII}
characters used by @TeX{} and net tradition, and @file{latin-2.el}, code
which sets up case-conversion and syntax tables for the ISO Latin-2
character set.
@item
Ken'ichi Handa implemented most of the support for international
character sets, and wrote @file{isearch-x.el}, a facility for searching
-non-ASCII text. Together with Naoto Takahashi, he wrote
-@file{quail.el}, a simple input facility for typing non-ASCII text from
-an ASCII keyboard. Ken'ichi also wrote @file{ps-bdf.el}, a BDF font
-support for printing non-ASCII text on a PostScript printer.
+non-@acronym{ASCII} text. Together with Naoto Takahashi, he wrote
+@file{quail.el}, a simple input facility for typing non-@acronym{ASCII} text from
+an @acronym{ASCII} keyboard. Ken'ichi also wrote @file{ps-bdf.el}, a BDF font
+support for printing non-@acronym{ASCII} text on a PostScript printer.
@item
Chris Hanson wrote @file{netuname.el}, a package to use HP-UX's Remote
@item
@file{emacsbug.el}, a package for reporting Emacs bugs,
@item
-@file{picture.el}, a mode for editing ASCII pictures, and
+@file{picture.el}, a mode for editing @acronym{ASCII} pictures, and
@item
@file{view.el}, a package for perusing files and buffers without editing
them.
The four values after @samp{Char:} describe the character that follows
point, first by showing it and then by giving its character code in
-octal, decimal and hex. For a non-ASCII multibyte character, these are
+octal, decimal and hex. For a non-@acronym{ASCII} multibyte character, these are
followed by @samp{ext} and the character's representation, in hex, in
the buffer's coding system, if that coding system encodes the character
safely and with a single byte (@pxref{Coding Systems}). If the
@cindex text properties at point
@w{@kbd{C-u C-x =}} displays additional information about a
character, including the character set name and the codes that
-identify the character within that character set; ASCII characters are
+identify the character within that character set; @acronym{ASCII} characters are
identified as belonging to the @code{ascii} character set. It also
shows the character's syntax, categories, and encodings both
internally in the buffer and externally if you save the file. It also
@end smallexample
You can inhibit the direct use of the window system and GUI with the
-@samp{-nw} option. It tells Emacs to display using ordinary ASCII on
+@samp{-nw} option. It tells Emacs to display using ordinary @acronym{ASCII} on
its controlling terminal. This is also an initial option.
Sometimes, security arrangements prevent a program on a remote system
@cindex input with the keyboard
@cindex keyboard input
@cindex character set (keyboard)
-@cindex ASCII
+@cindex @acronym{ASCII}
@cindex C-
@cindex Control
@cindex control characters
- GNU Emacs uses an extension of the ASCII character set for keyboard
+ GNU Emacs uses an extension of the @acronym{ASCII} character set for keyboard
input; it also accepts non-character input events including function
keys and mouse button actions.
- ASCII consists of 128 character codes. Some of these codes are
+ @acronym{ASCII} consists of 128 character codes. Some of these codes are
assigned graphic symbols such as @samp{a} and @samp{=}; the rest are
control characters, such as @kbd{Control-a} (usually written @kbd{C-a}
for short). @kbd{C-a} gets its name from the fact that you type it by
holding down the @key{CTRL} key while pressing @kbd{a}.
- Some ASCII control characters have special names, and most terminals
+ Some @acronym{ASCII} control characters have special names, and most terminals
have special keys you can type them with: for example, @key{RET},
@key{TAB}, @key{DEL} and @key{ESC}. The space character is usually
referred to below as @key{SPC}, even though strictly speaking it is a
graphic character whose graphic happens to be blank. Some keyboards
have a key labeled ``linefeed'' which is an alias for @kbd{C-j}.
- Emacs extends the ASCII character set with thousands more printing
+ Emacs extends the @acronym{ASCII} character set with thousands more printing
characters (@pxref{International}), additional control characters, and a
few more modifiers that can be combined with any character.
- On ASCII terminals, there are only 32 possible control characters.
+ On @acronym{ASCII} terminals, there are only 32 possible control characters.
These are the control variants of letters and @samp{@@[]\^_}. In
addition, the shift key is meaningless with control characters:
@kbd{C-a} and @kbd{C-A} are the same character, and Emacs cannot
programming, but simply want to redefine the meaning of some characters
or non-character events, see @ref{Customization}.
- ASCII terminals cannot really send anything to the computer except
-ASCII characters. These terminals use a sequence of characters to
+ @acronym{ASCII} terminals cannot really send anything to the computer except
+@acronym{ASCII} characters. These terminals use a sequence of characters to
represent each function key. But that is invisible to the Emacs user,
because the keyboard input routines recognize these special sequences
and convert them to function key events before any other part of Emacs
@cindex characters (in text)
Text in Emacs buffers is a sequence of 8-bit bytes. Each byte can
-hold a single ASCII character. Both ASCII control characters (octal
-codes 000 through 037, and 0177) and ASCII printing characters (codes
-040 through 0176) are allowed; however, non-ASCII control characters
+hold a single @acronym{ASCII} character. Both @acronym{ASCII} control characters (octal
+codes 000 through 037, and 0177) and @acronym{ASCII} printing characters (codes
+040 through 0176) are allowed; however, non-@acronym{ASCII} control characters
cannot appear in a buffer. The other modifier flags used in keyboard
input, such as Meta, are not allowed in buffers either.
- Some ASCII control characters serve special purposes in text, and have
+ Some @acronym{ASCII} control characters serve special purposes in text, and have
special names. For example, the newline character (octal code 012) is
used in the buffer to end a line, and the tab character (octal code 011)
is used for indenting to the next tab stop column (normally every 8
columns). @xref{Text Display}.
- Non-ASCII printing characters can also appear in buffers. When
-multibyte characters are enabled, you can use any of the non-ASCII
+ Non-@acronym{ASCII} printing characters can also appear in buffers. When
+multibyte characters are enabled, you can use any of the non-@acronym{ASCII}
printing characters that Emacs supports. They have character codes
starting at 256, octal 0400, and each one is represented as a sequence
of two or more bytes. @xref{International}. Single-byte characters
with codes 128 through 255 can also appear in multibyte buffers.
If you disable multibyte characters, then you can use only one
-alphabet of non-ASCII characters, but they all fit in one byte. They
+alphabet of non-@acronym{ASCII} characters, but they all fit in one byte. They
use codes 0200 through 0377. @xref{Single-Byte Character Support}.
@ignore
* Init Rebinding:: Rebinding keys with your init file, @file{.emacs}.
* Function Keys:: Rebinding terminal function keys.
* Named ASCII Chars:: Distinguishing @key{TAB} from @kbd{C-i}, and so on.
-* Non-ASCII Rebinding:: Rebinding non-ASCII characters such as Latin-1.
+* Non-ASCII Rebinding:: Rebinding non-@acronym{ASCII} characters such as Latin-1.
* Mouse Buttons:: Rebinding mouse buttons in Emacs.
* Disabling:: Disabling a command means confirmation is required
before it can be executed. This is done to protect
you can specify them in your @file{.emacs} file by using their Lisp
syntax. (@xref{Init File}.)
- The simplest method for doing this works for ASCII characters and
-Meta-modified ASCII characters only. This method uses a string to
+ The simplest method for doing this works for @acronym{ASCII} characters and
+Meta-modified @acronym{ASCII} characters only. This method uses a string to
represent the key sequence you want to rebind. For example, here's how
to bind @kbd{C-z} to @code{shell}:
(global-set-key "\C-x\t" 'indent-rigidly)
@end example
- These examples show how to write some other special ASCII characters
+ These examples show how to write some other special @acronym{ASCII} characters
in strings for key bindings:
@example
@end example
When the key sequence includes function keys or mouse button events,
-or non-ASCII characters such as @code{C-=} or @code{H-a}, you must use
+or non-@acronym{ASCII} characters such as @code{C-=} or @code{H-a}, you must use
the more general method of rebinding, which uses a vector to specify the
key sequence.
the character as it would appear in a string.
Here are examples of using vectors to rebind @kbd{C-=} (a control
-character not in ASCII), @kbd{C-M-=} (not in ASCII because @kbd{C-=}
-is not), @kbd{H-a} (a Hyper character; ASCII doesn't have Hyper at
+character not in @acronym{ASCII}), @kbd{C-M-=} (not in @acronym{ASCII} because @kbd{C-=}
+is not), @kbd{H-a} (a Hyper character; @acronym{ASCII} doesn't have Hyper at
all), @key{F7} (a function key), and @kbd{C-Mouse-1} (a
keyboard-modified mouse button):
delimit the vector.
Language and coding systems can cause problems with key bindings
-for non-ASCII characters. @xref{Non-ASCII Rebinding}.
+for non-@acronym{ASCII} characters. @xref{Non-ASCII Rebinding}.
@node Function Keys
@subsection Rebinding Function Keys
key.
A key sequence which contains function key symbols (or anything but
-ASCII characters) must be a vector rather than a string. The vector
+@acronym{ASCII} characters) must be a vector rather than a string. The vector
syntax uses spaces between the elements, and square brackets around the
whole vector. Thus, to bind function key @samp{f1} to the command
@code{rmail}, write the following:
@end example
@node Named ASCII Chars
-@subsection Named ASCII Control Characters
+@subsection Named @acronym{ASCII} Control Characters
@key{TAB}, @key{RET}, @key{BS}, @key{LFD}, @key{ESC} and @key{DEL}
-started out as names for certain ASCII control characters, used so often
+started out as names for certain @acronym{ASCII} control characters, used so often
that they have special keys of their own. Later, users found it
convenient to distinguish in Emacs between these keys and the ``same''
control characters typed with the @key{CTRL} key.
reports these keys to Emacs. It treats the ``special'' keys as function
keys named @code{tab}, @code{return}, @code{backspace}, @code{linefeed},
@code{escape}, and @code{delete}. These function keys translate
-automatically into the corresponding ASCII characters @emph{if} they
+automatically into the corresponding @acronym{ASCII} characters @emph{if} they
have no bindings of their own. As a result, neither users nor Lisp
programs need to pay attention to the distinction unless they care to.
If you do not want to distinguish between (for example) @key{TAB} and
-@kbd{C-i}, make just one binding, for the ASCII character @key{TAB}
+@kbd{C-i}, make just one binding, for the @acronym{ASCII} character @key{TAB}
(octal code 011). If you do want to distinguish, make one binding for
-this ASCII character, and another for the ``function key'' @code{tab}.
+this @acronym{ASCII} character, and another for the ``function key'' @code{tab}.
- With an ordinary ASCII terminal, there is no way to distinguish
+ With an ordinary @acronym{ASCII} terminal, there is no way to distinguish
between @key{TAB} and @kbd{C-i} (and likewise for other such pairs),
because the terminal sends the same character in both cases.
@node Non-ASCII Rebinding
-@subsection Non-ASCII Characters on the Keyboard
-@cindex rebinding non-ASCII keys
-@cindex non-ASCII keys, binding
+@subsection Non-@acronym{ASCII} Characters on the Keyboard
+@cindex rebinding non-@acronym{ASCII} keys
+@cindex non-@acronym{ASCII} keys, binding
-If your keyboard has keys that send non-ASCII characters, such as
+If your keyboard has keys that send non-@acronym{ASCII} characters, such as
accented letters, rebinding these keys is a bit tricky. There are two
solutions you can use. One is to specify a keyboard coding system,
using @code{set-keyboard-coding-system} (@pxref{Specify Coding}).
@noindent
Type @kbd{C-q} followed by the key you want to bind, to insert @var{char}.
-Since this puts a non-ASCII character in the @file{.emacs}, you should
+Since this puts a non-@acronym{ASCII} character in the @file{.emacs}, you should
specify the proper coding system for that file. @xref{Init Syntax}.
Specify the same coding system for the file that you use for your
keyboard.
characters that result from keyboard translation.
On a window system, the keyboard key named @key{DELETE} is a function
-key and is distinct from the ASCII character named @key{DEL}.
-@xref{Named ASCII Chars}. Keyboard translations affect only ASCII
+key and is distinct from the @acronym{ASCII} character named @key{DEL}.
+@xref{Named ASCII Chars}. Keyboard translations affect only @acronym{ASCII}
character input, not function keys; thus, the above example used on a
window system does not affect the @key{DELETE} key. However, the
translation above isn't necessary on window systems, because Emacs can
sequences are mandatory.
@samp{\C-} can be used as a prefix for a control character, as in
-@samp{\C-s} for ASCII control-S, and @samp{\M-} can be used as a prefix for
+@samp{\C-s} for @acronym{ASCII} control-S, and @samp{\M-} can be used as a prefix for
a Meta character, as in @samp{\M-a} for @kbd{Meta-A} or @samp{\M-\C-a} for
@kbd{Control-Meta-A}.@refill
@cindex international characters in @file{.emacs}
-@cindex non-ASCII characters in @file{.emacs}
-If you want to include non-ASCII characters in strings in your init
+@cindex non-@acronym{ASCII} characters in @file{.emacs}
+If you want to include non-@acronym{ASCII} characters in strings in your init
file, you should consider putting a @w{@samp{-*-coding:
@var{coding-system}-*-}} tag on the first line which states the coding
system used to save your @file{.emacs}, as explained in @ref{Recognize
-Coding}. This is because the defaults for decoding non-ASCII text might
+Coding}. This is because the defaults for decoding non-@acronym{ASCII} text might
not yet be set up by the time Emacs reads those parts of your init file
which use such strings, possibly leading Emacs to decode those strings
incorrectly.
require one and some contexts require the other.
@xref{Non-ASCII Rebinding}, for information about binding commands to
-keys which send non-ASCII characters.
+keys which send non-@acronym{ASCII} characters.
@item True:
@code{t} stands for `true'.
@section How Text Is Displayed
@cindex characters (in text)
- ASCII printing characters (octal codes 040 through 0176) in Emacs
+ @acronym{ASCII} printing characters (octal codes 040 through 0176) in Emacs
buffers are displayed with their graphics, as are non-ASCII multibyte
printing characters (octal codes above 0400).
- Some ASCII control characters are displayed in special ways. The
+ Some @acronym{ASCII} control characters are displayed in special ways. The
newline character (octal code 012) is displayed by starting a new line.
The tab character (octal code 011) is displayed by moving to the next
tab stop column (normally every 8 columns).
- Other ASCII control characters are normally displayed as a caret
+ Other @acronym{ASCII} control characters are normally displayed as a caret
(@samp{^}) followed by the non-control version of the character; thus,
control-A is displayed as @samp{^A}.
- Non-ASCII characters 0200 through 0237 (octal) are displayed with
+ Non-@acronym{ASCII} characters 0200 through 0237 (octal) are displayed with
octal escape sequences; thus, character code 0230 (octal) is displayed
as @samp{\230}. The display of character codes 0240 through 0377
(octal) may be either as escape sequences or as graphics. They do not
@kindex h
Cycles between full highlighting, the mode where fine differences are not
highlighted (but computed), and the mode where highlighting is done with
-ASCII strings. The latter is not really recommended, unless on a dumb TTY.
+@acronym{ASCII} strings. The latter is not really recommended, unless on a dumb TTY.
@item r
@kindex r
* Buffers:: Multiple buffers; editing several files at once.
* Windows:: Viewing two pieces of text at once.
* Frames:: Running the same Emacs session in multiple X windows.
-* International:: Using non-ASCII character sets (the MULE features).
+* International:: Using non-@acronym{ASCII} character sets (the MULE features).
Advanced Features
* Major Modes:: Text mode vs. Lisp mode vs. C mode ...
* Adding to Diary:: Commands to create diary entries.
* Special Diary Entries:: Anniversaries, blocks of dates, cyclic entries, etc.
-@sc{Gnus}
+Gnus
* Buffers of Gnus:: The group, summary, and article buffers.
* Gnus Startup:: What you should know about starting Gnus.
Any real spaces in such a key sequence should be ignored; only @key{SPC}
really means press the space key.
-The ASCII code sent by @kbd{C-x} (except for @kbd{C-?}) is the value
+The @acronym{ASCII} code sent by @kbd{C-x} (except for @kbd{C-?}) is the value
that would be sent by pressing just @key{x} minus 96 (or 64 for
upper-case @key{X}) and will be from 0 to 31. On Unix and GNU/Linux
-terminals, the ASCII code sent by @kbd{M-x} is the sum of 128 and the
-ASCII code that would be sent by pressing just @key{x}. Essentially,
+terminals, the @acronym{ASCII} code sent by @kbd{M-x} is the sum of 128 and the
+@acronym{ASCII} code that would be sent by pressing just @key{x}. Essentially,
@key{Control} turns off bits 5 and 6 and @key{Meta} turns on bit
7@footnote{
DOS and Windows terminals don't set bit 7 when the @key{Meta} key is
pressed.}.
-@kbd{C-?} (aka @key{DEL}) is ASCII code 127. It is a misnomer to call
+@kbd{C-?} (aka @key{DEL}) is @acronym{ASCII} code 127. It is a misnomer to call
@kbd{C-?} a ``control'' key, since 127 has both bits 5 and 6 turned ON.
-Also, on very few keyboards does @kbd{C-?} generate ASCII code 127.
+Also, on very few keyboards does @kbd{C-?} generate @acronym{ASCII} code 127.
@inforef{Text Characters, Text Characters, emacs}, and @inforef{Keys,
Keys, emacs}, for more information. (@xref{On-line manual}, for more
@cindex Help invoked by Backspace
@cindex DEL key does not delete
-The @key{Backspace} key (on most keyboards) generates ASCII code 8.
+The @key{Backspace} key (on most keyboards) generates @acronym{ASCII} code 8.
@kbd{C-h} sends the same code. In Emacs by default @kbd{C-h} invokes
help-command. This is intended to be easy to remember since the first
letter of @samp{help} is @samp{h}. The easiest solution to this problem
@cindex Lacking an Escape key
@cindex Escape key, lacking
-Type @kbd{C-[} instead. This should send ASCII code 27 just like an
+Type @kbd{C-[} instead. This should send @acronym{ASCII} code 27 just like an
Escape key would. @kbd{C-3} may also work on some terminal (but not
under X). For many terminals (notably DEC terminals) @key{F11}
generates @key{ESC}. If not, the following form can be used to bind it:
@item
Not all modifiers are permitted in all situations. @key{Hyper},
@key{Super}, and @key{Alt} are not available on Unix character
-terminals. Non-ASCII keys and mouse events (e.g. @kbd{C-=} and
+terminals. Non-@acronym{ASCII} keys and mouse events (e.g. @kbd{C-=} and
@kbd{Mouse-1}) also fall under this category.
@end itemize
find out what keysym your @key{Meta} key generates. It should be either
@code{Meta_L} or @code{Meta_R}. If it isn't, use @file{xmodmap} to fix
the situation. If @key{Meta} does generate @code{Meta_L} or
-@code{Meta_R}, but @kbd{M-x} produces a non-ASCII character, put this in
+@code{Meta_R}, but @kbd{M-x} produces a non-@acronym{ASCII} character, put this in
your @file{~/.Xdefaults} file:
@example
display or is invoked with @samp{emacs -nw}, you typically need to use
@code{set-terminal-coding-system} to tell Emacs what the terminal can
display, even after setting the language environment; otherwise
-non-ASCII characters will display as @samp{?}. On other operating
+non-@acronym{ASCII} characters will display as @samp{?}. On other operating
systems, such as MS-DOS and MS-Windows, Emacs queries the OS about the
character set supported by the display, and sets up the required
terminal coding system automatically.
@code{substitute-in-file-name}. The substitution is performed only on
file names read as such using the minibuffer.
- You can include non-ASCII characters in file names if you set the
+ You can include non-@acronym{ASCII} characters in file names if you set the
variable @code{file-name-coding-system} to a non-@code{nil} value.
@xref{Specify Coding}.
system. @xref{Frames}.
@findex find-file-literally
- If you wish to edit a file as a sequence of ASCII characters with no special
+ If you wish to edit a file as a sequence of @acronym{ASCII} characters with no special
encoding or conversion, use the @kbd{M-x find-file-literally} command.
It visits a file, like @kbd{C-x C-f}, but does not do format conversion
(@pxref{Formatted Text}), character code conversion (@pxref{Coding
If you select a region with any of these mouse commands, and then
immediately afterward type the @key{DELETE} function key, it deletes the
region that you selected. The @key{BACKSPACE} function key and the
-ASCII character @key{DEL} do not do this; if you type any other key
+@acronym{ASCII} character @key{DEL} do not do this; if you type any other key
in between the mouse command and @key{DELETE}, it does not do this.
@findex mouse-set-region
@item Argument
See `numeric argument.'
-@item ASCII character
-An ASCII character is either an ASCII control character or an ASCII
+@item @acronym{ASCII} character
+An @acronym{ASCII} character is either an @acronym{ASCII} control character or an @acronym{ASCII}
printing character. @xref{User Input}.
-@item ASCII control character
-An ASCII control character is the Control version of an upper-case
+@item @acronym{ASCII} control character
+An @acronym{ASCII} control character is the Control version of an upper-case
letter, or the Control version of one of the characters @samp{@@[\]^_?}.
-@item ASCII printing character
-ASCII printing characters include letters, digits, space, and these
+@item @acronym{ASCII} printing character
+@acronym{ASCII} printing characters include letters, digits, space, and these
punctuation characters: @samp{!@@#$%^& *()_-+=|\~` @{@}[]:;"' <>,.?/}.
@item Auto Fill Mode
frames. @xref{User Input}.
@item Input Method
-An input method is a system for entering non-ASCII text characters by
-typing sequences of ASCII characters (q.v.@:). @xref{Input Methods}.
+An input method is a system for entering non-@acronym{ASCII} text characters by
+typing sequences of @acronym{ASCII} characters (q.v.@:). @xref{Input Methods}.
@item Insertion
Insertion means copying text into the buffer, either from the keyboard
@item Language Environment
Your choice of language environment specifies defaults for the input
method (q.v.@:) and coding system (q.v.@:). @xref{Language
-Environments}. These defaults are relevant if you edit non-ASCII text
+Environments}. These defaults are relevant if you edit non-@acronym{ASCII} text
(@pxref{International}).
@item Line Wrapping
yanking (q.v.@:). @xref{Killing}.
@item MULE
-MULE refers to the Emacs features for editing multilingual non-ASCII text
+MULE refers to the Emacs features for editing multilingual non-@acronym{ASCII} text
using multibyte characters (q.v.@:). @xref{International}.
@item Multibyte Character
A multibyte character is a character that takes up several bytes in a
-buffer. Emacs uses multibyte characters to represent non-ASCII text,
-since the number of non-ASCII characters is much more than 256.
+buffer. Emacs uses multibyte characters to represent non-@acronym{ASCII} text,
+since the number of non-@acronym{ASCII} characters is much more than 256.
@xref{International Chars, International Characters}.
@item Named Mark
it to the right. @xref{Minor Modes}.
@item Page
-A page is a unit of text, delimited by formfeed characters (ASCII
+A page is a unit of text, delimited by formfeed characters (@acronym{ASCII}
control-L, code 014) coming at the beginning of a line. Some Emacs
commands are provided for moving over and operating on pages.
@xref{Pages}.
@findex normal-erase-is-backspace-mode
On most text-only terminals, Emacs cannot tell which keys the
keyboard really has, so it follows a uniform plan which may or may not
-fit your keyboard. The uniform plan is that the ASCII @key{DEL}
-character deletes, and the ASCII @key{BS} (backspace) character asks
+fit your keyboard. The uniform plan is that the @acronym{ASCII} @key{DEL}
+character deletes, and the @acronym{ASCII} @key{BS} (backspace) character asks
for help (it is the same as @kbd{C-h}). If this is not right for your
keyboard, such as if you find that the key which ought to delete backwards
enters Help instead, see @ref{DEL Does Not Delete}.
Most people should want to use the @key{command} key as the @key{META} key,
so that dead-key processing with the @key{option} key will still work. This is
-useful for entering non-ASCII Latin characters directly from the Mac
+useful for entering non-@acronym{ASCII} Latin characters directly from the Mac
keyboard, for example.
Emacs recognizes the setting in the Keyboard control panel and
@ref{Mark Ring}.
@kindex C-@@
- There is no such character as @kbd{C-@key{SPC}} in ASCII; when you
+ There is no such character as @kbd{C-@key{SPC}} in @acronym{ASCII}; when you
type @key{SPC} while holding down @key{CTRL}, what you get on most
ordinary terminals is the character @kbd{C-@@}. This key is actually
bound to @code{set-mark-command}. But unless you are unlucky enough to
@item C-d
@kindex C-d @r{(Shell mode)}
@findex comint-delchar-or-maybe-eof
-Either delete a character or send @sc{eof}
+Either delete a character or send @acronym{EOF}
(@code{comint-delchar-or-maybe-eof}). Typed at the end of the shell
-buffer, @kbd{C-d} sends @sc{eof} to the subshell. Typed at any other
+buffer, @kbd{C-d} sends @acronym{EOF} to the subshell. Typed at any other
position in the buffer, @kbd{C-d} deletes a character as usual.
@item C-c C-a
the fonts supplied with the printer with those from the GNU Intlfonts
package, or you can instruct Emacs to use Intlfonts exclusively. The
variable @code{ps-multibyte-buffer} controls this: the default value,
-@code{nil}, is appropriate for printing ASCII and Latin-1
+@code{nil}, is appropriate for printing @acronym{ASCII} and Latin-1
characters; a value of @code{non-latin-printer} is for printers which
-have the fonts for ASCII, Latin-1, Japanese, and Korean
+have the fonts for @acronym{ASCII}, Latin-1, Japanese, and Korean
characters built into them. A value of @code{bdf-font} arranges for
the BDF fonts from the Intlfonts package to be used for @emph{all}
characters. Finally, a value of @code{bdf-font-except-latin}
-instructs the printer to use built-in fonts for ASCII and Latin-1
+instructs the printer to use built-in fonts for @acronym{ASCII} and Latin-1
characters, and Intlfonts BDF fonts for the rest.
@vindex bdf-directory-list
into the order determined by the sort keys. The records are ordered so
that their keys are in alphabetical order, or, for numeric sorting, in
numeric order. In alphabetic sorting, all upper-case letters `A' through
-`Z' come before lower-case `a', in accord with the ASCII character
+`Z' come before lower-case `a', in accord with the @acronym{ASCII} character
sequence.
The various sort commands differ in how they divide the text into sort
@vindex dos-display-scancodes
The variable @code{dos-display-scancodes}, when non-@code{nil},
-directs Emacs to display the ASCII value and the keyboard scan code of
+directs Emacs to display the @acronym{ASCII} value and the keyboard scan code of
each keystroke; this feature serves as a complement to the
@code{view-lossage} command, for debugging.
redirect it to a networked printer via the @w{@code{Control
Panel->Printers}} applet instead of @samp{net use}.
- Some printers expect DOS codepage encoding of non-ASCII text, even
+ Some printers expect DOS codepage encoding of non-@acronym{ASCII} text, even
though they are connected to a Windows machine which uses a different
encoding for the same locale. For example, in the Latin-1 locale, DOS
uses codepage 850 whereas Windows uses codepage 1252. @xref{MS-DOS and
MS-DOS is designed to support one character set of 256 characters at
any given time, but gives you a variety of character sets to choose
from. The alternative character sets are known as @dfn{DOS codepages}.
-Each codepage includes all 128 ASCII characters, but the other 128
+Each codepage includes all 128 @acronym{ASCII} characters, but the other 128
characters (codes 128 through 255) vary from one codepage to another.
Each DOS codepage is identified by a 3-digit number, such as 850, 862,
etc.
@cindex unibyte operation @r{(MS-DOS)}
If you invoke Emacs on MS-DOS with the @samp{--unibyte} option
(@pxref{Initial Options}), Emacs does not perform any conversion of
-non-ASCII characters. Instead, it reads and writes any non-ASCII
+non-@acronym{ASCII} characters. Instead, it reads and writes any non-@acronym{ASCII}
characters verbatim, and sends their 8-bit codes to the display
verbatim. Thus, unibyte Emacs on MS-DOS supports the current codepage,
whatever it may be, but cannot even represent any other characters.
If a buffer contains a character belonging to some other ISO 8859
character set, not the one that the chosen DOS codepage supports, Emacs
-displays it using a sequence of ASCII characters. For example, if the
+displays it using a sequence of @acronym{ASCII} characters. For example, if the
current codepage doesn't have a glyph for the letter @samp{@`o} (small
@samp{o} with a grave accent), it is displayed as @samp{@{`o@}}, where
the braces serve as a visual indication that this is a single character.
@itemize @bullet
@item
-You can visit files with non-ASCII characters, save non-ASCII text, and
-pass non-ASCII text between Emacs and programs it invokes (such as
+You can visit files with non-@acronym{ASCII} characters, save non-@acronym{ASCII} text, and
+pass non-@acronym{ASCII} text between Emacs and programs it invokes (such as
compilers, spell-checkers, and mailers). Setting your language
environment (@pxref{Language Environments}) takes care of setting up the
coding systems and other options for a specific language or culture.
for each command; see @ref{Specify Coding}.
@item
-You can display non-ASCII characters encoded by the various scripts.
+You can display non-@acronym{ASCII} characters encoded by the various scripts.
This works by using appropriate fonts on X and similar graphics
displays (@pxref{Defining Fontsets}), and by sending special codes to
text-only displays (@pxref{Specify Coding}). If some characters are
describes possible problems and explains how to solve them.
@item
-You can insert non-ASCII characters or search for them. To do that,
+You can insert non-@acronym{ASCII} characters or search for them. To do that,
you can specify an input method (@pxref{Select Input Method}) suitable
for your language, or use the default input method set up when you set
your language environment. (Emacs input methods are part of the Leim
package, which must be installed for you to be able to use them.) If
-your keyboard can produce non-ASCII characters, you can select an
+your keyboard can produce non-@acronym{ASCII} characters, you can select an
appropriate keyboard coding system (@pxref{Specify Coding}), and Emacs
will accept those characters. Latin-1 characters can also be input by
using the @kbd{C-x 8} prefix, see @ref{Single-Byte Character Support,
many more-or-less standard coding systems for storing files. Emacs
internally uses a single multibyte character encoding, so that it can
intermix characters from all these scripts in a single buffer or string.
-This encoding represents each non-ASCII character as a sequence of bytes
+This encoding represents each non-@acronym{ASCII} character as a sequence of bytes
in the range 0200 through 0377. Emacs translates between the multibyte
character encoding and various other coding systems when reading and
writing files, when exchanging data with subprocesses, and (in some
@cindex Lisp files, and multibyte operation
@cindex multibyte operation, and Lisp files
@cindex unibyte operation, and Lisp files
-@cindex init file, and non-ASCII characters
-@cindex environment variables, and non-ASCII characters
+@cindex init file, and non-@acronym{ASCII} characters
+@cindex environment variables, and non-@acronym{ASCII} characters
With @samp{--unibyte}, multibyte strings are not created during
initialization from the values of environment variables,
-@file{/etc/passwd} entries etc.@: that contain non-ASCII 8-bit
+@file{/etc/passwd} entries etc.@: that contain non-@acronym{ASCII} 8-bit
characters.
Emacs normally loads Lisp files as multibyte, regardless of whether
(The former variable overrides the latter.) It also adjusts the display
table and terminal coding system, the locale coding system, the
preferred coding system as needed for the locale, and---last but not
-least---the way Emacs decodes non-ASCII characters sent by your keyboard.
+least---the way Emacs decodes non-@acronym{ASCII} characters sent by your keyboard.
If you modify the @env{LC_ALL}, @env{LC_CTYPE}, or @env{LANG}
environment variables while running Emacs, you may want to invoke the
characters can share one input method. A few languages support several
input methods.
- The simplest kind of input method works by mapping ASCII letters
+ The simplest kind of input method works by mapping @acronym{ASCII} letters
into another alphabet; this allows you to use one other alphabet
-instead of ASCII. The Greek and Russian input methods
+instead of @acronym{ASCII}. The Greek and Russian input methods
work this way.
A more powerful technique is composition: converting sequences of
characters into one letter. Many European input methods use composition
-to produce a single non-ASCII letter from a sequence that consists of a
+to produce a single non-@acronym{ASCII} letter from a sequence that consists of a
letter followed by accent characters (or vice versa). For example, some
methods convert the sequence @kbd{a'} into a single accented letter.
These input methods have no special commands of their own; all they do
@findex toggle-input-method
@kindex C-\
- Input methods use various sequences of ASCII characters to stand for
-non-ASCII characters. Sometimes it is useful to turn off the input
+ Input methods use various sequences of @acronym{ASCII} characters to stand for
+non-@acronym{ASCII} characters. Sometimes it is useful to turn off the input
method temporarily. To do this, type @kbd{C-\}
(@code{toggle-input-method}). To reenable the input method, type
@kbd{C-\} again.
method, including the string that stands for it in the mode line.
@node Multibyte Conversion
-@section Unibyte and Multibyte Non-ASCII characters
+@section Unibyte and Multibyte Non-@acronym{ASCII} characters
When multibyte characters are enabled, character codes 0240 (octal)
through 0377 (octal) are not really legitimate in the buffer. The valid
-non-ASCII printing characters have codes that start from 0400.
+non-@acronym{ASCII} printing characters have codes that start from 0400.
If you type a self-inserting character in the range 0240 through
0377, or if you use @kbd{C-q} to insert one, Emacs assumes you
850, type @kbd{C-x @key{RET} c cp850 @key{RET} C-x C-f @var{filename}
@key{RET}}.
- In addition to converting various representations of non-ASCII
+ In addition to converting various representations of non-@acronym{ASCII}
characters, a coding system can perform end-of-line conversion. Emacs
handles three different conventions for how to separate lines in a file:
newline, carriage-return linefeed, and just carriage-return.
@code{iso-latin-1-mac}.
The coding system @code{raw-text} is good for a file which is mainly
-ASCII text, but may contain byte values above 127 which are not meant to
-encode non-ASCII characters. With @code{raw-text}, Emacs copies those
+@acronym{ASCII} text, but may contain byte values above 127 which are not meant to
+encode non-@acronym{ASCII} characters. With @code{raw-text}, Emacs copies those
byte values unchanged, and sets @code{enable-multibyte-characters} to
@code{nil} in the current buffer so that they will be interpreted
properly. @code{raw-text} handles end-of-line conversion in the usual
specify the kind of end-of-line conversion to use.
In contrast, the coding system @code{no-conversion} specifies no
-character code conversion at all---none for non-ASCII byte values and
+character code conversion at all---none for non-@acronym{ASCII} byte values and
none for end of line. This is useful for reading or writing binary
files, tar files, and other files that must be examined verbatim. It,
too, sets @code{enable-multibyte-characters} to @code{nil}.
might convert the file contents before you see them. @xref{Visiting}.
The coding system @code{emacs-mule} means that the file contains
-non-ASCII characters stored with the internal Emacs encoding. It
+non-@acronym{ASCII} characters stored with the internal Emacs encoding. It
handles end-of-line conversion based on the data encountered, and has
the usual three variants to specify the kind of end-of-line conversion.
The default value of @code{inhibit-iso-escape-detection} is
@code{nil}. We recommend that you not change it permanently, only for
one specific operation. That's because many Emacs Lisp source files
-in the Emacs distribution contain non-ASCII characters encoded in the
+in the Emacs distribution contain non-@acronym{ASCII} characters encoded in the
coding system @code{iso-2022-7bit}, and they won't be
decoded correctly when you visit those files if you suppress the
escape sequence detection.
@findex unify-8859-on-decoding-mode
The command @code{unify-8859-on-decoding-mode} enables a mode that
``unifies'' the Latin alphabets when decoding text. This works by
-converting all non-ASCII Latin-@var{n} characters to either Latin-1 or
+converting all non-@acronym{ASCII} Latin-@var{n} characters to either Latin-1 or
Unicode characters. This way it is easier to use various
Latin-@var{n} alphabets together. In a future Emacs version we hope
to move towards full Unicode support and complete unification of
most coding systems can only handle some of the possible characters.
This means that it is possible for you to insert characters that
cannot be encoded with the coding system that will be used to save the
-buffer. For example, you could start with an ASCII file and insert a
+buffer. For example, you could start with an @acronym{ASCII} file and insert a
few Latin-1 characters into it, or you could edit a text file in
Polish encoded in @code{iso-8859-2} and add some Russian words to it.
When you save the buffer, Emacs cannot use the current value of
or the Custom option @code{keyboard-coding-system}
specifies the coding system for keyboard input. Character-code
translation of keyboard input is useful for terminals with keys that
-send non-ASCII graphic characters---for example, some terminals designed
+send non-@acronym{ASCII} graphic characters---for example, some terminals designed
for ISO Latin-1 or subsets of it.
By default, keyboard input is translated based on your system locale
setting. If your terminal does not really support the encoding
implied by your locale (for example, if you find it inserts a
-non-ASCII character if you type @kbd{M-i}), you will need to set
+non-@acronym{ASCII} character if you type @kbd{M-i}), you will need to set
@code{keyboard-coding-system} to @code{nil} to turn off encoding.
You can do this by putting
keyboard input, and using an input method: both define sequences of
keyboard input that translate into single characters. However, input
methods are designed to be convenient for interactive use by humans, and
-the sequences that are translated are typically sequences of ASCII
+the sequences that are translated are typically sequences of @acronym{ASCII}
printing characters. Coding systems typically translate sequences of
non-graphic characters.
current language environment.
@vindex file-name-coding-system
-@cindex file names with non-ASCII characters
+@cindex file names with non-@acronym{ASCII} characters
The variable @code{file-name-coding-system} specifies a coding system
to use for encoding file names. If you set the variable to a coding
system name (as a Lisp symbol or a string), Emacs encodes file names
using that coding system for all file operations. This makes it
-possible to use non-ASCII characters in file names---or, at least, those
-non-ASCII characters which the specified coding system can encode.
+possible to use non-@acronym{ASCII} characters in file names---or, at least, those
+non-@acronym{ASCII} characters which the specified coding system can encode.
If @code{file-name-coding-system} is @code{nil}, Emacs uses a default
coding system determined by the selected language environment. In the
-default language environment, any non-ASCII characters in file names are
+default language environment, any non-@acronym{ASCII} characters in file names are
not encoded specially; they appear in the file system using the internal
Emacs representation.
C-w} to specify a new file name for that buffer.
@vindex locale-coding-system
-@cindex decoding non-ASCII keyboard input on X
+@cindex decoding non-@acronym{ASCII} keyboard input on X
The variable @code{locale-coding-system} specifies a coding system
to use when encoding and decoding system strings such as system error
messages and @code{format-time-string} formats and time stamps. That
-coding system is also used for decoding non-ASCII keyboard input on X
+coding system is also used for decoding non-@acronym{ASCII} keyboard input on X
Window systems. You should choose a coding system that is compatible
with the underlying system's text representation, which is normally
specified by one of the environment variables @env{LC_ALL},
Emacs creates two fontsets automatically: the @dfn{standard fontset}
and the @dfn{startup fontset}. The standard fontset is most likely to
-have fonts for a wide variety of non-ASCII characters; however, this is
+have fonts for a wide variety of non-@acronym{ASCII} characters; however, this is
not the default for Emacs to use. (By default, Emacs tries to find a
font that has bold and italic variants.) You can specify use of the
standard fontset with the @samp{-fn} option, or with the @samp{Font} X
@samp{medium}, or @samp{i} instead of @samp{r}, or both.
@cindex startup fontset
- If you specify a default ASCII font with the @samp{Font} resource or
+ If you specify a default @acronym{ASCII} font with the @samp{Font} resource or
the @samp{-fn} argument, Emacs generates a fontset from it
automatically. This is the @dfn{startup fontset} and its name is
@code{fontset-startup}. It does this by replacing the @var{foundry},
For the other character sets, Emacs chooses a font based on
@var{fontpattern}. It replaces @samp{fontset-@var{alias}} with values
-that describe the character set. For the ASCII character font,
+that describe the character set. For the @acronym{ASCII} character font,
@samp{fontset-@var{alias}} is replaced with @samp{ISO8859-1}.
In addition, when several consecutive fields are wildcards, Emacs
@end example
@noindent
-the font specification for ASCII characters would be this:
+the font specification for @acronym{ASCII} characters would be this:
@example
-*-fixed-medium-r-normal-*-24-*-ISO8859-1
@node Undisplayable Characters
@section Undisplayable Characters
- There may be a some non-ASCII characters that your terminal cannot
+ There may be a some non-@acronym{ASCII} characters that your terminal cannot
display. Most non-windowing terminals support just a single character
set (use the variable @code{default-terminal-coding-system}
(@pxref{Specify Coding}) to tell Emacs which one); characters which
no font appear as a hollow box.
If you use Latin-1 characters but your terminal can't display
-Latin-1, you can arrange to display mnemonic ASCII sequences
+Latin-1, you can arrange to display mnemonic @acronym{ASCII} sequences
instead, e.g.@: @samp{"o} for o-umlaut. Load the library
@file{iso-ascii} to do this.
@vindex latin1-display
If your terminal can display Latin-1, you can display characters
from other European character sets using a mixture of equivalent
-Latin-1 characters and ASCII mnemonics. Use the Custom option
-@code{latin1-display} to enable this. The mnemonic ASCII
+Latin-1 characters and @acronym{ASCII} mnemonics. Use the Custom option
+@code{latin1-display} to enable this. The mnemonic @acronym{ASCII}
sequences mostly correspond to those of the prefix input methods.
@node Single-Byte Character Support
For more information about unibyte operation, see @ref{Enabling
Multibyte}. Note particularly that you probably want to ensure that
-your initialization files are read as unibyte if they contain non-ASCII
+your initialization files are read as unibyte if they contain non-@acronym{ASCII}
characters.
@vindex unibyte-display-via-language-environment
@cindex @code{iso-ascii} library
If your terminal does not support display of the Latin-1 character
-set, Emacs can display these characters as ASCII sequences which at
+set, Emacs can display these characters as @acronym{ASCII} sequences which at
least give you a clear idea of what the characters are. To do this,
load the library @code{iso-ascii}. Similar libraries for other
Latin-@var{n} character sets could be implemented, but we don't have
non-standard ``extended'' versions of ISO-8859 character sets by using the
function @code{standard-display-8bit} in the @code{disp-table} library.
- There are several ways you can input single-byte non-ASCII
+ There are several ways you can input single-byte non-@acronym{ASCII}
characters:
@itemize @bullet
@cindex 8-bit input
@item
If your keyboard can generate character codes 128 (decimal) and up,
-representing non-ASCII characters, you can type those character codes
+representing non-@acronym{ASCII} characters, you can type those character codes
directly.
On a windowing terminal, you should not need to do anything special to
@item
You can use an input method for the selected language environment.
@xref{Input Methods}. When you use an input method in a unibyte buffer,
-the non-ASCII character you specify with it is converted to unibyte.
+the non-@acronym{ASCII} character you specify with it is converted to unibyte.
@kindex C-x 8
@cindex @code{iso-transl} library
@item
For Latin-1 only, you can use the
key @kbd{C-x 8} as a ``compose character'' prefix for entry of
-non-ASCII Latin-1 printing characters. @kbd{C-x 8} is good for
+non-@acronym{ASCII} Latin-1 printing characters. @kbd{C-x 8} is good for
insertion (in the minibuffer as well as other buffers), for searching,
and in any other context where a key sequence is allowed.
Emacs groups all supported characters into disjoint @dfn{charsets}.
Each character code belongs to one and only one charset. For
historical reasons, Emacs typically divides an 8-bit character code
-for an extended version of ASCII into two charsets: ASCII, which
+for an extended version of @acronym{ASCII} into two charsets: @acronym{ASCII}, which
covers the codes 0 through 127, plus another charset which covers the
``right-hand part'' (the codes 128 and up). For instance, the
characters of Latin-1 include the Emacs charset @code{ascii} plus the
@section Rmail and Coding Systems
@cindex decoding mail messages (Rmail)
- Rmail automatically decodes messages which contain non-ASCII
+ Rmail automatically decodes messages which contain non-@acronym{ASCII}
characters, just as Emacs does with files you visit and with subprocess
output. Rmail uses the standard @samp{charset=@var{charset}} header in
the message, if any, to determine how the message was encoded by the
treated in the same context. You can also specify a character by its
octal code: enter @kbd{C-q} followed by a sequence of octal digits.
-@cindex searching for non-ASCII characters
+@cindex searching for non-@acronym{ASCII} characters
@cindex input method, during incremental search
- To search for non-ASCII characters, you must use an input method
+ To search for non-@acronym{ASCII} characters, you must use an input method
(@pxref{Input Methods}). If an input method is enabled in the
current buffer when you start the search, you can use it while you
type the search string also. Emacs indicates that by including the
You can also include character ranges in a character set, by writing the
starting and ending characters with a @samp{-} between them. Thus,
-@samp{[a-z]} matches any lower-case ASCII letter. Ranges may be
+@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 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
@item @kbd{[^ @dots{} ]}
@samp{[^} begins a @dfn{complemented character set}, which matches any
character except the ones specified. Thus, @samp{[^a-z0-9A-Z]} matches
-all characters @emph{except} ASCII letters and digits.
+all characters @emph{except} @acronym{ASCII} letters and digits.
@samp{^} is not special in a character set unless it is the first
character. The character following the @samp{^} is treated as if it
@c This is indexed in mule.texi, node "Recognize Coding".
@c @vindex sendmail-coding-system
- When you send a message that contains non-ASCII characters, they need
+ When you send a message that contains non-@acronym{ASCII} characters, they need
to be encoded with a coding system (@pxref{Coding Systems}). Usually
the coding system is specified automatically by your chosen language
environment (@pxref{Language Environments}). You can explicitly specify
@cindex pages
@cindex formfeed
Files are often thought of as divided into @dfn{pages} by the
-@dfn{formfeed} character (ASCII control-L, octal code 014). When you
+@dfn{formfeed} character (@acronym{ASCII} control-L, octal code 014). When you
print hardcopy for a file, this character forces a page break; thus,
each page of the file goes on a separate page on paper. Most Emacs
commands treat the page-separator character just like any other
Your access to the remote machine can be with the @command{rsh},
@command{rlogin}, @command{telnet} programs or with any similar
-connection method. This connection must pass ASCII successfully to be
+connection method. This connection must pass @acronym{ASCII} successfully to be
usable but need not be 8-bit clean.
The package provides support for @command{ssh} connections out of the
stimulates the bug.@refill
@item
-If non-ASCII text or internationalization is relevant, the locale that
+If non-@acronym{ASCII} text or internationalization is relevant, the locale that
was current when you started Emacs. On GNU/Linux and Unix systems, or
if you use a Posix-style shell such as Bash, you can use this shell
command to view the relevant values:
@cindex end (of buffer)
@cindex region
-Conceptually, a @dfn{buffer} is just a string of ASCII characters and two
+Conceptually, a @dfn{buffer} is just a string of @acronym{ASCII} characters and two
special characters @key{PNT} (@dfn{point}) and @key{MRK} (@dfn{mark}) such
that the character @key{PNT} occurs exactly once and @key{MRK} occurs at
most once. The @dfn{text} of a buffer is obtained by deleting the
@item m @var{ch}
@kindex 155 @kbd{m} (@code{vip-mark-point})
Store current point in the register @var{ch}. @var{ch} must be a
-lower-case ASCII letter.
+lower-case @acronym{ASCII} letter.
@item m <
Set mark at the beginning of current buffer.
@item m >
We also use @samp{word} for alphanumeric/non-alphanumeric words, and
@samp{WORD} for whitespace delimited words. @samp{char} refers to any
-ASCII character, @samp{CHAR} to non-whitespace character.
+@acronym{ASCII} character, @samp{CHAR} to non-whitespace character.
Brackets @samp{[]} indicate optional parameters; @samp{<count>} also
optional, usually defaulting to 1. Brackets are elided for
@samp{<count>} to eschew obfuscation.
meaning. The user is not supposed to change or delete any of the text
between the fields. Examples of forms in Emacs are the @file{forms}
package (of course), the customize buffers, the mail and news compose
-modes, and the @sc{html} form support in the @file{w3} browser.
+modes, and the @acronym{HTML} form support in the @file{w3} browser.
@cindex widget library, why use it
The advantages for a programmer of using the @code{widget} package to
@end example
@findex browse-url-browser-function@r{, and @code{url-link} widget}
-When this link is invoked, the @sc{www} browser specified by
+When this link is invoked, the @acronym{WWW} browser specified by
@code{browse-url-browser-function} will be called with @var{url}.
@node info-link, push-button, url-link, Basic Types
\input texinfo @c -*-texinfo-*-
-@c $Id: woman.texi,v 1.14 2003/09/01 15:45:46 miles Exp $
+@c $Id: woman.texi,v 1.15 2003/09/30 20:42:15 rms Exp $
@c %**start of header
@setfilename ../info/woman
@settitle WoMan: Browse Unix Manual Pages ``W.O. (without) Man''
The distinction between @code{TROFF} and @code{NROFF} is that
@code{TROFF} was designed to drive a phototypesetter whereas
-@code{NROFF} was designed to produce essentially @sc{ascii} output for a
+@code{NROFF} was designed to produce essentially @acronym{ASCII} output for a
character-based device similar to a teletypewriter (usually abbreviated
to ``teletype'' or ``tty''). Hence, @code{TROFF} supports much finer
control over output positioning than does @code{NROFF} and can be seen
@code{man} uses machine code, and is a testimony to the quality of the
Emacs Lisp system.
-@code{NROFF} simulates non-@sc{ascii} characters by using one or more
-@sc{ascii} characters. WoMan should be able to do much better than
+@code{NROFF} simulates non-@acronym{ASCII} characters by using one or more
+@acronym{ASCII} characters. WoMan should be able to do much better than
this. I have recently begun to add support for WoMan to use more of the
characters in its default font and to use a symbol font, and it is an
aspect that I intend to develop further in the near future. It should
Emacs provides an interface to detect automatically the format of a file
and decode it when it is visited. It is used primarily by the
facilities for editing rich (i.e.@: formatted) text, as a way to store
-formatting information transparently as @sc{ascii} markup. WoMan can in
+formatting information transparently as @acronym{ASCII} markup. WoMan can in
principle use this interface, but it must be configured explicitly.
This use of WoMan does not seem to be particularly advantageous, so it
If @code{nil} then they are left in the buffer, which may aid debugging.
@item woman-preserve-ascii
-A boolean value. If non-@code{nil} then preserve @sc{ascii} characters in the
-WoMan buffer. Otherwise, non-@sc{ascii} characters (that display as
-@sc{ascii}) may remain, which is irrelevant unless the buffer is to be
+A boolean value. If non-@code{nil} then preserve @acronym{ASCII} characters in the
+WoMan buffer. Otherwise, non-@acronym{ASCII} characters (that display as
+@acronym{ASCII}) may remain, which is irrelevant unless the buffer is to be
saved to a file. Default is @code{nil}.
@item woman-emulation
WoMan provides partial experimental support for special symbols,
initially only for MS-Windows and only for MS-Windows fonts. This
-includes both non-@sc{ascii} characters from the main text font and use
+includes both non-@acronym{ASCII} characters from the main text font and use
of a separate symbol font. Later, support will be added for other font
types (e.g.@: @code{bdf} fonts) and for the X Window System. In Emacs
20.7, the current support works partially under Windows 9x but may not
@vtable @code
@item woman-use-extended-font
-A boolean value. If non-@code{nil} then WoMan may use non-@sc{ascii} characters
+A boolean value. If non-@code{nil} then WoMan may use non-@acronym{ASCII} characters
from the default font. Default is @code{t}.
@item woman-use-symbol-font
HCoop / bpt / emacs.git / commitdiff