2 Copyright 2006-2007 John Maddock.
3 Distributed under the Boost Software License, Version 1.0.
4 (See accompanying file LICENSE_1_0.txt or copy at
5 http://www.boost.org/LICENSE_1_0.txt).
9 [section:collating_names Collating Names]
11 [section:digraphs Digraphs]
13 The following are treated as valid digraphs when used as a collating name:
15 "ae", "Ae", "AE", "ch", "Ch", "CH", "ll", "Ll", "LL", "ss", "Ss", "SS", "nj", "Nj", "NJ", "dz", "Dz", "DZ", "lj", "Lj", "LJ".
17 So for example the expression:
21 will match any character that collates between the digraph "ae" and the character "c".
25 [section:posix_symbolic_names POSIX Symbolic Names]
27 The following symbolic names are recognised as valid collating element names,
28 in addition to any single character, this allows you to write for example:
30 [pre \[\[.left-square-bracket.\]\[.right-square-bracket.\]\]]
32 if you wanted to match either "\[" or "\]".
47 [[vertical-tab] [\\v]]
49 [[carriage-return] [\\r]]
69 [[exclamation-mark] [!]]
70 [[quotation-mark] ["]]
76 [[left-parenthesis] [(]]
77 [[right-parenthesis] [)]]
96 [[less-than-sign] [<]]
98 [[greater-than-sign] [>]]
100 [[commercial-at] [@]]
101 [[left-square-bracket] [\[]]
103 [[right-square-bracket][\]]]
107 [[left-curly-bracket][{]]
109 [[right-curly-bracket][}]]
116 [section:named_unicode Named Unicode Characters]
118 When using [link boost_regex.unicode Unicode aware regular expressions] (with the `u32regex` type), all
119 the normal symbolic names for Unicode characters (those given in Unidata.txt)
120 are recognised. So for example:
122 [pre \[\[.CYRILLIC CAPITAL LETTER I.\]\] ]
124 would match the Unicode character 0x0418.