2 @c This is part of the GNU Emacs Lisp Reference Manual.
3 @c Copyright (C) 1990, 1991, 1992, 1993, 1994, 1995, 1998, 1999
4 @c Free Software Foundation, Inc.
5 @c See the file elisp.texi for copying conditions.
6 @setfilename ../info/strings
7 @node Strings and Characters, Lists, Numbers, Top
8 @comment node-name, next, previous, up
9 @chapter Strings and Characters
11 @cindex character arrays
15 A string in Emacs Lisp is an array that contains an ordered sequence
16 of characters. Strings are used as names of symbols, buffers, and
17 files; to send messages to users; to hold text being copied between
18 buffers; and for many other purposes. Because strings are so important,
19 Emacs Lisp has many functions expressly for manipulating them. Emacs
20 Lisp programs use strings more often than individual characters.
22 @xref{Strings of Events}, for special considerations for strings of
23 keyboard character events.
26 * Basics: String Basics. Basic properties of strings and characters.
27 * Predicates for Strings:: Testing whether an object is a string or char.
28 * Creating Strings:: Functions to allocate new strings.
29 * Modifying Strings:: Altering the contents of an existing string.
30 * Text Comparison:: Comparing characters or strings.
31 * String Conversion:: Converting to and from characters and strings.
32 * Formatting Strings:: @code{format}: Emacs's analogue of @code{printf}.
33 * Case Conversion:: Case conversion functions.
34 * Case Tables:: Customizing case conversion.
38 @section String and Character Basics
40 Characters are represented in Emacs Lisp as integers;
41 whether an integer is a character or not is determined only by how it is
42 used. Thus, strings really contain integers.
44 The length of a string (like any array) is fixed, and cannot be
45 altered once the string exists. Strings in Lisp are @emph{not}
46 terminated by a distinguished character code. (By contrast, strings in
47 C are terminated by a character with @sc{ascii} code 0.)
49 Since strings are arrays, and therefore sequences as well, you can
50 operate on them with the general array and sequence functions.
51 (@xref{Sequences Arrays Vectors}.) For example, you can access or
52 change individual characters in a string using the functions @code{aref}
53 and @code{aset} (@pxref{Array Functions}).
55 There are two text representations for non-@sc{ascii} characters in
56 Emacs strings (and in buffers): unibyte and multibyte (@pxref{Text
57 Representations}). An @sc{ascii} character always occupies one byte in a
58 string; in fact, when a string is all @sc{ascii}, there is no real
59 difference between the unibyte and multibyte representations.
60 For most Lisp programming, you don't need to be concerned with these two
63 Sometimes key sequences are represented as strings. When a string is
64 a key sequence, string elements in the range 128 to 255 represent meta
65 characters (which are large integers) rather than character
66 codes in the range 128 to 255.
68 Strings cannot hold characters that have the hyper, super or alt
69 modifiers; they can hold @sc{ascii} control characters, but no other
70 control characters. They do not distinguish case in @sc{ascii} control
71 characters. If you want to store such characters in a sequence, such as
72 a key sequence, you must use a vector instead of a string.
73 @xref{Character Type}, for more information about the representation of meta
74 and other modifiers for keyboard input characters.
76 Strings are useful for holding regular expressions. You can also
77 match regular expressions against strings (@pxref{Regexp Search}). The
78 functions @code{match-string} (@pxref{Simple Match Data}) and
79 @code{replace-match} (@pxref{Replacing Match}) are useful for
80 decomposing and modifying strings based on regular expression matching.
82 Like a buffer, a string can contain text properties for the characters
83 in it, as well as the characters themselves. @xref{Text Properties}.
84 All the Lisp primitives that copy text from strings to buffers or other
85 strings also copy the properties of the characters being copied.
87 @xref{Text}, for information about functions that display strings or
88 copy them into buffers. @xref{Character Type}, and @ref{String Type},
89 for information about the syntax of characters and strings.
90 @xref{Non-ASCII Characters}, for functions to convert between text
91 representations and to encode and decode character codes.
93 @node Predicates for Strings
94 @section The Predicates for Strings
96 For more information about general sequence and array predicates,
97 see @ref{Sequences Arrays Vectors}, and @ref{Arrays}.
100 This function returns @code{t} if @var{object} is a string, @code{nil}
104 @defun char-or-string-p object
105 This function returns @code{t} if @var{object} is a string or a
106 character (i.e., an integer), @code{nil} otherwise.
109 @node Creating Strings
110 @section Creating Strings
112 The following functions create strings, either from scratch, or by
113 putting strings together, or by taking them apart.
115 @defun make-string count character
116 This function returns a string made up of @var{count} repetitions of
117 @var{character}. If @var{count} is negative, an error is signaled.
126 Other functions to compare with this one include @code{char-to-string}
127 (@pxref{String Conversion}), @code{make-vector} (@pxref{Vectors}), and
128 @code{make-list} (@pxref{Building Lists}).
131 @defun string &rest characters
132 This returns a string containing the characters @var{characters}.
140 @defun substring string start &optional end
141 This function returns a new string which consists of those characters
142 from @var{string} in the range from (and including) the character at the
143 index @var{start} up to (but excluding) the character at the index
144 @var{end}. The first character is at index zero.
148 (substring "abcdefg" 0 3)
154 Here the index for @samp{a} is 0, the index for @samp{b} is 1, and the
155 index for @samp{c} is 2. Thus, three letters, @samp{abc}, are copied
156 from the string @code{"abcdefg"}. The index 3 marks the character
157 position up to which the substring is copied. The character whose index
158 is 3 is actually the fourth character in the string.
160 A negative number counts from the end of the string, so that @minus{}1
161 signifies the index of the last character of the string. For example:
165 (substring "abcdefg" -3 -1)
171 In this example, the index for @samp{e} is @minus{}3, the index for
172 @samp{f} is @minus{}2, and the index for @samp{g} is @minus{}1.
173 Therefore, @samp{e} and @samp{f} are included, and @samp{g} is excluded.
175 When @code{nil} is used as an index, it stands for the length of the
180 (substring "abcdefg" -3 nil)
185 Omitting the argument @var{end} is equivalent to specifying @code{nil}.
186 It follows that @code{(substring @var{string} 0)} returns a copy of all
191 (substring "abcdefg" 0)
197 But we recommend @code{copy-sequence} for this purpose (@pxref{Sequence
200 If the characters copied from @var{string} have text properties, the
201 properties are copied into the new string also. @xref{Text Properties}.
203 @code{substring} also accepts a vector for the first argument.
207 (substring [a b (c) "d"] 1 3)
211 A @code{wrong-type-argument} error is signaled if either @var{start} or
212 @var{end} is not an integer or @code{nil}. An @code{args-out-of-range}
213 error is signaled if @var{start} indicates a character following
214 @var{end}, or if either integer is out of range for @var{string}.
216 Contrast this function with @code{buffer-substring} (@pxref{Buffer
217 Contents}), which returns a string containing a portion of the text in
218 the current buffer. The beginning of a string is at index 0, but the
219 beginning of a buffer is at index 1.
222 @defun concat &rest sequences
223 @cindex copying strings
224 @cindex concatenating strings
225 This function returns a new string consisting of the characters in the
226 arguments passed to it (along with their text properties, if any). The
227 arguments may be strings, lists of numbers, or vectors of numbers; they
228 are not themselves changed. If @code{concat} receives no arguments, it
229 returns an empty string.
232 (concat "abc" "-def")
234 (concat "abc" (list 120 121) [122])
236 ;; @r{@code{nil} is an empty sequence.}
237 (concat "abc" nil "-def")
239 (concat "The " "quick brown " "fox.")
240 @result{} "The quick brown fox."
246 The @code{concat} function always constructs a new string that is
247 not @code{eq} to any existing string.
249 When an argument is an integer (not a sequence of integers), it is
250 converted to a string of digits making up the decimal printed
251 representation of the integer. @strong{Don't use this feature; we plan
252 to eliminate it. If you already use this feature, change your programs
253 now!} The proper way to convert an integer to its decimal printed form
254 is with @code{format} (@pxref{Formatting Strings}) or
255 @code{number-to-string} (@pxref{String Conversion}).
266 For information about other concatenation functions, see the
267 description of @code{mapconcat} in @ref{Mapping Functions},
268 @code{vconcat} in @ref{Vectors}, and @code{append} in @ref{Building
272 @defun split-string string separators
273 This function splits @var{string} into substrings at matches for the regular
274 expression @var{separators}. Each match for @var{separators} defines a
275 splitting point; the substrings between the splitting points are made
276 into a list, which is the value returned by @code{split-string}.
277 If @var{separators} is @code{nil} (or omitted),
278 the default is @code{"[ \f\t\n\r\v]+"}.
283 (split-string "Soup is good food" "o")
284 @result{} ("S" "up is g" "" "d f" "" "d")
285 (split-string "Soup is good food" "o+")
286 @result{} ("S" "up is g" "d f" "d")
289 When there is a match adjacent to the beginning or end of the string,
290 this does not cause a null string to appear at the beginning or end
294 (split-string "out to moo" "o+")
295 @result{} ("ut t" " m")
298 Empty matches do count, when not adjacent to another match:
301 (split-string "Soup is good food" "o*")
302 @result{}("S" "u" "p" " " "i" "s" " " "g" "d" " " "f" "d")
303 (split-string "Nice doggy!" "")
304 @result{}("N" "i" "c" "e" " " "d" "o" "g" "g" "y" "!")
308 @node Modifying Strings
309 @section Modifying Strings
311 The most basic way to alter the contents of an existing string is with
312 @code{aset} (@pxref{Array Functions}). @code{(aset @var{string}
313 @var{idx} @var{char})} stores @var{char} into @var{string} at index
314 @var{idx}. Each character occupies one or more bytes, and if @var{char}
315 needs a different number of bytes from the character already present at
316 that index, @code{aset} signals an error.
318 A more powerful function is @code{store-substring}:
320 @defun store-substring string idx obj
321 This function alters part of the contents of the string @var{string}, by
322 storing @var{obj} starting at index @var{idx}. The argument @var{obj}
323 may be either a character or a (smaller) string.
325 Since it is impossible to change the length of an existing string, it is
326 an error if @var{obj} doesn't fit within @var{string}'s actual length,
327 or if any new character requires a different number of bytes from the
328 character currently present at that point in @var{string}.
332 @node Text Comparison
333 @section Comparison of Characters and Strings
334 @cindex string equality
336 @defun char-equal character1 character2
337 This function returns @code{t} if the arguments represent the same
338 character, @code{nil} otherwise. This function ignores differences
339 in case if @code{case-fold-search} is non-@code{nil}.
344 (let ((case-fold-search nil))
350 @defun string= string1 string2
351 This function returns @code{t} if the characters of the two strings
353 Case is always significant, regardless of @code{case-fold-search}.
356 (string= "abc" "abc")
358 (string= "abc" "ABC")
364 The function @code{string=} ignores the text properties of the two
365 strings. When @code{equal} (@pxref{Equality Predicates}) compares two
366 strings, it uses @code{string=}.
368 If the strings contain non-@sc{ascii} characters, and one is unibyte
369 while the other is multibyte, then they cannot be equal. @xref{Text
373 @defun string-equal string1 string2
374 @code{string-equal} is another name for @code{string=}.
377 @cindex lexical comparison
378 @defun string< string1 string2
379 @c (findex string< causes problems for permuted index!!)
380 This function compares two strings a character at a time. It
381 scans both the strings at the same time to find the first pair of corresponding
382 characters that do not match. If the lesser character of these two is
383 the character from @var{string1}, then @var{string1} is less, and this
384 function returns @code{t}. If the lesser character is the one from
385 @var{string2}, then @var{string1} is greater, and this function returns
386 @code{nil}. If the two strings match entirely, the value is @code{nil}.
388 Pairs of characters are compared according to their character codes.
389 Keep in mind that lower case letters have higher numeric values in the
390 @sc{ascii} character set than their upper case counterparts; digits and
391 many punctuation characters have a lower numeric value than upper case
392 letters. An @sc{ascii} character is less than any non-@sc{ascii}
393 character; a unibyte non-@sc{ascii} character is always less than any
394 multibyte non-@sc{ascii} character (@pxref{Text Representations}).
398 (string< "abc" "abd")
400 (string< "abd" "abc")
402 (string< "123" "abc")
407 When the strings have different lengths, and they match up to the
408 length of @var{string1}, then the result is @code{t}. If they match up
409 to the length of @var{string2}, the result is @code{nil}. A string of
410 no characters is less than any other string.
428 @defun string-lessp string1 string2
429 @code{string-lessp} is another name for @code{string<}.
432 @defun compare-strings string1 start1 end1 string2 start2 end2 &optional ignore-case
433 This function compares the specified part of @var{string1} with the
434 specified part of @var{string2}. The specified part of @var{string1}
435 runs from index @var{start1} up to index @var{end1} (@code{nil} means
436 the end of the string). The specified part of @var{string2} runs from
437 index @var{start2} up to index @var{end2} (@code{nil} means the end of
440 The strings are both converted to multibyte for the comparison
441 (@pxref{Text Representations}) so that a unibyte string can be equal to
442 a multibyte string. If @var{ignore-case} is non-@code{nil}, then case
443 is ignored, so that upper case letters can be equal to lower case letters.
445 If the specified portions of the two strings match, the value is
446 @code{t}. Otherwise, the value is an integer which indicates how many
447 leading characters agree, and which string is less. Its absolute value
448 is one plus the number of characters that agree at the beginning of the
449 two strings. The sign is negative if @var{string1} (or its specified
453 @defun assoc-ignore-case key alist
454 This function works like @code{assoc}, except that @var{key} must be a
455 string, and comparison is done using @code{compare-strings}.
456 Case differences are ignored in this comparison.
459 @defun assoc-ignore-representation key alist
460 This function works like @code{assoc}, except that @var{key} must be a
461 string, and comparison is done using @code{compare-strings}.
462 Case differences are significant.
465 See also @code{compare-buffer-substrings} in @ref{Comparing Text}, for
466 a way to compare text in buffers. The function @code{string-match},
467 which matches a regular expression against a string, can be used
468 for a kind of string comparison; see @ref{Regexp Search}.
470 @node String Conversion
471 @comment node-name, next, previous, up
472 @section Conversion of Characters and Strings
473 @cindex conversion of strings
475 This section describes functions for conversions between characters,
476 strings and integers. @code{format} and @code{prin1-to-string}
477 (@pxref{Output Functions}) can also convert Lisp objects into strings.
478 @code{read-from-string} (@pxref{Input Functions}) can ``convert'' a
479 string representation of a Lisp object into an object. The functions
480 @code{string-make-multibyte} and @code{string-make-unibyte} convert the
481 text representation of a string (@pxref{Converting Representations}).
483 @xref{Documentation}, for functions that produce textual descriptions
484 of text characters and general input events
485 (@code{single-key-description} and @code{text-char-description}). These
486 functions are used primarily for making help messages.
488 @defun char-to-string character
489 @cindex character to string
490 This function returns a new string containing one character,
491 @var{character}. This function is semi-obsolete because the function
492 @code{string} is more general. @xref{Creating Strings}.
495 @defun string-to-char string
496 @cindex string to character
497 This function returns the first character in @var{string}. If the
498 string is empty, the function returns 0. The value is also 0 when the
499 first character of @var{string} is the null character, @sc{ascii} code
503 (string-to-char "ABC")
505 (string-to-char "xyz")
510 (string-to-char "\000")
515 This function may be eliminated in the future if it does not seem useful
519 @defun number-to-string number
520 @cindex integer to string
521 @cindex integer to decimal
522 This function returns a string consisting of the printed base-ten
523 representation of @var{number}, which may be an integer or a floating
524 point number. The returned value starts with a minus sign if the argument is
528 (number-to-string 256)
530 (number-to-string -23)
532 (number-to-string -23.5)
536 @cindex int-to-string
537 @code{int-to-string} is a semi-obsolete alias for this function.
539 See also the function @code{format} in @ref{Formatting Strings}.
542 @defun string-to-number string &optional base
543 @cindex string to number
544 This function returns the numeric value of the characters in
545 @var{string}. If @var{base} is non-@code{nil}, integers are converted
546 in that base. If @var{base} is @code{nil}, then base ten is used.
547 Floating point conversion always uses base ten; we have not implemented
548 other radices for floating point numbers, because that would be much
549 more work and does not seem useful.
551 The parsing skips spaces and tabs at the beginning of @var{string}, then
552 reads as much of @var{string} as it can interpret as a number. (On some
553 systems it ignores other whitespace at the beginning, not just spaces
554 and tabs.) If the first character after the ignored whitespace is
555 neither a digit, nor a plus or minus sign, nor the leading dot of a
556 floating point number, this function returns 0.
559 (string-to-number "256")
561 (string-to-number "25 is a perfect square.")
563 (string-to-number "X256")
565 (string-to-number "-4.5")
569 @findex string-to-int
570 @code{string-to-int} is an obsolete alias for this function.
573 Here are some other functions that can convert to or from a string:
577 @code{concat} can convert a vector or a list into a string.
578 @xref{Creating Strings}.
581 @code{vconcat} can convert a string into a vector. @xref{Vector
585 @code{append} can convert a string into a list. @xref{Building Lists}.
588 @node Formatting Strings
589 @comment node-name, next, previous, up
590 @section Formatting Strings
591 @cindex formatting strings
592 @cindex strings, formatting them
594 @dfn{Formatting} means constructing a string by substitution of
595 computed values at various places in a constant string. This constant string
596 controls how the other values are printed, as well as where they appear;
597 it is called a @dfn{format string}.
599 Formatting is often useful for computing messages to be displayed. In
600 fact, the functions @code{message} and @code{error} provide the same
601 formatting feature described here; they differ from @code{format} only
602 in how they use the result of formatting.
604 @defun format string &rest objects
605 This function returns a new string that is made by copying
606 @var{string} and then replacing any format specification
607 in the copy with encodings of the corresponding @var{objects}. The
608 arguments @var{objects} are the computed values to be formatted.
610 The characters in @var{string}, other than the format specifications,
611 are copied directly into the output; starting in Emacs 21, if they have
612 text properties, these are copied into the output also.
615 @cindex @samp{%} in format
616 @cindex format specification
617 A format specification is a sequence of characters beginning with a
618 @samp{%}. Thus, if there is a @samp{%d} in @var{string}, the
619 @code{format} function replaces it with the printed representation of
620 one of the values to be formatted (one of the arguments @var{objects}).
625 (format "The value of fill-column is %d." fill-column)
626 @result{} "The value of fill-column is 72."
630 If @var{string} contains more than one format specification, the
631 format specifications correspond to successive values from
632 @var{objects}. Thus, the first format specification in @var{string}
633 uses the first such value, the second format specification uses the
634 second such value, and so on. Any extra format specifications (those
635 for which there are no corresponding values) cause unpredictable
636 behavior. Any extra values to be formatted are ignored.
638 Certain format specifications require values of particular types. If
639 you supply a value that doesn't fit the requirements, an error is
642 Here is a table of valid format specifications:
646 Replace the specification with the printed representation of the object,
647 made without quoting (that is, using @code{princ}, not
648 @code{prin1}---@pxref{Output Functions}). Thus, strings are represented
649 by their contents alone, with no @samp{"} characters, and symbols appear
650 without @samp{\} characters.
652 Starting in Emacs 21, if the object is a string, its text properties are
653 copied into the output. The text properties of the @samp{%s} itself
654 are also copied, but those of the object take priority.
656 If there is no corresponding object, the empty string is used.
659 Replace the specification with the printed representation of the object,
660 made with quoting (that is, using @code{prin1}---@pxref{Output
661 Functions}). Thus, strings are enclosed in @samp{"} characters, and
662 @samp{\} characters appear where necessary before special characters.
664 If there is no corresponding object, the empty string is used.
667 @cindex integer to octal
668 Replace the specification with the base-eight representation of an
672 Replace the specification with the base-ten representation of an
676 @cindex integer to hexadecimal
677 Replace the specification with the base-sixteen representation of an
681 Replace the specification with the character which is the value given.
684 Replace the specification with the exponential notation for a floating
688 Replace the specification with the decimal-point notation for a floating
692 Replace the specification with notation for a floating point number,
693 using either exponential notation or decimal-point notation, whichever
697 Replace the specification with a single @samp{%}. This format specification is
698 unusual in that it does not use a value. For example, @code{(format "%%
699 %d" 30)} returns @code{"% 30"}.
702 Any other format character results in an @samp{Invalid format
705 Here are several examples:
709 (format "The name of this buffer is %s." (buffer-name))
710 @result{} "The name of this buffer is strings.texi."
712 (format "The buffer object prints as %s." (current-buffer))
713 @result{} "The buffer object prints as strings.texi."
715 (format "The octal value of %d is %o,
716 and the hex value is %x." 18 18 18)
717 @result{} "The octal value of 18 is 22,
718 and the hex value is 12."
722 @cindex numeric prefix
725 All the specification characters allow an optional numeric prefix
726 between the @samp{%} and the character. The optional numeric prefix
727 defines the minimum width for the object. If the printed representation
728 of the object contains fewer characters than this, then it is padded.
729 The padding is on the left if the prefix is positive (or starts with
730 zero) and on the right if the prefix is negative. The padding character
731 is normally a space, but if the numeric prefix starts with a zero, zeros
732 are used for padding. Here are some examples of padding:
735 (format "%06d is padded on the left with zeros" 123)
736 @result{} "000123 is padded on the left with zeros"
738 (format "%-6d is padded on the right" 123)
739 @result{} "123 is padded on the right"
742 @code{format} never truncates an object's printed representation, no
743 matter what width you specify. Thus, you can use a numeric prefix to
744 specify a minimum spacing between columns with no risk of losing
747 In the following three examples, @samp{%7s} specifies a minimum width
748 of 7. In the first case, the string inserted in place of @samp{%7s} has
749 only 3 letters, so 4 blank spaces are inserted for padding. In the
750 second case, the string @code{"specification"} is 13 letters wide but is
751 not truncated. In the third case, the padding is on the right.
755 (format "The word `%7s' actually has %d letters in it."
756 "foo" (length "foo"))
757 @result{} "The word ` foo' actually has 3 letters in it."
761 (format "The word `%7s' actually has %d letters in it."
762 "specification" (length "specification"))
763 @result{} "The word `specification' actually has 13 letters in it."
767 (format "The word `%-7s' actually has %d letters in it."
768 "foo" (length "foo"))
769 @result{} "The word `foo ' actually has 3 letters in it."
773 @node Case Conversion
774 @comment node-name, next, previous, up
775 @section Case Conversion in Lisp
778 @cindex character case
779 @cindex case conversion in Lisp
781 The character case functions change the case of single characters or
782 of the contents of strings. The functions normally convert only
783 alphabetic characters (the letters @samp{A} through @samp{Z} and
784 @samp{a} through @samp{z}, as well as non-@sc{ascii} letters); other
785 characters are not altered. You can specify a different case
786 conversion mapping by specifying a case table (@pxref{Case Tables}).
788 These functions do not modify the strings that are passed to them as
791 The examples below use the characters @samp{X} and @samp{x} which have
792 @sc{ascii} codes 88 and 120 respectively.
794 @defun downcase string-or-char
795 This function converts a character or a string to lower case.
797 When the argument to @code{downcase} is a string, the function creates
798 and returns a new string in which each letter in the argument that is
799 upper case is converted to lower case. When the argument to
800 @code{downcase} is a character, @code{downcase} returns the
801 corresponding lower case character. This value is an integer. If the
802 original character is lower case, or is not a letter, then the value
803 equals the original character.
806 (downcase "The cat in the hat")
807 @result{} "the cat in the hat"
814 @defun upcase string-or-char
815 This function converts a character or a string to upper case.
817 When the argument to @code{upcase} is a string, the function creates
818 and returns a new string in which each letter in the argument that is
819 lower case is converted to upper case.
821 When the argument to @code{upcase} is a character, @code{upcase}
822 returns the corresponding upper case character. This value is an integer.
823 If the original character is upper case, or is not a letter, then the
824 value returned equals the original character.
827 (upcase "The cat in the hat")
828 @result{} "THE CAT IN THE HAT"
835 @defun capitalize string-or-char
836 @cindex capitalization
837 This function capitalizes strings or characters. If
838 @var{string-or-char} is a string, the function creates and returns a new
839 string, whose contents are a copy of @var{string-or-char} in which each
840 word has been capitalized. This means that the first character of each
841 word is converted to upper case, and the rest are converted to lower
844 The definition of a word is any sequence of consecutive characters that
845 are assigned to the word constituent syntax class in the current syntax
846 table (@pxref{Syntax Class Table}).
848 When the argument to @code{capitalize} is a character, @code{capitalize}
849 has the same result as @code{upcase}.
852 (capitalize "The cat in the hat")
853 @result{} "The Cat In The Hat"
855 (capitalize "THE 77TH-HATTED CAT")
856 @result{} "The 77th-Hatted Cat"
865 @defun upcase-initials string
866 This function capitalizes the initials of the words in @var{string},
867 without altering any letters other than the initials. It returns a new
868 string whose contents are a copy of @var{string}, in which each word has
869 had its initial letter converted to upper case.
871 The definition of a word is any sequence of consecutive characters that
872 are assigned to the word constituent syntax class in the current syntax
873 table (@pxref{Syntax Class Table}).
877 (upcase-initials "The CAT in the hAt")
878 @result{} "The CAT In The HAt"
883 @xref{Text Comparison}, for functions that compare strings; some of
884 them ignore case differences, or can optionally ignore case differences.
887 @section The Case Table
889 You can customize case conversion by installing a special @dfn{case
890 table}. A case table specifies the mapping between upper case and lower
891 case letters. It affects both the case conversion functions for Lisp
892 objects (see the previous section) and those that apply to text in the
893 buffer (@pxref{Case Changes}). Each buffer has a case table; there is
894 also a standard case table which is used to initialize the case table
897 A case table is a char-table (@pxref{Char-Tables}) whose subtype is
898 @code{case-table}. This char-table maps each character into the
899 corresponding lower case character. It has three extra slots, which
904 The upcase table maps each character into the corresponding upper
907 The canonicalize table maps all of a set of case-related characters
908 into a particular member of that set.
910 The equivalences table maps each one of a set of case-related characters
911 into the next character in that set.
914 In simple cases, all you need to specify is the mapping to lower-case;
915 the three related tables will be calculated automatically from that one.
917 For some languages, upper and lower case letters are not in one-to-one
918 correspondence. There may be two different lower case letters with the
919 same upper case equivalent. In these cases, you need to specify the
920 maps for both lower case and upper case.
922 The extra table @var{canonicalize} maps each character to a canonical
923 equivalent; any two characters that are related by case-conversion have
924 the same canonical equivalent character. For example, since @samp{a}
925 and @samp{A} are related by case-conversion, they should have the same
926 canonical equivalent character (which should be either @samp{a} for both
927 of them, or @samp{A} for both of them).
929 The extra table @var{equivalences} is a map that cyclicly permutes
930 each equivalence class (of characters with the same canonical
931 equivalent). (For ordinary @sc{ascii}, this would map @samp{a} into
932 @samp{A} and @samp{A} into @samp{a}, and likewise for each set of
933 equivalent characters.)
935 When you construct a case table, you can provide @code{nil} for
936 @var{canonicalize}; then Emacs fills in this slot from the lower case
937 and upper case mappings. You can also provide @code{nil} for
938 @var{equivalences}; then Emacs fills in this slot from
939 @var{canonicalize}. In a case table that is actually in use, those
940 components are non-@code{nil}. Do not try to specify @var{equivalences}
941 without also specifying @var{canonicalize}.
943 Here are the functions for working with case tables:
945 @defun case-table-p object
946 This predicate returns non-@code{nil} if @var{object} is a valid case
950 @defun set-standard-case-table table
951 This function makes @var{table} the standard case table, so that it will
952 be used in any buffers created subsequently.
955 @defun standard-case-table
956 This returns the standard case table.
959 @defun current-case-table
960 This function returns the current buffer's case table.
963 @defun set-case-table table
964 This sets the current buffer's case table to @var{table}.
967 The following three functions are convenient subroutines for packages
968 that define non-@sc{ascii} character sets. They modify the specified
969 case table @var{case-table}; they also modify the standard syntax table.
970 @xref{Syntax Tables}. Normally you would use these functions to change
971 the standard case table.
973 @defun set-case-syntax-pair uc lc case-table
974 This function specifies a pair of corresponding letters, one upper case
978 @defun set-case-syntax-delims l r case-table
979 This function makes characters @var{l} and @var{r} a matching pair of
980 case-invariant delimiters.
983 @defun set-case-syntax char syntax case-table
984 This function makes @var{char} case-invariant, with syntax
988 @deffn Command describe-buffer-case-table
989 This command displays a description of the contents of the current