diff options
author | ph10 <ph10@6239d852-aaf2-0410-a92c-79f79f948069> | 2015-06-18 16:39:25 +0000 |
---|---|---|
committer | ph10 <ph10@6239d852-aaf2-0410-a92c-79f79f948069> | 2015-06-18 16:39:25 +0000 |
commit | e9a99c8b4a2cce0cdf8b3f8e4e87649d703fdd16 (patch) | |
tree | 15ea422f2f5886fd0db4c9d93ced760544351d1b /doc/pcre2.3 | |
parent | 1c894d888dbae3a4972c7b98c7a722dabb6ead09 (diff) | |
download | pcre2-e9a99c8b4a2cce0cdf8b3f8e4e87649d703fdd16.tar.gz |
Source and document file tidies for 10.20-RC1.
git-svn-id: svn://vcs.exim.org/pcre2/code/trunk@288 6239d852-aaf2-0410-a92c-79f79f948069
Diffstat (limited to 'doc/pcre2.3')
-rw-r--r-- | doc/pcre2.3 | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/pcre2.3 b/doc/pcre2.3 index 3fc8038..e315bbb 100644 --- a/doc/pcre2.3 +++ b/doc/pcre2.3 @@ -103,12 +103,12 @@ lose performance. .P One way of guarding against this possibility is to use the \fBpcre2_pattern_info()\fP function to check the compiled pattern's options for -PCRE2_UTF. Alternatively, you can set the PCRE2_NEVER_UTF option when calling +PCRE2_UTF. Alternatively, you can set the PCRE2_NEVER_UTF option when calling \fBpcre2_compile()\fP. This causes an compile time error if a pattern contains a UTF-setting sequence. .P -The use of Unicode properties for character types such as \ed can also be -enabled from within the pattern, by specifying "(*UCP)". This feature can be +The use of Unicode properties for character types such as \ed can also be +enabled from within the pattern, by specifying "(*UCP)". This feature can be disallowed by setting the PCRE2_NEVER_UCP option. .P If your application is one that supports UTF, be aware that validity checking |