summaryrefslogtreecommitdiff
path: root/doc/lispref
diff options
context:
space:
mode:
authorEli Zaretskii <eliz@gnu.org>2012-06-23 15:39:23 +0300
committerEli Zaretskii <eliz@gnu.org>2012-06-23 15:39:23 +0300
commit0bd8297f9cee150f34cbab14c71825d21d7bf91c (patch)
tree16a94bc4ac8fa7ea10b3de78584695a3d364487d /doc/lispref
parent63def6b6d1acb18d90c705687359edd4f4c2f49a (diff)
downloademacs-0bd8297f9cee150f34cbab14c71825d21d7bf91c.tar.gz
Improve and document the language-change event on MS-Windows.
src/keyboard.c (kbd_buffer_get_event): Include the codepage and the language ID in the event parameters. src/w32term.c (w32_read_socket): Put the new keyboard codepage into event.code, not the obscure "character set ID". doc/lispref/commands.texi (Misc Events): Document the language-change event.
Diffstat (limited to 'doc/lispref')
-rw-r--r--doc/lispref/ChangeLog4
-rw-r--r--doc/lispref/commands.texi32
2 files changed, 36 insertions, 0 deletions
diff --git a/doc/lispref/ChangeLog b/doc/lispref/ChangeLog
index 838617cf866..154b4487d5e 100644
--- a/doc/lispref/ChangeLog
+++ b/doc/lispref/ChangeLog
@@ -1,3 +1,7 @@
+2012-06-23 Eli Zaretskii <eliz@gnu.org>
+
+ * commands.texi (Misc Events): Document the language-change event.
+
2012-06-22 Paul Eggert <eggert@cs.ucla.edu>
Support higher-resolution time stamps (Bug#9000).
diff --git a/doc/lispref/commands.texi b/doc/lispref/commands.texi
index 59ad2927411..a5fb4638c9d 100644
--- a/doc/lispref/commands.texi
+++ b/doc/lispref/commands.texi
@@ -1716,6 +1716,38 @@ To test the signal handler, you can make Emacs send a signal to itself:
@smallexample
(signal-process (emacs-pid) 'sigusr1)
@end smallexample
+
+@cindex @code{language-change} event
+@item language-change
+This kind of event is generated on MS-Windows when the input language
+has changed. This typically means that the keyboard keys will send to
+Emacs characters from a different language. The generated event has
+this form:
+
+@smallexample
+(language-change @var{frame} @var{codepage} @var{language-id})
+@end smallexample
+
+@noindent
+Here @var{frame} is the frame which was current when the input
+language changed; @var{codepage} is the new codepage number; and
+@var{language-id} is the numerical ID of the new input language. The
+coding-system (@pxref{Coding Systems}) that corresponds to
+@var{codepage} is @code{cp@var{codepage}} or
+@code{windows-@var{codepage}}. To convert @var{language-id} to a
+string (e.g., to use it for various language-dependent features, such
+as @code{set-language-environment}), use the
+@code{w32-get-locale-info} function, like this:
+
+@smallexample
+;; Get the abbreviated language name, such as "ENU" for English
+(w32-get-locale-info language-id)
+;; Get the full English name of the language,
+;; such as "English (United States)"
+(w32-get-locale-info language-id 4097)
+;; Get the full localized name of the language
+(w32-get-locale-info language-id t)
+@end smallexample
@end table
If one of these events arrives in the middle of a key sequence---that