Load pcre-6.5 into code/trunk.

git-svn-id: svn://vcs.exim.org/pcre/code/trunk@87 2f5784b3-3f2a-0410-8824-cb99058d5e15

1 files changed, 20 insertions, 21 deletions

diff --git a/doc/pcre.3 b/doc/pcre.3
index 155e532..6123a2c 100644
--- a/doc/pcre.3
+++ b/doc/pcre.3
@@ -156,12 +156,15 @@ If PCRE is built with Unicode character property support (which implies UTF-8
 support), the escape sequences \ep{..}, \eP{..}, and \eX are supported.
 The available properties that can be tested are limited to the general
 category properties such as Lu for an upper case letter or Nd for a decimal
-number. A full list is given in the
+number, the Unicode script names such as Arabic or Han, and the derived
+properties Any and L&. A full list is given in the
 .\" HREF
 \fBpcrepattern\fP
 .\"
-documentation. The PCRE library is increased in size by about 90K when Unicode
-property support is included.
+documentation. Only the short names for properties are supported. For example,
+\ep{L} matches a letter. Its Perl synonym, \ep{Letter}, is not supported.
+Furthermore, in Perl, many properties may optionally be prefixed by "Is", for
+compatibility with Perl 5.6. PCRE does not support this.
 .P
 The following comments apply when PCRE is running in UTF-8 mode:
 .P
@@ -176,26 +179,19 @@ not diagnose an invalid UTF-8 string. If you pass an invalid UTF-8 string to
 PCRE when PCRE_NO_UTF8_CHECK is set, the results are undefined. Your program
 may crash.
 .P
-2. In a pattern, the escape sequence \ex{...}, where the contents of the braces
-is a string of hexadecimal digits, is interpreted as a UTF-8 character whose
-code number is the given hexadecimal number, for example: \ex{1234}. If a
-non-hexadecimal digit appears between the braces, the item is not recognized.
-This escape sequence can be used either as a literal, or within a character
-class.
+2. An unbraced hexadecimal escape sequence (such as \exb3) matches a two-byte
+UTF-8 character if the value is greater than 127.
 .P
-3. The original hexadecimal escape sequence, \exhh, matches a two-byte UTF-8
-character if the value is greater than 127.
-.P
-4. Repeat quantifiers apply to complete UTF-8 characters, not to individual
+3. Repeat quantifiers apply to complete UTF-8 characters, not to individual
 bytes, for example: \ex{100}{3}.
 .P
-5. The dot metacharacter matches one UTF-8 character instead of a single byte.
+4. The dot metacharacter matches one UTF-8 character instead of a single byte.
 .P
-6. The escape sequence \eC can be used to match a single byte in UTF-8 mode,
+5. The escape sequence \eC can be used to match a single byte in UTF-8 mode,
 but its use can lead to some strange effects. This facility is not available in
 the alternative matching function, \fBpcre_dfa_exec()\fP.
 .P
-7. The character escapes \eb, \eB, \ed, \eD, \es, \eS, \ew, and \eW correctly
+6. The character escapes \eb, \eB, \ed, \eD, \es, \eS, \ew, and \eW correctly
 test characters of any code value, but the characters that PCRE recognizes as
 digits, spaces, or word characters remain the same set as before, all with
 values less than 256. This remains true even when PCRE includes Unicode
@@ -203,15 +199,18 @@ property support, because to do otherwise would slow down PCRE in many common
 cases. If you really want to test for a wider sense of, say, "digit", you
 must use Unicode property tests such as \ep{Nd}.
 .P
-8. Similarly, characters that match the POSIX named character classes are all
+7. Similarly, characters that match the POSIX named character classes are all
 low-valued characters.
 .P
-9. Case-insensitive matching applies only to characters whose values are less
+8. Case-insensitive matching applies only to characters whose values are less
 than 128, unless PCRE is built with Unicode property support. Even when Unicode
 property support is available, PCRE still uses its own character tables when
 checking the case of low-valued characters, so as not to degrade performance.
 The Unicode property information is used only for characters with higher
-values.
+values. Even when Unicode property support is available, PCRE supports
+case-insensitive matching only when there is a one-to-one mapping between a
+letter's cases. There are a small number of many-to-one mappings in Unicode;
+these are not supported by PCRE.
 .
 .SH AUTHOR
 .rs
@@ -227,6 +226,6 @@ taken it away. If you want to email me, use my initial and surname, separated
 by a dot, at the domain ucs.cam.ac.uk.
 .sp
 .in 0
-Last updated: 07 March 2005
+Last updated: 24 January 2006
 .br
-Copyright (c) 1997-2005 University of Cambridge.
+Copyright (c) 1997-2006 University of Cambridge.