Fix non-ASCII characters in User and ELisp manuals.

 doc/lispref/modes.texi (Operator Precedence Grammars): Don't use characters
 outside ISO-8859-1.
 doc/emacs/search.texi (Regexp Example):
 doc/emacs/mule.texi (International Chars):
 doc/emacs/building.texi (External Lisp): Don't use characters outside
 ISO-8859-1.

diff --git a/doc/emacs/ChangeLog b/doc/emacs/ChangeLog
index 4bdd1448adde30594b7e8e7ae87e340104518233..a53aa095cc2be2a55d871e07c7966dd4e16bb9a6 100644 (file)
--- a/doc/emacs/ChangeLog
+++ b/doc/emacs/ChangeLog
@@ -1,3 +1,10 @@
+2011-03-10  Eli Zaretskii  <eliz@gnu.org>
+
+       * search.texi (Regexp Example):
+       * mule.texi (International Chars):
+       * building.texi (External Lisp): Don't use characters outside
+       ISO-8859-1.
+
 2011-03-09  Eli Zaretskii  <eliz@gnu.org>
 
        * ack.texi (Acknowledgments): Convert to ISO-8859-1 encoding.  Use

diff --git a/doc/emacs/building.texi b/doc/emacs/building.texi
index 1a02e92b67f498dedbb4408f0c363e421c1219c8..a07e75820119e2ce4992908ebcbbaca2f5f87ef5 100644 (file)
--- a/doc/emacs/building.texi
+++ b/doc/emacs/building.texi
@@ -1056,7 +1056,7 @@ Show file information or library names in threads buffer.
 Show addresses for thread frames in threads buffer.
 @end table
 
-  It’s possible to observe information for several threads
+  It's possible to observe information for several threads
 simultaneously (in addition to buffers which show information for
 currently selected thread) using the following keys from the threads
 buffer.

diff --git a/doc/emacs/mule.texi b/doc/emacs/mule.texi
index 22c155d26deb97393baa84ce6607811a0561f679..e12ec7070636458a4c58349c9b351bd52f889584 100644 (file)
--- a/doc/emacs/mule.texi
+++ b/doc/emacs/mule.texi
@@ -237,7 +237,7 @@ preferred charset: unicode (Unicode (ISO10646))
 Character code properties: customize what to show
   name: LATIN CAPITAL LETTER A WITH GRAVE
   general-category: Lu (Letter, Uppercase)
-  decomposition: (65 768) ('A' '̀')
+  decomposition: (65 768) ('A' '`')
   old-name: LATIN CAPITAL LETTER A GRAVE
 
 There are text properties here:

diff --git a/doc/emacs/search.texi b/doc/emacs/search.texi
index 9fdccc3218d971e7118e1cfa89cdc9cc586b1181..b5d426210aa7cc2503bb301ad39d6f8d1d360fb6 100644 (file)
--- a/doc/emacs/search.texi
+++ b/doc/emacs/search.texi
@@ -917,13 +917,13 @@ setting of the syntax table (@pxref{Syntax}).
 @node Regexp Example
 @section Regular Expression Example
 
-  Here is an example of a regexp---the regexp that Emacs uses, by
-default, to recognize the end of a sentence, not including the
-following space (i.e., the variable @code{sentence-end-base}):
+  Here is an example of a regexp---similar to the regexp that Emacs
+uses, by default, to recognize the end of a sentence, not including
+the following space (i.e., the variable @code{sentence-end-base}):
 
 @example
 @verbatim
-[.?!][]\"'””)}]*
+[.?!][]\"')}]*
 @end verbatim
 @end example
 

diff --git a/doc/lispref/ChangeLog b/doc/lispref/ChangeLog
index fb99bee7aee91386d2ca4d901ac7a9ad361ad715..a0498bf46c2402463edc47bad4c4c01c693cec16 100644 (file)
--- a/doc/lispref/ChangeLog
+++ b/doc/lispref/ChangeLog
@@ -1,3 +1,8 @@
+2011-03-10  Eli Zaretskii  <eliz@gnu.org>
+
+       * modes.texi (Operator Precedence Grammars): Don't use characters
+       outside ISO-8859-1.
+
 2011-03-09  Eli Zaretskii  <eliz@gnu.org>
 
        * intro.texi (Acknowledgements): Convert to ISO-8859-1 encoding.

diff --git a/doc/lispref/modes.texi b/doc/lispref/modes.texi
index f238f38462fd4e41d62a45aae63fbc3fdece1258..f0a8985fa75f8a6fe9dac7f511044549813111c1 100644 (file)
--- a/doc/lispref/modes.texi
+++ b/doc/lispref/modes.texi
@@ -3403,7 +3403,7 @@ Such pairs of precedences are sufficient to express left-associativity
 or right-associativity of infix operators, nesting of tokens like
 parentheses and many other cases.
 
-@c ¡Let's leave this undocumented to leave it more open for change!
+@c Let's leave this undocumented to leave it more open for change!
 @c @defvar smie-grammar
 @c The value of this variable is an alist specifying the left and right
 @c precedence of each token.  It is meant to be initialized by using one of