Make --enable-unicode the default.

git-svn-id: svn://vcs.exim.org/pcre2/code/trunk@132 6239d852-aaf2-0410-a92c-79f79f948069

1 files changed, 16 insertions, 19 deletions

diff --git a/doc/pcre2build.3 b/doc/pcre2build.3
index 561cc35..a8391e8 100644
--- a/doc/pcre2build.3
+++ b/doc/pcre2build.3
@@ -1,4 +1,4 @@
-.TH PCRE2BUILD 3 "28 Sepember 2014" "PCRE2 10.00"
+.TH PCRE2BUILD 3 "03 November 2014" "PCRE2 10.00"
 .SH NAME
 PCRE2 - Perl-compatible regular expressions (revised API)
 .
@@ -102,25 +102,22 @@ to the \fBconfigure\fP command, as required.
 .SH "Unicode and UTF SUPPORT"
 .rs
 .sp
-To build PCRE2 with support for Unicode and UTF character strings, add
+By default, PCRE2 is built with support for Unicode and UTF character strings.
+To build it without Unicode support, add
 .sp
-  --enable-unicode
+  --disable-unicode
 .sp
-to the \fBconfigure\fP command. This setting applies to all three libraries,
-adding support for UTF-8 to the 8-bit library, support for UTF-16 to the 16-bit
-library, and support for UTF-32 to the to the 32-bit library.
-It is not possible to build one library with
-UTF support and another without in the same configuration.
+to the \fBconfigure\fP command. This setting applies to all three libraries. It
+is not possible to build one library with Unicode support, and another without,
+in the same configuration.
 .P
-Of itself, this setting does not make PCRE2 treat strings as UTF-8, UTF-16 or
-UTF-32. As well as compiling PCRE2 with this option, you also have have to set
-the PCRE2_UTF option when you call \fBpcre2_compile()\fP to compile a pattern.
+Of itself, Unicode support does not make PCRE2 treat strings as UTF-8, UTF-16
+or UTF-32. To do that you have have to set the PCRE2_UTF option when you call
+\fBpcre2_compile()\fP to compile a pattern.
 .P
-If you set --enable-unicode when compiling in an EBCDIC environment, PCRE2
-expects its input to be either ASCII or UTF-8 (depending on the run-time
-option). It is not possible to support both EBCDIC and UTF-8 codes in the same
-version of the library. Consequently, --enable-unicode and --enable-ebcdic are
-mutually exclusive.
+It is not possible to support both EBCDIC and UTF-8 codes in the same version
+of the library. Consequently, --enable-unicode and --enable-ebcdic are mutually
+exclusive.
 .P
 UTF support allows the libraries to process character codepoints up to 0x10ffff
 in the strings that they handle. It also provides support for accessing the
@@ -306,12 +303,12 @@ code is ASCII (or Unicode, which is a superset of ASCII). This is the case for
 most computer operating systems. PCRE2 can, however, be compiled to run in an
 EBCDIC environment by adding
 .sp
-  --enable-ebcdic
+  --enable-ebcdic --disable-unicode
 .sp
 to the \fBconfigure\fP command. This setting implies
 --enable-rebuild-chartables. You should only use it if you know that you are in
 an EBCDIC environment (for example, an IBM mainframe operating system). The
---enable-ebcdic option is incompatible with --enable-unicode.
+--enable-ebcdic option is incompatible with Unicode support.
 .P
 The EBCDIC character that corresponds to an ASCII LF is assumed to have the
 value 0x15 by default. However, in some EBCDIC environments, 0x25 is used. In
@@ -485,6 +482,6 @@ Cambridge CB2 3QH, England.
 .rs
 .sp
 .nf
-Last updated: 28 September 2014
+Last updated: 03 November 2014
 Copyright (c) 1997-2014 University of Cambridge.
 .fi