/[pcre]/code/trunk/doc/pcreunicode.3
ViewVC logotype

Diff of /code/trunk/doc/pcreunicode.3

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 683 by ph10, Tue Sep 6 10:37:15 2011 UTC revision 691 by ph10, Sun Sep 11 14:31:21 2011 UTC
# Line 12  the code, and, in addition, you must cal Line 12  the code, and, in addition, you must cal
12  with the PCRE_UTF8 option flag, or the pattern must start with the sequence  with the PCRE_UTF8 option flag, or the pattern must start with the sequence
13  (*UTF8). When either of these is the case, both the pattern and any subject  (*UTF8). When either of these is the case, both the pattern and any subject
14  strings that are matched against it are treated as UTF-8 strings instead of  strings that are matched against it are treated as UTF-8 strings instead of
15  strings of 1-byte characters. PCRE does not support any other formats (in  strings of 1-byte characters. PCRE does not support any other formats (in
16  particular, it does not support UTF-16).  particular, it does not support UTF-16).
17  .P  .P
18  If you compile PCRE with UTF-8 support, but do not use it at run time, the  If you compile PCRE with UTF-8 support, but do not use it at run time, the
# Line 81  program may crash. Line 81  program may crash.
81  If you want to process strings of values in the full range 0 to 0x7FFFFFFF,  If you want to process strings of values in the full range 0 to 0x7FFFFFFF,
82  encoded in a UTF-8-like manner as per the old RFC, you can set  encoded in a UTF-8-like manner as per the old RFC, you can set
83  PCRE_NO_UTF8_CHECK to bypass the more restrictive test. However, in this  PCRE_NO_UTF8_CHECK to bypass the more restrictive test. However, in this
84  situation, you will have to apply your own validity check, and avoid the use of  situation, you will have to apply your own validity check, and avoid the use of
85  JIT optimization.  JIT optimization.
86  .  .
87  .  .
# Line 101  bytes, for example: \ex{100}{3}. Line 101  bytes, for example: \ex{100}{3}.
101  .P  .P
102  5. 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,
103  but its use can lead to some strange effects. This facility is not available in  but its use can lead to some strange effects. This facility is not available in
104  the alternative matching function, \fBpcre_dfa_exec()\fP, nor is it supported  the alternative matching function, \fBpcre_dfa_exec()\fP, nor is it supported
105  by the JIT optimization of \fBpcre_exec()\fP. If JIT optimization is requested  by the JIT optimization of \fBpcre_exec()\fP. If JIT optimization is requested
106  for a pattern that contains \eC, it will not succeed, and so the matching will  for a pattern that contains \eC, it will not succeed, and so the matching will
107  be carried out by the normal interpretive function.  be carried out by the normal interpretive function.
108  .P  .P
109  6. 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
Legend:
Removed from v.683  
changed lines
  Added in v.691
webmaster@exim.org
 ViewVC Help
Powered by ViewVC 1.1.12