https://bugs.exim.org/show_bug.cgi?id=2657
Bug ID: 2657
Summary: Fix typos in documentation
Product: PCRE
Version: 8.44
Hardware: All
OS: All
Status: NEW
Severity: bug
Priority: medium
Component: Documentation
Assignee: philip.ha...@gmail.com
Reporter: feri...@riseup.net
CC: pcre-dev@exim.org
diff -Naur pcre-8.44/doc/html/pcredemo.html~ pcre-8.44/doc/html/pcredemo.html
--- pcre-8.44/doc/html/pcredemo.html~ 2020-02-12 17:35:18.000000000 +0000
+++ pcre-8.44/doc/html/pcredemo.html 2020-10-03 11:59:46.893325570 +0000
@@ -161,7 +161,7 @@
return 1;
}
-/* Match succeded */
+/* Match succeeded */
printf("\nMatch succeeded at offset %d\n", ovector[0]);
@@ -379,7 +379,7 @@
return 1;
}
- /* Match succeded */
+ /* Match succeeded */
printf("\nMatch succeeded again at offset %d\n", ovector[0]);
diff -Naur pcre-8.44/doc/html/pcrejit.html~ pcre-8.44/doc/html/pcrejit.html
--- pcre-8.44/doc/html/pcrejit.html~ 2020-02-12 17:35:18.000000000 +0000
+++ pcre-8.44/doc/html/pcrejit.html 2020-10-03 11:59:46.894325581 +0000
@@ -299,7 +299,7 @@
This is a suggestion for how a multithreaded program that needs to set up
non-default JIT stacks might operate:
<pre>
- During thread initalization
+ During thread initialization
thread_local_var = pcre_jit_stack_alloc(...)
During thread exit
diff -Naur pcre-8.44/doc/html/pcrepattern.html~
pcre-8.44/doc/html/pcrepattern.html
--- pcre-8.44/doc/html/pcrepattern.html~ 2020-02-12 17:35:18.000000000
+0000
+++ pcre-8.44/doc/html/pcrepattern.html 2020-10-03 11:59:46.905325703 +0000
@@ -655,7 +655,7 @@
<P>
It is possible to restrict \R to match only CR, LF, or CRLF (instead of the
complete set of Unicode line endings) by setting the option PCRE_BSR_ANYCRLF
-either at compile time or when the pattern is matched. (BSR is an abbrevation
+either at compile time or when the pattern is matched. (BSR is an abbreviation
for "backslash R".) This can be made the default when PCRE is built; if this
is
the case, the other behaviour can be requested via the PCRE_BSR_UNICODE
option.
It is also possible to specify these settings by starting a pattern string
with
@@ -972,7 +972,7 @@
3. Do not break Hangul (a Korean script) syllable sequences. Hangul characters
are of five types: L, V, T, LV, and LVT. An L character may be followed by an
L, V, LV, or LVT character; an LV or V character may be followed by a V or T
-character; an LVT or T character may be follwed only by a T character.
+character; an LVT or T character may be followed only by a T character.
</P>
<P>
4. Do not end before extending characters or spacing marks. Characters with
@@ -1574,7 +1574,7 @@
2, and 3, respectively.
</P>
<P>
-The fact that plain parentheses fulfil two functions is not always helpful.
+The fact that plain parentheses fulfill two functions is not always helpful.
There are often times when a grouping subpattern is required without a
capturing requirement. If an opening parenthesis is followed by a question
mark
and a colon, the subpattern does not do any capturing, and is not counted when
@@ -3080,7 +3080,7 @@
</pre>
If the subject is "aaaac...", after the first match attempt fails (starting at
the first character in the string), the starting point skips on to start the
-next attempt at "c". Note that a possessive quantifer does not have the same
+next attempt at "c". Note that a possessive quantifier does not have the same
effect as this example; although it would suppress backtracking during the
first match attempt, the second attempt would start at the second character
instead of skipping on to "c".
diff -Naur pcre-8.44/doc/pcreapi.3~ pcre-8.44/doc/pcreapi.3
--- pcre-8.44/doc/pcreapi.3~ 2019-07-22 11:10:08.000000000 +0000
+++ pcre-8.44/doc/pcreapi.3 2020-10-03 11:59:46.897325615 +0000
@@ -1699,7 +1699,7 @@
.P
The default value for the limit can be set when PCRE is built; the default
default is 10 million, which handles all but the most extreme cases. You can
-override the default by suppling \fBpcre_exec()\fP with a \fBpcre_extra\fP
+override the default by supplying \fBpcre_exec()\fP with a \fBpcre_extra\fP
block in which \fImatch_limit\fP is set, and PCRE_EXTRA_MATCH_LIMIT is set in
the \fIflags\fP field. If the limit is exceeded, \fBpcre_exec()\fP returns
PCRE_ERROR_MATCHLIMIT.
@@ -1726,7 +1726,7 @@
.P
The default value for \fImatch_limit_recursion\fP can be set when PCRE is
built; the default default is the same value as the default for
-\fImatch_limit\fP. You can override the default by suppling \fBpcre_exec()\fP
+\fImatch_limit\fP. You can override the default by supplying \fBpcre_exec()\fP
with a \fBpcre_extra\fP block in which \fImatch_limit_recursion\fP is set, and
PCRE_EXTRA_MATCH_LIMIT_RECURSION is set in the \fIflags\fP field. If the limit
is exceeded, \fBpcre_exec()\fP returns PCRE_ERROR_RECURSIONLIMIT.
@@ -2044,9 +2044,9 @@
.sp
which finds occurrences of "iss" in the middle of words. (\eB matches only if
the current position in the subject is not a word boundary.) When applied to
-the string "Mississipi" the first call to \fBpcre_exec()\fP finds the first
+the string "Mississippi" the first call to \fBpcre_exec()\fP finds the first
occurrence. If \fBpcre_exec()\fP is called again with just the remainder of
the
-subject, namely "issipi", it does not match, because \eB is always false at
the
+subject, namely "issippi", it does not match, because \eB is always false at
the
start of the subject, which is deemed to be a word boundary. However, if
\fBpcre_exec()\fP is passed the entire string again, but with
\fIstartoffset\fP
set to 4, it finds the second occurrence of "iss" because it is able to look
diff -Naur pcre-8.44/doc/pcredemo.3~ pcre-8.44/doc/pcredemo.3
--- pcre-8.44/doc/pcredemo.3~ 2020-02-12 17:35:17.000000000 +0000
+++ pcre-8.44/doc/pcredemo.3 2020-10-03 11:59:46.897325615 +0000
@@ -161,7 +161,7 @@
return 1;
}
-/* Match succeded */
+/* Match succeeded */
printf("\enMatch succeeded at offset %d\en", ovector[0]);
@@ -379,7 +379,7 @@
return 1;
}
- /* Match succeded */
+ /* Match succeeded */
printf("\enMatch succeeded again at offset %d\en", ovector[0]);
diff -Naur pcre-8.44/doc/pcrejit.3~ pcre-8.44/doc/pcrejit.3
--- pcre-8.44/doc/pcrejit.3~ 2017-07-05 10:27:56.000000000 +0000
+++ pcre-8.44/doc/pcrejit.3 2020-10-03 11:59:46.898325626 +0000
@@ -285,7 +285,7 @@
This is a suggestion for how a multithreaded program that needs to set up
non-default JIT stacks might operate:
.sp
- During thread initalization
+ During thread initialization
thread_local_var = pcre_jit_stack_alloc(...)
.sp
During thread exit
diff -Naur pcre-8.44/doc/pcrepattern.3~ pcre-8.44/doc/pcrepattern.3
--- pcre-8.44/doc/pcrepattern.3~ 2016-12-12 11:03:00.000000000 +0000
+++ pcre-8.44/doc/pcrepattern.3 2020-10-03 11:59:46.906325714 +0000
@@ -656,7 +656,7 @@
.P
It is possible to restrict \eR to match only CR, LF, or CRLF (instead of the
complete set of Unicode line endings) by setting the option PCRE_BSR_ANYCRLF
-either at compile time or when the pattern is matched. (BSR is an abbrevation
+either at compile time or when the pattern is matched. (BSR is an abbreviation
for "backslash R".) This can be made the default when PCRE is built; if this
is
the case, the other behaviour can be requested via the PCRE_BSR_UNICODE
option.
It is also possible to specify these settings by starting a pattern string
with
@@ -968,7 +968,7 @@
3. Do not break Hangul (a Korean script) syllable sequences. Hangul characters
are of five types: L, V, T, LV, and LVT. An L character may be followed by an
L, V, LV, or LVT character; an LV or V character may be followed by a V or T
-character; an LVT or T character may be follwed only by a T character.
+character; an LVT or T character may be followed only by a T character.
.P
4. Do not end before extending characters or spacing marks. Characters with
the "mark" property always have the "extend" grapheme breaking property.
@@ -1574,7 +1574,7 @@
the captured substrings are "red king", "red", and "king", and are numbered 1,
2, and 3, respectively.
.P
-The fact that plain parentheses fulfil two functions is not always helpful.
+The fact that plain parentheses fulfill two functions is not always helpful.
There are often times when a grouping subpattern is required without a
capturing requirement. If an opening parenthesis is followed by a question
mark
and a colon, the subpattern does not do any capturing, and is not counted when
@@ -3115,7 +3115,7 @@
.sp
If the subject is "aaaac...", after the first match attempt fails (starting at
the first character in the string), the starting point skips on to start the
-next attempt at "c". Note that a possessive quantifer does not have the same
+next attempt at "c". Note that a possessive quantifier does not have the same
effect as this example; although it would suppress backtracking during the
first match attempt, the second attempt would start at the second character
instead of skipping on to "c".
diff -Naur pcre-8.44/doc/pcresyntax.3~ pcre-8.44/doc/pcresyntax.3
--- pcre-8.44/doc/pcresyntax.3~ 2014-06-20 11:26:05.000000000 +0000
+++ pcre-8.44/doc/pcresyntax.3 2020-10-03 11:59:46.900325648 +0000
@@ -123,7 +123,7 @@
Xan Alphanumeric: union of properties L and N
Xps POSIX space: property Z or tab, NL, VT, FF, CR
Xsp Perl space: property Z or tab, NL, VT, FF, CR
- Xuc Univerally-named character: one that can be
+ Xuc Universally-named character: one that can be
represented by a Universal Character Name
Xwd Perl word: property Xan or underscore
.sp
diff -Naur pcre-8.44/doc/pcre.txt~ pcre-8.44/doc/pcre.txt
--- pcre-8.44/doc/pcre.txt~ 2020-02-12 17:35:18.000000000 +0000
+++ pcre-8.44/doc/pcre.txt 2020-10-03 11:59:46.910325758 +0000
@@ -3155,7 +3155,7 @@
The default value for the limit can be set when PCRE is built; the de-
fault default is 10 million, which handles all but the most extreme
- cases. You can override the default by suppling pcre_exec() with a
+ cases. You can override the default by supplying pcre_exec() with a
pcre_extra block in which match_limit is set, and PCRE_EX-
TRA_MATCH_LIMIT is set in the flags field. If the limit is exceeded,
pcre_exec() returns PCRE_ERROR_MATCHLIMIT.
@@ -3183,7 +3183,7 @@
The default value for match_limit_recursion can be set when PCRE is
built; the default default is the same value as the default for
- match_limit. You can override the default by suppling pcre_exec() with
+ match_limit. You can override the default by supplying pcre_exec() with
a pcre_extra block in which match_limit_recursion is set, and PCRE_EX-
TRA_MATCH_LIMIT_RECURSION is set in the flags field. If the limit is
exceeded, pcre_exec() returns PCRE_ERROR_RECURSIONLIMIT.
@@ -3475,9 +3475,9 @@
which finds occurrences of "iss" in the middle of words. (\B matches
only if the current position in the subject is not a word boundary.)
- When applied to the string "Mississipi" the first call to pcre_exec()
+ When applied to the string "Mississippi" the first call to pcre_exec()
finds the first occurrence. If pcre_exec() is called again with just
- the remainder of the subject, namely "issipi", it does not match, be-
+ the remainder of the subject, namely "issippi", it does not match, be-
cause \B is always false at the start of the subject, which is deemed
to be a word boundary. However, if pcre_exec() is passed the entire
string again, but with startoffset set to 4, it finds the second occur-
@@ -5292,11 +5292,11 @@
It is possible to restrict \R to match only CR, LF, or CRLF (instead of
the complete set of Unicode line endings) by setting the option
PCRE_BSR_ANYCRLF either at compile time or when the pattern is matched.
- (BSR is an abbrevation for "backslash R".) This can be made the default
- when PCRE is built; if this is the case, the other behaviour can be re-
- quested via the PCRE_BSR_UNICODE option. It is also possible to spec-
- ify these settings by starting a pattern string with one of the follow-
- ing sequences:
+ (BSR is an abbreviation for "backslash R".) This can be made the de-
+ fault when PCRE is built; if this is the case, the other behaviour can
+ be requested via the PCRE_BSR_UNICODE option. It is also possible to
+ specify these settings by starting a pattern string with one of the
+ following sequences:
(*BSR_ANYCRLF) CR, LF, or CRLF only
(*BSR_UNICODE) any Unicode newline sequence
@@ -5488,8 +5488,8 @@
3. Do not break Hangul (a Korean script) syllable sequences. Hangul
characters are of five types: L, V, T, LV, and LVT. An L character may
be followed by an L, V, LV, or LVT character; an LV or V character may
- be followed by a V or T character; an LVT or T character may be follwed
- only by a T character.
+ be followed by a V or T character; an LVT or T character may be fol-
+ lowed only by a T character.
4. Do not end before extending characters or spacing marks. Characters
with the "mark" property always have the "extend" grapheme breaking
@@ -6056,7 +6056,7 @@
the captured substrings are "red king", "red", and "king", and are num-
bered 1, 2, and 3, respectively.
- The fact that plain parentheses fulfil two functions is not always
+ The fact that plain parentheses fulfill two functions is not always
helpful. There are often times when a grouping subpattern is required
without a capturing requirement. If an opening parenthesis is followed
by a question mark and a colon, the subpattern does not do any captur-
@@ -7793,7 +7793,7 @@
Xan Alphanumeric: union of properties L and N
Xps POSIX space: property Z or tab, NL, VT, FF, CR
Xsp Perl space: property Z or tab, NL, VT, FF, CR
- Xuc Univerally-named character: one that can be
+ Xuc Universally-named character: one that can be
represented by a Universal Character Name
Xwd Perl word: property Xan or underscore
@@ -8571,7 +8571,7 @@
This is a suggestion for how a multithreaded program that needs to set
up non-default JIT stacks might operate:
- During thread initalization
+ During thread initialization
thread_local_var = pcre_jit_stack_alloc(...)
During thread exit
diff -Naur pcre-8.44/pcredemo.c~ pcre-8.44/pcredemo.c
--- pcre-8.44/pcredemo.c~ 2014-01-31 14:32:54.000000000 +0000
+++ pcre-8.44/pcredemo.c 2020-10-03 11:59:46.904325692 +0000
@@ -144,7 +144,7 @@
return 1;
}
-/* Match succeded */
+/* Match succeeded */
printf("\nMatch succeeded at offset %d\n", ovector[0]);
@@ -362,7 +362,7 @@
return 1;
}
- /* Match succeded */
+ /* Match succeeded */
printf("\nMatch succeeded again at offset %d\n", ovector[0]);
--
You are receiving this mail because:
You are on the CC list for the bug.
--
## List details at https://lists.exim.org/mailman/listinfo/pcre-dev
