[Emacs-diffs] Changes to emacs/lispref/loading.texi

[Eli Zaretskii]

Index: emacs/lispref/loading.texi
diff -c emacs/lispref/loading.texi:1.44 emacs/lispref/loading.texi:1.45
*** emacs/lispref/loading.texi:1.44     Sun Oct  5 19:21:48 2003
--- emacs/lispref/loading.texi  Sun Nov  2 01:29:58 2003
***************
*** 37,43 ****
  @menu
  * How Programs Do Loading::     The @code{load} function and others.
  * Library Search::              Finding a library to load.
! * Loading Non-ASCII::           address@hidden 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.
--- 37,43 ----
  @menu
  * How Programs Do Loading::     The @code{load} function and others.
  * Library Search::              Finding a library to load.
! * Loading Non-ASCII::           address@hidden 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,301 ****
  @end defvar
  
  @node Loading Non-ASCII
! @section Loading address@hidden Characters
  
!   When Emacs Lisp programs contain string constants with address@hidden
  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
--- 293,301 ----
  @end defvar
  
  @node Loading Non-ASCII
! @section Loading address@hidden Characters
  
!   When Emacs Lisp programs contain string constants with address@hidden
  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,315 ****
    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 address@hidden characters translate into multibyte
  strings.  The only exception is when a particular file specifies no
  decoding.
  
--- 309,315 ----
    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 address@hidden characters translate into multibyte
  strings.  The only exception is when a particular file specifies no
  decoding.
  
***************
*** 321,327 ****
  @code{default-enable-multibyte-characters}, and convert representations
  appropriately.
  
!   In most Emacs Lisp programs, the fact that address@hidden 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
--- 321,327 ----
  @code{default-enable-multibyte-characters}, and convert representations
  appropriately.
  
!   In most Emacs Lisp programs, the fact that address@hidden 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,335 ****
  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
! address@hidden characters written as @address@hidden
  
  @node Autoload
  @section Autoload
--- 329,335 ----
  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
! address@hidden characters written as @address@hidden
  
  @node Autoload
  @section Autoload