summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKarl Williamson <public@khwilliamson.com>2011-04-18 21:28:07 -0600
committerKarl Williamson <public@khwilliamson.com>2011-04-18 21:45:10 -0600
commit0314f483456049570589b710f227253c48b5fb07 (patch)
tree9b929c3baab8a72773b1543bc7e7805dd7404707
parent5027a30ba7c234d69994192a1031579771161b14 (diff)
downloadperl-0314f483456049570589b710f227253c48b5fb07.tar.gz
perlunicode.pod: Nits
-rw-r--r--pod/perlunicode.pod6
1 files changed, 4 insertions, 2 deletions
diff --git a/pod/perlunicode.pod b/pod/perlunicode.pod
index a979f83942..d77c40cbbd 100644
--- a/pod/perlunicode.pod
+++ b/pod/perlunicode.pod
@@ -11,7 +11,8 @@ implement the Unicode standard or the accompanying technical reports
from cover to cover, Perl does support many Unicode features.
People who want to learn to use Unicode in Perl, should probably read
-the L<Perl Unicode tutorial, perlunitut|perlunitut>, before reading
+the L<Perl Unicode tutorial, perlunitut|perlunitut> and
+L<perluniintro>, before reading
this reference document.
Also, the use of Unicode may present security issues that aren't obvious.
@@ -90,7 +91,8 @@ without additional information from the user, Perl decides in favor of
compatibility and chooses to use byte semantics.
When C<use locale> is in effect (which overrides
-C<use feature 'unicode_strings'>), Perl uses the semantics associated
+C<use feature 'unicode_strings'> in the same scope), Perl uses the
+semantics associated
with the current locale. Otherwise, Perl uses the platform's native
byte semantics for characters whose code points are less than 256, and
Unicode semantics for those greater than 255. On EBCDIC platforms, this