sigmasternchen/php-doc-en
1
0
Fork 0
mirror of https://github.com/sigmasternchen/php-doc-en synced 2025-03-16 00:48:54 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Updated to show that, yes, 'caseless' and 'case-insensitive' are the same thing.

Browse source 
git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@277112 c90b9560-bf6c-de11-be94-00142212c4b1
This commit is contained in:
Daniel P. Brown 2009-03-13 16:05:09 +00:00
parent 08ab232bdc
commit 082b624991
1 changed files with 16 additions and 15 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

31
reference/pcre/pattern.syntax.xml
View file

@ -1,5 +1,5 @@
<?xml version="1.0" encoding="iso-8859-1"?>
<!-- $Revision: 1.24 $ -->
<!-- $Revision: 1.25 $ -->
<!-- splitted from ./en/functions/pcre.xml, last change in rev 1.2 -->
<chapter xml:id="reference.pcre.pattern.syntax" xmlns="http://docbook.org/ns/docbook">
<title>Pattern Syntax</title>
@ -580,7 +580,7 @@
supported by PCRE.
</para>
<para>
Specifying caseless matching does not affect these escape sequences.
Specifying case-insensitive (caseless) matching does not affect these escape sequences.
For example, <literal>\p{Lu}</literal> always matches only upper case letters.
</para>
<para>
@ -713,11 +713,11 @@
the string.
</para>
<para>
When caseless matching is set, any letters in a class
represent both their upper case and lower case versions, so
for example, a caseless [aeiou] matches "A" as well as "a",
and a caseless [^aeiou] does not match "A", whereas a
caseful version would.
When case-insensitive (caseless) matching is set, any letters
in a class represent both their upper case and lower case
versions, so for example, an insensitive [aeiou] matches "A"
as well as "a", and an insensitive [^aeiou] does not match
"A", whereas a sensitive (caseful) version would.
</para>
<para>
The newline character is never treated in any special way in
@ -750,11 +750,11 @@
Ranges operate in ASCII collating sequence. They can also be
used for characters specified numerically, for example
[\000-\037]. If a range that includes letters is used when
caseless matching is set, it matches the letters in either
case. For example, [W-c] is equivalent to [][\^_`wxyzabc],
matched caselessly, and if character tables for the "fr"
locale are in use, [\xc8-\xcb] matches accented E characters
in both cases.
case-insensitive (caseless) matching is set, it matches the
letters in either case. For example, [W-c] is equivalent to
[][\^_`wxyzabc], matched case-insensitively, and if character
tables for the "fr" locale are in use, [\xc8-\xcb] matches
accented E characters in both cases.
</para>
<para>
The character types \d, \D, \s, \S, \w, and \W may also
@ -842,7 +842,7 @@
</table>
</para>
<para>
For example, (?im) sets caseless, multiline matching. It is
For example, (?im) sets case-insensitive (caseless), multiline matching. It is
also possible to unset these options by preceding the letter
with a hyphen, and a combined setting and unsetting such as
(?im-sx), which sets <link
@ -1185,14 +1185,15 @@
<literal>(sens|respons)e and \1ibility</literal>
matches "sense and sensibility" and "response and responsibility",
but not "sense and responsibility". If caseful
but not "sense and responsibility". If case-sensitive (caseful)
matching is in force at the time of the back reference, then
the case of letters is relevant. For example,
<literal>((?i)rah)\s+\1</literal>
matches "rah rah" and "RAH RAH", but not "RAH rah", even
though the original capturing subpattern is matched caselessly.
though the original capturing subpattern is matched
case-insensitively (caselessly).
</para>
<para>
There may be more than one back reference to the same subpattern.