emacs-diffs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Emacs-diffs] /srv/bzr/emacs/emacs-23 r100528: * strings.texi (String Co


From: Stefan Monnier
Subject: [Emacs-diffs] /srv/bzr/emacs/emacs-23 r100528: * strings.texi (String Conversion): Don't mention string-make-(uni|multi)byte.
Date: Wed, 16 Mar 2011 10:54:21 -0400
User-agent: Bazaar (2.0.3)

------------------------------------------------------------
revno: 100528
committer: Stefan Monnier <address@hidden>
branch nick: emacs-23
timestamp: Wed 2011-03-16 10:54:21 -0400
message:
  * strings.texi (String Conversion): Don't mention string-make-(uni|multi)byte.
  * nonascii.texi (Converting Representations): Fix up range.
  * keymaps.texi (Key Binding Commands): Update code point, avoid
  "unibyte character" and remove mention of unibyte bindings.
modified:
  doc/lispref/ChangeLog
  doc/lispref/keymaps.texi
  doc/lispref/nonascii.texi
  doc/lispref/strings.texi
=== modified file 'doc/lispref/ChangeLog'
--- a/doc/lispref/ChangeLog     2011-03-07 05:20:23 +0000
+++ b/doc/lispref/ChangeLog     2011-03-16 14:54:21 +0000
@@ -1,3 +1,11 @@
+2011-03-16  Stefan Monnier  <address@hidden>
+
+       * strings.texi (String Conversion): Don't mention
+       string-make-(uni|multi)byte (bug#8262).
+       * nonascii.texi (Converting Representations): Fix up range.
+       * keymaps.texi (Key Binding Commands): Update code point, avoid
+       "unibyte character" and remove mention of unibyte bindings.
+
 2011-03-07  Chong Yidong  <address@hidden>
 
        * Version 23.3 released.

=== modified file 'doc/lispref/keymaps.texi'
--- a/doc/lispref/keymaps.texi  2011-02-18 05:11:26 +0000
+++ b/doc/lispref/keymaps.texi  2011-03-16 14:54:21 +0000
@@ -1707,15 +1707,11 @@
 
 @noindent
 and your language environment is multibyte Latin-1, these commands
-actually bind the multibyte character with code 2294, not the unibyte
-Latin-1 character with code 246 (@kbd{M-v}).  In order to use this
-binding, you need to enter the multibyte Latin-1 character as keyboard
-input.  One way to do this is by using an appropriate input method
-(@pxref{Input Methods, , Input Methods, emacs, The GNU Emacs Manual}).
-
-  If you want to use a unibyte character in the key binding, you can
-construct the key sequence string using @code{multibyte-char-to-unibyte}
-or @code{string-make-unibyte} (@pxref{Converting Representations}).
+actually bind the multibyte character with code 246, not the byte
+code 246 (@kbd{M-v}) sent by a Latin-1 terminal.  In order to use this
+binding, you need to teach Emacs how to decode the keyboard by using an
+appropriate input method (@pxref{Input Methods, , Input Methods, emacs, The GNU
+Emacs Manual}).
 
 @deffn Command global-set-key key binding
 This function sets the binding of @var{key} in the current global map

=== modified file 'doc/lispref/nonascii.texi'
--- a/doc/lispref/nonascii.texi 2011-01-02 23:50:46 +0000
+++ b/doc/lispref/nonascii.texi 2011-03-16 14:54:21 +0000
@@ -171,7 +171,7 @@
 user that cannot be overridden automatically.
 
   Converting unibyte text to multibyte text leaves @acronym{ASCII}
-characters unchanged, and converts bytes with codes 128 through 159 to
+characters unchanged, and converts bytes with codes 128 through 255 to
 the multibyte representation of raw eight-bit bytes.
 
   Converting multibyte text to unibyte converts all @acronym{ASCII}

=== modified file 'doc/lispref/strings.texi'
--- a/doc/lispref/strings.texi  2011-01-02 23:50:46 +0000
+++ b/doc/lispref/strings.texi  2011-03-16 14:54:21 +0000
@@ -555,8 +555,8 @@
 @code{prin1-to-string} (@pxref{Output Functions}) can also convert
 Lisp objects into strings.  @code{read-from-string} (@pxref{Input
 Functions}) can ``convert'' a string representation of a Lisp object
-into an object.  The functions @code{string-make-multibyte} and
address@hidden convert the text representation of a string
+into an object.  The functions @code{string-to-multibyte} and
address@hidden convert the text representation of a string
 (@pxref{Converting Representations}).
 
   @xref{Documentation}, for functions that produce textual descriptions


reply via email to

[Prev in Thread] Current Thread [Next in Thread]