1 @c -*- mode: texinfo; coding: utf-8 -*-
2 @c This is part of the GNU Emacs Lisp Reference Manual.
3 @c Copyright (C) 1998-1999, 2001-2015 Free Software Foundation, Inc.
4 @c See the file elisp.texi for copying conditions.
5 @node Non-ASCII Characters
6 @chapter Non-@acronym{ASCII} Characters
7 @cindex multibyte characters
8 @cindex characters, multi-byte
9 @cindex non-@acronym{ASCII} characters
11 This chapter covers the special issues relating to characters and
12 how they are stored in strings and buffers.
15 * Text Representations:: How Emacs represents text.
16 * Disabling Multibyte:: Controlling whether to use multibyte characters.
17 * Converting Representations:: Converting unibyte to multibyte and vice versa.
18 * Selecting a Representation:: Treating a byte sequence as unibyte or multi.
19 * Character Codes:: How unibyte and multibyte relate to
20 codes of individual characters.
21 * Character Properties:: Character attributes that define their
22 behavior and handling.
23 * Character Sets:: The space of possible character codes
24 is divided into various character sets.
25 * Scanning Charsets:: Which character sets are used in a buffer?
26 * Translation of Characters:: Translation tables are used for conversion.
27 * Coding Systems:: Coding systems are conversions for saving files.
28 * Input Methods:: Input methods allow users to enter various
29 non-ASCII characters without special keyboards.
30 * Locales:: Interacting with the POSIX locale.
33 @node Text Representations
34 @section Text Representations
35 @cindex text representation
37 Emacs buffers and strings support a large repertoire of characters
38 from many different scripts, allowing users to type and display text
39 in almost any known written language.
41 @cindex character codepoint
44 To support this multitude of characters and scripts, Emacs closely
45 follows the @dfn{Unicode Standard}. The Unicode Standard assigns a
46 unique number, called a @dfn{codepoint}, to each and every character.
47 The range of codepoints defined by Unicode, or the Unicode
48 @dfn{codespace}, is @code{0..#x10FFFF} (in hexadecimal notation),
49 inclusive. Emacs extends this range with codepoints in the range
50 @code{#x110000..#x3FFFFF}, which it uses for representing characters
51 that are not unified with Unicode and @dfn{raw 8-bit bytes} that
52 cannot be interpreted as characters. Thus, a character codepoint in
53 Emacs is a 22-bit integer.
55 @cindex internal representation of characters
56 @cindex characters, representation in buffers and strings
57 @cindex multibyte text
58 To conserve memory, Emacs does not hold fixed-length 22-bit numbers
59 that are codepoints of text characters within buffers and strings.
60 Rather, Emacs uses a variable-length internal representation of
61 characters, that stores each character as a sequence of 1 to 5 8-bit
62 bytes, depending on the magnitude of its codepoint@footnote{
63 This internal representation is based on one of the encodings defined
64 by the Unicode Standard, called @dfn{UTF-8}, for representing any
65 Unicode codepoint, but Emacs extends UTF-8 to represent the additional
66 codepoints it uses for raw 8-bit bytes and characters not unified with
67 Unicode.}. For example, any @acronym{ASCII} character takes up only 1
68 byte, a Latin-1 character takes up 2 bytes, etc. We call this
69 representation of text @dfn{multibyte}.
71 Outside Emacs, characters can be represented in many different
72 encodings, such as ISO-8859-1, GB-2312, Big-5, etc. Emacs converts
73 between these external encodings and its internal representation, as
74 appropriate, when it reads text into a buffer or a string, or when it
75 writes text to a disk file or passes it to some other process.
77 Occasionally, Emacs needs to hold and manipulate encoded text or
78 binary non-text data in its buffers or strings. For example, when
79 Emacs visits a file, it first reads the file's text verbatim into a
80 buffer, and only then converts it to the internal representation.
81 Before the conversion, the buffer holds encoded text.
84 Encoded text is not really text, as far as Emacs is concerned, but
85 rather a sequence of raw 8-bit bytes. We call buffers and strings
86 that hold encoded text @dfn{unibyte} buffers and strings, because
87 Emacs treats them as a sequence of individual bytes. Usually, Emacs
88 displays unibyte buffers and strings as octal codes such as
89 @code{\237}. We recommend that you never use unibyte buffers and
90 strings except for manipulating encoded text or binary non-text data.
92 In a buffer, the buffer-local value of the variable
93 @code{enable-multibyte-characters} specifies the representation used.
94 The representation for a string is determined and recorded in the string
95 when the string is constructed.
97 @defvar enable-multibyte-characters
98 This variable specifies the current buffer's text representation.
99 If it is non-@code{nil}, the buffer contains multibyte text; otherwise,
100 it contains unibyte encoded text or binary non-text data.
102 You cannot set this variable directly; instead, use the function
103 @code{set-buffer-multibyte} to change a buffer's representation.
106 @defun position-bytes position
107 Buffer positions are measured in character units. This function
108 returns the byte-position corresponding to buffer position
109 @var{position} in the current buffer. This is 1 at the start of the
110 buffer, and counts upward in bytes. If @var{position} is out of
111 range, the value is @code{nil}.
114 @defun byte-to-position byte-position
115 Return the buffer position, in character units, corresponding to given
116 @var{byte-position} in the current buffer. If @var{byte-position} is
117 out of range, the value is @code{nil}. In a multibyte buffer, an
118 arbitrary value of @var{byte-position} can be not at character
119 boundary, but inside a multibyte sequence representing a single
120 character; in this case, this function returns the buffer position of
121 the character whose multibyte sequence includes @var{byte-position}.
122 In other words, the value does not change for all byte positions that
123 belong to the same character.
126 @defun multibyte-string-p string
127 Return @code{t} if @var{string} is a multibyte string, @code{nil}
128 otherwise. This function also returns @code{nil} if @var{string} is
129 some object other than a string.
132 @defun string-bytes string
133 @cindex string, number of bytes
134 This function returns the number of bytes in @var{string}.
135 If @var{string} is a multibyte string, this can be greater than
136 @code{(length @var{string})}.
139 @defun unibyte-string &rest bytes
140 This function concatenates all its argument @var{bytes} and makes the
141 result a unibyte string.
144 @node Disabling Multibyte
145 @section Disabling Multibyte Characters
146 @cindex disabling multibyte
148 By default, Emacs starts in multibyte mode: it stores the contents
149 of buffers and strings using an internal encoding that represents
150 non-@acronym{ASCII} characters using multi-byte sequences. Multibyte
151 mode allows you to use all the supported languages and scripts without
154 @cindex turn multibyte support on or off
155 Under very special circumstances, you may want to disable multibyte
156 character support, for a specific buffer.
157 When multibyte characters are disabled in a buffer, we call
158 that @dfn{unibyte mode}. In unibyte mode, each character in the
159 buffer has a character code ranging from 0 through 255 (0377 octal); 0
160 through 127 (0177 octal) represent @acronym{ASCII} characters, and 128
161 (0200 octal) through 255 (0377 octal) represent non-@acronym{ASCII}
164 To edit a particular file in unibyte representation, visit it using
165 @code{find-file-literally}. @xref{Visiting Functions}. You can
166 convert a multibyte buffer to unibyte by saving it to a file, killing
167 the buffer, and visiting the file again with
168 @code{find-file-literally}. Alternatively, you can use @kbd{C-x
169 @key{RET} c} (@code{universal-coding-system-argument}) and specify
170 @samp{raw-text} as the coding system with which to visit or save a
171 file. @xref{Text Coding, , Specifying a Coding System for File Text,
172 emacs, GNU Emacs Manual}. Unlike @code{find-file-literally}, finding
173 a file as @samp{raw-text} doesn't disable format conversion,
174 uncompression, or auto mode selection.
176 @c See http://debbugs.gnu.org/11226 for lack of unibyte tooltip.
177 @vindex enable-multibyte-characters
178 The buffer-local variable @code{enable-multibyte-characters} is
179 non-@code{nil} in multibyte buffers, and @code{nil} in unibyte ones.
180 The mode line also indicates whether a buffer is multibyte or not.
181 With a graphical display, in a multibyte buffer, the portion of the
182 mode line that indicates the character set has a tooltip that (amongst
183 other things) says that the buffer is multibyte. In a unibyte buffer,
184 the character set indicator is absent. Thus, in a unibyte buffer
185 (when using a graphical display) there is normally nothing before the
186 indication of the visited file's end-of-line convention (colon,
187 backslash, etc.), unless you are using an input method.
189 @findex toggle-enable-multibyte-characters
190 You can turn off multibyte support in a specific buffer by invoking the
191 command @code{toggle-enable-multibyte-characters} in that buffer.
193 @node Converting Representations
194 @section Converting Text Representations
196 Emacs can convert unibyte text to multibyte; it can also convert
197 multibyte text to unibyte, provided that the multibyte text contains
198 only @acronym{ASCII} and 8-bit raw bytes. In general, these
199 conversions happen when inserting text into a buffer, or when putting
200 text from several strings together in one string. You can also
201 explicitly convert a string's contents to either representation.
203 Emacs chooses the representation for a string based on the text from
204 which it is constructed. The general rule is to convert unibyte text
205 to multibyte text when combining it with other multibyte text, because
206 the multibyte representation is more general and can hold whatever
207 characters the unibyte text has.
209 When inserting text into a buffer, Emacs converts the text to the
210 buffer's representation, as specified by
211 @code{enable-multibyte-characters} in that buffer. In particular, when
212 you insert multibyte text into a unibyte buffer, Emacs converts the text
213 to unibyte, even though this conversion cannot in general preserve all
214 the characters that might be in the multibyte text. The other natural
215 alternative, to convert the buffer contents to multibyte, is not
216 acceptable because the buffer's representation is a choice made by the
217 user that cannot be overridden automatically.
219 Converting unibyte text to multibyte text leaves @acronym{ASCII}
220 characters unchanged, and converts bytes with codes 128 through 255 to
221 the multibyte representation of raw eight-bit bytes.
223 Converting multibyte text to unibyte converts all @acronym{ASCII}
224 and eight-bit characters to their single-byte form, but loses
225 information for non-@acronym{ASCII} characters by discarding all but
226 the low 8 bits of each character's codepoint. Converting unibyte text
227 to multibyte and back to unibyte reproduces the original unibyte text.
229 The next two functions either return the argument @var{string}, or a
230 newly created string with no text properties.
232 @defun string-to-multibyte string
233 This function returns a multibyte string containing the same sequence
234 of characters as @var{string}. If @var{string} is a multibyte string,
235 it is returned unchanged. The function assumes that @var{string}
236 includes only @acronym{ASCII} characters and raw 8-bit bytes; the
237 latter are converted to their multibyte representation corresponding
238 to the codepoints @code{#x3FFF80} through @code{#x3FFFFF}, inclusive
239 (@pxref{Text Representations, codepoints}).
242 @defun string-to-unibyte string
243 This function returns a unibyte string containing the same sequence of
244 characters as @var{string}. It signals an error if @var{string}
245 contains a non-@acronym{ASCII} character. If @var{string} is a
246 unibyte string, it is returned unchanged. Use this function for
247 @var{string} arguments that contain only @acronym{ASCII} and eight-bit
251 @c FIXME: Should '@var{character}' be '@var{byte}'?
252 @defun byte-to-string byte
253 @cindex byte to string
254 This function returns a unibyte string containing a single byte of
255 character data, @var{character}. It signals an error if
256 @var{character} is not an integer between 0 and 255.
259 @defun multibyte-char-to-unibyte char
260 This converts the multibyte character @var{char} to a unibyte
261 character, and returns that character. If @var{char} is neither
262 @acronym{ASCII} nor eight-bit, the function returns @minus{}1.
265 @defun unibyte-char-to-multibyte char
266 This convert the unibyte character @var{char} to a multibyte
267 character, assuming @var{char} is either @acronym{ASCII} or raw 8-bit
271 @node Selecting a Representation
272 @section Selecting a Representation
274 Sometimes it is useful to examine an existing buffer or string as
275 multibyte when it was unibyte, or vice versa.
277 @defun set-buffer-multibyte multibyte
278 Set the representation type of the current buffer. If @var{multibyte}
279 is non-@code{nil}, the buffer becomes multibyte. If @var{multibyte}
280 is @code{nil}, the buffer becomes unibyte.
282 This function leaves the buffer contents unchanged when viewed as a
283 sequence of bytes. As a consequence, it can change the contents
284 viewed as characters; for instance, a sequence of three bytes which is
285 treated as one character in multibyte representation will count as
286 three characters in unibyte representation. Eight-bit characters
287 representing raw bytes are an exception. They are represented by one
288 byte in a unibyte buffer, but when the buffer is set to multibyte,
289 they are converted to two-byte sequences, and vice versa.
291 This function sets @code{enable-multibyte-characters} to record which
292 representation is in use. It also adjusts various data in the buffer
293 (including overlays, text properties and markers) so that they cover the
294 same text as they did before.
296 This function signals an error if the buffer is narrowed, since the
297 narrowing might have occurred in the middle of multibyte character
300 This function also signals an error if the buffer is an indirect
301 buffer. An indirect buffer always inherits the representation of its
305 @defun string-as-unibyte string
306 If @var{string} is already a unibyte string, this function returns
307 @var{string} itself. Otherwise, it returns a new string with the same
308 bytes as @var{string}, but treating each byte as a separate character
309 (so that the value may have more characters than @var{string}); as an
310 exception, each eight-bit character representing a raw byte is
311 converted into a single byte. The newly-created string contains no
315 @defun string-as-multibyte string
316 If @var{string} is a multibyte string, this function returns
317 @var{string} itself. Otherwise, it returns a new string with the same
318 bytes as @var{string}, but treating each multibyte sequence as one
319 character. This means that the value may have fewer characters than
320 @var{string} has. If a byte sequence in @var{string} is invalid as a
321 multibyte representation of a single character, each byte in the
322 sequence is treated as a raw 8-bit byte. The newly-created string
323 contains no text properties.
326 @node Character Codes
327 @section Character Codes
328 @cindex character codes
330 The unibyte and multibyte text representations use different
331 character codes. The valid character codes for unibyte representation
332 range from 0 to @code{#xFF} (255)---the values that can fit in one
333 byte. The valid character codes for multibyte representation range
334 from 0 to @code{#x3FFFFF}. In this code space, values 0 through
335 @code{#x7F} (127) are for @acronym{ASCII} characters, and values
336 @code{#x80} (128) through @code{#x3FFF7F} (4194175) are for
337 non-@acronym{ASCII} characters.
339 Emacs character codes are a superset of the Unicode standard.
340 Values 0 through @code{#x10FFFF} (1114111) correspond to Unicode
341 characters of the same codepoint; values @code{#x110000} (1114112)
342 through @code{#x3FFF7F} (4194175) represent characters that are not
343 unified with Unicode; and values @code{#x3FFF80} (4194176) through
344 @code{#x3FFFFF} (4194303) represent eight-bit raw bytes.
346 @defun characterp charcode
347 This returns @code{t} if @var{charcode} is a valid character, and
348 @code{nil} otherwise.
366 @cindex maximum value of character codepoint
367 @cindex codepoint, largest value
369 This function returns the largest value that a valid character
374 (characterp (max-char))
378 (characterp (1+ (max-char)))
384 @defun get-byte &optional pos string
385 This function returns the byte at character position @var{pos} in the
386 current buffer. If the current buffer is unibyte, this is literally
387 the byte at that position. If the buffer is multibyte, byte values of
388 @acronym{ASCII} characters are the same as character codepoints,
389 whereas eight-bit raw bytes are converted to their 8-bit codes. The
390 function signals an error if the character at @var{pos} is
393 The optional argument @var{string} means to get a byte value from that
394 string instead of the current buffer.
397 @node Character Properties
398 @section Character Properties
399 @cindex character properties
400 A @dfn{character property} is a named attribute of a character that
401 specifies how the character behaves and how it should be handled
402 during text processing and display. Thus, character properties are an
403 important part of specifying the character's semantics.
405 @c FIXME: Use the latest URI of this chapter?
406 @c http://www.unicode.org/versions/latest/ch04.pdf
407 On the whole, Emacs follows the Unicode Standard in its implementation
408 of character properties. In particular, Emacs supports the
409 @uref{http://www.unicode.org/reports/tr23/, Unicode Character Property
410 Model}, and the Emacs character property database is derived from the
411 Unicode Character Database (@acronym{UCD}). See the
412 @uref{http://www.unicode.org/versions/Unicode6.2.0/ch04.pdf, Character
413 Properties chapter of the Unicode Standard}, for a detailed
414 description of Unicode character properties and their meaning. This
415 section assumes you are already familiar with that chapter of the
416 Unicode Standard, and want to apply that knowledge to Emacs Lisp
419 In Emacs, each property has a name, which is a symbol, and a set of
420 possible values, whose types depend on the property; if a character
421 does not have a certain property, the value is @code{nil}. As a
422 general rule, the names of character properties in Emacs are produced
423 from the corresponding Unicode properties by downcasing them and
424 replacing each @samp{_} character with a dash @samp{-}. For example,
425 @code{Canonical_Combining_Class} becomes
426 @code{canonical-combining-class}. However, sometimes we shorten the
427 names to make their use easier.
429 @cindex unassigned character codepoints
430 Some codepoints are left @dfn{unassigned} by the
431 @acronym{UCD}---they don't correspond to any character. The Unicode
432 Standard defines default values of properties for such codepoints;
433 they are mentioned below for each property.
435 Here is the full list of value types for all the character
436 properties that Emacs knows about:
440 Corresponds to the @code{Name} Unicode property. The value is a
441 string consisting of upper-case Latin letters A to Z, digits, spaces,
442 and hyphen @samp{-} characters. For unassigned codepoints, the value
445 @cindex unicode general category
446 @item general-category
447 Corresponds to the @code{General_Category} Unicode property. The
448 value is a symbol whose name is a 2-letter abbreviation of the
449 character's classification. For unassigned codepoints, the value
452 @item canonical-combining-class
453 Corresponds to the @code{Canonical_Combining_Class} Unicode property.
454 The value is an integer. For unassigned codepoints, the value
457 @cindex bidirectional class of characters
459 Corresponds to the Unicode @code{Bidi_Class} property. The value is a
460 symbol whose name is the Unicode @dfn{directional type} of the
461 character. Emacs uses this property when it reorders bidirectional
462 text for display (@pxref{Bidirectional Display}). For unassigned
463 codepoints, the value depends on the code blocks to which the
464 codepoint belongs: most unassigned codepoints get the value of
465 @code{L} (strong L), but some get values of @code{AL} (Arabic letter)
466 or @code{R} (strong R).
469 Corresponds to the Unicode properties @code{Decomposition_Type} and
470 @code{Decomposition_Value}. The value is a list, whose first element
471 may be a symbol representing a compatibility formatting tag, such as
472 @code{small}@footnote{The Unicode specification writes these tag names
473 inside @samp{<..>} brackets, but the tag names in Emacs do not include
474 the brackets; e.g., Unicode specifies @samp{<small>} where Emacs uses
475 @samp{small}. }; the other elements are characters that give the
476 compatibility decomposition sequence of this character. For
477 unassigned codepoints, the value is the character itself.
479 @item decimal-digit-value
480 Corresponds to the Unicode @code{Numeric_Value} property for
481 characters whose @code{Numeric_Type} is @samp{Decimal}. The value is
482 an integer. For unassigned codepoints, the value is
483 @code{nil}, which means @acronym{NaN}, or ``not-a-number''.
486 Corresponds to the Unicode @code{Numeric_Value} property for
487 characters whose @code{Numeric_Type} is @samp{Digit}. The value is an
488 integer. Examples of such characters include compatibility
489 subscript and superscript digits, for which the value is the
490 corresponding number. For unassigned codepoints, the value is
491 @code{nil}, which means @acronym{NaN}.
494 Corresponds to the Unicode @code{Numeric_Value} property for
495 characters whose @code{Numeric_Type} is @samp{Numeric}. The value of
496 this property is a number. Examples of
497 characters that have this property include fractions, subscripts,
498 superscripts, Roman numerals, currency numerators, and encircled
499 numbers. For example, the value of this property for the character
500 @code{U+2155} (@sc{vulgar fraction one fifth}) is @code{0.2}. For
501 unassigned codepoints, the value is @code{nil}, which means
504 @cindex mirroring of characters
506 Corresponds to the Unicode @code{Bidi_Mirrored} property. The value
507 of this property is a symbol, either @code{Y} or @code{N}. For
508 unassigned codepoints, the value is @code{N}.
511 Corresponds to the Unicode @code{Bidi_Mirroring_Glyph} property. The
512 value of this property is a character whose glyph represents the
513 mirror image of the character's glyph, or @code{nil} if there's no
514 defined mirroring glyph. All the characters whose @code{mirrored}
515 property is @code{N} have @code{nil} as their @code{mirroring}
516 property; however, some characters whose @code{mirrored} property is
517 @code{Y} also have @code{nil} for @code{mirroring}, because no
518 appropriate characters exist with mirrored glyphs. Emacs uses this
519 property to display mirror images of characters when appropriate
520 (@pxref{Bidirectional Display}). For unassigned codepoints, the value
524 Corresponds to the Unicode @code{Bidi_Paired_Bracket} property. The
525 value of this property is the codepoint of a character's @dfn{paired
526 bracket}, or @code{nil} if the character is not a bracket character.
527 This establishes a mapping between characters that are treated as
528 bracket pairs by the Unicode Bidirectional Algorithm; Emacs uses this
529 property when it decides how to reorder for display parentheses,
530 braces, and other similar characters (@pxref{Bidirectional Display}).
533 Corresponds to the Unicode @code{Bidi_Paired_Bracket_Type} property.
534 For characters whose @code{paired-bracket} property is non-@code{nil},
535 the value of this property is a symbol, either @code{o} (for opening
536 bracket characters) or @code{c} (for closing bracket characters). For
537 characters whose @code{paired-bracket} property is @code{nil}, the
538 value is the symbol @code{n} (None). Like @code{paired-bracket}, this
539 property is used for bidirectional display.
542 Corresponds to the Unicode @code{Unicode_1_Name} property. The value
543 is a string. For unassigned codepoints, and characters that have no
544 value for this property, the value is @code{nil}.
546 @item iso-10646-comment
547 Corresponds to the Unicode @code{ISO_Comment} property. The value is
548 a string. For unassigned codepoints, the value is an empty string.
551 Corresponds to the Unicode @code{Simple_Uppercase_Mapping} property.
552 The value of this property is a single character. For unassigned
553 codepoints, the value is @code{nil}, which means the character itself.
556 Corresponds to the Unicode @code{Simple_Lowercase_Mapping} property.
557 The value of this property is a single character. For unassigned
558 codepoints, the value is @code{nil}, which means the character itself.
561 Corresponds to the Unicode @code{Simple_Titlecase_Mapping} property.
562 @dfn{Title case} is a special form of a character used when the first
563 character of a word needs to be capitalized. The value of this
564 property is a single character. For unassigned codepoints, the value
565 is @code{nil}, which means the character itself.
568 @defun get-char-code-property char propname
569 This function returns the value of @var{char}'s @var{propname} property.
573 (get-char-code-property ?\s 'general-category)
577 (get-char-code-property ?1 'general-category)
582 (get-char-code-property ?\u2084 'digit-value)
587 (get-char-code-property ?\u2155 'numeric-value)
592 (get-char-code-property ?\u2163 'numeric-value)
596 (get-char-code-property ?\( 'paired-bracket)
597 @result{} 41 ;; closing parenthesis
600 (get-char-code-property ?\) 'bracket-type)
606 @defun char-code-property-description prop value
607 This function returns the description string of property @var{prop}'s
608 @var{value}, or @code{nil} if @var{value} has no description.
612 (char-code-property-description 'general-category 'Zs)
613 @result{} "Separator, Space"
616 (char-code-property-description 'general-category 'Nd)
617 @result{} "Number, Decimal Digit"
620 (char-code-property-description 'numeric-value '1/5)
626 @defun put-char-code-property char propname value
627 This function stores @var{value} as the value of the property
628 @var{propname} for the character @var{char}.
631 @defvar unicode-category-table
632 The value of this variable is a char-table (@pxref{Char-Tables}) that
633 specifies, for each character, its Unicode @code{General_Category}
634 property as a symbol.
637 @defvar char-script-table
638 @cindex script symbols
639 The value of this variable is a char-table that specifies, for each
640 character, a symbol whose name is the script to which the character
641 belongs, according to the Unicode Standard classification of the
642 Unicode code space into script-specific blocks. This char-table has a
643 single extra slot whose value is the list of all script symbols.
646 @defvar char-width-table
647 The value of this variable is a char-table that specifies the width of
648 each character in columns that it will occupy on the screen.
651 @defvar printable-chars
652 The value of this variable is a char-table that specifies, for each
653 character, whether it is printable or not. That is, if evaluating
654 @code{(aref printable-chars char)} results in @code{t}, the character
655 is printable, and if it results in @code{nil}, it is not.
659 @section Character Sets
660 @cindex character sets
663 @cindex coded character set
664 An Emacs @dfn{character set}, or @dfn{charset}, is a set of characters
665 in which each character is assigned a numeric code point. (The
666 Unicode Standard calls this a @dfn{coded character set}.) Each Emacs
667 charset has a name which is a symbol. A single character can belong
668 to any number of different character sets, but it will generally have
669 a different code point in each charset. Examples of character sets
670 include @code{ascii}, @code{iso-8859-1}, @code{greek-iso8859-7}, and
671 @code{windows-1255}. The code point assigned to a character in a
672 charset is usually different from its code point used in Emacs buffers
675 @cindex @code{emacs}, a charset
676 @cindex @code{unicode}, a charset
677 @cindex @code{eight-bit}, a charset
678 Emacs defines several special character sets. The character set
679 @code{unicode} includes all the characters whose Emacs code points are
680 in the range @code{0..#x10FFFF}. The character set @code{emacs}
681 includes all @acronym{ASCII} and non-@acronym{ASCII} characters.
682 Finally, the @code{eight-bit} charset includes the 8-bit raw bytes;
683 Emacs uses it to represent raw bytes encountered in text.
685 @defun charsetp object
686 Returns @code{t} if @var{object} is a symbol that names a character set,
687 @code{nil} otherwise.
691 The value is a list of all defined character set names.
694 @defun charset-priority-list &optional highestp
695 This function returns a list of all defined character sets ordered by
696 their priority. If @var{highestp} is non-@code{nil}, the function
697 returns a single character set of the highest priority.
700 @defun set-charset-priority &rest charsets
701 This function makes @var{charsets} the highest priority character sets.
704 @defun char-charset character &optional restriction
705 This function returns the name of the character set of highest
706 priority that @var{character} belongs to. @acronym{ASCII} characters
707 are an exception: for them, this function always returns @code{ascii}.
709 If @var{restriction} is non-@code{nil}, it should be a list of
710 charsets to search. Alternatively, it can be a coding system, in
711 which case the returned charset must be supported by that coding
712 system (@pxref{Coding Systems}).
715 @c TODO: Explain the properties here and add indexes such as 'charset property'.
716 @defun charset-plist charset
717 This function returns the property list of the character set
718 @var{charset}. Although @var{charset} is a symbol, this is not the
719 same as the property list of that symbol. Charset properties include
720 important information about the charset, such as its documentation
721 string, short name, etc.
724 @defun put-charset-property charset propname value
725 This function sets the @var{propname} property of @var{charset} to the
729 @defun get-charset-property charset propname
730 This function returns the value of @var{charset}s property
734 @deffn Command list-charset-chars charset
735 This command displays a list of characters in the character set
739 Emacs can convert between its internal representation of a character
740 and the character's codepoint in a specific charset. The following
741 two functions support these conversions.
743 @c FIXME: decode-char and encode-char accept and ignore an additional
744 @c argument @var{restriction}. When that argument actually makes a
745 @c difference, it should be documented here.
746 @defun decode-char charset code-point
747 This function decodes a character that is assigned a @var{code-point}
748 in @var{charset}, to the corresponding Emacs character, and returns
749 it. If @var{charset} doesn't contain a character of that code point,
750 the value is @code{nil}. If @var{code-point} doesn't fit in a Lisp
751 integer (@pxref{Integer Basics, most-positive-fixnum}), it can be
752 specified as a cons cell @code{(@var{high} . @var{low})}, where
753 @var{low} are the lower 16 bits of the value and @var{high} are the
757 @defun encode-char char charset
758 This function returns the code point assigned to the character
759 @var{char} in @var{charset}. If the result does not fit in a Lisp
760 integer, it is returned as a cons cell @code{(@var{high} . @var{low})}
761 that fits the second argument of @code{decode-char} above. If
762 @var{charset} doesn't have a codepoint for @var{char}, the value is
766 The following function comes in handy for applying a certain
767 function to all or part of the characters in a charset:
769 @defun map-charset-chars function charset &optional arg from-code to-code
770 Call @var{function} for characters in @var{charset}. @var{function}
771 is called with two arguments. The first one is a cons cell
772 @code{(@var{from} . @var{to})}, where @var{from} and @var{to}
773 indicate a range of characters contained in charset. The second
774 argument passed to @var{function} is @var{arg}.
776 By default, the range of codepoints passed to @var{function} includes
777 all the characters in @var{charset}, but optional arguments
778 @var{from-code} and @var{to-code} limit that to the range of
779 characters between these two codepoints of @var{charset}. If either
780 of them is @code{nil}, it defaults to the first or last codepoint of
781 @var{charset}, respectively.
784 @node Scanning Charsets
785 @section Scanning for Character Sets
786 @cindex scanning for character sets
787 @cindex character set, searching
789 Sometimes it is useful to find out which character set a particular
790 character belongs to. One use for this is in determining which coding
791 systems (@pxref{Coding Systems}) are capable of representing all of
792 the text in question; another is to determine the font(s) for
793 displaying that text.
795 @defun charset-after &optional pos
796 This function returns the charset of highest priority containing the
797 character at position @var{pos} in the current buffer. If @var{pos}
798 is omitted or @code{nil}, it defaults to the current value of point.
799 If @var{pos} is out of range, the value is @code{nil}.
802 @defun find-charset-region beg end &optional translation
803 This function returns a list of the character sets of highest priority
804 that contain characters in the current buffer between positions
805 @var{beg} and @var{end}.
807 The optional argument @var{translation} specifies a translation table
808 to use for scanning the text (@pxref{Translation of Characters}). If
809 it is non-@code{nil}, then each character in the region is translated
810 through this table, and the value returned describes the translated
811 characters instead of the characters actually in the buffer.
814 @defun find-charset-string string &optional translation
815 This function returns a list of character sets of highest priority
816 that contain characters in @var{string}. It is just like
817 @code{find-charset-region}, except that it applies to the contents of
818 @var{string} instead of part of the current buffer.
821 @node Translation of Characters
822 @section Translation of Characters
823 @cindex character translation tables
824 @cindex translation tables
826 A @dfn{translation table} is a char-table (@pxref{Char-Tables}) that
827 specifies a mapping of characters into characters. These tables are
828 used in encoding and decoding, and for other purposes. Some coding
829 systems specify their own particular translation tables; there are
830 also default translation tables which apply to all other coding
833 A translation table has two extra slots. The first is either
834 @code{nil} or a translation table that performs the reverse
835 translation; the second is the maximum number of characters to look up
836 for translating sequences of characters (see the description of
837 @code{make-translation-table-from-alist} below).
839 @defun make-translation-table &rest translations
840 This function returns a translation table based on the argument
841 @var{translations}. Each element of @var{translations} should be a
842 list of elements of the form @code{(@var{from} . @var{to})}; this says
843 to translate the character @var{from} into @var{to}.
845 The arguments and the forms in each argument are processed in order,
846 and if a previous form already translates @var{to} to some other
847 character, say @var{to-alt}, @var{from} is also translated to
851 During decoding, the translation table's translations are applied to
852 the characters that result from ordinary decoding. If a coding system
853 has the property @code{:decode-translation-table}, that specifies the
854 translation table to use, or a list of translation tables to apply in
855 sequence. (This is a property of the coding system, as returned by
856 @code{coding-system-get}, not a property of the symbol that is the
857 coding system's name. @xref{Coding System Basics,, Basic Concepts of
858 Coding Systems}.) Finally, if
859 @code{standard-translation-table-for-decode} is non-@code{nil}, the
860 resulting characters are translated by that table.
862 During encoding, the translation table's translations are applied to
863 the characters in the buffer, and the result of translation is
864 actually encoded. If a coding system has property
865 @code{:encode-translation-table}, that specifies the translation table
866 to use, or a list of translation tables to apply in sequence. In
867 addition, if the variable @code{standard-translation-table-for-encode}
868 is non-@code{nil}, it specifies the translation table to use for
869 translating the result.
871 @defvar standard-translation-table-for-decode
872 This is the default translation table for decoding. If a coding
873 systems specifies its own translation tables, the table that is the
874 value of this variable, if non-@code{nil}, is applied after them.
877 @defvar standard-translation-table-for-encode
878 This is the default translation table for encoding. If a coding
879 systems specifies its own translation tables, the table that is the
880 value of this variable, if non-@code{nil}, is applied after them.
883 @c FIXME: This variable is obsolete since 23.1. We should mention
884 @c that here or simply remove this defvar. --xfq
885 @defvar translation-table-for-input
886 Self-inserting characters are translated through this translation
887 table before they are inserted. Search commands also translate their
888 input through this table, so they can compare more reliably with
889 what's in the buffer.
891 This variable automatically becomes buffer-local when set.
894 @defun make-translation-table-from-vector vec
895 This function returns a translation table made from @var{vec} that is
896 an array of 256 elements to map bytes (values 0 through #xFF) to
897 characters. Elements may be @code{nil} for untranslated bytes. The
898 returned table has a translation table for reverse mapping in the
899 first extra slot, and the value @code{1} in the second extra slot.
901 This function provides an easy way to make a private coding system
902 that maps each byte to a specific character. You can specify the
903 returned table and the reverse translation table using the properties
904 @code{:decode-translation-table} and @code{:encode-translation-table}
905 respectively in the @var{props} argument to
906 @code{define-coding-system}.
909 @defun make-translation-table-from-alist alist
910 This function is similar to @code{make-translation-table} but returns
911 a complex translation table rather than a simple one-to-one mapping.
912 Each element of @var{alist} is of the form @code{(@var{from}
913 . @var{to})}, where @var{from} and @var{to} are either characters or
914 vectors specifying a sequence of characters. If @var{from} is a
915 character, that character is translated to @var{to} (i.e., to a
916 character or a character sequence). If @var{from} is a vector of
917 characters, that sequence is translated to @var{to}. The returned
918 table has a translation table for reverse mapping in the first extra
919 slot, and the maximum length of all the @var{from} character sequences
920 in the second extra slot.
924 @section Coding Systems
926 @cindex coding system
927 When Emacs reads or writes a file, and when Emacs sends text to a
928 subprocess or receives text from a subprocess, it normally performs
929 character code conversion and end-of-line conversion as specified
930 by a particular @dfn{coding system}.
932 How to define a coding system is an arcane matter, and is not
936 * Coding System Basics:: Basic concepts.
937 * Encoding and I/O:: How file I/O functions handle coding systems.
938 * Lisp and Coding Systems:: Functions to operate on coding system names.
939 * User-Chosen Coding Systems:: Asking the user to choose a coding system.
940 * Default Coding Systems:: Controlling the default choices.
941 * Specifying Coding Systems:: Requesting a particular coding system
942 for a single file operation.
943 * Explicit Encoding:: Encoding or decoding text without doing I/O.
944 * Terminal I/O Encoding:: Use of encoding for terminal I/O.
947 @node Coding System Basics
948 @subsection Basic Concepts of Coding Systems
950 @cindex character code conversion
951 @dfn{Character code conversion} involves conversion between the
952 internal representation of characters used inside Emacs and some other
953 encoding. Emacs supports many different encodings, in that it can
954 convert to and from them. For example, it can convert text to or from
955 encodings such as Latin 1, Latin 2, Latin 3, Latin 4, Latin 5, and
956 several variants of ISO 2022. In some cases, Emacs supports several
957 alternative encodings for the same characters; for example, there are
958 three coding systems for the Cyrillic (Russian) alphabet: ISO,
959 Alternativnyj, and KOI8.
961 Every coding system specifies a particular set of character code
962 conversions, but the coding system @code{undecided} is special: it
963 leaves the choice unspecified, to be chosen heuristically for each
964 file, based on the file's data.
966 In general, a coding system doesn't guarantee roundtrip identity:
967 decoding a byte sequence using coding system, then encoding the
968 resulting text in the same coding system, can produce a different byte
969 sequence. But some coding systems do guarantee that the byte sequence
970 will be the same as what you originally decoded. Here are a few
974 iso-8859-1, utf-8, big5, shift_jis, euc-jp
977 Encoding buffer text and then decoding the result can also fail to
978 reproduce the original text. For instance, if you encode a character
979 with a coding system which does not support that character, the result
980 is unpredictable, and thus decoding it using the same coding system
981 may produce a different text. Currently, Emacs can't report errors
982 that result from encoding unsupported characters.
984 @cindex EOL conversion
985 @cindex end-of-line conversion
986 @cindex line end conversion
987 @dfn{End of line conversion} handles three different conventions
988 used on various systems for representing end of line in files. The
989 Unix convention, used on GNU and Unix systems, is to use the linefeed
990 character (also called newline). The DOS convention, used on
991 MS-Windows and MS-DOS systems, is to use a carriage-return and a
992 linefeed at the end of a line. The Mac convention is to use just
993 carriage-return. (This was the convention used on the Macintosh
994 system prior to OS X.)
996 @cindex base coding system
997 @cindex variant coding system
998 @dfn{Base coding systems} such as @code{latin-1} leave the end-of-line
999 conversion unspecified, to be chosen based on the data. @dfn{Variant
1000 coding systems} such as @code{latin-1-unix}, @code{latin-1-dos} and
1001 @code{latin-1-mac} specify the end-of-line conversion explicitly as
1002 well. Most base coding systems have three corresponding variants whose
1003 names are formed by adding @samp{-unix}, @samp{-dos} and @samp{-mac}.
1005 @vindex raw-text@r{ coding system}
1006 The coding system @code{raw-text} is special in that it prevents
1007 character code conversion, and causes the buffer visited with this
1008 coding system to be a unibyte buffer. For historical reasons, you can
1009 save both unibyte and multibyte text with this coding system. When
1010 you use @code{raw-text} to encode multibyte text, it does perform one
1011 character code conversion: it converts eight-bit characters to their
1012 single-byte external representation. @code{raw-text} does not specify
1013 the end-of-line conversion, allowing that to be determined as usual by
1014 the data, and has the usual three variants which specify the
1015 end-of-line conversion.
1017 @vindex no-conversion@r{ coding system}
1018 @vindex binary@r{ coding system}
1019 @code{no-conversion} (and its alias @code{binary}) is equivalent to
1020 @code{raw-text-unix}: it specifies no conversion of either character
1021 codes or end-of-line.
1023 @vindex emacs-internal@r{ coding system}
1024 @vindex utf-8-emacs@r{ coding system}
1025 The coding system @code{utf-8-emacs} specifies that the data is
1026 represented in the internal Emacs encoding (@pxref{Text
1027 Representations}). This is like @code{raw-text} in that no code
1028 conversion happens, but different in that the result is multibyte
1029 data. The name @code{emacs-internal} is an alias for
1032 @defun coding-system-get coding-system property
1033 This function returns the specified property of the coding system
1034 @var{coding-system}. Most coding system properties exist for internal
1035 purposes, but one that you might find useful is @code{:mime-charset}.
1036 That property's value is the name used in MIME for the character coding
1037 which this coding system can read and write. Examples:
1040 (coding-system-get 'iso-latin-1 :mime-charset)
1041 @result{} iso-8859-1
1042 (coding-system-get 'iso-2022-cn :mime-charset)
1043 @result{} iso-2022-cn
1044 (coding-system-get 'cyrillic-koi8 :mime-charset)
1048 The value of the @code{:mime-charset} property is also defined
1049 as an alias for the coding system.
1052 @cindex alias, for coding systems
1053 @defun coding-system-aliases coding-system
1054 This function returns the list of aliases of @var{coding-system}.
1057 @node Encoding and I/O
1058 @subsection Encoding and I/O
1060 The principal purpose of coding systems is for use in reading and
1061 writing files. The function @code{insert-file-contents} uses a coding
1062 system to decode the file data, and @code{write-region} uses one to
1063 encode the buffer contents.
1065 You can specify the coding system to use either explicitly
1066 (@pxref{Specifying Coding Systems}), or implicitly using a default
1067 mechanism (@pxref{Default Coding Systems}). But these methods may not
1068 completely specify what to do. For example, they may choose a coding
1069 system such as @code{undefined} which leaves the character code
1070 conversion to be determined from the data. In these cases, the I/O
1071 operation finishes the job of choosing a coding system. Very often
1072 you will want to find out afterwards which coding system was chosen.
1074 @defvar buffer-file-coding-system
1075 This buffer-local variable records the coding system used for saving the
1076 buffer and for writing part of the buffer with @code{write-region}. If
1077 the text to be written cannot be safely encoded using the coding system
1078 specified by this variable, these operations select an alternative
1079 encoding by calling the function @code{select-safe-coding-system}
1080 (@pxref{User-Chosen Coding Systems}). If selecting a different encoding
1081 requires to ask the user to specify a coding system,
1082 @code{buffer-file-coding-system} is updated to the newly selected coding
1085 @code{buffer-file-coding-system} does @emph{not} affect sending text
1089 @defvar save-buffer-coding-system
1090 This variable specifies the coding system for saving the buffer (by
1091 overriding @code{buffer-file-coding-system}). Note that it is not used
1092 for @code{write-region}.
1094 When a command to save the buffer starts out to use
1095 @code{buffer-file-coding-system} (or @code{save-buffer-coding-system}),
1096 and that coding system cannot handle
1097 the actual text in the buffer, the command asks the user to choose
1098 another coding system (by calling @code{select-safe-coding-system}).
1099 After that happens, the command also updates
1100 @code{buffer-file-coding-system} to represent the coding system that
1104 @defvar last-coding-system-used
1105 I/O operations for files and subprocesses set this variable to the
1106 coding system name that was used. The explicit encoding and decoding
1107 functions (@pxref{Explicit Encoding}) set it too.
1109 @strong{Warning:} Since receiving subprocess output sets this variable,
1110 it can change whenever Emacs waits; therefore, you should copy the
1111 value shortly after the function call that stores the value you are
1115 The variable @code{selection-coding-system} specifies how to encode
1116 selections for the window system. @xref{Window System Selections}.
1118 @defvar file-name-coding-system
1119 The variable @code{file-name-coding-system} specifies the coding
1120 system to use for encoding file names. Emacs encodes file names using
1121 that coding system for all file operations. If
1122 @code{file-name-coding-system} is @code{nil}, Emacs uses a default
1123 coding system determined by the selected language environment. In the
1124 default language environment, any non-@acronym{ASCII} characters in
1125 file names are not encoded specially; they appear in the file system
1126 using the internal Emacs representation.
1129 @strong{Warning:} if you change @code{file-name-coding-system} (or
1130 the language environment) in the middle of an Emacs session, problems
1131 can result if you have already visited files whose names were encoded
1132 using the earlier coding system and are handled differently under the
1133 new coding system. If you try to save one of these buffers under the
1134 visited file name, saving may use the wrong file name, or it may get
1135 an error. If such a problem happens, use @kbd{C-x C-w} to specify a
1136 new file name for that buffer.
1138 @cindex file-name encoding, MS-Windows
1139 On Windows 2000 and later, Emacs by default uses Unicode APIs to
1140 pass file names to the OS, so the value of
1141 @code{file-name-coding-system} is largely ignored. Lisp applications
1142 that need to encode or decode file names on the Lisp level should use
1143 @code{utf-8} coding-system when @code{system-type} is
1144 @code{windows-nt}; the conversion of UTF-8 encoded file names to the
1145 encoding appropriate for communicating with the OS is performed
1146 internally by Emacs.
1148 @node Lisp and Coding Systems
1149 @subsection Coding Systems in Lisp
1151 Here are the Lisp facilities for working with coding systems:
1153 @cindex list all coding systems
1154 @defun coding-system-list &optional base-only
1155 This function returns a list of all coding system names (symbols). If
1156 @var{base-only} is non-@code{nil}, the value includes only the
1157 base coding systems. Otherwise, it includes alias and variant coding
1161 @defun coding-system-p object
1162 This function returns @code{t} if @var{object} is a coding system
1166 @cindex validity of coding system
1167 @cindex coding system, validity check
1168 @defun check-coding-system coding-system
1169 This function checks the validity of @var{coding-system}. If that is
1170 valid, it returns @var{coding-system}. If @var{coding-system} is
1171 @code{nil}, the function return @code{nil}. For any other values, it
1172 signals an error whose @code{error-symbol} is @code{coding-system-error}
1173 (@pxref{Signaling Errors, signal}).
1176 @cindex eol type of coding system
1177 @defun coding-system-eol-type coding-system
1178 This function returns the type of end-of-line (a.k.a.@: @dfn{eol})
1179 conversion used by @var{coding-system}. If @var{coding-system}
1180 specifies a certain eol conversion, the return value is an integer 0,
1181 1, or 2, standing for @code{unix}, @code{dos}, and @code{mac},
1182 respectively. If @var{coding-system} doesn't specify eol conversion
1183 explicitly, the return value is a vector of coding systems, each one
1184 with one of the possible eol conversion types, like this:
1187 (coding-system-eol-type 'latin-1)
1188 @result{} [latin-1-unix latin-1-dos latin-1-mac]
1192 If this function returns a vector, Emacs will decide, as part of the
1193 text encoding or decoding process, what eol conversion to use. For
1194 decoding, the end-of-line format of the text is auto-detected, and the
1195 eol conversion is set to match it (e.g., DOS-style CRLF format will
1196 imply @code{dos} eol conversion). For encoding, the eol conversion is
1197 taken from the appropriate default coding system (e.g.,
1198 default value of @code{buffer-file-coding-system} for
1199 @code{buffer-file-coding-system}), or from the default eol conversion
1200 appropriate for the underlying platform.
1203 @cindex eol conversion of coding system
1204 @defun coding-system-change-eol-conversion coding-system eol-type
1205 This function returns a coding system which is like @var{coding-system}
1206 except for its eol conversion, which is specified by @code{eol-type}.
1207 @var{eol-type} should be @code{unix}, @code{dos}, @code{mac}, or
1208 @code{nil}. If it is @code{nil}, the returned coding system determines
1209 the end-of-line conversion from the data.
1211 @var{eol-type} may also be 0, 1 or 2, standing for @code{unix},
1212 @code{dos} and @code{mac}, respectively.
1215 @cindex text conversion of coding system
1216 @defun coding-system-change-text-conversion eol-coding text-coding
1217 This function returns a coding system which uses the end-of-line
1218 conversion of @var{eol-coding}, and the text conversion of
1219 @var{text-coding}. If @var{text-coding} is @code{nil}, it returns
1220 @code{undecided}, or one of its variants according to @var{eol-coding}.
1223 @cindex safely encode region
1224 @cindex coding systems for encoding region
1225 @defun find-coding-systems-region from to
1226 This function returns a list of coding systems that could be used to
1227 encode a text between @var{from} and @var{to}. All coding systems in
1228 the list can safely encode any multibyte characters in that portion of
1231 If the text contains no multibyte characters, the function returns the
1232 list @code{(undecided)}.
1235 @cindex safely encode a string
1236 @cindex coding systems for encoding a string
1237 @defun find-coding-systems-string string
1238 This function returns a list of coding systems that could be used to
1239 encode the text of @var{string}. All coding systems in the list can
1240 safely encode any multibyte characters in @var{string}. If the text
1241 contains no multibyte characters, this returns the list
1245 @cindex charset, coding systems to encode
1246 @cindex safely encode characters in a charset
1247 @defun find-coding-systems-for-charsets charsets
1248 This function returns a list of coding systems that could be used to
1249 encode all the character sets in the list @var{charsets}.
1252 @defun check-coding-systems-region start end coding-system-list
1253 This function checks whether coding systems in the list
1254 @code{coding-system-list} can encode all the characters in the region
1255 between @var{start} and @var{end}. If all of the coding systems in
1256 the list can encode the specified text, the function returns
1257 @code{nil}. If some coding systems cannot encode some of the
1258 characters, the value is an alist, each element of which has the form
1259 @code{(@var{coding-system1} @var{pos1} @var{pos2} @dots{})}, meaning
1260 that @var{coding-system1} cannot encode characters at buffer positions
1261 @var{pos1}, @var{pos2}, @enddots{}.
1263 @var{start} may be a string, in which case @var{end} is ignored and
1264 the returned value references string indices instead of buffer
1268 @defun detect-coding-region start end &optional highest
1269 This function chooses a plausible coding system for decoding the text
1270 from @var{start} to @var{end}. This text should be a byte sequence,
1271 i.e., unibyte text or multibyte text with only @acronym{ASCII} and
1272 eight-bit characters (@pxref{Explicit Encoding}).
1274 Normally this function returns a list of coding systems that could
1275 handle decoding the text that was scanned. They are listed in order of
1276 decreasing priority. But if @var{highest} is non-@code{nil}, then the
1277 return value is just one coding system, the one that is highest in
1280 If the region contains only @acronym{ASCII} characters except for such
1281 ISO-2022 control characters ISO-2022 as @code{ESC}, the value is
1282 @code{undecided} or @code{(undecided)}, or a variant specifying
1283 end-of-line conversion, if that can be deduced from the text.
1285 If the region contains null bytes, the value is @code{no-conversion},
1286 even if the region contains text encoded in some coding system.
1289 @defun detect-coding-string string &optional highest
1290 This function is like @code{detect-coding-region} except that it
1291 operates on the contents of @var{string} instead of bytes in the buffer.
1294 @cindex null bytes, and decoding text
1295 @defvar inhibit-null-byte-detection
1296 If this variable has a non-@code{nil} value, null bytes are ignored
1297 when detecting the encoding of a region or a string. This allows to
1298 correctly detect the encoding of text that contains null bytes, such
1299 as Info files with Index nodes.
1302 @defvar inhibit-iso-escape-detection
1303 If this variable has a non-@code{nil} value, ISO-2022 escape sequences
1304 are ignored when detecting the encoding of a region or a string. The
1305 result is that no text is ever detected as encoded in some ISO-2022
1306 encoding, and all escape sequences become visible in a buffer.
1307 @strong{Warning:} @emph{Use this variable with extreme caution,
1308 because many files in the Emacs distribution use ISO-2022 encoding.}
1311 @cindex charsets supported by a coding system
1312 @defun coding-system-charset-list coding-system
1313 This function returns the list of character sets (@pxref{Character
1314 Sets}) supported by @var{coding-system}. Some coding systems that
1315 support too many character sets to list them all yield special values:
1318 If @var{coding-system} supports all Emacs characters, the value is
1321 If @var{coding-system} supports all Unicode characters, the value is
1324 If @var{coding-system} supports all ISO-2022 charsets, the value is
1327 If @var{coding-system} supports all the characters in the internal
1328 coding system used by Emacs version 21 (prior to the implementation of
1329 internal Unicode support), the value is @code{emacs-mule}.
1333 @xref{Coding systems for a subprocess,, Process Information}, in
1334 particular the description of the functions
1335 @code{process-coding-system} and @code{set-process-coding-system}, for
1336 how to examine or set the coding systems used for I/O to a subprocess.
1338 @node User-Chosen Coding Systems
1339 @subsection User-Chosen Coding Systems
1341 @cindex select safe coding system
1342 @defun select-safe-coding-system from to &optional default-coding-system accept-default-p file
1343 This function selects a coding system for encoding specified text,
1344 asking the user to choose if necessary. Normally the specified text
1345 is the text in the current buffer between @var{from} and @var{to}. If
1346 @var{from} is a string, the string specifies the text to encode, and
1347 @var{to} is ignored.
1349 If the specified text includes raw bytes (@pxref{Text
1350 Representations}), @code{select-safe-coding-system} suggests
1351 @code{raw-text} for its encoding.
1353 If @var{default-coding-system} is non-@code{nil}, that is the first
1354 coding system to try; if that can handle the text,
1355 @code{select-safe-coding-system} returns that coding system. It can
1356 also be a list of coding systems; then the function tries each of them
1357 one by one. After trying all of them, it next tries the current
1358 buffer's value of @code{buffer-file-coding-system} (if it is not
1359 @code{undecided}), then the default value of
1360 @code{buffer-file-coding-system} and finally the user's most
1361 preferred coding system, which the user can set using the command
1362 @code{prefer-coding-system} (@pxref{Recognize Coding,, Recognizing
1363 Coding Systems, emacs, The GNU Emacs Manual}).
1365 If one of those coding systems can safely encode all the specified
1366 text, @code{select-safe-coding-system} chooses it and returns it.
1367 Otherwise, it asks the user to choose from a list of coding systems
1368 which can encode all the text, and returns the user's choice.
1370 @var{default-coding-system} can also be a list whose first element is
1371 t and whose other elements are coding systems. Then, if no coding
1372 system in the list can handle the text, @code{select-safe-coding-system}
1373 queries the user immediately, without trying any of the three
1374 alternatives described above.
1376 The optional argument @var{accept-default-p}, if non-@code{nil},
1377 should be a function to determine whether a coding system selected
1378 without user interaction is acceptable. @code{select-safe-coding-system}
1379 calls this function with one argument, the base coding system of the
1380 selected coding system. If @var{accept-default-p} returns @code{nil},
1381 @code{select-safe-coding-system} rejects the silently selected coding
1382 system, and asks the user to select a coding system from a list of
1383 possible candidates.
1385 @vindex select-safe-coding-system-accept-default-p
1386 If the variable @code{select-safe-coding-system-accept-default-p} is
1387 non-@code{nil}, it should be a function taking a single argument.
1388 It is used in place of @var{accept-default-p}, overriding any
1389 value supplied for this argument.
1391 As a final step, before returning the chosen coding system,
1392 @code{select-safe-coding-system} checks whether that coding system is
1393 consistent with what would be selected if the contents of the region
1394 were read from a file. (If not, this could lead to data corruption in
1395 a file subsequently re-visited and edited.) Normally,
1396 @code{select-safe-coding-system} uses @code{buffer-file-name} as the
1397 file for this purpose, but if @var{file} is non-@code{nil}, it uses
1398 that file instead (this can be relevant for @code{write-region} and
1399 similar functions). If it detects an apparent inconsistency,
1400 @code{select-safe-coding-system} queries the user before selecting the
1404 Here are two functions you can use to let the user specify a coding
1405 system, with completion. @xref{Completion}.
1407 @defun read-coding-system prompt &optional default
1408 This function reads a coding system using the minibuffer, prompting with
1409 string @var{prompt}, and returns the coding system name as a symbol. If
1410 the user enters null input, @var{default} specifies which coding system
1411 to return. It should be a symbol or a string.
1414 @defun read-non-nil-coding-system prompt
1415 This function reads a coding system using the minibuffer, prompting with
1416 string @var{prompt}, and returns the coding system name as a symbol. If
1417 the user tries to enter null input, it asks the user to try again.
1418 @xref{Coding Systems}.
1421 @node Default Coding Systems
1422 @subsection Default Coding Systems
1423 @cindex default coding system
1424 @cindex coding system, automatically determined
1426 This section describes variables that specify the default coding
1427 system for certain files or when running certain subprograms, and the
1428 function that I/O operations use to access them.
1430 The idea of these variables is that you set them once and for all to the
1431 defaults you want, and then do not change them again. To specify a
1432 particular coding system for a particular operation in a Lisp program,
1433 don't change these variables; instead, override them using
1434 @code{coding-system-for-read} and @code{coding-system-for-write}
1435 (@pxref{Specifying Coding Systems}).
1437 @cindex file contents, and default coding system
1438 @defopt auto-coding-regexp-alist
1439 This variable is an alist of text patterns and corresponding coding
1440 systems. Each element has the form @code{(@var{regexp}
1441 . @var{coding-system})}; a file whose first few kilobytes match
1442 @var{regexp} is decoded with @var{coding-system} when its contents are
1443 read into a buffer. The settings in this alist take priority over
1444 @code{coding:} tags in the files and the contents of
1445 @code{file-coding-system-alist} (see below). The default value is set
1446 so that Emacs automatically recognizes mail files in Babyl format and
1447 reads them with no code conversions.
1450 @cindex file name, and default coding system
1451 @defopt file-coding-system-alist
1452 This variable is an alist that specifies the coding systems to use for
1453 reading and writing particular files. Each element has the form
1454 @code{(@var{pattern} . @var{coding})}, where @var{pattern} is a regular
1455 expression that matches certain file names. The element applies to file
1456 names that match @var{pattern}.
1458 The @sc{cdr} of the element, @var{coding}, should be either a coding
1459 system, a cons cell containing two coding systems, or a function name (a
1460 symbol with a function definition). If @var{coding} is a coding system,
1461 that coding system is used for both reading the file and writing it. If
1462 @var{coding} is a cons cell containing two coding systems, its @sc{car}
1463 specifies the coding system for decoding, and its @sc{cdr} specifies the
1464 coding system for encoding.
1466 If @var{coding} is a function name, the function should take one
1467 argument, a list of all arguments passed to
1468 @code{find-operation-coding-system}. It must return a coding system
1469 or a cons cell containing two coding systems. This value has the same
1470 meaning as described above.
1472 If @var{coding} (or what returned by the above function) is
1473 @code{undecided}, the normal code-detection is performed.
1476 @defopt auto-coding-alist
1477 This variable is an alist that specifies the coding systems to use for
1478 reading and writing particular files. Its form is like that of
1479 @code{file-coding-system-alist}, but, unlike the latter, this variable
1480 takes priority over any @code{coding:} tags in the file.
1483 @cindex program name, and default coding system
1484 @defvar process-coding-system-alist
1485 This variable is an alist specifying which coding systems to use for a
1486 subprocess, depending on which program is running in the subprocess. It
1487 works like @code{file-coding-system-alist}, except that @var{pattern} is
1488 matched against the program name used to start the subprocess. The coding
1489 system or systems specified in this alist are used to initialize the
1490 coding systems used for I/O to the subprocess, but you can specify
1491 other coding systems later using @code{set-process-coding-system}.
1494 @strong{Warning:} Coding systems such as @code{undecided}, which
1495 determine the coding system from the data, do not work entirely reliably
1496 with asynchronous subprocess output. This is because Emacs handles
1497 asynchronous subprocess output in batches, as it arrives. If the coding
1498 system leaves the character code conversion unspecified, or leaves the
1499 end-of-line conversion unspecified, Emacs must try to detect the proper
1500 conversion from one batch at a time, and this does not always work.
1502 Therefore, with an asynchronous subprocess, if at all possible, use a
1503 coding system which determines both the character code conversion and
1504 the end of line conversion---that is, one like @code{latin-1-unix},
1505 rather than @code{undecided} or @code{latin-1}.
1507 @cindex port number, and default coding system
1508 @cindex network service name, and default coding system
1509 @defvar network-coding-system-alist
1510 This variable is an alist that specifies the coding system to use for
1511 network streams. It works much like @code{file-coding-system-alist},
1512 with the difference that the @var{pattern} in an element may be either a
1513 port number or a regular expression. If it is a regular expression, it
1514 is matched against the network service name used to open the network
1518 @defvar default-process-coding-system
1519 This variable specifies the coding systems to use for subprocess (and
1520 network stream) input and output, when nothing else specifies what to
1523 The value should be a cons cell of the form @code{(@var{input-coding}
1524 . @var{output-coding})}. Here @var{input-coding} applies to input from
1525 the subprocess, and @var{output-coding} applies to output to it.
1528 @cindex default coding system, functions to determine
1529 @defopt auto-coding-functions
1530 This variable holds a list of functions that try to determine a
1531 coding system for a file based on its undecoded contents.
1533 Each function in this list should be written to look at text in the
1534 current buffer, but should not modify it in any way. The buffer will
1535 contain undecoded text of parts of the file. Each function should
1536 take one argument, @var{size}, which tells it how many characters to
1537 look at, starting from point. If the function succeeds in determining
1538 a coding system for the file, it should return that coding system.
1539 Otherwise, it should return @code{nil}.
1541 If a file has a @samp{coding:} tag, that takes precedence, so these
1542 functions won't be called.
1545 @defun find-auto-coding filename size
1546 This function tries to determine a suitable coding system for
1547 @var{filename}. It examines the buffer visiting the named file, using
1548 the variables documented above in sequence, until it finds a match for
1549 one of the rules specified by these variables. It then returns a cons
1550 cell of the form @code{(@var{coding} . @var{source})}, where
1551 @var{coding} is the coding system to use and @var{source} is a symbol,
1552 one of @code{auto-coding-alist}, @code{auto-coding-regexp-alist},
1553 @code{:coding}, or @code{auto-coding-functions}, indicating which one
1554 supplied the matching rule. The value @code{:coding} means the coding
1555 system was specified by the @code{coding:} tag in the file
1556 (@pxref{Specify Coding,, coding tag, emacs, The GNU Emacs Manual}).
1557 The order of looking for a matching rule is @code{auto-coding-alist}
1558 first, then @code{auto-coding-regexp-alist}, then the @code{coding:}
1559 tag, and lastly @code{auto-coding-functions}. If no matching rule was
1560 found, the function returns @code{nil}.
1562 The second argument @var{size} is the size of text, in characters,
1563 following point. The function examines text only within @var{size}
1564 characters after point. Normally, the buffer should be positioned at
1565 the beginning when this function is called, because one of the places
1566 for the @code{coding:} tag is the first one or two lines of the file;
1567 in that case, @var{size} should be the size of the buffer.
1570 @defun set-auto-coding filename size
1571 This function returns a suitable coding system for file
1572 @var{filename}. It uses @code{find-auto-coding} to find the coding
1573 system. If no coding system could be determined, the function returns
1574 @code{nil}. The meaning of the argument @var{size} is like in
1575 @code{find-auto-coding}.
1578 @defun find-operation-coding-system operation &rest arguments
1579 This function returns the coding system to use (by default) for
1580 performing @var{operation} with @var{arguments}. The value has this
1584 (@var{decoding-system} . @var{encoding-system})
1587 The first element, @var{decoding-system}, is the coding system to use
1588 for decoding (in case @var{operation} does decoding), and
1589 @var{encoding-system} is the coding system for encoding (in case
1590 @var{operation} does encoding).
1592 The argument @var{operation} is a symbol; it should be one of
1593 @code{write-region}, @code{start-process}, @code{call-process},
1594 @code{call-process-region}, @code{insert-file-contents}, or
1595 @code{open-network-stream}. These are the names of the Emacs I/O
1596 primitives that can do character code and eol conversion.
1598 The remaining arguments should be the same arguments that might be given
1599 to the corresponding I/O primitive. Depending on the primitive, one
1600 of those arguments is selected as the @dfn{target}. For example, if
1601 @var{operation} does file I/O, whichever argument specifies the file
1602 name is the target. For subprocess primitives, the process name is the
1603 target. For @code{open-network-stream}, the target is the service name
1606 Depending on @var{operation}, this function looks up the target in
1607 @code{file-coding-system-alist}, @code{process-coding-system-alist},
1608 or @code{network-coding-system-alist}. If the target is found in the
1609 alist, @code{find-operation-coding-system} returns its association in
1610 the alist; otherwise it returns @code{nil}.
1612 If @var{operation} is @code{insert-file-contents}, the argument
1613 corresponding to the target may be a cons cell of the form
1614 @code{(@var{filename} . @var{buffer})}. In that case, @var{filename}
1615 is a file name to look up in @code{file-coding-system-alist}, and
1616 @var{buffer} is a buffer that contains the file's contents (not yet
1617 decoded). If @code{file-coding-system-alist} specifies a function to
1618 call for this file, and that function needs to examine the file's
1619 contents (as it usually does), it should examine the contents of
1620 @var{buffer} instead of reading the file.
1623 @node Specifying Coding Systems
1624 @subsection Specifying a Coding System for One Operation
1625 @cindex specify coding system
1626 @cindex force coding system for operation
1627 @cindex coding system for operation
1629 You can specify the coding system for a specific operation by binding
1630 the variables @code{coding-system-for-read} and/or
1631 @code{coding-system-for-write}.
1633 @defvar coding-system-for-read
1634 If this variable is non-@code{nil}, it specifies the coding system to
1635 use for reading a file, or for input from a synchronous subprocess.
1637 It also applies to any asynchronous subprocess or network stream, but in
1638 a different way: the value of @code{coding-system-for-read} when you
1639 start the subprocess or open the network stream specifies the input
1640 decoding method for that subprocess or network stream. It remains in
1641 use for that subprocess or network stream unless and until overridden.
1643 The right way to use this variable is to bind it with @code{let} for a
1644 specific I/O operation. Its global value is normally @code{nil}, and
1645 you should not globally set it to any other value. Here is an example
1646 of the right way to use the variable:
1649 ;; @r{Read the file with no character code conversion.}
1650 (let ((coding-system-for-read 'no-conversion))
1651 (insert-file-contents filename))
1654 When its value is non-@code{nil}, this variable takes precedence over
1655 all other methods of specifying a coding system to use for input,
1656 including @code{file-coding-system-alist},
1657 @code{process-coding-system-alist} and
1658 @code{network-coding-system-alist}.
1661 @defvar coding-system-for-write
1662 This works much like @code{coding-system-for-read}, except that it
1663 applies to output rather than input. It affects writing to files,
1664 as well as sending output to subprocesses and net connections.
1666 When a single operation does both input and output, as do
1667 @code{call-process-region} and @code{start-process}, both
1668 @code{coding-system-for-read} and @code{coding-system-for-write}
1672 @defopt inhibit-eol-conversion
1673 When this variable is non-@code{nil}, no end-of-line conversion is done,
1674 no matter which coding system is specified. This applies to all the
1675 Emacs I/O and subprocess primitives, and to the explicit encoding and
1676 decoding functions (@pxref{Explicit Encoding}).
1679 @cindex priority order of coding systems
1680 @cindex coding systems, priority
1681 Sometimes, you need to prefer several coding systems for some
1682 operation, rather than fix a single one. Emacs lets you specify a
1683 priority order for using coding systems. This ordering affects the
1684 sorting of lists of coding systems returned by functions such as
1685 @code{find-coding-systems-region} (@pxref{Lisp and Coding Systems}).
1687 @defun coding-system-priority-list &optional highestp
1688 This function returns the list of coding systems in the order of their
1689 current priorities. Optional argument @var{highestp}, if
1690 non-@code{nil}, means return only the highest priority coding system.
1693 @defun set-coding-system-priority &rest coding-systems
1694 This function puts @var{coding-systems} at the beginning of the
1695 priority list for coding systems, thus making their priority higher
1699 @defmac with-coding-priority coding-systems &rest body@dots{}
1700 This macro execute @var{body}, like @code{progn} does
1701 (@pxref{Sequencing, progn}), with @var{coding-systems} at the front of
1702 the priority list for coding systems. @var{coding-systems} should be
1703 a list of coding systems to prefer during execution of @var{body}.
1706 @node Explicit Encoding
1707 @subsection Explicit Encoding and Decoding
1708 @cindex encoding in coding systems
1709 @cindex decoding in coding systems
1711 All the operations that transfer text in and out of Emacs have the
1712 ability to use a coding system to encode or decode the text.
1713 You can also explicitly encode and decode text using the functions
1716 The result of encoding, and the input to decoding, are not ordinary
1717 text. They logically consist of a series of byte values; that is, a
1718 series of @acronym{ASCII} and eight-bit characters. In unibyte
1719 buffers and strings, these characters have codes in the range 0
1720 through #xFF (255). In a multibyte buffer or string, eight-bit
1721 characters have character codes higher than #xFF (@pxref{Text
1722 Representations}), but Emacs transparently converts them to their
1723 single-byte values when you encode or decode such text.
1725 The usual way to read a file into a buffer as a sequence of bytes, so
1726 you can decode the contents explicitly, is with
1727 @code{insert-file-contents-literally} (@pxref{Reading from Files});
1728 alternatively, specify a non-@code{nil} @var{rawfile} argument when
1729 visiting a file with @code{find-file-noselect}. These methods result in
1732 The usual way to use the byte sequence that results from explicitly
1733 encoding text is to copy it to a file or process---for example, to write
1734 it with @code{write-region} (@pxref{Writing to Files}), and suppress
1735 encoding by binding @code{coding-system-for-write} to
1736 @code{no-conversion}.
1738 Here are the functions to perform explicit encoding or decoding. The
1739 encoding functions produce sequences of bytes; the decoding functions
1740 are meant to operate on sequences of bytes. All of these functions
1741 discard text properties. They also set @code{last-coding-system-used}
1742 to the precise coding system they used.
1744 @deffn Command encode-coding-region start end coding-system &optional destination
1745 This command encodes the text from @var{start} to @var{end} according
1746 to coding system @var{coding-system}. Normally, the encoded text
1747 replaces the original text in the buffer, but the optional argument
1748 @var{destination} can change that. If @var{destination} is a buffer,
1749 the encoded text is inserted in that buffer after point (point does
1750 not move); if it is @code{t}, the command returns the encoded text as
1751 a unibyte string without inserting it.
1753 If encoded text is inserted in some buffer, this command returns the
1754 length of the encoded text.
1756 The result of encoding is logically a sequence of bytes, but the
1757 buffer remains multibyte if it was multibyte before, and any 8-bit
1758 bytes are converted to their multibyte representation (@pxref{Text
1761 @cindex @code{undecided} coding-system, when encoding
1762 Do @emph{not} use @code{undecided} for @var{coding-system} when
1763 encoding text, since that may lead to unexpected results. Instead,
1764 use @code{select-safe-coding-system} (@pxref{User-Chosen Coding
1765 Systems, select-safe-coding-system}) to suggest a suitable encoding,
1766 if there's no obvious pertinent value for @var{coding-system}.
1769 @defun encode-coding-string string coding-system &optional nocopy buffer
1770 This function encodes the text in @var{string} according to coding
1771 system @var{coding-system}. It returns a new string containing the
1772 encoded text, except when @var{nocopy} is non-@code{nil}, in which
1773 case the function may return @var{string} itself if the encoding
1774 operation is trivial. The result of encoding is a unibyte string.
1777 @deffn Command decode-coding-region start end coding-system &optional destination
1778 This command decodes the text from @var{start} to @var{end} according
1779 to coding system @var{coding-system}. To make explicit decoding
1780 useful, the text before decoding ought to be a sequence of byte
1781 values, but both multibyte and unibyte buffers are acceptable (in the
1782 multibyte case, the raw byte values should be represented as eight-bit
1783 characters). Normally, the decoded text replaces the original text in
1784 the buffer, but the optional argument @var{destination} can change
1785 that. If @var{destination} is a buffer, the decoded text is inserted
1786 in that buffer after point (point does not move); if it is @code{t},
1787 the command returns the decoded text as a multibyte string without
1790 If decoded text is inserted in some buffer, this command returns the
1791 length of the decoded text.
1793 This command puts a @code{charset} text property on the decoded text.
1794 The value of the property states the character set used to decode the
1798 @defun decode-coding-string string coding-system &optional nocopy buffer
1799 This function decodes the text in @var{string} according to
1800 @var{coding-system}. It returns a new string containing the decoded
1801 text, except when @var{nocopy} is non-@code{nil}, in which case the
1802 function may return @var{string} itself if the decoding operation is
1803 trivial. To make explicit decoding useful, the contents of
1804 @var{string} ought to be a unibyte string with a sequence of byte
1805 values, but a multibyte string is also acceptable (assuming it
1806 contains 8-bit bytes in their multibyte form).
1808 If optional argument @var{buffer} specifies a buffer, the decoded text
1809 is inserted in that buffer after point (point does not move). In this
1810 case, the return value is the length of the decoded text.
1812 @cindex @code{charset}, text property
1813 This function puts a @code{charset} text property on the decoded text.
1814 The value of the property states the character set used to decode the
1819 (decode-coding-string "Gr\374ss Gott" 'latin-1)
1820 @result{} #("GrĂ¼ss Gott" 0 9 (charset iso-8859-1))
1825 @defun decode-coding-inserted-region from to filename &optional visit beg end replace
1826 This function decodes the text from @var{from} to @var{to} as if
1827 it were being read from file @var{filename} using @code{insert-file-contents}
1828 using the rest of the arguments provided.
1830 The normal way to use this function is after reading text from a file
1831 without decoding, if you decide you would rather have decoded it.
1832 Instead of deleting the text and reading it again, this time with
1833 decoding, you can call this function.
1836 @node Terminal I/O Encoding
1837 @subsection Terminal I/O Encoding
1839 Emacs can use coding systems to decode keyboard input and encode
1840 terminal output. This is useful for terminals that transmit or
1841 display text using a particular encoding, such as Latin-1. Emacs does
1842 not set @code{last-coding-system-used} when encoding or decoding
1845 @defun keyboard-coding-system &optional terminal
1846 This function returns the coding system used for decoding keyboard
1847 input from @var{terminal}. A value of @code{no-conversion} means no
1848 decoding is done. If @var{terminal} is omitted or @code{nil}, it
1849 means the selected frame's terminal. @xref{Multiple Terminals}.
1852 @deffn Command set-keyboard-coding-system coding-system &optional terminal
1853 This command specifies @var{coding-system} as the coding system to use
1854 for decoding keyboard input from @var{terminal}. If
1855 @var{coding-system} is @code{nil}, that means not to decode keyboard
1856 input. If @var{terminal} is a frame, it means that frame's terminal;
1857 if it is @code{nil}, that means the currently selected frame's
1858 terminal. @xref{Multiple Terminals}.
1861 @defun terminal-coding-system &optional terminal
1862 This function returns the coding system that is in use for encoding
1863 terminal output from @var{terminal}. A value of @code{no-conversion}
1864 means no encoding is done. If @var{terminal} is a frame, it means
1865 that frame's terminal; if it is @code{nil}, that means the currently
1866 selected frame's terminal.
1869 @deffn Command set-terminal-coding-system coding-system &optional terminal
1870 This command specifies @var{coding-system} as the coding system to use
1871 for encoding terminal output from @var{terminal}. If
1872 @var{coding-system} is @code{nil}, that means not to encode terminal
1873 output. If @var{terminal} is a frame, it means that frame's terminal;
1874 if it is @code{nil}, that means the currently selected frame's
1879 @section Input Methods
1880 @cindex input methods
1882 @dfn{Input methods} provide convenient ways of entering non-@acronym{ASCII}
1883 characters from the keyboard. Unlike coding systems, which translate
1884 non-@acronym{ASCII} characters to and from encodings meant to be read by
1885 programs, input methods provide human-friendly commands. (@xref{Input
1886 Methods,,, emacs, The GNU Emacs Manual}, for information on how users
1887 use input methods to enter text.) How to define input methods is not
1888 yet documented in this manual, but here we describe how to use them.
1890 Each input method has a name, which is currently a string;
1891 in the future, symbols may also be usable as input method names.
1893 @defvar current-input-method
1894 This variable holds the name of the input method now active in the
1895 current buffer. (It automatically becomes local in each buffer when set
1896 in any fashion.) It is @code{nil} if no input method is active in the
1900 @defopt default-input-method
1901 This variable holds the default input method for commands that choose an
1902 input method. Unlike @code{current-input-method}, this variable is
1906 @deffn Command set-input-method input-method
1907 This command activates input method @var{input-method} for the current
1908 buffer. It also sets @code{default-input-method} to @var{input-method}.
1909 If @var{input-method} is @code{nil}, this command deactivates any input
1910 method for the current buffer.
1913 @defun read-input-method-name prompt &optional default inhibit-null
1914 This function reads an input method name with the minibuffer, prompting
1915 with @var{prompt}. If @var{default} is non-@code{nil}, that is returned
1916 by default, if the user enters empty input. However, if
1917 @var{inhibit-null} is non-@code{nil}, empty input signals an error.
1919 The returned value is a string.
1922 @defvar input-method-alist
1923 This variable defines all the supported input methods.
1924 Each element defines one input method, and should have the form:
1927 (@var{input-method} @var{language-env} @var{activate-func}
1928 @var{title} @var{description} @var{args}...)
1931 Here @var{input-method} is the input method name, a string;
1932 @var{language-env} is another string, the name of the language
1933 environment this input method is recommended for. (That serves only for
1934 documentation purposes.)
1936 @var{activate-func} is a function to call to activate this method. The
1937 @var{args}, if any, are passed as arguments to @var{activate-func}. All
1938 told, the arguments to @var{activate-func} are @var{input-method} and
1941 @var{title} is a string to display in the mode line while this method is
1942 active. @var{description} is a string describing this method and what
1946 The fundamental interface to input methods is through the
1947 variable @code{input-method-function}. @xref{Reading One Event},
1948 and @ref{Invoking the Input Method}.
1954 POSIX defines a concept of ``locales'' which control which language
1955 to use in language-related features. These Emacs variables control
1956 how Emacs interacts with these features.
1958 @defvar locale-coding-system
1959 @cindex keyboard input decoding on X
1960 This variable specifies the coding system to use for decoding system
1961 error messages and---on X Window system only---keyboard input, for
1962 sending batch output to the standard output and error streams, for
1963 encoding the format argument to @code{format-time-string}, and for
1964 decoding the return value of @code{format-time-string}.
1967 @defvar system-messages-locale
1968 This variable specifies the locale to use for generating system error
1969 messages. Changing the locale can cause messages to come out in a
1970 different language or in a different orthography. If the variable is
1971 @code{nil}, the locale is specified by environment variables in the
1972 usual POSIX fashion.
1975 @defvar system-time-locale
1976 This variable specifies the locale to use for formatting time values.
1977 Changing the locale can cause messages to appear according to the
1978 conventions of a different language. If the variable is @code{nil}, the
1979 locale is specified by environment variables in the usual POSIX fashion.
1982 @defun locale-info item
1983 This function returns locale data @var{item} for the current POSIX
1984 locale, if available. @var{item} should be one of these symbols:
1988 Return the character set as a string (locale item @code{CODESET}).
1991 Return a 7-element vector of day names (locale items
1992 @code{DAY_1} through @code{DAY_7});
1995 Return a 12-element vector of month names (locale items @code{MON_1}
1996 through @code{MON_12}).
1999 Return a list @code{(@var{width} @var{height})} for the default paper
2000 size measured in millimeters (locale items @code{PAPER_WIDTH} and
2001 @code{PAPER_HEIGHT}).
2004 If the system can't provide the requested information, or if
2005 @var{item} is not one of those symbols, the value is @code{nil}. All
2006 strings in the return value are decoded using
2007 @code{locale-coding-system}. @xref{Locales,,, libc, The GNU Libc Manual},
2008 for more information about locales and locale items.