diff options
| author | Stephen P. Potter <spp@ds.net> | 2000-11-06 13:56:43 -0500 |
|---|---|---|
| committer | Jarkko Hietaniemi <jhi@iki.fi> | 2000-11-07 00:12:54 +0000 |
| commit | 13a2d996abe42696bc5ca08abf08030d440c6148 (patch) | |
| tree | 1919c2c419a4d5a14d2cbb83e40e7f0fe6abaddf /pod/perllocale.pod | |
| parent | 9e29e5ff005da001be364f21377fa2a6364952d5 (diff) | |
| download | perl-13a2d996abe42696bc5ca08abf08030d440c6148.tar.gz | |
Pod updates
Message-Id: <200011062357.SAA18173@spotter.yi.org>
p4raw-id: //depot/perl@7585
Diffstat (limited to 'pod/perllocale.pod')
| -rw-r--r-- | pod/perllocale.pod | 19 |
1 files changed, 10 insertions, 9 deletions
diff --git a/pod/perllocale.pod b/pod/perllocale.pod index 3d9a58a007..fb93792fdc 100644 --- a/pod/perllocale.pod +++ b/pod/perllocale.pod @@ -124,8 +124,8 @@ B<The POSIX date formatting function> (strftime()) uses C<LC_TIME>. =back -C<LC_COLLATE>, C<LC_CTYPE>, and so on, are discussed further in L<LOCALE -CATEGORIES>. +C<LC_COLLATE>, C<LC_CTYPE>, and so on, are discussed further in +L<LOCALE CATEGORIES>. The default behavior is restored with the S<C<no locale>> pragma, or upon reaching the end of block enclosing C<use locale>. @@ -348,8 +348,8 @@ commands. You may see things like "en_US.ISO8859-1", but that isn't the same. In this case, try running under a locale that you can list and which somehow matches what you tried. The rules for matching locale names are a bit vague because -standardization is weak in this area. See again the L<Finding -locales> about general rules. +standardization is weak in this area. See again the +L<Finding locales> about general rules. =head2 Fixing system locale configuration @@ -580,11 +580,12 @@ The C standard defines the C<LC_MONETARY> category, but no function that is affected by its contents. (Those with experience of standards committees will recognize that the working group decided to punt on the issue.) Consequently, Perl takes no notice of it. If you really want -to use C<LC_MONETARY>, you can query its contents--see L<The localeconv -function>--and use the information that it returns in your application's -own formatting of currency amounts. However, you may well find that -the information, voluminous and complex though it may be, still does not -quite meet your requirements: currency formatting is a hard nut to crack. +to use C<LC_MONETARY>, you can query its contents--see +L<The localeconv function>--and use the information that it returns in your +application's own formatting of currency amounts. However, you may well +find that the information, voluminous and complex though it may be, still +does not quite meet your requirements: currency formatting is a hard nut +to crack. =head2 LC_TIME |