summaryrefslogtreecommitdiff
path: root/pcre_valid_utf8.c
diff options
context:
space:
mode:
authorph10 <ph10@2f5784b3-3f2a-0410-8824-cb99058d5e15>2007-12-29 16:50:30 +0000
committerph10 <ph10@2f5784b3-3f2a-0410-8824-cb99058d5e15>2007-12-29 16:50:30 +0000
commitc70cd335a19ef1aec5bf5e5af58318b6e951fc40 (patch)
tree9219d6161764f30cc10df556c6f21dea75effd2f /pcre_valid_utf8.c
parent92415e846a548487639644948cfad38032ba1c8e (diff)
downloadpcre-c70cd335a19ef1aec5bf5e5af58318b6e951fc40.tar.gz
Fix typo in comment.
git-svn-id: svn://vcs.exim.org/pcre/code/trunk@293 2f5784b3-3f2a-0410-8824-cb99058d5e15
Diffstat (limited to 'pcre_valid_utf8.c')
-rw-r--r--pcre_valid_utf8.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/pcre_valid_utf8.c b/pcre_valid_utf8.c
index 1899142..834ea6e 100644
--- a/pcre_valid_utf8.c
+++ b/pcre_valid_utf8.c
@@ -62,7 +62,7 @@ an invalid string are then undefined.
Originally, this function checked according to RFC 2279, allowing for values in
the range 0 to 0x7fffffff, up to 6 bytes long, but ensuring that they were in
the canonical format. Once somebody had pointed out RFC 3629 to me (it
-obsoletes 2279), additional restrictions were applies. The values are now
+obsoletes 2279), additional restrictions were applied. The values are now
limited to be between 0 and 0x0010ffff, no more than 4 bytes long, and the
subrange 0xd000 to 0xdfff is excluded.