From 16a494ca8f167327b6c4fa3845bdb1e865d2c955 Mon Sep 17 00:00:00 2001
From: John Maddock
- The following are treated as valid digraphs when used as a collating name:
+The following are treated as valid digraphs when used as a collating name:
"ae", "Ae", "AE", "ch", "Ch", "CH", "ll", "Ll", "LL", "ss", "Ss", "SS", "nj", "Nj", "NJ", "dz", "Dz", "DZ", "lj", "Lj", "LJ".
+The following symbolic names are recognised as valid collating element names, in addition to any single character:
@@ -342,15 +349,18 @@
++
When using Unicode aware regular expressions (with + the u32regex type), all the normal symbolic names for Unicode + characters (those given in Unidata.txt) are recognised.
Revised - - 24 Oct 2003 -
-© Copyright John Maddock 1998- - 2003
+Revised 12 Jan 2005 +
+© Copyright John Maddock 2004-2005
Use, modification and distribution are subject to the Boost Software License, Version 1.0. (See accompanying file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt)
diff --git a/doc/Attic/history.html b/doc/Attic/history.html index 99edeb73..6f3618e5 100644 --- a/doc/Attic/history.html +++ b/doc/Attic/history.html @@ -40,7 +40,10 @@Boost 1.32.1.
The following comments refer to Unicode + Technical + Standard +#18: Unicode Regular Expressions version 9.
++
# | +Feature | +Support | +
1.1 | +Hex Notation | +Yes: use \x{DDDD} to refer to code point UDDDD. | +
1.2 | +Character Properties | +All the names listed under the General + Category Property are supported. Script names and Other Names are + not currently supported. | +
1.3 | +Subtraction and Intersection | +
+ Indirectly support by forward-lookahead: + +(?=[[:X:]])[[:Y:]] +Gives the intersection of character properties X and Y. +(?![[:X:]])[[:Y:]] +Gives everything in Y that is not in X (subtraction). + |
+
1.4 | +Simple Word Boundaries | +Conforming: non-spacing marks are included in the set of word characters. | +
1.5 | +Caseless Matching | +Supported, note that at this level, case transformations are 1:1, many to many + case folding operations are not supported (for example "ß" to "SS"). | +
1.6 | +Line Boundaries | +Supported, except that "." matches only one character of "\r\n". Other than + that word boundaries match correctly; including not matching in the middle of a + "\r\n" sequence. | +
1.7 | +Code Points | +Supported: provided you use the u32* algorithms, + then UTF-8, UTF-16 and UTF-32 are all treated as sequences of 32-bit code + points. | +
2.1 | +Canonical Equivalence | +Not supported: it is up to the user of the library to convert all text into + the same canonical form as the regular expression. | +
2.2 | +Default Grapheme Clusters | +Not supported. | +
2.3 | ++ + | +Not supported. | +
2.4 | ++ + | +Not Supported. | +
2.5 | +Name Properties | +Supported: the expression "[[:name:]]" or \N{name} matches the named character + "name". | +
2.6 | +Wildcard properties | +Not Supported. | +
3.1 | +Tailored Punctuation. | +Not Supported. | +
3.2 | +Tailored Grapheme Clusters | +Not Supported. | +
3.3 | +Tailored Word Boundaries. | +Not Supported. | +
3.4 | +Tailored Loose Matches | +Partial support: [[=c=]] matches characters with the same primary equivalence + class as "c". | +
3.5 | +Tailored Ranges | +Supported: [a-b] matches any character that collates in the range a to b, when + the expression is constructed with the collate + flag set. | +
3.6 | +Context Matches | +Not Supported. | +
3.7 | +Incremental Matches | +Supported: pass the flag match_partial to + the regex algorithms. | +
3.8 | +Unicode Set Sharing | +Not Supported. | +
3.9 | +Possible Match Sets | +Not supported, however this information is used internally to optimise the + matching of regular expressions, and return quickly if no match is possible. | +
3.10 | +Folded Matching | +Partial Support: It is possible to achieve a similar effect by using a + custom regular expression traits class. | +
3.11 | +Custom Submatch Evaluation | +Not Supported. | +
Revised @@ -73,3 +233,4 @@ or copy at http://www.boost.org/LICENSE_1_0.txt)