384 |
</b><br> |
</b><br> |
385 |
<P> |
<P> |
386 |
When PCRE is built with Unicode character property support, three additional |
When PCRE is built with Unicode character property support, three additional |
387 |
escape sequences to match character properties are available when UTF-8 mode |
escape sequences that match characters with specific properties are available. |
388 |
is selected. They are: |
When not in UTF-8 mode, these sequences are of course limited to testing |
389 |
|
characters whose codepoints are less than 256, but they do work in this mode. |
390 |
|
The extra escape sequences are: |
391 |
<pre> |
<pre> |
392 |
\p{<i>xx</i>} a character with the <i>xx</i> property |
\p{<i>xx</i>} a character with the <i>xx</i> property |
393 |
\P{<i>xx</i>} a character without the <i>xx</i> property |
\P{<i>xx</i>} a character without the <i>xx</i> property |
568 |
atomic group |
atomic group |
569 |
<a href="#atomicgroup">(see below).</a> |
<a href="#atomicgroup">(see below).</a> |
570 |
Characters with the "mark" property are typically accents that affect the |
Characters with the "mark" property are typically accents that affect the |
571 |
preceding character. |
preceding character. None of them have codepoints less than 256, so in |
572 |
|
non-UTF-8 mode \X matches any one character. |
573 |
</P> |
</P> |
574 |
<P> |
<P> |
575 |
Matching characters by Unicode property is not fast, because PCRE has to search |
Matching characters by Unicode property is not fast, because PCRE has to search |
1990 |
</P> |
</P> |
1991 |
<br><a name="SEC25" href="#TOC1">REVISION</a><br> |
<br><a name="SEC25" href="#TOC1">REVISION</a><br> |
1992 |
<P> |
<P> |
1993 |
Last updated: 13 June 2007 |
Last updated: 19 June 2007 |
1994 |
<br> |
<br> |
1995 |
Copyright © 1997-2007 University of Cambridge. |
Copyright © 1997-2007 University of Cambridge. |
1996 |
<br> |
<br> |