summaryrefslogtreecommitdiff
path: root/pod
diff options
context:
space:
mode:
authorKarl Williamson <public@khwilliamson.com>2011-04-18 21:35:33 -0600
committerKarl Williamson <public@khwilliamson.com>2011-04-18 21:45:10 -0600
commitafba153847998f7056cb1eb03e5b36c87f9b074a (patch)
treecb0e1e03a957710ff30b5c6e035edb4d97853fd7 /pod
parent0314f483456049570589b710f227253c48b5fb07 (diff)
downloadperl-afba153847998f7056cb1eb03e5b36c87f9b074a.tar.gz
perluniintro: Update for 5.14 changes
Diffstat (limited to 'pod')
-rw-r--r--pod/perluniintro.pod13
1 files changed, 10 insertions, 3 deletions
diff --git a/pod/perluniintro.pod b/pod/perluniintro.pod
index ac12109b75..3fbff0024f 100644
--- a/pod/perluniintro.pod
+++ b/pod/perluniintro.pod
@@ -544,7 +544,8 @@ L<Unicode Normalization Forms|http://www.unicode.org/unicode/reports/tr15> and
sections on case mapping in the L<Unicode Standard|http://www.unicode.org>.
As of Perl 5.8.0, the "Full" case-folding of I<Case
-Mappings/SpecialCasing> is implemented, but bugs remain in C<qr//i> with them.
+Mappings/SpecialCasing> is implemented, but bugs remain in C<qr//i> with them,
+mostly fixed by 5.14.
=item *
@@ -784,8 +785,14 @@ L<http://www.cl.cam.ac.uk/~mgk25/unicode.html>
How Does Unicode Work With Traditional Locales?
-In Perl, not very well. Avoid using locales through the C<locale>
-pragma. Use only one or the other. But see L<perlrun> for the
+Perl tries to keep the two separated. Code points that are above 255
+are treated as Unicode; those below 256, generally as locale. This
+works reasonably well except in some case-insensitive regular expression
+pattern matches that in Unicode would cross the 255/256 boundary. These
+are disallowed.
+Also, the C<\p{}> and C<\N{}> constructs silently assume Unicode values
+even for code points below 256.
+See also L<perlrun> for the
description of the C<-C> switch and its environment counterpart,
C<$ENV{PERL_UNICODE}> to see how to enable various Unicode features,
for example by using locale settings.