Change 13763 by jhi@alpha on 2001/12/18 20:54:28
Subject: [PATCH] pod/perluniintro.pod
From: Jeffrey Friedl <[EMAIL PROTECTED]>
Date: Tue, 18 Dec 2001 10:27:45 -0800 (PST)
Message-Id: <[EMAIL PROTECTED]>
Affected files ...
.... //depot/perl/pod/perluniintro.pod#10 edit
Differences ...
==== //depot/perl/pod/perluniintro.pod#10 (text) ====
Index: perl/pod/perluniintro.pod
--- perl/pod/perluniintro.pod.~1~ Tue Dec 18 14:00:05 2001
+++ perl/pod/perluniintro.pod Tue Dec 18 14:00:05 2001
@@ -142,7 +142,7 @@
Internally, Perl currently uses either whatever the native eight-bit
character set of the platform (for example Latin-1) or UTF-8 to encode
Unicode strings. Specifically, if all code points in the string are
-0xFF or less, Perl uses Latin-1. Otherwise, it uses UTF-8.
+0xFF or less, Perl uses the native eight-bit character set. Otherwise, it uses UTF-8.
A user of Perl does not normally need to know nor care how Perl happens
to encodes its internal strings, but it becomes relevant when outputting
@@ -164,8 +164,7 @@
binmode(STDOUT, ":utf8");
to this sample program ensures the output is completely UTF-8, and
-of course, removes the warning. Another way to achieve this is the
-L<encoding> pragma, discussed later in L</Legacy Encodings>.
+of course, removes the warning.
Perl 5.8.0 will also support Unicode on EBCDIC platforms. There the
support is somewhat harder to implement since additional conversions
End of Patch.
