Warning: This is the manual of the legacy Guile 2.2 series. You may want to read the manual of the current stable series instead.

Next: , Previous: , Up: Data Types   [Contents][Index]


6.6.3 Characters

In Scheme, there is a data type to describe a single character.

Defining what exactly a character is can be more complicated than it seems. Guile follows the advice of R6RS and uses The Unicode Standard to help define what a character is. So, for Guile, a character is anything in the Unicode Character Database.

The Unicode Character Database is basically a table of characters indexed using integers called ’code points’. Valid code points are in the ranges 0 to #xD7FF inclusive or #xE000 to #x10FFFF inclusive, which is about 1.1 million code points.

Any code point that has been assigned to a character or that has otherwise been given a meaning by Unicode is called a ’designated code point’. Most of the designated code points, about 200,000 of them, indicate characters, accents or other combining marks that modify other characters, symbols, whitespace, and control characters. Some are not characters but indicators that suggest how to format or display neighboring characters.

If a code point is not a designated code point – if it has not been assigned to a character by The Unicode Standard – it is a ’reserved code point’, meaning that they are reserved for future use. Most of the code points, about 800,000, are ’reserved code points’.

By convention, a Unicode code point is written as “U+XXXX” where “XXXX” is a hexadecimal number. Please note that this convenient notation is not valid code. Guile does not interpret “U+XXXX” as a character.

In Scheme, a character literal is written as #\name where name is the name of the character that you want. Printable characters have their usual single character name; for example, #\a is a lower case a.

Some of the code points are ’combining characters’ that are not meant to be printed by themselves but are instead meant to modify the appearance of the previous character. For combining characters, an alternate form of the character literal is #\ followed by U+25CC (a small, dotted circle), followed by the combining character. This allows the combining character to be drawn on the circle, not on the backslash of #\.

Many of the non-printing characters, such as whitespace characters and control characters, also have names.

The most commonly used non-printing characters have long character names, described in the table below.

Character NameCodepoint
#\nulU+0000
#\alarmU+0007
#\backspaceU+0008
#\tabU+0009
#\linefeedU+000A
#\newlineU+000A
#\vtabU+000B
#\pageU+000C
#\returnU+000D
#\escU+001B
#\spaceU+0020
#\deleteU+007F

There are also short names for all of the “C0 control characters” (those with code points below 32). The following table lists the short name for each character.

0 = #\nul1 = #\soh2 = #\stx3 = #\etx
4 = #\eot5 = #\enq6 = #\ack7 = #\bel
8 = #\bs9 = #\ht10 = #\lf11 = #\vt
12 = #\ff13 = #\cr14 = #\so15 = #\si
16 = #\dle17 = #\dc118 = #\dc219 = #\dc3
20 = #\dc421 = #\nak22 = #\syn23 = #\etb
24 = #\can25 = #\em26 = #\sub27 = #\esc
28 = #\fs29 = #\gs30 = #\rs31 = #\us
32 = #\sp

The short name for the “delete” character (code point U+007F) is #\del.

The R7RS name for the “escape” character (code point U+001B) is #\escape.

There are also a few alternative names left over for compatibility with previous versions of Guile.

AlternateStandard
#\nl#\newline
#\np#\page
#\null#\nul

Characters may also be written using their code point values. They can be written with as an octal number, such as #\10 for #\bs or #\177 for #\del.

If one prefers hex to octal, there is an additional syntax for character escapes: #\xHHHH – the letter ’x’ followed by a hexadecimal number of one to eight digits.

Scheme Procedure: char? x
C Function: scm_char_p (x)

Return #t if x is a character, else #f.

Fundamentally, the character comparison operations below are numeric comparisons of the character’s code points.

Scheme Procedure: char=? x y

Return #t if code point of x is equal to the code point of y, else #f.

Scheme Procedure: char<? x y

Return #t if the code point of x is less than the code point of y, else #f.

Scheme Procedure: char<=? x y

Return #t if the code point of x is less than or equal to the code point of y, else #f.

Scheme Procedure: char>? x y

Return #t if the code point of x is greater than the code point of y, else #f.

Scheme Procedure: char>=? x y

Return #t if the code point of x is greater than or equal to the code point of y, else #f.

Case-insensitive character comparisons use Unicode case folding. In case folding comparisons, if a character is lowercase and has an uppercase form that can be expressed as a single character, it is converted to uppercase before comparison. All other characters undergo no conversion before the comparison occurs. This includes the German sharp S (Eszett) which is not uppercased before conversion because its uppercase form has two characters. Unicode case folding is language independent: it uses rules that are generally true, but, it cannot cover all cases for all languages.

Scheme Procedure: char-ci=? x y

Return #t if the case-folded code point of x is the same as the case-folded code point of y, else #f.

Scheme Procedure: char-ci<? x y

Return #t if the case-folded code point of x is less than the case-folded code point of y, else #f.

Scheme Procedure: char-ci<=? x y

Return #t if the case-folded code point of x is less than or equal to the case-folded code point of y, else #f.

Scheme Procedure: char-ci>? x y

Return #t if the case-folded code point of x is greater than the case-folded code point of y, else #f.

Scheme Procedure: char-ci>=? x y

Return #t if the case-folded code point of x is greater than or equal to the case-folded code point of y, else #f.

Scheme Procedure: char-alphabetic? chr
C Function: scm_char_alphabetic_p (chr)

Return #t if chr is alphabetic, else #f.

Scheme Procedure: char-numeric? chr
C Function: scm_char_numeric_p (chr)

Return #t if chr is numeric, else #f.

Scheme Procedure: char-whitespace? chr
C Function: scm_char_whitespace_p (chr)

Return #t if chr is whitespace, else #f.

Scheme Procedure: char-upper-case? chr
C Function: scm_char_upper_case_p (chr)

Return #t if chr is uppercase, else #f.

Scheme Procedure: char-lower-case? chr
C Function: scm_char_lower_case_p (chr)

Return #t if chr is lowercase, else #f.

Scheme Procedure: char-is-both? chr
C Function: scm_char_is_both_p (chr)

Return #t if chr is either uppercase or lowercase, else #f.

Scheme Procedure: char-general-category chr
C Function: scm_char_general_category (chr)

Return a symbol giving the two-letter name of the Unicode general category assigned to chr or #f if no named category is assigned. The following table provides a list of category names along with their meanings.

LuUppercase letterPfFinal quote punctuation
LlLowercase letterPoOther punctuation
LtTitlecase letterSmMath symbol
LmModifier letterScCurrency symbol
LoOther letterSkModifier symbol
MnNon-spacing markSoOther symbol
McCombining spacing markZsSpace separator
MeEnclosing markZlLine separator
NdDecimal digit numberZpParagraph separator
NlLetter numberCcControl
NoOther numberCfFormat
PcConnector punctuationCsSurrogate
PdDash punctuationCoPrivate use
PsOpen punctuationCnUnassigned
PeClose punctuation
PiInitial quote punctuation
Scheme Procedure: char->integer chr
C Function: scm_char_to_integer (chr)

Return the code point of chr.

Scheme Procedure: integer->char n
C Function: scm_integer_to_char (n)

Return the character that has code point n. The integer n must be a valid code point. Valid code points are in the ranges 0 to #xD7FF inclusive or #xE000 to #x10FFFF inclusive.

Scheme Procedure: char-upcase chr
C Function: scm_char_upcase (chr)

Return the uppercase character version of chr.

Scheme Procedure: char-downcase chr
C Function: scm_char_downcase (chr)

Return the lowercase character version of chr.

Scheme Procedure: char-titlecase chr
C Function: scm_char_titlecase (chr)

Return the titlecase character version of chr if one exists; otherwise return the uppercase version.

For most characters these will be the same, but the Unicode Standard includes certain digraph compatibility characters, such as U+01F3 “dz”, for which the uppercase and titlecase characters are different (U+01F1 “DZ” and U+01F2 “Dz” in this case, respectively).

C Function: scm_t_wchar scm_c_upcase (scm_t_wchar c)
C Function: scm_t_wchar scm_c_downcase (scm_t_wchar c)
C Function: scm_t_wchar scm_c_titlecase (scm_t_wchar c)

These C functions take an integer representation of a Unicode codepoint and return the codepoint corresponding to its uppercase, lowercase, and titlecase forms respectively. The type scm_t_wchar is a signed, 32-bit integer.

Characters also have “formal names”, which are defined by Unicode. These names can be accessed in Guile from the (ice-9 unicode) module:

(use-modules (ice-9 unicode))
Scheme Procedure: char->formal-name chr

Return the formal all-upper-case Unicode name of ch, as a string, or #f if the character has no name.

Scheme Procedure: formal-name->char name

Return the character whose formal all-upper-case Unicode name is name, or #f if no such character is known.


Next: , Previous: , Up: Data Types   [Contents][Index]