summaryrefslogtreecommitdiff
path: root/pod/perlunifaq.pod
diff options
context:
space:
mode:
authorKarl Williamson <public@khwilliamson.com>2013-03-11 21:13:38 -0600
committerKarl Williamson <public@khwilliamson.com>2013-03-11 21:21:03 -0600
commit4b9734bf16232aac75ed56df6352c09d1caad7b3 (patch)
treeb1fe580a02d6ae63b54c758d033c9722519e86b5 /pod/perlunifaq.pod
parent020c4f9110283940e8755ca2f70f6e943b42efe3 (diff)
downloadperl-4b9734bf16232aac75ed56df6352c09d1caad7b3.tar.gz
EBCDIC has the Unicode bug too
We have not had a working modern Perl on EBCDIC for some years. When I started out, comments and code led me to conclude erroneously that natively it supported semantics for all 256 characters 0-255. It turns out that I was wrong; it natively (at least on some platforms) has the same rules (essentially none) for the characters which don't correspond to ASCII onees, as the rules for these on ASCII platforms. This commit is documentation only, mostly just removing the special mentions of EBCDIC.
Diffstat (limited to 'pod/perlunifaq.pod')
-rw-r--r--pod/perlunifaq.pod4
1 files changed, 2 insertions, 2 deletions
diff --git a/pod/perlunifaq.pod b/pod/perlunifaq.pod
index ca3a180cfd..f952d1a3f9 100644
--- a/pod/perlunifaq.pod
+++ b/pod/perlunifaq.pod
@@ -149,8 +149,8 @@ rely on the way things worked before Unicode came along. Those older
programs knew only about the ASCII character set, and so may not work
properly for additional characters. When a string is encoded in UTF-8,
Perl assumes that the program is prepared to deal with Unicode, but when
-the string isn't, Perl assumes that only ASCII (unless it is an EBCDIC
-platform) is wanted, and so those characters that are not ASCII
+the string isn't, Perl assumes that only ASCII
+is wanted, and so those characters that are not ASCII
characters aren't recognized as to what they would be in Unicode.
C<use feature 'unicode_strings'> tells Perl to treat all characters as
Unicode, whether the string is encoded in UTF-8 or not, thus avoiding