summaryrefslogtreecommitdiff
path: root/pod/perllocale.pod
diff options
context:
space:
mode:
authorDan Book <grinnz@grinnz.com>2020-01-13 16:22:49 -0500
committerTony Cook <tony@develop-help.com>2020-01-28 14:23:34 +1100
commit028611faa42c95e8e0d93cda0301349939476d04 (patch)
tree003a16ea286ce16e21315626cb5e067206650afc /pod/perllocale.pod
parentbb84ab0e628823dd987990df941b347d0aa7875c (diff)
downloadperl-028611faa42c95e8e0d93cda0301349939476d04.tar.gz
Update links to perlrun to link to specific items
Diffstat (limited to 'pod/perllocale.pod')
-rw-r--r--pod/perllocale.pod7
1 files changed, 4 insertions, 3 deletions
diff --git a/pod/perllocale.pod b/pod/perllocale.pod
index b2053a1444..241a72e9dd 100644
--- a/pod/perllocale.pod
+++ b/pod/perllocale.pod
@@ -1533,8 +1533,8 @@ instead use the L<PerlIO::locale> module, or the L<Encode::Locale>
module, both available from CPAN. The latter module also has methods to
ease the handling of C<ARGV> and environment variables, and can be used
on individual strings. If you know that all your locales will be
-UTF-8, as many are these days, you can use the L<B<-C>|perlrun/-C>
-command line switch.
+UTF-8, as many are these days, you can use the
+L<B<-C>|perlrun/-C [numberE<sol>list]> command line switch.
This form of the pragma allows essentially seamless handling of locales
with Unicode. The collation order will be by Unicode code point order.
@@ -1610,7 +1610,8 @@ lowercase of U+0178 is itself.
The same problems ensue if you enable automatic UTF-8-ification of your
standard file handles, default C<open()> layer, and C<@ARGV> on non-ISO8859-1,
non-UTF-8 locales (by using either the B<-C> command line switch or the
-C<PERL_UNICODE> environment variable; see L<perlrun>).
+C<PERL_UNICODE> environment variable; see
+L<perlrun|perlrun/-C [numberE<sol>list]>).
Things are read in as UTF-8, which would normally imply a Unicode
interpretation, but the presence of a locale causes them to be interpreted
in that locale instead. For example, a 0xD7 code point in the Unicode