Commit | Line | Data |
---|---|---|
66cbab2c KW |
1 | =encoding utf8 |
2 | ||
5f05dabc | 3 | =head1 NAME |
4 | ||
b0c42ed9 | 5 | perllocale - Perl locale handling (internationalization and localization) |
5f05dabc | 6 | |
7 | =head1 DESCRIPTION | |
8 | ||
66cbab2c KW |
9 | In the beginning there was ASCII, the "American Standard Code for |
10 | Information Interchange", which works quite well for Americans with | |
11 | their English alphabet and dollar-denominated currency. But it doesn't | |
12 | work so well even for other English speakers, who may use different | |
13 | currencies, such as the pound sterling (as the symbol for that currency | |
14 | is not in ASCII); and it's hopelessly inadequate for many of the | |
15 | thousands of the world's other languages. | |
16 | ||
17 | To address these deficiencies, the concept of locales was invented | |
18 | (formally the ISO C, XPG4, POSIX 1.c "locale system"). And applications | |
19 | were and are being written that use the locale mechanism. The process of | |
20 | making such an application take account of its users' preferences in | |
21 | these kinds of matters is called B<internationalization> (often | |
22 | abbreviated as B<i18n>); telling such an application about a particular | |
23 | set of preferences is known as B<localization> (B<l10n>). | |
24 | ||
39332f68 | 25 | Perl has been extended to support the locale system. This |
66cbab2c KW |
26 | is controlled per application by using one pragma, one function call, |
27 | and several environment variables. | |
28 | ||
29 | Unfortunately, there are quite a few deficiencies with the design (and | |
31f05a37 KW |
30 | often, the implementations) of locales. Unicode was invented (see |
31 | L<perlunitut> for an introduction to that) in part to address these | |
32 | design deficiencies, and nowadays, there is a series of "UTF-8 | |
33 | locales", based on Unicode. These are locales whose character set is | |
34 | Unicode, encoded in UTF-8. Starting in v5.20, Perl fully supports | |
35 | UTF-8 locales, except for sorting and string comparisions. (Use | |
36 | L<Unicode::Collate> for these.) Perl continues to support the old | |
37 | non UTF-8 locales as well. | |
38 | ||
66cbab2c KW |
39 | (Unicode is also creating C<CLDR>, the "Common Locale Data Repository", |
40 | L<http://cldr.unicode.org/> which includes more types of information than | |
41 | are available in the POSIX locale system. At the time of this writing, | |
42 | there was no CPAN module that provides access to this XML-encoded data. | |
43 | However, many of its locales have the POSIX-only data extracted, and are | |
31f05a37 KW |
44 | available as UTF-8 locales at |
45 | L<http://unicode.org/Public/cldr/latest/>.) | |
66cbab2c KW |
46 | |
47 | =head1 WHAT IS A LOCALE | |
48 | ||
49 | A locale is a set of data that describes various aspects of how various | |
50 | communities in the world categorize their world. These categories are | |
51 | broken down into the following types (some of which include a brief | |
52 | note here): | |
53 | ||
54 | =over | |
55 | ||
56 | =item Category LC_NUMERIC: Numeric formatting | |
57 | ||
58 | This indicates how numbers should be formatted for human readability, | |
59 | for example the character used as the decimal point. | |
60 | ||
61 | =item Category LC_MONETARY: Formatting of monetary amounts | |
62 | ||
63 | =for comment | |
ebc3223b | 64 | The nbsp below makes this look better (though not great) |
66cbab2c KW |
65 | |
66 | E<160> | |
67 | ||
68 | =item Category LC_TIME: Date/Time formatting | |
69 | ||
70 | =for comment | |
ebc3223b | 71 | The nbsp below makes this look better (though not great) |
66cbab2c KW |
72 | |
73 | E<160> | |
74 | ||
75 | =item Category LC_MESSAGES: Error and other messages | |
76 | ||
2619d284 | 77 | This is used by Perl itself only for accessing operating system error |
03c702c5 | 78 | messages via L<$!|perlvar/$ERRNO> and L<$^E|perlvar/$EXTENDED_OS_ERROR>. |
66cbab2c KW |
79 | |
80 | =item Category LC_COLLATE: Collation | |
81 | ||
76073c88 | 82 | This indicates the ordering of letters for comparison and sorting. |
66cbab2c KW |
83 | In Latin alphabets, for example, "b", generally follows "a". |
84 | ||
85 | =item Category LC_CTYPE: Character Types | |
86 | ||
87 | This indicates, for example if a character is an uppercase letter. | |
88 | ||
2619d284 KW |
89 | =item Other categories |
90 | ||
91 | Some platforms have other categories, dealing with such things as | |
92 | measurement units and paper sizes. None of these are used directly by | |
93 | Perl, but outside operations that Perl interacts with may use | |
4c9b78f4 | 94 | these. See L</Not within the scope of any "use locale" variant> below. |
2619d284 | 95 | |
66cbab2c KW |
96 | =back |
97 | ||
2619d284 KW |
98 | More details on the categories used by Perl are given below in L</LOCALE |
99 | CATEGORIES>. | |
66cbab2c KW |
100 | |
101 | Together, these categories go a long way towards being able to customize | |
102 | a single program to run in many different locations. But there are | |
103 | deficiencies, so keep reading. | |
5f05dabc | 104 | |
105 | =head1 PREPARING TO USE LOCALES | |
106 | ||
2619d284 KW |
107 | Perl itself will not use locales unless specifically requested to (but |
108 | again note that Perl may interact with code that does use them). Even | |
109 | if there is such a request, B<all> of the following must be true | |
b960a36e | 110 | for it to work properly: |
5f05dabc | 111 | |
112 | =over 4 | |
113 | ||
114 | =item * | |
115 | ||
116 | B<Your operating system must support the locale system>. If it does, | |
39332f68 | 117 | you should find that the C<setlocale()> function is a documented part of |
5f05dabc | 118 | its C library. |
119 | ||
120 | =item * | |
121 | ||
5a964f20 | 122 | B<Definitions for locales that you use must be installed>. You, or |
14280422 DD |
123 | your system administrator, must make sure that this is the case. The |
124 | available locales, the location in which they are kept, and the manner | |
5a964f20 TC |
125 | in which they are installed all vary from system to system. Some systems |
126 | provide only a few, hard-wired locales and do not allow more to be | |
127 | added. Others allow you to add "canned" locales provided by the system | |
128 | supplier. Still others allow you or the system administrator to define | |
14280422 | 129 | and add arbitrary locales. (You may have to ask your supplier to |
5a964f20 | 130 | provide canned locales that are not delivered with your operating |
14280422 | 131 | system.) Read your system documentation for further illumination. |
5f05dabc | 132 | |
133 | =item * | |
134 | ||
135 | B<Perl must believe that the locale system is supported>. If it does, | |
136 | C<perl -V:d_setlocale> will say that the value for C<d_setlocale> is | |
137 | C<define>. | |
138 | ||
139 | =back | |
140 | ||
141 | If you want a Perl application to process and present your data | |
142 | according to a particular locale, the application code should include | |
2ae324a7 | 143 | the S<C<use locale>> pragma (see L<The use locale pragma>) where |
5f05dabc | 144 | appropriate, and B<at least one> of the following must be true: |
145 | ||
146 | =over 4 | |
147 | ||
c052850d | 148 | =item 1 |
5f05dabc | 149 | |
66cbab2c | 150 | B<The locale-determining environment variables (see L</"ENVIRONMENT">) |
5a964f20 | 151 | must be correctly set up> at the time the application is started, either |
ef3087ec | 152 | by yourself or by whomever set up your system account; or |
5f05dabc | 153 | |
c052850d | 154 | =item 2 |
5f05dabc | 155 | |
14280422 DD |
156 | B<The application must set its own locale> using the method described in |
157 | L<The setlocale function>. | |
5f05dabc | 158 | |
159 | =back | |
160 | ||
161 | =head1 USING LOCALES | |
162 | ||
163 | =head2 The use locale pragma | |
164 | ||
2619d284 | 165 | By default, Perl itself ignores the current locale. The S<C<use locale>> |
66cbab2c | 166 | pragma tells Perl to use the current locale for some operations. |
7ee2ae1e | 167 | Starting in v5.16, there is an optional parameter to this pragma: |
66cbab2c KW |
168 | |
169 | use locale ':not_characters'; | |
170 | ||
31f05a37 KW |
171 | This parameter allows better mixing of locales and Unicode (less useful |
172 | in v5.20 and later), and is | |
66cbab2c KW |
173 | described fully in L</Unicode and UTF-8>, but briefly, it tells Perl to |
174 | not use the character portions of the locale definition, that is | |
175 | the C<LC_CTYPE> and C<LC_COLLATE> categories. Instead it will use the | |
2619d284 | 176 | native character set (extended by Unicode). When using this parameter, |
66cbab2c KW |
177 | you are responsible for getting the external character set translated |
178 | into the native/Unicode one (which it already will be if it is one of | |
179 | the increasingly popular UTF-8 locales). There are convenient ways of | |
180 | doing this, as described in L</Unicode and UTF-8>. | |
c052850d KW |
181 | |
182 | The current locale is set at execution time by | |
183 | L<setlocale()|/The setlocale function> described below. If that function | |
184 | hasn't yet been called in the course of the program's execution, the | |
66cbab2c | 185 | current locale is that which was determined by the L</"ENVIRONMENT"> in |
ebc3223b | 186 | effect at the start of the program. |
dfcc8045 | 187 | If there is no valid environment, the current locale is whatever the |
65ebb059 KW |
188 | system default has been set to. On POSIX systems, it is likely, but |
189 | not necessarily, the "C" locale. On Windows, the default is set via the | |
190 | computer's S<C<Control Panel-E<gt>Regional and Language Options>> (or its | |
191 | current equivalent). | |
c052850d KW |
192 | |
193 | The operations that are affected by locale are: | |
5f05dabc | 194 | |
195 | =over 4 | |
196 | ||
4c9b78f4 | 197 | =item B<Not within the scope of any C<"use locale"> variant> |
b960a36e | 198 | |
1d2ab946 KW |
199 | Only operations originating outside Perl should be affected, as follows: |
200 | ||
201 | =over 4 | |
202 | ||
203 | =item * | |
2619d284 | 204 | |
b38d7779 KW |
205 | The variables L<$!|perlvar/$ERRNO> (and its synonyms C<$ERRNO> and |
206 | C<$OS_ERROR>) and L<$^E|perlvar/$EXTENDED_OS_ERROR> (and its synonym | |
207 | C<$^E>) when used as strings always are in terms of the current | |
2619d284 KW |
208 | locale. |
209 | ||
1d2ab946 KW |
210 | =item * |
211 | ||
2619d284 KW |
212 | The current locale is also used when going outside of Perl with |
213 | operations like L<system()|perlfunc/system LIST> or | |
214 | L<qxE<sol>E<sol>|perlop/qxE<sol>STRINGE<sol>>, if those operations are | |
215 | locale-sensitive. | |
216 | ||
1d2ab946 KW |
217 | =item * |
218 | ||
2619d284 KW |
219 | Also Perl gives access to various C library functions through the |
220 | L<POSIX> module. Some of those functions are always affected by the | |
221 | current locale. For example, C<POSIX::strftime()> uses C<LC_TIME>; | |
222 | C<POSIX::strtod()> uses C<LC_NUMERIC>; C<POSIX::strcoll()> and | |
223 | C<POSIX::strxfrm()> use C<LC_COLLATE>; and character classification | |
224 | functions like C<POSIX::isalnum()> use C<LC_CTYPE>. All such functions | |
225 | will behave according to the current underlying locale, even if that | |
1d2ab946 | 226 | locale isn't exposed to Perl space. |
2619d284 | 227 | |
1d2ab946 KW |
228 | =item * |
229 | ||
52686f2a KW |
230 | XS modules for all categories but C<LC_NUMERIC> get the underlying |
231 | locale, and hence any C library functions they call will use that | |
232 | underlying locale. Perl always initializes C<LC_NUMERIC> to C<"C"> | |
233 | because too many modules are unable to cope with the decimal point in a | |
234 | floating point number not being a dot (it's a comma in many locales). | |
235 | But note that these modules are vulnerable because C<LC_NUMERIC> | |
236 | currently can be changed at any time by a call to the C C<set_locale()> | |
237 | by XS code or by something XS code calls, or by C<POSIX::setlocale()> by | |
238 | Perl code. This is true also for the Perl-provided lite wrappers for XS | |
239 | modules to use some C library C<printf> functions: | |
240 | C<Gconvert>, | |
9fe6720f KW |
241 | L<my_sprintf|perlapi/my_sprintf>, |
242 | L<my_snprintf|perlapi/my_snprintf>, | |
1d2ab946 | 243 | and |
9fe6720f | 244 | L<my_vsnprintf|perlapi/my_vsnprintf>. |
1d2ab946 KW |
245 | |
246 | =back | |
247 | ||
ebc3223b KW |
248 | =for comment |
249 | The nbsp below makes this look better (though not great) | |
250 | ||
251 | E<160> | |
252 | ||
253 | =item B<Lingering effects of C<S<use locale>>> | |
1d2ab946 KW |
254 | |
255 | Certain Perl operations that are set-up within the scope of a | |
b960a36e KW |
256 | C<use locale> variant retain that effect even outside the scope. |
257 | These include: | |
258 | ||
259 | =over 4 | |
260 | ||
261 | =item * | |
262 | ||
263 | The output format of a L<write()|perlfunc/write> is determined by an | |
264 | earlier format declaration (L<perlfunc/format>), so whether or not the | |
265 | output is affected by locale is determined by if the C<format()> is | |
266 | within the scope of a C<use locale> variant, not whether the C<write()> | |
267 | is. | |
268 | ||
269 | =item * | |
270 | ||
271 | Regular expression patterns can be compiled using | |
272 | L<qrE<sol>E<sol>|perlop/qrE<sol>STRINGE<sol>msixpodual> with actual | |
273 | matching deferred to later. Again, it is whether or not the compilation | |
274 | was done within the scope of C<use locale> that determines the match | |
275 | behavior, not if the matches are done within such a scope or not. | |
276 | ||
277 | =back | |
278 | ||
ebc3223b KW |
279 | =for comment |
280 | The nbsp below makes this look better (though not great) | |
281 | ||
282 | E<160> | |
283 | ||
4c9b78f4 | 284 | =item B<Under C<"use locale ':not_characters';">> |
66cbab2c KW |
285 | |
286 | =over 4 | |
287 | ||
288 | =item * | |
289 | ||
b960a36e KW |
290 | All the non-Perl operations. |
291 | ||
292 | =item * | |
293 | ||
294 | B<Format declarations> (L<perlfunc/format>) and hence any subsequent | |
295 | C<write()>s use C<LC_NUMERIC>. | |
66cbab2c KW |
296 | |
297 | =item * | |
298 | ||
b960a36e KW |
299 | B<stringification and output> use C<LC_NUMERIC>. |
300 | These include the results of | |
301 | C<print()>, | |
302 | C<printf()>, | |
303 | C<say()>, | |
304 | and | |
305 | C<sprintf()>. | |
66cbab2c KW |
306 | |
307 | =back | |
308 | ||
309 | =for comment | |
ebc3223b | 310 | The nbsp below makes this look better (though not great) |
66cbab2c KW |
311 | |
312 | E<160> | |
313 | ||
4c9b78f4 | 314 | =item B<Under just plain C<"use locale";>> |
66cbab2c | 315 | |
66cbab2c KW |
316 | =over 4 |
317 | ||
5f05dabc | 318 | =item * |
319 | ||
b960a36e KW |
320 | All the above operations |
321 | ||
322 | =item * | |
323 | ||
324 | B<The comparison operators> (C<lt>, C<le>, C<cmp>, C<ge>, and C<gt>) use | |
39332f68 | 325 | C<LC_COLLATE>. C<sort()> is also affected if used without an |
5a964f20 | 326 | explicit comparison function, because it uses C<cmp> by default. |
14280422 | 327 | |
5a964f20 | 328 | B<Note:> C<eq> and C<ne> are unaffected by locale: they always |
de108802 | 329 | perform a char-by-char comparison of their scalar operands. What's |
14280422 DD |
330 | more, if C<cmp> finds that its operands are equal according to the |
331 | collation sequence specified by the current locale, it goes on to | |
de108802 RGS |
332 | perform a char-by-char comparison, and only returns I<0> (equal) if the |
333 | operands are char-for-char identical. If you really want to know whether | |
5a964f20 | 334 | two strings--which C<eq> and C<cmp> may consider different--are equal |
14280422 DD |
335 | as far as collation in the locale is concerned, see the discussion in |
336 | L<Category LC_COLLATE: Collation>. | |
5f05dabc | 337 | |
338 | =item * | |
339 | ||
39332f68 KW |
340 | B<Regular expressions and case-modification functions> (C<uc()>, C<lc()>, |
341 | C<ucfirst()>, and C<lcfirst()>) use C<LC_CTYPE> | |
5f05dabc | 342 | |
5f05dabc | 343 | =back |
344 | ||
66cbab2c | 345 | =back |
5f05dabc | 346 | |
5a964f20 | 347 | The default behavior is restored with the S<C<no locale>> pragma, or |
ef3087ec | 348 | upon reaching the end of the block enclosing C<use locale>. |
66cbab2c KW |
349 | Note that C<use locale> and C<use locale ':not_characters'> may be |
350 | nested, and that what is in effect within an inner scope will revert to | |
351 | the outer scope's rules at the end of the inner scope. | |
5f05dabc | 352 | |
5a964f20 | 353 | The string result of any operation that uses locale |
14280422 DD |
354 | information is tainted, as it is possible for a locale to be |
355 | untrustworthy. See L<"SECURITY">. | |
5f05dabc | 356 | |
357 | =head2 The setlocale function | |
358 | ||
14280422 | 359 | You can switch locales as often as you wish at run time with the |
39332f68 | 360 | C<POSIX::setlocale()> function: |
5f05dabc | 361 | |
5f05dabc | 362 | # Import locale-handling tool set from POSIX module. |
363 | # This example uses: setlocale -- the function call | |
364 | # LC_CTYPE -- explained below | |
2619d284 KW |
365 | # (Showing the testing for success/failure of operations is |
366 | # omitted in these examples to avoid distracting from the main | |
ebc3223b | 367 | # point) |
6ea81ccf | 368 | |
5f05dabc | 369 | use POSIX qw(locale_h); |
dfcc8045 KW |
370 | use locale; |
371 | my $old_locale; | |
5f05dabc | 372 | |
14280422 | 373 | # query and save the old locale |
5f05dabc | 374 | $old_locale = setlocale(LC_CTYPE); |
375 | ||
376 | setlocale(LC_CTYPE, "fr_CA.ISO8859-1"); | |
377 | # LC_CTYPE now in locale "French, Canada, codeset ISO 8859-1" | |
378 | ||
379 | setlocale(LC_CTYPE, ""); | |
65ebb059 KW |
380 | # LC_CTYPE now reset to the default defined by the |
381 | # LC_ALL/LC_CTYPE/LANG environment variables, or to the system | |
382 | # default. See below for documentation. | |
5f05dabc | 383 | |
384 | # restore the old locale | |
385 | setlocale(LC_CTYPE, $old_locale); | |
386 | ||
39332f68 | 387 | The first argument of C<setlocale()> gives the B<category>, the second the |
14280422 DD |
388 | B<locale>. The category tells in what aspect of data processing you |
389 | want to apply locale-specific rules. Category names are discussed in | |
66cbab2c | 390 | L</LOCALE CATEGORIES> and L</"ENVIRONMENT">. The locale is the name of a |
14280422 DD |
391 | collection of customization information corresponding to a particular |
392 | combination of language, country or territory, and codeset. Read on for | |
393 | hints on the naming of locales: not all systems name locales as in the | |
394 | example. | |
395 | ||
39332f68 | 396 | If no second argument is provided and the category is something other |
502a173a JH |
397 | than LC_ALL, the function returns a string naming the current locale |
398 | for the category. You can use this value as the second argument in a | |
f170b852 KW |
399 | subsequent call to C<setlocale()>, B<but> on some platforms the string |
400 | is opaque, not something that most people would be able to decipher as | |
401 | to what locale it means. | |
502a173a JH |
402 | |
403 | If no second argument is provided and the category is LC_ALL, the | |
404 | result is implementation-dependent. It may be a string of | |
c052850d | 405 | concatenated locale names (separator also implementation-dependent) |
39332f68 | 406 | or a single locale name. Please consult your L<setlocale(3)> man page for |
502a173a JH |
407 | details. |
408 | ||
409 | If a second argument is given and it corresponds to a valid locale, | |
410 | the locale for the category is set to that value, and the function | |
411 | returns the now-current locale value. You can then use this in yet | |
39332f68 | 412 | another call to C<setlocale()>. (In some implementations, the return |
502a173a JH |
413 | value may sometimes differ from the value you gave as the second |
414 | argument--think of it as an alias for the value you gave.) | |
5f05dabc | 415 | |
416 | As the example shows, if the second argument is an empty string, the | |
417 | category's locale is returned to the default specified by the | |
418 | corresponding environment variables. Generally, this results in a | |
5a964f20 | 419 | return to the default that was in force when Perl started up: changes |
54310121 | 420 | to the environment made by the application after startup may or may not |
5a964f20 | 421 | be noticed, depending on your system's C library. |
5f05dabc | 422 | |
66cbab2c KW |
423 | Note that Perl ignores the current C<LC_CTYPE> and C<LC_COLLATE> locales |
424 | within the scope of a C<use locale ':not_characters'>. | |
425 | ||
f170b852 | 426 | If C<set_locale()> fails for some reason (for example, an attempt to set |
dfcc8045 KW |
427 | to a locale unknown to the system), the locale for the category is not |
428 | changed, and the function returns C<undef>. | |
429 | ||
2619d284 | 430 | |
39332f68 | 431 | For further information about the categories, consult L<setlocale(3)>. |
3e6e419a JH |
432 | |
433 | =head2 Finding locales | |
434 | ||
39332f68 | 435 | For locales available in your system, consult also L<setlocale(3)> to |
5a964f20 TC |
436 | see whether it leads to the list of available locales (search for the |
437 | I<SEE ALSO> section). If that fails, try the following command lines: | |
5f05dabc | 438 | |
439 | locale -a | |
440 | ||
441 | nlsinfo | |
442 | ||
443 | ls /usr/lib/nls/loc | |
444 | ||
445 | ls /usr/lib/locale | |
446 | ||
447 | ls /usr/lib/nls | |
448 | ||
b478f28d JH |
449 | ls /usr/share/locale |
450 | ||
5f05dabc | 451 | and see whether they list something resembling these |
452 | ||
2bdf8add | 453 | en_US.ISO8859-1 de_DE.ISO8859-1 ru_RU.ISO8859-5 |
502a173a | 454 | en_US.iso88591 de_DE.iso88591 ru_RU.iso88595 |
2bdf8add | 455 | en_US de_DE ru_RU |
14280422 | 456 | en de ru |
2bdf8add JH |
457 | english german russian |
458 | english.iso88591 german.iso88591 russian.iso88595 | |
502a173a | 459 | english.roman8 russian.koi8r |
5f05dabc | 460 | |
39332f68 | 461 | Sadly, even though the calling interface for C<setlocale()> has been |
528d65ad | 462 | standardized, names of locales and the directories where the |
5a964f20 | 463 | configuration resides have not been. The basic form of the name is |
528d65ad JH |
464 | I<language_territory>B<.>I<codeset>, but the latter parts after |
465 | I<language> are not always present. The I<language> and I<country> | |
466 | are usually from the standards B<ISO 3166> and B<ISO 639>, the | |
467 | two-letter abbreviations for the countries and the languages of the | |
468 | world, respectively. The I<codeset> part often mentions some B<ISO | |
469 | 8859> character set, the Latin codesets. For example, C<ISO 8859-1> | |
470 | is the so-called "Western European codeset" that can be used to encode | |
471 | most Western European languages adequately. Again, there are several | |
472 | ways to write even the name of that one standard. Lamentably. | |
5f05dabc | 473 | |
14280422 DD |
474 | Two special locales are worth particular mention: "C" and "POSIX". |
475 | Currently these are effectively the same locale: the difference is | |
5a964f20 TC |
476 | mainly that the first one is defined by the C standard, the second by |
477 | the POSIX standard. They define the B<default locale> in which | |
14280422 | 478 | every program starts in the absence of locale information in its |
5a964f20 | 479 | environment. (The I<default> default locale, if you will.) Its language |
39332f68 KW |
480 | is (American) English and its character codeset ASCII or, rarely, a |
481 | superset thereof (such as the "DEC Multinational Character Set | |
482 | (DEC-MCS)"). B<Warning>. The C locale delivered by some vendors | |
483 | may not actually exactly match what the C standard calls for. So | |
484 | beware. | |
5f05dabc | 485 | |
14280422 DD |
486 | B<NOTE>: Not all systems have the "POSIX" locale (not all systems are |
487 | POSIX-conformant), so use "C" when you need explicitly to specify this | |
488 | default locale. | |
5f05dabc | 489 | |
3e6e419a JH |
490 | =head2 LOCALE PROBLEMS |
491 | ||
5a964f20 | 492 | You may encounter the following warning message at Perl startup: |
3e6e419a JH |
493 | |
494 | perl: warning: Setting locale failed. | |
495 | perl: warning: Please check that your locale settings: | |
496 | LC_ALL = "En_US", | |
497 | LANG = (unset) | |
498 | are supported and installed on your system. | |
499 | perl: warning: Falling back to the standard locale ("C"). | |
500 | ||
5a964f20 TC |
501 | This means that your locale settings had LC_ALL set to "En_US" and |
502 | LANG exists but has no value. Perl tried to believe you but could not. | |
503 | Instead, Perl gave up and fell back to the "C" locale, the default locale | |
65ebb059 KW |
504 | that is supposed to work no matter what. (On Windows, it first tries |
505 | falling back to the system default locale.) This usually means your | |
506 | locale settings were wrong, they mention locales your system has never | |
507 | heard of, or the locale installation in your system has problems (for | |
508 | example, some system files are broken or missing). There are quick and | |
509 | temporary fixes to these problems, as well as more thorough and lasting | |
510 | fixes. | |
3e6e419a | 511 | |
83fb1bf0 KW |
512 | =head2 Testing for broken locales |
513 | ||
514 | If you are building Perl from source, the Perl test suite file | |
515 | F<lib/locale.t> can be used to test the locales on your system. | |
516 | Setting the environment variable C<PERL_DEBUG_FULL_TEST> to 1 | |
517 | will cause it to output detailed results. For example, on Linux, you | |
518 | could say | |
519 | ||
1d2ab946 | 520 | PERL_DEBUG_FULL_TEST=1 ./perl -T -Ilib lib/locale.t > locale.log 2>&1 |
83fb1bf0 KW |
521 | |
522 | Besides many other tests, it will test every locale it finds on your | |
523 | system to see if they conform to the POSIX standard. If any have | |
524 | errors, it will include a summary near the end of the output of which | |
525 | locales passed all its tests, and which failed, and why. | |
526 | ||
3e6e419a JH |
527 | =head2 Temporarily fixing locale problems |
528 | ||
5a964f20 | 529 | The two quickest fixes are either to render Perl silent about any |
3e6e419a JH |
530 | locale inconsistencies or to run Perl under the default locale "C". |
531 | ||
532 | Perl's moaning about locale problems can be silenced by setting the | |
900bd440 JH |
533 | environment variable PERL_BADLANG to a zero value, for example "0". |
534 | This method really just sweeps the problem under the carpet: you tell | |
535 | Perl to shut up even when Perl sees that something is wrong. Do not | |
536 | be surprised if later something locale-dependent misbehaves. | |
3e6e419a JH |
537 | |
538 | Perl can be run under the "C" locale by setting the environment | |
5a964f20 TC |
539 | variable LC_ALL to "C". This method is perhaps a bit more civilized |
540 | than the PERL_BADLANG approach, but setting LC_ALL (or | |
541 | other locale variables) may affect other programs as well, not just | |
542 | Perl. In particular, external programs run from within Perl will see | |
3e6e419a | 543 | these changes. If you make the new settings permanent (read on), all |
f979aebc | 544 | programs you run see the changes. See L<"ENVIRONMENT"> for |
5a964f20 | 545 | the full list of relevant environment variables and L<USING LOCALES> |
e05ffc7d | 546 | for their effects in Perl. Effects in other programs are |
5a964f20 | 547 | easily deducible. For example, the variable LC_COLLATE may well affect |
b432a672 | 548 | your B<sort> program (or whatever the program that arranges "records" |
3e6e419a JH |
549 | alphabetically in your system is called). |
550 | ||
5a964f20 TC |
551 | You can test out changing these variables temporarily, and if the |
552 | new settings seem to help, put those settings into your shell startup | |
553 | files. Consult your local documentation for the exact details. For in | |
554 | Bourne-like shells (B<sh>, B<ksh>, B<bash>, B<zsh>): | |
3e6e419a JH |
555 | |
556 | LC_ALL=en_US.ISO8859-1 | |
557 | export LC_ALL | |
558 | ||
5a964f20 TC |
559 | This assumes that we saw the locale "en_US.ISO8859-1" using the commands |
560 | discussed above. We decided to try that instead of the above faulty | |
561 | locale "En_US"--and in Cshish shells (B<csh>, B<tcsh>) | |
3e6e419a JH |
562 | |
563 | setenv LC_ALL en_US.ISO8859-1 | |
c47ff5f1 | 564 | |
c406981e JH |
565 | or if you have the "env" application you can do in any shell |
566 | ||
567 | env LC_ALL=en_US.ISO8859-1 perl ... | |
568 | ||
5a964f20 | 569 | If you do not know what shell you have, consult your local |
3e6e419a JH |
570 | helpdesk or the equivalent. |
571 | ||
572 | =head2 Permanently fixing locale problems | |
573 | ||
5a964f20 TC |
574 | The slower but superior fixes are when you may be able to yourself |
575 | fix the misconfiguration of your own environment variables. The | |
3e6e419a JH |
576 | mis(sing)configuration of the whole system's locales usually requires |
577 | the help of your friendly system administrator. | |
578 | ||
5a964f20 TC |
579 | First, see earlier in this document about L<Finding locales>. That tells |
580 | how to find which locales are really supported--and more importantly, | |
581 | installed--on your system. In our example error message, environment | |
582 | variables affecting the locale are listed in the order of decreasing | |
583 | importance (and unset variables do not matter). Therefore, having | |
584 | LC_ALL set to "En_US" must have been the bad choice, as shown by the | |
585 | error message. First try fixing locale settings listed first. | |
3e6e419a | 586 | |
5a964f20 TC |
587 | Second, if using the listed commands you see something B<exactly> |
588 | (prefix matches do not count and case usually counts) like "En_US" | |
589 | without the quotes, then you should be okay because you are using a | |
590 | locale name that should be installed and available in your system. | |
4a4eefd0 | 591 | In this case, see L<Permanently fixing your system's locale configuration>. |
3e6e419a | 592 | |
4a4eefd0 | 593 | =head2 Permanently fixing your system's locale configuration |
3e6e419a | 594 | |
5a964f20 | 595 | This is when you see something like: |
3e6e419a JH |
596 | |
597 | perl: warning: Please check that your locale settings: | |
598 | LC_ALL = "En_US", | |
599 | LANG = (unset) | |
600 | are supported and installed on your system. | |
601 | ||
602 | but then cannot see that "En_US" listed by the above-mentioned | |
5a964f20 TC |
603 | commands. You may see things like "en_US.ISO8859-1", but that isn't |
604 | the same. In this case, try running under a locale | |
605 | that you can list and which somehow matches what you tried. The | |
3e6e419a | 606 | rules for matching locale names are a bit vague because |
e05ffc7d | 607 | standardization is weak in this area. See again the |
13a2d996 | 608 | L<Finding locales> about general rules. |
3e6e419a | 609 | |
b687b08b | 610 | =head2 Fixing system locale configuration |
3e6e419a | 611 | |
5a964f20 TC |
612 | Contact a system administrator (preferably your own) and report the exact |
613 | error message you get, and ask them to read this same documentation you | |
614 | are now reading. They should be able to check whether there is something | |
615 | wrong with the locale configuration of the system. The L<Finding locales> | |
616 | section is unfortunately a bit vague about the exact commands and places | |
617 | because these things are not that standardized. | |
3e6e419a | 618 | |
5f05dabc | 619 | =head2 The localeconv function |
620 | ||
39332f68 | 621 | The C<POSIX::localeconv()> function allows you to get particulars of the |
14280422 DD |
622 | locale-dependent numeric formatting information specified by the current |
623 | C<LC_NUMERIC> and C<LC_MONETARY> locales. (If you just want the name of | |
39332f68 | 624 | the current locale for a particular category, use C<POSIX::setlocale()> |
5a964f20 | 625 | with a single parameter--see L<The setlocale function>.) |
5f05dabc | 626 | |
627 | use POSIX qw(locale_h); | |
5f05dabc | 628 | |
629 | # Get a reference to a hash of locale-dependent info | |
630 | $locale_values = localeconv(); | |
631 | ||
632 | # Output sorted list of the values | |
633 | for (sort keys %$locale_values) { | |
14280422 | 634 | printf "%-20s = %s\n", $_, $locale_values->{$_} |
5f05dabc | 635 | } |
636 | ||
39332f68 | 637 | C<localeconv()> takes no arguments, and returns B<a reference to> a hash. |
5a964f20 | 638 | The keys of this hash are variable names for formatting, such as |
502a173a | 639 | C<decimal_point> and C<thousands_sep>. The values are the |
cea6626f | 640 | corresponding, er, values. See L<POSIX/localeconv> for a longer |
502a173a JH |
641 | example listing the categories an implementation might be expected to |
642 | provide; some provide more and others fewer. You don't need an | |
39332f68 | 643 | explicit C<use locale>, because C<localeconv()> always observes the |
502a173a | 644 | current locale. |
5f05dabc | 645 | |
5a964f20 TC |
646 | Here's a simple-minded example program that rewrites its command-line |
647 | parameters as integers correctly formatted in the current locale: | |
5f05dabc | 648 | |
ef3087ec KW |
649 | use POSIX qw(locale_h); |
650 | ||
651 | # Get some of locale's numeric formatting parameters | |
652 | my ($thousands_sep, $grouping) = | |
653 | @{localeconv()}{'thousands_sep', 'grouping'}; | |
654 | ||
655 | # Apply defaults if values are missing | |
656 | $thousands_sep = ',' unless $thousands_sep; | |
657 | ||
658 | # grouping and mon_grouping are packed lists | |
659 | # of small integers (characters) telling the | |
660 | # grouping (thousand_seps and mon_thousand_seps | |
661 | # being the group dividers) of numbers and | |
662 | # monetary quantities. The integers' meanings: | |
663 | # 255 means no more grouping, 0 means repeat | |
664 | # the previous grouping, 1-254 means use that | |
665 | # as the current grouping. Grouping goes from | |
666 | # right to left (low to high digits). In the | |
667 | # below we cheat slightly by never using anything | |
668 | # else than the first grouping (whatever that is). | |
669 | if ($grouping) { | |
670 | @grouping = unpack("C*", $grouping); | |
671 | } else { | |
672 | @grouping = (3); | |
673 | } | |
674 | ||
675 | # Format command line params for current locale | |
676 | for (@ARGV) { | |
677 | $_ = int; # Chop non-integer part | |
678 | 1 while | |
679 | s/(\d)(\d{$grouping[0]}($|$thousands_sep))/$1$thousands_sep$2/; | |
680 | print "$_"; | |
681 | } | |
682 | print "\n"; | |
5f05dabc | 683 | |
74c76037 | 684 | =head2 I18N::Langinfo |
4bbcc6e8 JH |
685 | |
686 | Another interface for querying locale-dependent information is the | |
39332f68 | 687 | C<I18N::Langinfo::langinfo()> function, available at least in Unix-like |
4bbcc6e8 JH |
688 | systems and VMS. |
689 | ||
39332f68 KW |
690 | The following example will import the C<langinfo()> function itself and |
691 | three constants to be used as arguments to C<langinfo()>: a constant for | |
74c76037 JH |
692 | the abbreviated first day of the week (the numbering starts from |
693 | Sunday = 1) and two more constants for the affirmative and negative | |
694 | answers for a yes/no question in the current locale. | |
4bbcc6e8 | 695 | |
74c76037 | 696 | use I18N::Langinfo qw(langinfo ABDAY_1 YESSTR NOSTR); |
4bbcc6e8 | 697 | |
ef3087ec KW |
698 | my ($abday_1, $yesstr, $nostr) |
699 | = map { langinfo } qw(ABDAY_1 YESSTR NOSTR); | |
4bbcc6e8 | 700 | |
74c76037 | 701 | print "$abday_1? [$yesstr/$nostr] "; |
4bbcc6e8 | 702 | |
74c76037 JH |
703 | In other words, in the "C" (or English) locale the above will probably |
704 | print something like: | |
705 | ||
e05ffc7d | 706 | Sun? [yes/no] |
4bbcc6e8 JH |
707 | |
708 | See L<I18N::Langinfo> for more information. | |
709 | ||
5f05dabc | 710 | =head1 LOCALE CATEGORIES |
711 | ||
5a964f20 TC |
712 | The following subsections describe basic locale categories. Beyond these, |
713 | some combination categories allow manipulation of more than one | |
714 | basic category at a time. See L<"ENVIRONMENT"> for a discussion of these. | |
5f05dabc | 715 | |
716 | =head2 Category LC_COLLATE: Collation | |
717 | ||
66cbab2c KW |
718 | In the scope of S<C<use locale>> (but not a |
719 | C<use locale ':not_characters'>), Perl looks to the C<LC_COLLATE> | |
5a964f20 | 720 | environment variable to determine the application's notions on collation |
b4ffc3db TC |
721 | (ordering) of characters. For example, "b" follows "a" in Latin |
722 | alphabets, but where do "E<aacute>" and "E<aring>" belong? And while | |
f87fa335 | 723 | "color" follows "chocolate" in English, what about in traditional Spanish? |
5f05dabc | 724 | |
60f0fa02 JH |
725 | The following collations all make sense and you may meet any of them |
726 | if you "use locale". | |
727 | ||
728 | A B C D E a b c d e | |
35316ca3 | 729 | A a B b C c D d E e |
60f0fa02 JH |
730 | a A b B c C d D e E |
731 | a b c d e A B C D E | |
732 | ||
f1cbbd6e | 733 | Here is a code snippet to tell what "word" |
5a964f20 | 734 | characters are in the current locale, in that locale's order: |
5f05dabc | 735 | |
736 | use locale; | |
35316ca3 | 737 | print +(sort grep /\w/, map { chr } 0..255), "\n"; |
5f05dabc | 738 | |
14280422 DD |
739 | Compare this with the characters that you see and their order if you |
740 | state explicitly that the locale should be ignored: | |
5f05dabc | 741 | |
742 | no locale; | |
35316ca3 | 743 | print +(sort grep /\w/, map { chr } 0..255), "\n"; |
5f05dabc | 744 | |
745 | This machine-native collation (which is what you get unless S<C<use | |
746 | locale>> has appeared earlier in the same block) must be used for | |
747 | sorting raw binary data, whereas the locale-dependent collation of the | |
b0c42ed9 | 748 | first example is useful for natural text. |
5f05dabc | 749 | |
14280422 DD |
750 | As noted in L<USING LOCALES>, C<cmp> compares according to the current |
751 | collation locale when C<use locale> is in effect, but falls back to a | |
de108802 | 752 | char-by-char comparison for strings that the locale says are equal. You |
39332f68 | 753 | can use C<POSIX::strcoll()> if you don't want this fall-back: |
14280422 DD |
754 | |
755 | use POSIX qw(strcoll); | |
756 | $equal_in_locale = | |
757 | !strcoll("space and case ignored", "SpaceAndCaseIgnored"); | |
758 | ||
39332f68 | 759 | C<$equal_in_locale> will be true if the collation locale specifies a |
5a964f20 | 760 | dictionary-like ordering that ignores space characters completely and |
9e3a2af8 | 761 | which folds case. |
14280422 | 762 | |
31f05a37 KW |
763 | Perl only supports single-byte locales for C<LC_COLLATE>. This means |
764 | that a UTF-8 locale likely will just give you machine-native ordering. | |
765 | Use L<Unicode::Collate> for the full implementation of the Unicode | |
766 | Collation Algorithm. | |
767 | ||
5a964f20 | 768 | If you have a single string that you want to check for "equality in |
14280422 | 769 | locale" against several others, you might think you could gain a little |
39332f68 | 770 | efficiency by using C<POSIX::strxfrm()> in conjunction with C<eq>: |
14280422 DD |
771 | |
772 | use POSIX qw(strxfrm); | |
773 | $xfrm_string = strxfrm("Mixed-case string"); | |
774 | print "locale collation ignores spaces\n" | |
775 | if $xfrm_string eq strxfrm("Mixed-casestring"); | |
776 | print "locale collation ignores hyphens\n" | |
777 | if $xfrm_string eq strxfrm("Mixedcase string"); | |
778 | print "locale collation ignores case\n" | |
779 | if $xfrm_string eq strxfrm("mixed-case string"); | |
780 | ||
39332f68 | 781 | C<strxfrm()> takes a string and maps it into a transformed string for use |
de108802 | 782 | in char-by-char comparisons against other transformed strings during |
14280422 | 783 | collation. "Under the hood", locale-affected Perl comparison operators |
39332f68 KW |
784 | call C<strxfrm()> for both operands, then do a char-by-char |
785 | comparison of the transformed strings. By calling C<strxfrm()> explicitly | |
14280422 | 786 | and using a non locale-affected comparison, the example attempts to save |
5a964f20 | 787 | a couple of transformations. But in fact, it doesn't save anything: Perl |
2ae324a7 | 788 | magic (see L<perlguts/Magic Variables>) creates the transformed version of a |
5a964f20 | 789 | string the first time it's needed in a comparison, then keeps this version around |
14280422 | 790 | in case it's needed again. An example rewritten the easy way with |
e38874e2 | 791 | C<cmp> runs just about as fast. It also copes with null characters |
39332f68 | 792 | embedded in strings; if you call C<strxfrm()> directly, it treats the first |
5a964f20 TC |
793 | null it finds as a terminator. don't expect the transformed strings |
794 | it produces to be portable across systems--or even from one revision | |
39332f68 | 795 | of your operating system to the next. In short, don't call C<strxfrm()> |
e38874e2 | 796 | directly: let Perl do it for you. |
14280422 | 797 | |
5a964f20 | 798 | Note: C<use locale> isn't shown in some of these examples because it isn't |
dfcc8045 KW |
799 | needed: C<strcoll()> and C<strxfrm()> are POSIX functions |
800 | which use the standard system-supplied C<libc> functions that | |
801 | always obey the current C<LC_COLLATE> locale. | |
5f05dabc | 802 | |
803 | =head2 Category LC_CTYPE: Character Types | |
804 | ||
66cbab2c KW |
805 | In the scope of S<C<use locale>> (but not a |
806 | C<use locale ':not_characters'>), Perl obeys the C<LC_CTYPE> locale | |
14280422 | 807 | setting. This controls the application's notion of which characters are |
ebc3223b KW |
808 | alphabetic, numeric, punctuation, I<etc>. This affects Perl's C<\w> |
809 | regular expression metanotation, | |
f1cbbd6e | 810 | which stands for alphanumeric characters--that is, alphabetic, |
ebc3223b KW |
811 | numeric, and the platform's native underscore. |
812 | (Consult L<perlre> for more information about | |
14280422 | 813 | regular expressions.) Thanks to C<LC_CTYPE>, depending on your locale |
b4ffc3db TC |
814 | setting, characters like "E<aelig>", "E<eth>", "E<szlig>", and |
815 | "E<oslash>" may be understood as C<\w> characters. | |
ebc3223b KW |
816 | It also affects things like C<\s>, C<\D>, and the POSIX character |
817 | classes, like C<[[:graph:]]>. (See L<perlrecharclass> for more | |
818 | information on all these.) | |
5f05dabc | 819 | |
2c268ad5 | 820 | The C<LC_CTYPE> locale also provides the map used in transliterating |
68dc0745 | 821 | characters between lower and uppercase. This affects the case-mapping |
39332f68 | 822 | functions--C<fc()>, C<lc()>, C<lcfirst()>, C<uc()>, and C<ucfirst()>; case-mapping |
b9cc4f69 KW |
823 | interpolation with C<\F>, C<\l>, C<\L>, C<\u>, or C<\U> in double-quoted |
824 | strings and C<s///> substitutions; and case-independent regular expression | |
e38874e2 DD |
825 | pattern matching using the C<i> modifier. |
826 | ||
2da736a2 | 827 | Finally, C<LC_CTYPE> affects the (deprecated) POSIX character-class test |
1d2ab946 KW |
828 | functions--C<POSIX::isalpha()>, C<POSIX::islower()>, and so on. For |
829 | example, if you move from the "C" locale to a 7-bit Scandinavian one, | |
830 | you may find--possibly to your surprise--that "|" moves from the | |
831 | C<POSIX::ispunct()> class to C<POSIX::isalpha()>. | |
ef3087ec KW |
832 | Unfortunately, this creates big problems for regular expressions. "|" still |
833 | means alternation even though it matches C<\w>. | |
5f05dabc | 834 | |
31f05a37 KW |
835 | Starting in v5.20, Perl supports UTF-8 locales for C<LC_CTYPE>, but |
836 | otherwise Perl only supports single-byte locales, such as the ISO 8859 | |
837 | series. This means that wide character locales, for example for Asian | |
838 | languages, are not supported. The UTF-8 locale support is actually a | |
839 | superset of POSIX locales, because it is really full Unicode behavior | |
840 | as if no locale were in effect at all (except for tainting; see | |
841 | L</SECURITY>). POSIX locales, even UTF-8 ones, | |
842 | are lacking certain concepts in Unicode, such as the idea that changing | |
843 | the case of a character could expand to be more than one character. | |
844 | Perl in a UTF-8 locale, will give you that expansion. Prior to v5.20, | |
845 | Perl treated a UTF-8 locale on some platforms like an ISO 8859-1 one, | |
846 | with some restrictions, and on other platforms more like the "C" locale. | |
847 | For releases v5.16 and v5.18, C<S<use locale 'not_characters>> could be | |
848 | used as a workaround for this (see L</Unicode and UTF-8>). | |
849 | ||
5d63e270 KW |
850 | Note that there are quite a few things that are unaffected by the |
851 | current locale. All the escape sequences for particular characters, | |
852 | C<\n> for example, always mean the platform's native one. This means, | |
853 | for example, that C<\N> in regular expressions (every character | |
1d2ab946 | 854 | but new-line) works on the platform character set. |
5d63e270 | 855 | |
14280422 DD |
856 | B<Note:> A broken or malicious C<LC_CTYPE> locale definition may result |
857 | in clearly ineligible characters being considered to be alphanumeric by | |
e199995e | 858 | your application. For strict matching of (mundane) ASCII letters and |
5a964f20 | 859 | digits--for example, in command strings--locale-aware applications |
e199995e | 860 | should use C<\w> with the C</a> regular expression modifier. See L<"SECURITY">. |
5f05dabc | 861 | |
862 | =head2 Category LC_NUMERIC: Numeric Formatting | |
863 | ||
b960a36e KW |
864 | After a proper C<POSIX::setlocale()> call, and within the scope of one |
865 | of the C<use locale> variants, Perl obeys the C<LC_NUMERIC> | |
2095dafa | 866 | locale information, which controls an application's idea of how numbers |
b960a36e KW |
867 | should be formatted for human readability. |
868 | In most implementations the only effect is to | |
b4ffc3db | 869 | change the character used for the decimal point--perhaps from "." to ",". |
b960a36e | 870 | The functions aren't aware of such niceties as thousands separation and |
2095dafa | 871 | so on. (See L<The localeconv function> if you care about these things.) |
5a964f20 | 872 | |
b960a36e KW |
873 | use POSIX qw(strtod setlocale LC_NUMERIC); |
874 | use locale; | |
5f05dabc | 875 | |
b960a36e | 876 | setlocale LC_NUMERIC, ""; |
14280422 | 877 | |
b960a36e | 878 | $n = 5/2; # Assign numeric 2.5 to $n |
5f05dabc | 879 | |
b960a36e | 880 | $a = " $n"; # Locale-dependent conversion to string |
5f05dabc | 881 | |
b960a36e | 882 | print "half five is $n\n"; # Locale-dependent output |
5f05dabc | 883 | |
b960a36e | 884 | printf "half five is %g\n", $n; # Locale-dependent output |
5f05dabc | 885 | |
b960a36e KW |
886 | print "DECIMAL POINT IS COMMA\n" |
887 | if $n == (strtod("2,5"))[0]; # Locale-dependent conversion | |
5f05dabc | 888 | |
4bbcc6e8 JH |
889 | See also L<I18N::Langinfo> and C<RADIXCHAR>. |
890 | ||
5f05dabc | 891 | =head2 Category LC_MONETARY: Formatting of monetary amounts |
892 | ||
e199995e | 893 | The C standard defines the C<LC_MONETARY> category, but not a function |
5a964f20 | 894 | that is affected by its contents. (Those with experience of standards |
b0c42ed9 | 895 | committees will recognize that the working group decided to punt on the |
fa9b773e KW |
896 | issue.) Consequently, Perl essentially takes no notice of it. If you |
897 | really want to use C<LC_MONETARY>, you can query its contents--see | |
e05ffc7d KW |
898 | L<The localeconv function>--and use the information that it returns in your |
899 | application's own formatting of currency amounts. However, you may well | |
900 | find that the information, voluminous and complex though it may be, still | |
901 | does not quite meet your requirements: currency formatting is a hard nut | |
13a2d996 | 902 | to crack. |
5f05dabc | 903 | |
4bbcc6e8 JH |
904 | See also L<I18N::Langinfo> and C<CRNCYSTR>. |
905 | ||
5f05dabc | 906 | =head2 LC_TIME |
907 | ||
39332f68 | 908 | Output produced by C<POSIX::strftime()>, which builds a formatted |
5f05dabc | 909 | human-readable date/time string, is affected by the current C<LC_TIME> |
910 | locale. Thus, in a French locale, the output produced by the C<%B> | |
911 | format element (full month name) for the first month of the year would | |
5a964f20 | 912 | be "janvier". Here's how to get a list of long month names in the |
5f05dabc | 913 | current locale: |
914 | ||
915 | use POSIX qw(strftime); | |
14280422 DD |
916 | for (0..11) { |
917 | $long_month_name[$_] = | |
918 | strftime("%B", 0, 0, 0, 1, $_, 96); | |
5f05dabc | 919 | } |
920 | ||
2619d284 KW |
921 | Note: C<use locale> isn't needed in this example: C<strftime()> is a POSIX |
922 | function which uses the standard system-supplied C<libc> function that | |
923 | always obeys the current C<LC_TIME> locale. | |
5f05dabc | 924 | |
4bbcc6e8 | 925 | See also L<I18N::Langinfo> and C<ABDAY_1>..C<ABDAY_7>, C<DAY_1>..C<DAY_7>, |
2a2bf5f4 | 926 | C<ABMON_1>..C<ABMON_12>, and C<ABMON_1>..C<ABMON_12>. |
4bbcc6e8 | 927 | |
5f05dabc | 928 | =head2 Other categories |
929 | ||
2619d284 KW |
930 | The remaining locale categories are not currently used by Perl itself. |
931 | But again note that things Perl interacts with may use these, including | |
932 | extensions outside the standard Perl distribution, and by the | |
98a6f11e | 933 | operating system and its utilities. Note especially that the string |
934 | value of C<$!> and the error messages given by external utilities may | |
935 | be changed by C<LC_MESSAGES>. If you want to have portable error | |
265f5c4a | 936 | codes, use C<%!>. See L<Errno>. |
14280422 DD |
937 | |
938 | =head1 SECURITY | |
939 | ||
5a964f20 | 940 | Although the main discussion of Perl security issues can be found in |
14280422 DD |
941 | L<perlsec>, a discussion of Perl's locale handling would be incomplete |
942 | if it did not draw your attention to locale-dependent security issues. | |
5a964f20 TC |
943 | Locales--particularly on systems that allow unprivileged users to |
944 | build their own locales--are untrustworthy. A malicious (or just plain | |
14280422 DD |
945 | broken) locale can make a locale-aware application give unexpected |
946 | results. Here are a few possibilities: | |
947 | ||
948 | =over 4 | |
949 | ||
950 | =item * | |
951 | ||
952 | Regular expression checks for safe file names or mail addresses using | |
5a964f20 | 953 | C<\w> may be spoofed by an C<LC_CTYPE> locale that claims that |
14280422 DD |
954 | characters such as "E<gt>" and "|" are alphanumeric. |
955 | ||
956 | =item * | |
957 | ||
e38874e2 DD |
958 | String interpolation with case-mapping, as in, say, C<$dest = |
959 | "C:\U$name.$ext">, may produce dangerous results if a bogus LC_CTYPE | |
960 | case-mapping table is in effect. | |
961 | ||
962 | =item * | |
963 | ||
14280422 DD |
964 | A sneaky C<LC_COLLATE> locale could result in the names of students with |
965 | "D" grades appearing ahead of those with "A"s. | |
966 | ||
967 | =item * | |
968 | ||
5a964f20 | 969 | An application that takes the trouble to use information in |
14280422 | 970 | C<LC_MONETARY> may format debits as if they were credits and vice versa |
5a964f20 | 971 | if that locale has been subverted. Or it might make payments in US |
14280422 DD |
972 | dollars instead of Hong Kong dollars. |
973 | ||
974 | =item * | |
975 | ||
39332f68 | 976 | The date and day names in dates formatted by C<strftime()> could be |
14280422 | 977 | manipulated to advantage by a malicious user able to subvert the |
5a964f20 | 978 | C<LC_DATE> locale. ("Look--it says I wasn't in the building on |
14280422 DD |
979 | Sunday.") |
980 | ||
981 | =back | |
982 | ||
983 | Such dangers are not peculiar to the locale system: any aspect of an | |
5a964f20 | 984 | application's environment which may be modified maliciously presents |
14280422 | 985 | similar challenges. Similarly, they are not specific to Perl: any |
5a964f20 | 986 | programming language that allows you to write programs that take |
14280422 DD |
987 | account of their environment exposes you to these issues. |
988 | ||
5a964f20 TC |
989 | Perl cannot protect you from all possibilities shown in the |
990 | examples--there is no substitute for your own vigilance--but, when | |
14280422 | 991 | C<use locale> is in effect, Perl uses the tainting mechanism (see |
5a964f20 | 992 | L<perlsec>) to mark string results that become locale-dependent, and |
14280422 | 993 | which may be untrustworthy in consequence. Here is a summary of the |
5a964f20 | 994 | tainting behavior of operators and functions that may be affected by |
14280422 DD |
995 | the locale: |
996 | ||
997 | =over 4 | |
998 | ||
551e1d92 RB |
999 | =item * |
1000 | ||
1001 | B<Comparison operators> (C<lt>, C<le>, C<ge>, C<gt> and C<cmp>): | |
14280422 DD |
1002 | |
1003 | Scalar true/false (or less/equal/greater) result is never tainted. | |
1004 | ||
551e1d92 RB |
1005 | =item * |
1006 | ||
1d2ab946 | 1007 | B<Case-mapping interpolation> (with C<\l>, C<\L>, C<\u>, C<\U>, or C<\F>) |
e38874e2 DD |
1008 | |
1009 | Result string containing interpolated material is tainted if | |
66cbab2c | 1010 | C<use locale> (but not S<C<use locale ':not_characters'>>) is in effect. |
e38874e2 | 1011 | |
551e1d92 RB |
1012 | =item * |
1013 | ||
1014 | B<Matching operator> (C<m//>): | |
14280422 DD |
1015 | |
1016 | Scalar true/false result never tainted. | |
1017 | ||
1d2ab946 KW |
1018 | All subpatterns, either delivered as a list-context result or as C<$1> |
1019 | I<etc>., are tainted if C<use locale> (but not | |
1020 | S<C<use locale ':not_characters'>>) is in effect, and the subpattern | |
63baef57 KW |
1021 | regular expression contains a locale-dependent construct. These |
1022 | constructs include C<\w> (to match an alphanumeric character), C<\W> | |
1023 | (non-alphanumeric character), C<\b> and C<\B> (word-boundary and | |
1024 | non-boundardy, which depend on what C<\w> and C<\W> match), C<\s> | |
1025 | (whitespace character), C<\S> (non whitespace character), C<\d> and | |
1026 | C<\D> (digits and non-digits), and the POSIX character classes, such as | |
1027 | C<[:alpha:]> (see L<perlrecharclass/POSIX Character Classes>). | |
1028 | ||
1029 | Tainting is also likely if the pattern is to be matched | |
1030 | case-insensitively (via C</i>). The exception is if all the code points | |
1031 | to be matched this way are above 255 and do not have folds under Unicode | |
1032 | rules to below 256. Tainting is not done for these because Perl | |
1033 | only uses Unicode rules for such code points, and those rules are the | |
1034 | same no matter what the current locale. | |
1035 | ||
1d2ab946 KW |
1036 | The matched-pattern variables, C<$&>, C<$`> (pre-match), C<$'> |
1037 | (post-match), and C<$+> (last match) also are tainted. | |
14280422 | 1038 | |
551e1d92 RB |
1039 | =item * |
1040 | ||
1041 | B<Substitution operator> (C<s///>): | |
14280422 | 1042 | |
e38874e2 | 1043 | Has the same behavior as the match operator. Also, the left |
66cbab2c KW |
1044 | operand of C<=~> becomes tainted when C<use locale> |
1045 | (but not S<C<use locale ':not_characters'>>) is in effect if modified as | |
1046 | a result of a substitution based on a regular | |
1d2ab946 KW |
1047 | expression match involving any of the things mentioned in the previous |
1048 | item, or of case-mapping, such as C<\l>, C<\L>,C<\u>, C<\U>, or C<\F>. | |
14280422 | 1049 | |
551e1d92 RB |
1050 | =item * |
1051 | ||
39332f68 | 1052 | B<Output formatting functions> (C<printf()> and C<write()>): |
14280422 | 1053 | |
3cf03d68 JH |
1054 | Results are never tainted because otherwise even output from print, |
1055 | for example C<print(1/7)>, should be tainted if C<use locale> is in | |
1056 | effect. | |
14280422 | 1057 | |
551e1d92 RB |
1058 | =item * |
1059 | ||
39332f68 | 1060 | B<Case-mapping functions> (C<lc()>, C<lcfirst()>, C<uc()>, C<ucfirst()>): |
14280422 | 1061 | |
66cbab2c KW |
1062 | Results are tainted if C<use locale> (but not |
1063 | S<C<use locale ':not_characters'>>) is in effect. | |
14280422 | 1064 | |
551e1d92 RB |
1065 | =item * |
1066 | ||
39332f68 KW |
1067 | B<POSIX locale-dependent functions> (C<localeconv()>, C<strcoll()>, |
1068 | C<strftime()>, C<strxfrm()>): | |
14280422 DD |
1069 | |
1070 | Results are never tainted. | |
1071 | ||
551e1d92 RB |
1072 | =item * |
1073 | ||
1d2ab946 KW |
1074 | B<POSIX character class tests> (C<POSIX::isalnum()>, |
1075 | C<POSIX::isalpha()>, C<POSIX::isdigit()>, C<POSIX::isgraph()>, | |
1076 | C<POSIX::islower()>, C<POSIX::isprint()>, C<POSIX::ispunct()>, | |
1077 | C<POSIX::isspace()>, C<POSIX::isupper()>, C<POSIX::isxdigit()>): | |
14280422 DD |
1078 | |
1079 | True/false results are never tainted. | |
1080 | ||
1081 | =back | |
1082 | ||
1083 | Three examples illustrate locale-dependent tainting. | |
1084 | The first program, which ignores its locale, won't run: a value taken | |
54310121 | 1085 | directly from the command line may not be used to name an output file |
14280422 DD |
1086 | when taint checks are enabled. |
1087 | ||
1088 | #/usr/local/bin/perl -T | |
1089 | # Run with taint checking | |
1090 | ||
54310121 | 1091 | # Command line sanity check omitted... |
14280422 DD |
1092 | $tainted_output_file = shift; |
1093 | ||
1094 | open(F, ">$tainted_output_file") | |
3183d96c | 1095 | or warn "Open of $tainted_output_file failed: $!\n"; |
14280422 DD |
1096 | |
1097 | The program can be made to run by "laundering" the tainted value through | |
5a964f20 TC |
1098 | a regular expression: the second example--which still ignores locale |
1099 | information--runs, creating the file named on its command line | |
14280422 DD |
1100 | if it can. |
1101 | ||
1102 | #/usr/local/bin/perl -T | |
1103 | ||
1104 | $tainted_output_file = shift; | |
1105 | $tainted_output_file =~ m%[\w/]+%; | |
1106 | $untainted_output_file = $&; | |
1107 | ||
1108 | open(F, ">$untainted_output_file") | |
1109 | or warn "Open of $untainted_output_file failed: $!\n"; | |
1110 | ||
5a964f20 | 1111 | Compare this with a similar but locale-aware program: |
14280422 DD |
1112 | |
1113 | #/usr/local/bin/perl -T | |
1114 | ||
1115 | $tainted_output_file = shift; | |
1116 | use locale; | |
1117 | $tainted_output_file =~ m%[\w/]+%; | |
1118 | $localized_output_file = $&; | |
1119 | ||
1120 | open(F, ">$localized_output_file") | |
1121 | or warn "Open of $localized_output_file failed: $!\n"; | |
1122 | ||
1d2ab946 | 1123 | This third program fails to run because C<$&> is tainted: it is the result |
5a964f20 | 1124 | of a match involving C<\w> while C<use locale> is in effect. |
5f05dabc | 1125 | |
1126 | =head1 ENVIRONMENT | |
1127 | ||
1128 | =over 12 | |
1129 | ||
ee1ec05f KW |
1130 | =item PERL_SKIP_LOCALE_INIT |
1131 | ||
1132 | This environment variable, available starting in Perl v5.20, and if it | |
1133 | evaluates to a TRUE value, tells Perl to not use the rest of the | |
1134 | environment variables to initialize with. Instead, Perl uses whatever | |
1135 | the current locale settings are. This is particularly useful in | |
1136 | embedded environments, see | |
1137 | L<perlembed/Using embedded Perl with POSIX locales>. | |
1138 | ||
5f05dabc | 1139 | =item PERL_BADLANG |
1140 | ||
14280422 | 1141 | A string that can suppress Perl's warning about failed locale settings |
54310121 | 1142 | at startup. Failure can occur if the locale support in the operating |
5a964f20 | 1143 | system is lacking (broken) in some way--or if you mistyped the name of |
900bd440 JH |
1144 | a locale when you set up your environment. If this environment |
1145 | variable is absent, or has a value that does not evaluate to integer | |
1146 | zero--that is, "0" or ""-- Perl will complain about locale setting | |
1147 | failures. | |
5f05dabc | 1148 | |
14280422 DD |
1149 | B<NOTE>: PERL_BADLANG only gives you a way to hide the warning message. |
1150 | The message tells about some problem in your system's locale support, | |
1151 | and you should investigate what the problem is. | |
5f05dabc | 1152 | |
1153 | =back | |
1154 | ||
1155 | The following environment variables are not specific to Perl: They are | |
39332f68 | 1156 | part of the standardized (ISO C, XPG4, POSIX 1.c) C<setlocale()> method |
b385bb4d KW |
1157 | for controlling an application's opinion on data. Windows is non-POSIX, |
1158 | but Perl arranges for the following to work as described anyway. | |
65ebb059 KW |
1159 | If the locale given by an environment variable is not valid, Perl tries |
1160 | the next lower one in priority. If none are valid, on Windows, the | |
1161 | system default locale is then tried. If all else fails, the C<"C"> | |
1162 | locale is used. If even that doesn't work, something is badly broken, | |
1163 | but Perl tries to forge ahead with whatever the locale settinga might | |
1164 | be. | |
5f05dabc | 1165 | |
1166 | =over 12 | |
1167 | ||
1168 | =item LC_ALL | |
1169 | ||
5a964f20 | 1170 | C<LC_ALL> is the "override-all" locale environment variable. If |
5f05dabc | 1171 | set, it overrides all the rest of the locale environment variables. |
1172 | ||
528d65ad JH |
1173 | =item LANGUAGE |
1174 | ||
1175 | B<NOTE>: C<LANGUAGE> is a GNU extension, it affects you only if you | |
1176 | are using the GNU libc. This is the case if you are using e.g. Linux. | |
e1020413 | 1177 | If you are using "commercial" Unixes you are most probably I<not> |
22b6f60d JH |
1178 | using GNU libc and you can ignore C<LANGUAGE>. |
1179 | ||
1180 | However, in the case you are using C<LANGUAGE>: it affects the | |
1181 | language of informational, warning, and error messages output by | |
1182 | commands (in other words, it's like C<LC_MESSAGES>) but it has higher | |
96090e4f | 1183 | priority than C<LC_ALL>. Moreover, it's not a single value but |
22b6f60d JH |
1184 | instead a "path" (":"-separated list) of I<languages> (not locales). |
1185 | See the GNU C<gettext> library documentation for more information. | |
528d65ad | 1186 | |
5f05dabc | 1187 | =item LC_CTYPE |
1188 | ||
1189 | In the absence of C<LC_ALL>, C<LC_CTYPE> chooses the character type | |
1190 | locale. In the absence of both C<LC_ALL> and C<LC_CTYPE>, C<LANG> | |
1191 | chooses the character type locale. | |
1192 | ||
1193 | =item LC_COLLATE | |
1194 | ||
14280422 DD |
1195 | In the absence of C<LC_ALL>, C<LC_COLLATE> chooses the collation |
1196 | (sorting) locale. In the absence of both C<LC_ALL> and C<LC_COLLATE>, | |
1197 | C<LANG> chooses the collation locale. | |
5f05dabc | 1198 | |
1199 | =item LC_MONETARY | |
1200 | ||
14280422 DD |
1201 | In the absence of C<LC_ALL>, C<LC_MONETARY> chooses the monetary |
1202 | formatting locale. In the absence of both C<LC_ALL> and C<LC_MONETARY>, | |
1203 | C<LANG> chooses the monetary formatting locale. | |
5f05dabc | 1204 | |
1205 | =item LC_NUMERIC | |
1206 | ||
1207 | In the absence of C<LC_ALL>, C<LC_NUMERIC> chooses the numeric format | |
1208 | locale. In the absence of both C<LC_ALL> and C<LC_NUMERIC>, C<LANG> | |
1209 | chooses the numeric format. | |
1210 | ||
1211 | =item LC_TIME | |
1212 | ||
14280422 DD |
1213 | In the absence of C<LC_ALL>, C<LC_TIME> chooses the date and time |
1214 | formatting locale. In the absence of both C<LC_ALL> and C<LC_TIME>, | |
1215 | C<LANG> chooses the date and time formatting locale. | |
5f05dabc | 1216 | |
1217 | =item LANG | |
1218 | ||
14280422 DD |
1219 | C<LANG> is the "catch-all" locale environment variable. If it is set, it |
1220 | is used as the last resort after the overall C<LC_ALL> and the | |
5f05dabc | 1221 | category-specific C<LC_...>. |
1222 | ||
1223 | =back | |
1224 | ||
7e4353e9 RGS |
1225 | =head2 Examples |
1226 | ||
1227 | The LC_NUMERIC controls the numeric output: | |
1228 | ||
ef3087ec KW |
1229 | use locale; |
1230 | use POSIX qw(locale_h); # Imports setlocale() and the LC_ constants. | |
1231 | setlocale(LC_NUMERIC, "fr_FR") or die "Pardon"; | |
1232 | printf "%g\n", 1.23; # If the "fr_FR" succeeded, probably shows 1,23. | |
7e4353e9 | 1233 | |
39332f68 | 1234 | and also how strings are parsed by C<POSIX::strtod()> as numbers: |
7e4353e9 | 1235 | |
ef3087ec KW |
1236 | use locale; |
1237 | use POSIX qw(locale_h strtod); | |
1238 | setlocale(LC_NUMERIC, "de_DE") or die "Entschuldigung"; | |
1239 | my $x = strtod("2,34") + 5; | |
1240 | print $x, "\n"; # Probably shows 7,34. | |
7e4353e9 | 1241 | |
5f05dabc | 1242 | =head1 NOTES |
1243 | ||
b960a36e KW |
1244 | =head2 String C<eval> and C<LC_NUMERIC> |
1245 | ||
1246 | A string L<eval|perlfunc/eval EXPR> parses its expression as standard | |
1247 | Perl. It is therefore expecting the decimal point to be a dot. If | |
1248 | C<LC_NUMERIC> is set to have this be a comma instead, the parsing will | |
1249 | be confused, perhaps silently. | |
1250 | ||
1251 | use locale; | |
1252 | use POSIX qw(locale_h); | |
1253 | setlocale(LC_NUMERIC, "fr_FR") or die "Pardon"; | |
1254 | my $a = 1.2; | |
1255 | print eval "$a + 1.5"; | |
1256 | print "\n"; | |
1257 | ||
1258 | prints C<13,5>. This is because in that locale, the comma is the | |
1259 | decimal point character. The C<eval> thus expands to: | |
1260 | ||
1261 | eval "1,2 + 1.5" | |
1262 | ||
1263 | and the result is not what you likely expected. No warnings are | |
1264 | generated. If you do string C<eval>'s within the scope of | |
1265 | S<C<use locale>>, you should instead change the C<eval> line to do | |
1266 | something like: | |
1267 | ||
1268 | print eval "no locale; $a + 1.5"; | |
1269 | ||
1270 | This prints C<2.7>. | |
1271 | ||
5f05dabc | 1272 | =head2 Backward compatibility |
1273 | ||
b0c42ed9 | 1274 | Versions of Perl prior to 5.004 B<mostly> ignored locale information, |
5a964f20 TC |
1275 | generally behaving as if something similar to the C<"C"> locale were |
1276 | always in force, even if the program environment suggested otherwise | |
1277 | (see L<The setlocale function>). By default, Perl still behaves this | |
1278 | way for backward compatibility. If you want a Perl application to pay | |
1279 | attention to locale information, you B<must> use the S<C<use locale>> | |
062ca197 KW |
1280 | pragma (see L<The use locale pragma>) or, in the unlikely event |
1281 | that you want to do so for just pattern matching, the | |
70709c68 KW |
1282 | C</l> regular expression modifier (see L<perlre/Character set |
1283 | modifiers>) to instruct it to do so. | |
b0c42ed9 JH |
1284 | |
1285 | Versions of Perl from 5.002 to 5.003 did use the C<LC_CTYPE> | |
5a964f20 TC |
1286 | information if available; that is, C<\w> did understand what |
1287 | were the letters according to the locale environment variables. | |
b0c42ed9 JH |
1288 | The problem was that the user had no control over the feature: |
1289 | if the C library supported locales, Perl used them. | |
1290 | ||
1291 | =head2 I18N:Collate obsolete | |
1292 | ||
5a964f20 | 1293 | In versions of Perl prior to 5.004, per-locale collation was possible |
b0c42ed9 JH |
1294 | using the C<I18N::Collate> library module. This module is now mildly |
1295 | obsolete and should be avoided in new applications. The C<LC_COLLATE> | |
1296 | functionality is now integrated into the Perl core language: One can | |
1297 | use locale-specific scalar data completely normally with C<use locale>, | |
1298 | so there is no longer any need to juggle with the scalar references of | |
1299 | C<I18N::Collate>. | |
5f05dabc | 1300 | |
14280422 | 1301 | =head2 Sort speed and memory use impacts |
5f05dabc | 1302 | |
1303 | Comparing and sorting by locale is usually slower than the default | |
14280422 DD |
1304 | sorting; slow-downs of two to four times have been observed. It will |
1305 | also consume more memory: once a Perl scalar variable has participated | |
1306 | in any string comparison or sorting operation obeying the locale | |
1307 | collation rules, it will take 3-15 times more memory than before. (The | |
1308 | exact multiplier depends on the string's contents, the operating system | |
1309 | and the locale.) These downsides are dictated more by the operating | |
1310 | system's implementation of the locale system than by Perl. | |
5f05dabc | 1311 | |
5f05dabc | 1312 | =head2 Freely available locale definitions |
1313 | ||
66cbab2c KW |
1314 | The Unicode CLDR project extracts the POSIX portion of many of its |
1315 | locales, available at | |
1316 | ||
1317 | http://unicode.org/Public/cldr/latest/ | |
1318 | ||
08d7a6b2 LB |
1319 | There is a large collection of locale definitions at: |
1320 | ||
1321 | http://std.dkuug.dk/i18n/WG15-collection/locales/ | |
1322 | ||
1323 | You should be aware that it is | |
14280422 | 1324 | unsupported, and is not claimed to be fit for any purpose. If your |
5a964f20 | 1325 | system allows installation of arbitrary locales, you may find the |
14280422 DD |
1326 | definitions useful as they are, or as a basis for the development of |
1327 | your own locales. | |
5f05dabc | 1328 | |
14280422 | 1329 | =head2 I18n and l10n |
5f05dabc | 1330 | |
b0c42ed9 JH |
1331 | "Internationalization" is often abbreviated as B<i18n> because its first |
1332 | and last letters are separated by eighteen others. (You may guess why | |
1333 | the internalin ... internaliti ... i18n tends to get abbreviated.) In | |
1334 | the same way, "localization" is often abbreviated to B<l10n>. | |
14280422 DD |
1335 | |
1336 | =head2 An imperfect standard | |
1337 | ||
1338 | Internationalization, as defined in the C and POSIX standards, can be | |
1339 | criticized as incomplete, ungainly, and having too large a granularity. | |
1340 | (Locales apply to a whole process, when it would arguably be more useful | |
1341 | to have them apply to a single thread, window group, or whatever.) They | |
1342 | also have a tendency, like standards groups, to divide the world into | |
1343 | nations, when we all know that the world can equally well be divided | |
e199995e | 1344 | into bankers, bikers, gamers, and so on. |
5f05dabc | 1345 | |
b310b053 JH |
1346 | =head1 Unicode and UTF-8 |
1347 | ||
7ee2ae1e | 1348 | The support of Unicode is new starting from Perl version v5.6, and more fully |
31f05a37 KW |
1349 | implemented in versions v5.8 and later. See L<perluniintro>. |
1350 | ||
1351 | Starting in Perl v5.20, UTF-8 locales are supported in Perl, except for | |
1352 | C<LC_COLLATE> (use L<Unicode::Collate> instead). If you have Perl v5.16 | |
1353 | or v5.18 and can't upgrade, you can use | |
66cbab2c KW |
1354 | |
1355 | use locale ':not_characters'; | |
1356 | ||
1357 | When this form of the pragma is used, only the non-character portions of | |
1358 | locales are used by Perl, for example C<LC_NUMERIC>. Perl assumes that | |
1359 | you have translated all the characters it is to operate on into Unicode | |
1360 | (actually the platform's native character set (ASCII or EBCDIC) plus | |
1361 | Unicode). For data in files, this can conveniently be done by also | |
1362 | specifying | |
1363 | ||
1364 | use open ':locale'; | |
1365 | ||
1366 | This pragma arranges for all inputs from files to be translated into | |
1367 | Unicode from the current locale as specified in the environment (see | |
1368 | L</ENVIRONMENT>), and all outputs to files to be translated back | |
1369 | into the locale. (See L<open>). On a per-filehandle basis, you can | |
1370 | instead use the L<PerlIO::locale> module, or the L<Encode::Locale> | |
1371 | module, both available from CPAN. The latter module also has methods to | |
1372 | ease the handling of C<ARGV> and environment variables, and can be used | |
31f05a37 | 1373 | on individual strings. If you know that all your locales will be |
66cbab2c KW |
1374 | UTF-8, as many are these days, you can use the L<B<-C>|perlrun/-C> |
1375 | command line switch. | |
1376 | ||
1377 | This form of the pragma allows essentially seamless handling of locales | |
31f05a37 KW |
1378 | with Unicode. The collation order will be by Unicode code point order. |
1379 | It is strongly | |
66cbab2c KW |
1380 | recommended that when you need to order and sort strings that you use |
1381 | the standard module L<Unicode::Collate> which gives much better results | |
1382 | in many instances than you can get with the old-style locale handling. | |
1383 | ||
31f05a37 KW |
1384 | All the modules and switches just described can be used in v5.20 with |
1385 | just plain C<use locale>, and, should the input locales not be UTF-8, | |
1386 | you'll get the less than ideal behavior, described below, that you get | |
1387 | with pre-v5.16 Perls, or when you use the locale pragma without the | |
1388 | C<:not_characters> parameter in v5.16 and v5.18. If you are using | |
1389 | exclusively UTF-8 locales in v5.20 and higher, the rest of this section | |
1390 | does not apply to you. | |
1391 | ||
1392 | There are two cases, multi-byte and single-byte locales. First | |
1393 | multi-byte: | |
1394 | ||
1395 | The only multi-byte (or wide character) locale that Perl is ever likely | |
1396 | to support is UTF-8. This is due to the difficulty of implementation, | |
1397 | the fact that high quality UTF-8 locales are now published for every | |
1398 | area of the world (L<http://unicode.org/Public/cldr/latest/>), and that | |
1399 | failing all that you can use the L<Encode> module to translate to/from | |
1400 | your locale. So, you'll have to do one of those things if you're using | |
1401 | one of these locales, such as Big5 or Shift JIS. For UTF-8 locales, in | |
1402 | Perls (pre v5.20) that don't have full UTF-8 locale support, they may | |
1403 | work reasonably well (depending on your C library implementation) | |
1404 | simply because both | |
dc4bfc4b KW |
1405 | they and Perl store characters that take up multiple bytes the same way. |
1406 | However, some, if not most, C library implementations may not process | |
1407 | the characters in the upper half of the Latin-1 range (128 - 255) | |
1408 | properly under LC_CTYPE. To see if a character is a particular type | |
1409 | under a locale, Perl uses the functions like C<isalnum()>. Your C | |
1410 | library may not work for UTF-8 locales with those functions, instead | |
1411 | only working under the newer wide library functions like C<iswalnum()>. | |
31f05a37 KW |
1412 | However, they are treated like single-byte locales, and will have the |
1413 | restrictions described below. | |
e199995e | 1414 | |
31f05a37 | 1415 | For single-byte locales, |
e199995e | 1416 | Perl generally takes the tack to use locale rules on code points that can fit |
66cbab2c KW |
1417 | in a single byte, and Unicode rules for those that can't (though this |
1418 | isn't uniformly applied, see the note at the end of this section). This | |
1419 | prevents many problems in locales that aren't UTF-8. Suppose the locale | |
1420 | is ISO8859-7, Greek. The character at 0xD7 there is a capital Chi. But | |
1421 | in the ISO8859-1 locale, Latin1, it is a multiplication sign. The POSIX | |
1422 | regular expression character class C<[[:alpha:]]> will magically match | |
1423 | 0xD7 in the Greek locale but not in the Latin one. | |
e199995e | 1424 | |
1d2ab946 | 1425 | However, there are places where this breaks down. Certain Perl constructs are |
b4ffc3db TC |
1426 | for Unicode only, such as C<\p{Alpha}>. They assume that 0xD7 always has its |
1427 | Unicode meaning (or the equivalent on EBCDIC platforms). Since Latin1 is a | |
1428 | subset of Unicode and 0xD7 is the multiplication sign in both Latin1 and | |
1429 | Unicode, C<\p{Alpha}> will never match it, regardless of locale. A similar | |
31f05a37 KW |
1430 | issue occurs with C<\N{...}>. Prior to v5.20, It is therefore a bad |
1431 | idea to use C<\p{}> or | |
66cbab2c KW |
1432 | C<\N{}> under plain C<use locale>--I<unless> you can guarantee that the |
1433 | locale will be a ISO8859-1. Use POSIX character classes instead. | |
1434 | ||
1435 | Another problem with this approach is that operations that cross the | |
1436 | single byte/multiple byte boundary are not well-defined, and so are | |
1437 | disallowed. (This boundary is between the codepoints at 255/256.). | |
1438 | For example, lower casing LATIN CAPITAL LETTER Y WITH DIAERESIS (U+0178) | |
1439 | should return LATIN SMALL LETTER Y WITH DIAERESIS (U+00FF). But in the | |
1440 | Greek locale, for example, there is no character at 0xFF, and Perl | |
1441 | has no way of knowing what the character at 0xFF is really supposed to | |
1442 | represent. Thus it disallows the operation. In this mode, the | |
1443 | lowercase of U+0178 is itself. | |
1444 | ||
1445 | The same problems ensue if you enable automatic UTF-8-ification of your | |
e199995e | 1446 | standard file handles, default C<open()> layer, and C<@ARGV> on non-ISO8859-1, |
b4ffc3db TC |
1447 | non-UTF-8 locales (by using either the B<-C> command line switch or the |
1448 | C<PERL_UNICODE> environment variable; see L<perlrun>). | |
1449 | Things are read in as UTF-8, which would normally imply a Unicode | |
1450 | interpretation, but the presence of a locale causes them to be interpreted | |
1451 | in that locale instead. For example, a 0xD7 code point in the Unicode | |
1452 | input, which should mean the multiplication sign, won't be interpreted by | |
66cbab2c | 1453 | Perl that way under the Greek locale. This is not a problem |
b4ffc3db | 1454 | I<provided> you make certain that all locales will always and only be either |
66cbab2c | 1455 | an ISO8859-1, or, if you don't have a deficient C library, a UTF-8 locale. |
b4ffc3db | 1456 | |
1d2ab946 KW |
1457 | Still another problem is that this approach can lead to two code |
1458 | points meaning the same character. Thus in a Greek locale, both U+03A7 | |
1459 | and U+00D7 are GREEK CAPITAL LETTER CHI. | |
1460 | ||
b4ffc3db TC |
1461 | Vendor locales are notoriously buggy, and it is difficult for Perl to test |
1462 | its locale-handling code because this interacts with code that Perl has no | |
1463 | control over; therefore the locale-handling code in Perl may be buggy as | |
66cbab2c KW |
1464 | well. (However, the Unicode-supplied locales should be better, and |
1465 | there is a feed back mechanism to correct any problems. See | |
1466 | L</Freely available locale definitions>.) | |
1467 | ||
7ee2ae1e | 1468 | If you have Perl v5.16, the problems mentioned above go away if you use |
66cbab2c | 1469 | the C<:not_characters> parameter to the locale pragma (except for vendor |
7ee2ae1e | 1470 | bugs in the non-character portions). If you don't have v5.16, and you |
66cbab2c KW |
1471 | I<do> have locales that work, using them may be worthwhile for certain |
1472 | specific purposes, as long as you keep in mind the gotchas already | |
1473 | mentioned. For example, if the collation for your locales works, it | |
1474 | runs faster under locales than under L<Unicode::Collate>; and you gain | |
1475 | access to such things as the local currency symbol and the names of the | |
7ee2ae1e | 1476 | months and days of the week. (But to hammer home the point, in v5.16, |
66cbab2c KW |
1477 | you get this access without the downsides of locales by using the |
1478 | C<:not_characters> form of the pragma.) | |
1479 | ||
1480 | Note: The policy of using locale rules for code points that can fit in a | |
1481 | byte, and Unicode rules for those that can't is not uniformly applied. | |
7ee2ae1e | 1482 | Pre-v5.12, it was somewhat haphazard; in v5.12 it was applied fairly |
66cbab2c | 1483 | consistently to regular expression matching except for bracketed |
7ee2ae1e KW |
1484 | character classes; in v5.14 it was extended to all regex matches; and in |
1485 | v5.16 to the casing operations such as C<"\L"> and C<uc()>. For | |
66cbab2c KW |
1486 | collation, in all releases, the system's C<strxfrm()> function is called, |
1487 | and whatever it does is what you get. | |
b310b053 | 1488 | |
5f05dabc | 1489 | =head1 BUGS |
1490 | ||
1491 | =head2 Broken systems | |
1492 | ||
5a964f20 | 1493 | In certain systems, the operating system's locale support |
2bdf8add | 1494 | is broken and cannot be fixed or used by Perl. Such deficiencies can |
b4ffc3db | 1495 | and will result in mysterious hangs and/or Perl core dumps when |
2bdf8add | 1496 | C<use locale> is in effect. When confronted with such a system, |
7f2de2d2 | 1497 | please report in excruciating detail to <F<perlbug@perl.org>>, and |
b4ffc3db | 1498 | also contact your vendor: bug fixes may exist for these problems |
2bdf8add | 1499 | in your operating system. Sometimes such bug fixes are called an |
83fb1bf0 KW |
1500 | operating system upgrade. If you have the source for Perl, include in |
1501 | the perlbug email the output of the test described above in L</Testing | |
1502 | for broken locales>. | |
5f05dabc | 1503 | |
1504 | =head1 SEE ALSO | |
1505 | ||
b310b053 JH |
1506 | L<I18N::Langinfo>, L<perluniintro>, L<perlunicode>, L<open>, |
1507 | L<POSIX/isalnum>, L<POSIX/isalpha>, | |
4bbcc6e8 JH |
1508 | L<POSIX/isdigit>, L<POSIX/isgraph>, L<POSIX/islower>, |
1509 | L<POSIX/isprint>, L<POSIX/ispunct>, L<POSIX/isspace>, | |
1510 | L<POSIX/isupper>, L<POSIX/isxdigit>, L<POSIX/localeconv>, | |
1511 | L<POSIX/setlocale>, L<POSIX/strcoll>, L<POSIX/strftime>, | |
1512 | L<POSIX/strtod>, L<POSIX/strxfrm>. | |
5f05dabc | 1513 | |
ccd65d51 KW |
1514 | For special considerations when Perl is embedded in a C program, |
1515 | see L<perlembed/Using embedded Perl with POSIX locales>. | |
1516 | ||
5f05dabc | 1517 | =head1 HISTORY |
1518 | ||
b0c42ed9 | 1519 | Jarkko Hietaniemi's original F<perli18n.pod> heavily hacked by Dominic |
5a964f20 | 1520 | Dunlop, assisted by the perl5-porters. Prose worked over a bit by |
c052850d | 1521 | Tom Christiansen, and updated by Perl 5 porters. |