[Emacs-diffs] Changes to emacs/man/mule.texi

[Eli Zaretskii]

Index: emacs/man/mule.texi
diff -c emacs/man/mule.texi:1.66 emacs/man/mule.texi:1.67
*** emacs/man/mule.texi:1.66    Mon Sep  1 11:45:46 2003
--- emacs/man/mule.texi Sun Nov  2 02:01:12 2003
***************
*** 49,56 ****
  
  @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
  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.
--- 49,56 ----
  
  @itemize @bullet
  @item
! You can visit files with address@hidden characters, save address@hidden text, 
and
! pass address@hidden 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.
***************
*** 58,64 ****
  for each command; see @ref{Specify Coding}.
  
  @item
! You can display non-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
--- 58,64 ----
  for each command; see @ref{Specify Coding}.
  
  @item
! You can display address@hidden 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
***************
*** 66,77 ****
  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 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
  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,
--- 66,77 ----
  describes possible problems and explains how to solve them.
  
  @item
! You can insert address@hidden 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 address@hidden 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,
***************
*** 110,116 ****
  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
  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
--- 110,116 ----
  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 address@hidden 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
***************
*** 187,197 ****
  @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
    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
  characters.
  
    Emacs normally loads Lisp files as multibyte, regardless of whether
--- 187,197 ----
  @cindex Lisp files, and multibyte operation
  @cindex multibyte operation, and Lisp files
  @cindex unibyte operation, and Lisp files
! @cindex init file, and address@hidden characters
! @cindex environment variables, and address@hidden characters
    With @samp{--unibyte}, multibyte strings are not created during
  initialization from the values of environment variables,
! @file{/etc/passwd} entries etc.@: that contain address@hidden 8-bit
  characters.
  
    Emacs normally loads Lisp files as multibyte, regardless of whether
***************
*** 282,288 ****
  (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.
  
    If you modify the @env{LC_ALL}, @env{LC_CTYPE}, or @env{LANG}
  environment variables while running Emacs, you may want to invoke the
--- 282,288 ----
  (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 address@hidden 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
***************
*** 346,359 ****
  characters can share one input method.  A few languages support several
  input methods.
  
!   The simplest kind of input method works by mapping ASCII letters
  into another alphabet; this allows you to use one other alphabet
! instead of 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
  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
--- 346,359 ----
  characters can share one input method.  A few languages support several
  input methods.
  
!   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 @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 address@hidden 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
***************
*** 480,487 ****
  
  @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
  method temporarily.  To do this, type @kbd{C-\}
  (@code{toggle-input-method}).  To reenable the input method, type
  @kbd{C-\} again.
--- 480,487 ----
  
  @findex toggle-input-method
  @kindex C-\
!   Input methods use various sequences of @acronym{ASCII} characters to stand 
for
! address@hidden 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.
***************
*** 534,544 ****
  method, including the string that stands for it in the mode line.
  
  @node Multibyte Conversion
! @section Unibyte and Multibyte Non-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.
  
    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
--- 534,544 ----
  method, including the string that stands for it in the mode line.
  
  @node Multibyte Conversion
! @section Unibyte and Multibyte address@hidden characters
  
    When multibyte characters are enabled, character codes 0240 (octal)
  through 0377 (octal) are not really legitimate in the buffer.  The valid
! address@hidden 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
***************
*** 590,596 ****
  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
  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.
--- 590,596 ----
  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 address@hidden
  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.
***************
*** 661,668 ****
  @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
  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
--- 661,668 ----
  @code{iso-latin-1-mac}.
  
    The coding system @code{raw-text} is good for a file which is mainly
! @acronym{ASCII} text, but may contain byte values above 127 which are not 
meant to
! encode address@hidden 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
***************
*** 670,676 ****
  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
  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}.
--- 670,676 ----
  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 address@hidden 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}.
***************
*** 681,687 ****
  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
  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.
  
--- 681,687 ----
  might convert the file contents before you see them.  @xref{Visiting}.
  
    The coding system @code{emacs-mule} means that the file contains
! address@hidden 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.
  
***************
*** 774,780 ****
    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
  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.
--- 774,780 ----
    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 address@hidden 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.
***************
*** 817,823 ****
  @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 address@hidden characters to either Latin-1 or
  Unicode characters.  This way it is easier to use various
  address@hidden alphabets together.  In a future Emacs version we hope
  to move towards full Unicode support and complete unification of
--- 817,823 ----
  @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 address@hidden address@hidden characters to either Latin-1 or
  Unicode characters.  This way it is easier to use various
  address@hidden alphabets together.  In a future Emacs version we hope
  to move towards full Unicode support and complete unification of
***************
*** 837,843 ****
  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
  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
--- 837,843 ----
  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 @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
***************
*** 993,1005 ****
  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
  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
  @code{keyboard-coding-system} to @code{nil} to turn off encoding.
  You can do this by putting
  
--- 993,1005 ----
  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 address@hidden 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
! address@hidden 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
  
***************
*** 1014,1020 ****
  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
  printing characters.  Coding systems typically translate sequences of
  non-graphic characters.
  
--- 1014,1020 ----
  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 @acronym{ASCII}
  printing characters.  Coding systems typically translate sequences of
  non-graphic characters.
  
***************
*** 1043,1059 ****
  current language environment.
  
  @vindex file-name-coding-system
! @cindex file names with non-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.
  
    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
  not encoded specially; they appear in the file system using the internal
  Emacs representation.
  
--- 1043,1059 ----
  current language environment.
  
  @vindex file-name-coding-system
! @cindex file names with address@hidden 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 address@hidden characters in file names---or, at least, those
! address@hidden 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 address@hidden characters in file names are
  not encoded specially; they appear in the file system using the internal
  Emacs representation.
  
***************
*** 1067,1077 ****
  C-w} to specify a new file name for that buffer.
  
  @vindex locale-coding-system
! @cindex decoding non-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
  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},
--- 1067,1077 ----
  C-w} to specify a new file name for that buffer.
  
  @vindex locale-coding-system
! @cindex decoding address@hidden 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 address@hidden 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},
***************
*** 1101,1107 ****
  
    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
  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
--- 1101,1107 ----
  
    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 address@hidden 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
***************
*** 1137,1143 ****
  @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
  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},
--- 1137,1143 ----
  @samp{medium}, or @samp{i} instead of @samp{r}, or both.
  
  @cindex startup fontset
!   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},
***************
*** 1191,1197 ****
  
    For the other character sets, Emacs chooses a font based on
  @var{fontpattern}.  It replaces @address@hidden with values
! that describe the character set.  For the ASCII character font,
  @address@hidden is replaced with @samp{ISO8859-1}.
  
    In addition, when several consecutive fields are wildcards, Emacs
--- 1191,1197 ----
  
    For the other character sets, Emacs chooses a font based on
  @var{fontpattern}.  It replaces @address@hidden with values
! that describe the character set.  For the @acronym{ASCII} character font,
  @address@hidden is replaced with @samp{ISO8859-1}.
  
    In addition, when several consecutive fields are wildcards, Emacs
***************
*** 1208,1214 ****
  @end example
  
  @noindent
! the font specification for ASCII characters would be this:
  
  @example
  -*-fixed-medium-r-normal-*-24-*-ISO8859-1
--- 1208,1214 ----
  @end example
  
  @noindent
! the font specification for @acronym{ASCII} characters would be this:
  
  @example
  -*-fixed-medium-r-normal-*-24-*-ISO8859-1
***************
*** 1247,1253 ****
  @node Undisplayable Characters
  @section Undisplayable Characters
  
!   There may be a some non-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
--- 1247,1253 ----
  @node Undisplayable Characters
  @section Undisplayable Characters
  
!   There may be a some address@hidden 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
***************
*** 1259,1273 ****
  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
  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
  sequences mostly correspond to those of the prefix input methods.
  
  @node Single-Byte Character Support
--- 1259,1273 ----
  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 @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 @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
***************
*** 1288,1294 ****
  
    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
  characters.
  
  @vindex unibyte-display-via-language-environment
--- 1288,1294 ----
  
    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 address@hidden
  characters.
  
  @vindex unibyte-display-via-language-environment
***************
*** 1302,1308 ****
  
  @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
  least give you a clear idea of what the characters are.  To do this,
  load the library @code{iso-ascii}.  Similar libraries for other
  address@hidden character sets could be implemented, but we don't have
--- 1302,1308 ----
  
  @cindex @code{iso-ascii} library
    If your terminal does not support display of the Latin-1 character
! 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
  address@hidden character sets could be implemented, but we don't have
***************
*** 1315,1328 ****
  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
  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
  directly.
  
  On a windowing terminal, you should not need to do anything special to
--- 1315,1328 ----
  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 address@hidden
  characters:
  
  @itemize @bullet
  @cindex 8-bit input
  @item
  If your keyboard can generate character codes 128 (decimal) and up,
! representing address@hidden characters, you can type those character codes
  directly.
  
  On a windowing terminal, you should not need to do anything special to
***************
*** 1339,1345 ****
  @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.
  
  @kindex C-x 8
  @cindex @code{iso-transl} library
--- 1339,1345 ----
  @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 address@hidden character you specify with it is converted to unibyte.
  
  @kindex C-x 8
  @cindex @code{iso-transl} library
***************
*** 1348,1354 ****
  @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
  insertion (in the minibuffer as well as other buffers), for searching,
  and in any other context where a key sequence is allowed.
  
--- 1348,1354 ----
  @item
  For Latin-1 only, you can use the
  key @kbd{C-x 8} as a ``compose character'' prefix for entry of
! address@hidden 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.
  
***************
*** 1380,1386 ****
    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
  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
--- 1380,1386 ----
    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 @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