diff options
author | ph10 <ph10@2f5784b3-3f2a-0410-8824-cb99058d5e15> | 2010-11-24 17:39:25 +0000 |
---|---|---|
committer | ph10 <ph10@2f5784b3-3f2a-0410-8824-cb99058d5e15> | 2010-11-24 17:39:25 +0000 |
commit | 78d4828aaa1f15dfc4b40c0f718112f6508254f8 (patch) | |
tree | 6778081b7ffe34ee20aa62245e0fa8d2b4b00ee3 /pcre_valid_utf8.c | |
parent | 1c4a198f0a69223930a4b118a35a618342d20898 (diff) | |
download | pcre-78d4828aaa1f15dfc4b40c0f718112f6508254f8.tar.gz |
Tidies of documenation and code while preparing for release.
git-svn-id: svn://vcs.exim.org/pcre/code/trunk@579 2f5784b3-3f2a-0410-8824-cb99058d5e15
Diffstat (limited to 'pcre_valid_utf8.c')
-rw-r--r-- | pcre_valid_utf8.c | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/pcre_valid_utf8.c b/pcre_valid_utf8.c index 971d92d..78a96e1 100644 --- a/pcre_valid_utf8.c +++ b/pcre_valid_utf8.c @@ -72,19 +72,19 @@ Arguments: Returns: < 0 if the string is a valid UTF-8 string >= 0 otherwise; the value is the offset of the bad byte - + Bad bytes can be: . An isolated byte whose most significant bits are 0x80, because this can only correctly appear within a UTF-8 character; - + . A byte whose most significant bits are 0xc0, but whose other bits indicate - that there are more than 3 additional bytes (i.e. an RFC 2279 starting + that there are more than 3 additional bytes (i.e. an RFC 2279 starting byte, which is no longer valid under RFC 3629); - + . - -The returned offset may also be equal to the length of the string; this means + +The returned offset may also be equal to the length of the string; this means that one or more bytes is missing from the final UTF-8 character. */ |