1 .\" Copyright (C) 1994 Jochen Hein (Hein@Student.TU-Clausthal.de)
2 .\" Copyright (C) 2008 Petr Baudis (pasky@suse.cz)
3 .\" Copyright (C) 2014 Michael Kerrisk <mtk@manpages@gmail.com>
5 .\" %%%LICENSE_START(GPLv2+_SW_3_PARA)
6 .\" This program is free software; you can redistribute it and/or modify
7 .\" it under the terms of the GNU General Public License as published by
8 .\" the Free Software Foundation; either version 2 of the License, or
9 .\" (at your option) any later version.
11 .\" This program is distributed in the hope that it will be useful,
12 .\" but WITHOUT ANY WARRANTY; without even the implied warranty of
13 .\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
14 .\" GNU General Public License for more details.
16 .\" You should have received a copy of the GNU General Public
17 .\" License along with this manual; if not, see
18 .\" <http://www.gnu.org/licenses/>.
21 .\" 2008-06-17 Petr Baudis <pasky@suse.cz>
22 .\" LC_TIME: Describe first_weekday and first_workday
24 .TH LOCALE 5 2014-03-03 "Linux" "Linux User Manual"
26 locale \- describes a locale definition file
30 definition file contains all the information that the
32 command needs to convert it into the binary locale database.
34 The definition files consist of sections which each describe a
35 locale category in detail.
37 The locale definition file starts with a header that may consist
38 of the following keywords:
41 is followed by a character that should be used as the
42 escape-character for the rest of the file to mark characters that
43 should be interpreted in a special way.
44 It defaults to the backslash (\\).
47 is followed by a character that will be used as the
48 comment-character for the rest of the file.
49 It defaults to the number sign (#).
51 The locale definition has one part for each locale category.
52 Each part can be copied from another existing locale or
53 can be defined from scratch.
54 If the category should be copied,
55 the only valid keyword in the definition is
57 followed by the name of the locale which should be copied.
58 .SS Locale category sections
59 The following category sections are defined by POSIX:
73 In addition, since version 2.2,
74 the GNU C library supports the following nonstandard categories:
88 The definition for the
90 category starts with the string
94 The following keywords are allowed:
95 .\" Thanks to the kind folk who wrote localedata/locales/uk_UA
98 followed by a string containing field descriptors that define
99 the format used for postal addresses in the locale.
100 The following field descriptors are recognized:
101 .\" From localedata/locales/uk_UA:
105 .\" BUG: %l escape sequence from ISO/IEC 14652:2002 is not supported
107 .\" Person's name, possibly constructed with the
113 Care of person, or organization.
125 Street or block (e.g., Japanese) name.
128 House number or designation.
131 Insert an end-of-line if the previous descriptor's value was not an empty
132 string; otherwise ignore.
135 Insert a space if the previous descriptor's value was not an empty string;
139 Room number, door designation.
145 Country designation, from the <country_post> keyword.
148 .\" BUG: %l escape sequence from ISO/IEC 14652:2002 is not
149 .\" supported by glibc
150 .\" Local township within town or city.
153 Zip number, postal code.
159 State, province, or prefecture.
162 Country, as taken from data record.
164 Each field descriptor may have an \(aqR\(aq after
165 the \(aq%\(aq to specify that the
166 information is taken from a Romanized version string of the
172 followed by the country name in the language of the current document
173 (e.g., "Deutschland for the
178 followed by the abbreviation of the country (see CERT_MAILCODES).
181 followed by the two-letter abbreviation of the country (ISO 3166).
184 followed by the three-letter abbreviation of the country (ISO 3166).
187 followed by the numeric country code (ISO 3166).
190 followed by the code for the country car number.
193 followed by the ISBN code (for books).
196 followed by the language name in the language of the current document.
199 followed by the two-letter abbreviation of the language (ISO 639).
202 followed by the three-letter abbreviation of the language (ISO 639-2).
205 followed by the three-letter abbreviation of the language for
206 library use (ISO 639-2)
210 definition ends with the string
211 .IR "END LC_ADDRESS" .
213 The definition for the
215 category starts with the string
219 The following keywords are allowed:
220 .\" FIXME translit_start + translit_end are not documented
221 .\" FIXME 'charclass' is not documented
222 .\" FIXME 'charconv' is not documented
223 .\" FIXME 'outdigit' is not documented
224 .\" FIXME 'include' is not documented
225 .\" FIXME 'map' (to_inpunct, to_outpunct) is not documented
228 followed by a list of uppercase letters.
233 are included automatically.
234 Characters also specified as
243 followed by a list of lowercase letters.
248 are included automatically.
249 Characters also specified as
258 followed by a list of letters.
259 All character specified as either
263 are automatically included.
264 Characters also specified as
273 followed by the characters classified as numeric digits.
280 They are included by default in this class.
283 followed by a list of characters defined as white-space
285 Characters also specified as
298 .BR <carriage-return> ,
302 are automatically included.
305 followed by a list of control characters.
306 Characters also specified as
319 followed by a list of punctuation characters.
330 character are not allowed.
333 followed by a list of printable characters, not including the
336 The characters defined as
344 are automatically included.
345 Characters also specified as
350 followed by a list of printable characters, including the
353 The characters defined as
362 character are automatically included.
363 Characters also specified as
368 followed by a list of characters classified as hexadecimal
370 The decimal digits must be included followed by one or
371 more set of six characters in ascending order.
373 characters are included by default:
385 followed by a list of characters classified as
391 are automatically included.
394 followed by a list of mappings from lowercase to uppercase
396 Each mapping is a pair of a lowercase and an uppercase letter
399 and enclosed in parentheses.
400 The members of the list are separated
404 followed by a list of mappings from uppercase to lowercase
406 If the keyword tolower is not present, the reverse of the
407 toupper list is used.
411 definition ends with the string
414 .\" FIXME: the decsription of LC_COLLATE lacks a lot of details
417 category defines the rules for collating characters.
419 limitations of libc not all POSIX-options are implemented.
421 The definition starts with the string
425 The following keywords are allowed:
426 .\" FIXME 'reorder-after' is not documented
427 .\" FIXME 'reorder-end' is not documented
428 .\" FIXME 'reorder-sections-after' is not documented
429 .\" FIXME 'reorder-sections-end' is not documented
430 .\" FIXME 'script' is not documented
431 .\" FIXME 'symbol-equivalence' is not documented
437 The order-definition starts with a line:
441 followed by a list of keywords chosen from
446 The order definition consists of lines that describe the order
447 and is terminated with the keyword
451 For more details see the sources in
461 definition ends with the string
462 .IR "END LC_COLLATE" .
463 .SS LC_IDENTIFICATION
464 This category contains meta-information about the locale definition.
466 The definition starts with the string
470 The following keywords are allowed:
473 followed by the title of ths locale document
474 (e.g., "Maori language locale for New Zealand").
477 followed by the name of the organization that maintains this document.
480 followed by the address of the organization that maintains this document.
483 followed by the name of the contact person at
484 the organization that maintains this document.
487 followed by the email address of the person or
488 organization that maintains this document.
491 followed by the telephone number (in international format)
492 of the organization that maintains this document.
495 followed by the FAX number (in international format)
496 of the organization that maintains this document.
499 followed by the name of the language to which this document applies.
502 followed by the name of the country/geographic extent
503 to which this document applies.
506 followed by a description of the audience for which this document is intended.
509 followed by a description of any special application
510 for which this document is intended.
513 .\" as far as I can tell... (mtk)
514 followed by the short name for this document.
517 followed by the revision number of this document.
520 followed by the revision date of this document.
522 In addition, for each of the categories defined by the document,
523 there should be a line starting with the keyword
527 a string that identifies this locale category definition,
537 definition ends with the string
538 .IR "END LC_IDENTIFICATION" .
540 The definition starts with the string
544 The following keywords are allowed:
547 followed by a regular expression that describes possible
551 followed by a regular expression that describes possible
555 followed by the output string corresponding to "yes".
558 followed by the output string corresponding to "no".
562 definition ends with the string
563 .IR "END LC_MESSAGES" .
565 The definition starts with the string
569 The following keywords are allowed:
572 folowed by number identifying the standard used for measurement.
573 The following values are recognized:
580 US customary measurements.
585 definition ends with the string
586 .IR "END LC_MEASUREMENT" .
588 The definition starts with the string
592 The following keywords are allowed:
593 .\" FIXME 'int_n_cs_precedes' is not documented
594 .\" FIXME 'int_n_sep_by_space' is not documented
595 .\" FIXME 'int_n_sign_posn' is not documented
596 .\" FIXME 'int_p_cs_precedes' is not documented
597 .\" FIXME 'int_p_sep_by_space' is not documented
598 .\" FIXME 'int_p_sign_posn' is not documented
601 followed by the international currency symbol.
603 4-character string containing the international currency symbol as
604 defined by the ISO 4217 standard (three characters) followed by a
608 followed by the local currency symbol.
611 followed by the string that will be used as the decimal delimiter
612 when formatting monetary quantities.
615 followed by the string that will be used as a group separator
616 when formatting monetary quantities.
619 followed by a string that describes the formatting of numeric
623 followed by a string that is used to indicate a positive sign for
627 followed by a string that is used to indicate a negative sign for
631 followed by the number of fractional digits that should be used when
633 .BR int_curr_symbol .
636 followed by the number of fractional digits that should be used when
638 .BR currency_symbol .
641 followed by an integer set to
647 should precede a nonnegative formatted monetary quantity or set to
649 if the symbol succeeds the value.
652 followed by an integer.
656 means that no space should be printed between the symbol and the
660 means that a space should be printed between the symbol and the
664 means that a space should be printed between the symbol and the
665 sign string, if adjacent.
669 followed by an integer that indicates the placement of
671 for a negative formatted monetary quantity.
675 the symbol succeeds the value.
678 the symbol precedes the value.
684 if no space separates the
688 from the value for a negative monetary quantity, set to
690 if a space separates the symbol from the value and set to
692 if a space separates the symbol and the sign string, if adjacent.
695 followed by an integer that indicates where the
697 should be placed for a nonnegative monetary quantity:
701 Parentheses enclose the quantity and the
704 .IR int_curr_symbol .
707 The sign string precedes the quantity and the
710 .IR int_curr_symbol .
713 The sign string succeeds the quantity and the
716 .IR int_curr_symbol .
719 The sign string precedes the
722 .IR int_curr_symbol .
725 The sign string succeeds the
728 .IR int_curr_symbol .
732 followed by an integer that indicates where the
734 should be placed for a negative monetary quantity.
735 The same integer values are recognized as for
740 definition ends with the string
741 .IR "END LC_MONETARY" .
743 The definition starts with the string
747 The following keywords are allowed:
750 followed by a string containing field descriptors that define
751 the format used for names in the locale.
752 The following field descriptors are recognized:
753 .\" From localedata/locales/uk_UA:
760 Family names in uppercase.
769 First given name with Latin letters.
775 Additional given name(s).
778 Initials for additional given name(s).
784 Salutation, such as "Doctor".
787 Abbreviated salutation, such as "Mr." or "Dr.".
790 Salutation, using the FDCC-sets conventions.
791 .\" 1 for the name_gen
792 .\" In glibc 2.19, %d1 is used in only:
793 .\" /home/mtk/ARCHIVE/GLIBC/glibc-2.19/localedata/locales/bem_ZM
794 .\" /home/mtk/ARCHIVE/GLIBC/glibc-2.19/localedata/locales/zh_HK
795 .\" In glibc 2.19, %d[2-5] appear to be not used at all
802 If the preceding field descriptor resulted in an empty string,
803 then the empty string, otherwise a space character.
807 followed by the general salutation for any gender.
810 followed by the salutation for men.
813 followed by the salutation for married women.
816 followed by the salutation for unmarried women.
819 followed by the salutation valid for all women.
823 definition ends with the string
826 The definition starts with the string
830 The following keywords are allowed:
833 followed by the string that will be used as the decimal delimiter
834 when formatting numeric quantities.
837 followed by the string that will be used as a group separator
838 when formatting numeric quantities.
841 followed by a string that describes the formatting of numeric
846 definition ends with the string
847 .IR "END LC_NUMERIC" .
849 The definition starts with the string
853 The following keywords are allowed:
856 followed by the height, in millimeters, of the standard paper format.
859 followed by the width, in millimeters, of the standard paper format.
863 definition ends with the string
866 The definition starts with the string
870 The following keywords are allowed:
873 followed by a string that contains field descriptors that identify
874 the format used to dial international numbers.
875 The following field descriptors are recognized:
876 .\" From localedata/locales/uk_UA
880 Area code without nationwide prefix (the prefix is often "0").
883 Area code including nationwide prefix.
886 Local number (within area code).
889 Extension (to local number).
895 Alternate carrier service code used for dialling abroad.
898 If the preceding field descriptor resulted in an empty string,
899 then the empty string, otherwise a space character.
903 followed by a string that contains field descriptors that identify
904 the format used to dial domestic numbers.
905 The recognized field descriptrs are the same as for
909 followed by the prefix used to call international phone numbers.
912 followed by the prefix used from other countries to dial this country.
916 definition ends with the string
917 .IR "END LC_TELEPHONE" .
919 The definition starts with the string
923 The following keywords are allowed:
924 .\" FIXME 'era', 'era_d_fmt', 'era_d_t_fmt', 'era_t_fmt', are not documented
925 .\" FIXME 'timezone' is not documented
928 followed by a list of abbreviated names of the days of the week.
929 The list starts with the first day of the week
935 followed by a list of names of the days of the week.
936 The list starts with the first day of the week
942 followed by a list of abbreviated month names.
945 followed by a list of month names.
948 The appropriate representation of the
955 The appropriate date and time format.
958 The appropriate date format.
961 The appropriate time format.
964 The appropriate time format when using 12h clock format.
967 followed by a list of three values:
968 The number of days in a week (by default 7),
969 a date of beginning of the week (by default corresponds to Sunday),
970 and the minimal length of the first week in year (by default 4).
971 Regarding the start of the week,
973 shall be used for Sunday and
975 shall be used for Monday.
976 Thus, countries using
978 should have local Sunday name as the first day in the
981 while countries using
983 should have Monday translation as the first item in the
987 .IR first_weekday " (since glibc 2.2)"
988 Number of the first day from the
990 list to be shown in calendar applications.
993 corresponds to either Sunday or Monday depending
994 on the value of the second
998 .IR first_workday " (since glibc 2.2)"
999 Number of the first working day from the
1004 .\" from localedata/locales/uk_UA
1005 followed by a value that indicates the direction for the
1006 display of calendar dates, as follows:
1020 followed by the appropriate date representation for
1025 definition ends with the string
1029 \(em database for the current locale setting of that category
1031 /usr/lib/nls/charmap/* \(em charmap-files
1033 POSIX.2, ISO/IEC 14652.
1035 This manual page isn't complete.
1037 .\" Jochen Hein (Hein@Student.TU-Clausthal.de)