92c4c37
From 509ecc74dcbbcfabc01f4d290c9cc8b62c921ac4 Mon Sep 17 00:00:00 2001
92c4c37
From: ph10 <ph10@6239d852-aaf2-0410-a92c-79f79f948069>
92c4c37
Date: Thu, 6 Oct 2016 17:48:24 +0000
92c4c37
Subject: [PATCH] Missed typo fixed.
92c4c37
MIME-Version: 1.0
92c4c37
Content-Type: text/plain; charset=UTF-8
92c4c37
Content-Transfer-Encoding: 8bit
92c4c37
92c4c37
git-svn-id: svn://vcs.exim.org/pcre2/code/trunk@561 6239d852-aaf2-0410-a92c-79f79f948069
92c4c37
Signed-off-by: Petr Písař <ppisar@redhat.com>
92c4c37
---
92c4c37
 doc/pcre2pattern.3 | 8 ++++----
92c4c37
 1 file changed, 4 insertions(+), 4 deletions(-)
92c4c37
92c4c37
diff --git a/doc/pcre2pattern.3 b/doc/pcre2pattern.3
92c4c37
index 3cde744..f9d1f53 100644
92c4c37
--- a/doc/pcre2pattern.3
92c4c37
+++ b/doc/pcre2pattern.3
92c4c37
@@ -365,10 +365,10 @@ When PCRE2 is compiled in EBCDIC mode, \ea, \ee, \ef, \en, \er, and \et
92c4c37
 generate the appropriate EBCDIC code values. The \ec escape is processed
92c4c37
 as specified for Perl in the \fBperlebcdic\fP document. The only characters
92c4c37
 that are allowed after \ec are A-Z, a-z, or one of @, [, \e, ], ^, _, or ?. Any
92c4c37
-other character provokes a compile-time error. The sequence \e@ encodes
92c4c37
-character code 0; the letters (in either case) encode characters 1-26 (hex 01
92c4c37
-to hex 1A); [, \e, ], ^, and _ encode characters 27-31 (hex 1B to hex 1F), and
92c4c37
-\ec? becomes either 255 (hex FF) or 95 (hex 5F).
92c4c37
+other character provokes a compile-time error. The sequence \ec@ encodes
92c4c37
+character code 0; after \ec the letters (in either case) encode characters 1-26
92c4c37
+(hex 01 to hex 1A); [, \e, ], ^, and _ encode characters 27-31 (hex 1B to hex
92c4c37
+1F), and \ec? becomes either 255 (hex FF) or 95 (hex 5F).
92c4c37
 .P
92c4c37
 Thus, apart from \ec?, these escapes generate the same character code values as
92c4c37
 they do in an ASCII environment, though the meanings of the values mostly
92c4c37
-- 
92c4c37
2.7.4
92c4c37