diff man/mule.texi @ 58624:a322009ca3d0

* custom.texi (File Variables): Add `unibyte' and make it more clear that `unibyte' and `coding' are special. Suggested by Simon Krahnke <[e-mail]>. * mule.texi (Enabling Multibyte): Refer to File Variables. Suggested by Simon Krahnke <[e-mail]>.

--- a/man/mule.texi	Mon Nov 29 15:35:15 2004 +0000
+++ b/man/mule.texi	Mon Nov 29 15:58:15 2004 +0000
@@ -195,15 +195,15 @@
 characters.
 
   Emacs normally loads Lisp files as multibyte, regardless of whether
-you used @samp{--unibyte}.  This includes the Emacs initialization
-file, @file{.emacs}, and the initialization files of Emacs packages
-such as Gnus.  However, you can specify unibyte loading for a
-particular Lisp file, by putting @w{@samp{-*-unibyte: t;-*-}} in a
-comment on the first line.  Then that file is always loaded as unibyte
-text, even if you did not start Emacs with @samp{--unibyte}.  The
-motivation for these conventions is that it is more reliable to always
-load any particular Lisp file in the same way.  However, you can load
-a Lisp file as unibyte, on any one occasion, by typing @kbd{C-x
+you used @samp{--unibyte}.  This includes the Emacs initialization file,
+@file{.emacs}, and the initialization files of Emacs packages such as
+Gnus.  However, you can specify unibyte loading for a particular Lisp
+file, by putting @w{@samp{-*-unibyte: t;-*-}} in a comment on the first
+line (@pxref{File Variables}).  Then that file is always loaded as
+unibyte text, even if you did not start Emacs with @samp{--unibyte}.
+The motivation for these conventions is that it is more reliable to
+always load any particular Lisp file in the same way.  However, you can
+load a Lisp file as unibyte, on any one occasion, by typing @kbd{C-x
 @key{RET} c raw-text @key{RET}} immediately before loading it.
 
   The mode line indicates whether multibyte character support is enabled