| 344 |
\et tab (\ex09) |
\et tab (\ex09) |
| 345 |
\ev vertical tab (\ex0b) |
\ev vertical tab (\ex0b) |
| 346 |
\ennn octal character (up to 3 octal digits) |
\ennn octal character (up to 3 octal digits) |
| 347 |
\exhh hexadecimal character (up to 2 hex digits) |
always a byte unless > 255 in UTF-8 mode |
| 348 |
|
\exhh hexadecimal byte (up to 2 hex digits) |
| 349 |
.\" JOIN |
.\" JOIN |
| 350 |
\ex{hh...} hexadecimal character, any number of digits |
\ex{hh...} hexadecimal character, any number of digits |
| 351 |
in UTF-8 mode |
in UTF-8 mode |
| 435 |
\e<any> pass the PCRE_NEWLINE_ANY option to \fBpcre_exec()\fP |
\e<any> pass the PCRE_NEWLINE_ANY option to \fBpcre_exec()\fP |
| 436 |
or \fBpcre_dfa_exec()\fP |
or \fBpcre_dfa_exec()\fP |
| 437 |
.sp |
.sp |
| 438 |
|
Note that \exhh always specifies one byte, even in UTF-8 mode; this makes it |
| 439 |
|
possible to construct invalid UTF-8 sequences for testing purposes. On the |
| 440 |
|
other hand, \ex{hh} is interpreted as a UTF-8 character in UTF-8 mode, |
| 441 |
|
generating more than one byte if the value is greater than 127. When not in |
| 442 |
|
UTF-8 mode, it generates one byte for values less than 256, and causes an error |
| 443 |
|
for greater values. |
| 444 |
|
.P |
| 445 |
The escapes that specify line ending sequences are literal strings, exactly as |
The escapes that specify line ending sequences are literal strings, exactly as |
| 446 |
shown. No more than one newline setting should be present in any data line. |
shown. No more than one newline setting should be present in any data line. |
| 447 |
.P |
.P |
| 778 |
.rs |
.rs |
| 779 |
.sp |
.sp |
| 780 |
.nf |
.nf |
| 781 |
Last updated: 06 November 2010 |
Last updated: 07 November 2010 |
| 782 |
Copyright (c) 1997-2010 University of Cambridge. |
Copyright (c) 1997-2010 University of Cambridge. |
| 783 |
.fi |
.fi |