1 '\" t -*- coding: UTF-8 -*-
2 .\" Copyright (C) 1994 Jochen Hein (Hein@Student.TU-Clausthal.de)
3 .\" Copyright (C) 2008 Petr Baudis (pasky@suse.cz)
4 .\" Copyright (C) 2014 Michael Kerrisk <mtk@manpages@gmail.com>
6 .\" %%%LICENSE_START(GPLv2+_SW_3_PARA)
7 .\" This program is free software; you can redistribute it and/or modify
8 .\" it under the terms of the GNU General Public License as published by
9 .\" the Free Software Foundation; either version 2 of the License, or
10 .\" (at your option) any later version.
12 .\" This program is distributed in the hope that it will be useful,
13 .\" but WITHOUT ANY WARRANTY; without even the implied warranty of
14 .\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
15 .\" GNU General Public License for more details.
17 .\" You should have received a copy of the GNU General Public
18 .\" License along with this manual; if not, see
19 .\" <http://www.gnu.org/licenses/>.
22 .\" 2008-06-17 Petr Baudis <pasky@suse.cz>
23 .\" LC_TIME: Describe first_weekday and first_workday
25 .TH LOCALE 5 2015-01-22 "Linux" "Linux User Manual"
27 locale \- describes a locale definition file
31 definition file contains all the information that the
33 command needs to convert it into the binary locale database.
35 The definition files consist of sections which each describe a
36 locale category in detail.
38 provides additional descriptions for these categories.
40 The locale definition file starts with a header that may consist
41 of the following keywords:
44 is followed by a character that should be used as the
45 escape-character for the rest of the file to mark characters that
46 should be interpreted in a special way.
47 It defaults to the backslash (\\).
50 is followed by a character that will be used as the
51 comment-character for the rest of the file.
52 It defaults to the number sign (#).
54 The locale definition has one part for each locale category.
55 Each part can be copied from another existing locale or
56 can be defined from scratch.
57 If the category should be copied,
58 the only valid keyword in the definition is
60 followed by the name of the locale in double quotes which should be
62 The exceptions for this rule are
68 statement can be followed by locale-specific rules and selected overrides.
70 When defining a category from scratch, all field descriptors and strings
71 should be defined as Unicode code points in angle brackets, unless
72 otherwise stated below.
73 For example, "€" is to be presented as "<U20AC>", "%a" as
74 "<U0025><U0061>", and "Monday" as
75 "<U0053><U0075><U006E><U0064><U0061><U0079>".
76 Values defined as Unicode code points must be in double quotes, plain
77 number values are not quoted (but
81 follow special formatting, see the system-provided locale files for
83 .SS Locale category sections
84 The following category sections are defined by POSIX:
98 In addition, since version 2.2,
99 the GNU C library supports the following nonstandard categories:
115 for a more detailed description of each category.
118 The definition starts with the string
122 The following keywords are allowed:
123 .\" Thanks to the kind folk who wrote localedata/locales/uk_UA
126 followed by a string containing field descriptors that define
127 the format used for postal addresses in the locale.
128 The following field descriptors are recognized:
129 .\" From localedata/locales/uk_UA:
133 .\" BUG: %l escape sequence from ISO/IEC 14652:2002 is not supported
135 .\" Person's name, possibly constructed with the
140 .\" https://sourceware.org/bugzilla/show_bug.cgi?id=16983
143 Care of person, or organization.
155 Street or block (e.g., Japanese) name.
158 House number or designation.
161 Insert an end-of-line if the previous descriptor's value was not an empty
162 string; otherwise ignore.
165 Insert a space if the previous descriptor's value was not an empty string;
169 Room number, door designation.
175 Country designation, from the <country_post> keyword.
178 .\" BUG: %l escape sequence from ISO/IEC 14652:2002 is not
179 .\" supported by glibc
180 .\" Local township within town or city.
182 .\" https://sourceware.org/bugzilla/show_bug.cgi?id=16983
185 Zip number, postal code.
191 State, province, or prefecture.
194 Country, as taken from data record.
196 Each field descriptor may have an \(aqR\(aq after
197 the \(aq%\(aq to specify that the
198 information is taken from a Romanized version string of the
204 followed by the country name in the language of the current document
205 (e.g., "Deutschland" for the
210 followed by the abbreviation of the country (see CERT_MAILCODES).
213 followed by the two-letter abbreviation of the country (ISO 3166).
216 followed by the three-letter abbreviation of the country (ISO 3166).
219 followed by the numeric country code as plain numbers (ISO 3166).
222 followed by the code for the country car number.
225 followed by the ISBN code (for books).
228 followed by the language name in the language of the current document.
231 followed by the two-letter abbreviation of the language (ISO 639).
234 followed by the three-letter abbreviation of the language (ISO 639-2/T).
237 followed by the three-letter abbreviation of the language for library
239 Applications should in general prefer
246 definition ends with the string
247 .IR "END LC_ADDRESS" .
249 The definition starts with the string
253 The following keywords are allowed:
256 followed by a list of uppercase letters.
261 are included automatically.
262 Characters also specified as
271 followed by a list of lowercase letters.
276 are included automatically.
277 Characters also specified as
286 followed by a list of letters.
287 All character specified as either
291 are automatically included.
292 Characters also specified as
301 followed by the characters classified as numeric digits.
308 They are included by default in this class.
311 followed by a list of characters defined as white-space
313 Characters also specified as
326 .BR <carriage-return> ,
330 are automatically included.
333 followed by a list of control characters.
334 Characters also specified as
347 followed by a list of punctuation characters.
358 character are not allowed.
361 followed by a list of printable characters, not including the
364 The characters defined as
372 are automatically included.
373 Characters also specified as
378 followed by a list of printable characters, including the
381 The characters defined as
390 character are automatically included.
391 Characters also specified as
396 followed by a list of characters classified as hexadecimal
398 The decimal digits must be included followed by one or
399 more set of six characters in ascending order.
401 characters are included by default:
413 followed by a list of characters classified as
419 are automatically included.
422 followed by a list of locale-specific character class names
423 which are then to be defined in the locale.
426 followed by a list of mappings from lowercase to uppercase
428 Each mapping is a pair of a lowercase and an uppercase letter
431 and enclosed in parentheses.
432 The members of the list are separated
436 followed by a list of mappings from uppercase to lowercase
438 If the keyword tolower is not present, the reverse of the
439 toupper list is used.
442 followed by a list of mapping pairs of
443 characters and letters
444 to be used in titles (headings).
447 followed by a locale-specific character class definition,
448 starting with the class name followed by the characters
449 belonging to the class.
452 followed by a list of locale-specific character map names
453 which are then to be defined in the locale.
456 followed by a list of alternate output digits for the locale.
459 followed by a list of mapping pairs of
460 alternate digits and separators
461 for input digits for the locale.
464 followed by a list of mapping pairs of
466 for output for the locale.
469 marks the start of the transliteration rules section.
470 The section can contain the
472 keyword in the beginning followed by
473 locale-specific rules and overrides.
474 Any rule specified in the locale file
475 will override any rule
476 copied or included from other files.
477 In case of duplicate rule definitions in the locale file,
478 only the first rule is used.
480 A transliteration rule consist of a character to be transliterated
481 followed by a list of transliteration targets separated by semicolons.
482 The first target which can be presented in the target character set
483 is used, if none of them can be used the
485 character will be used instead.
488 in the transliteration rules section includes
489 a transliteration rule file
490 (and optionally a repertoire map file)
494 in the transliteration rules section
495 defines the default character to be used for
496 transliteration where none of the targets cannot be presented
497 in the target character set.
500 marks the end of the transliteration rules.
504 definition ends with the string
507 Due to limitations of glibc not all POSIX-options are implemented.
509 The definition starts with the string
513 The following keywords are allowed:
514 .\" FIXME The following LC_COLLATE keywords are not documented:
517 .\" reorder-sections-after
518 .\" reorder-sections-end
520 .\" symbol-equivalence
523 followed by the definition of a collating-element symbol
524 representing a multicharacter collating element.
527 followed by the definition of a collating symbol
528 that can be used in collation order statements.
530 The order-definition starts with a line:
533 followed by a list of keywords chosen from
538 The order definition consists of lines that describe the order
539 and is terminated with the keyword
544 definition ends with the string
545 .IR "END LC_COLLATE" .
546 .SS LC_IDENTIFICATION
547 The definition starts with the string
551 The values in this category are defined as plain strings.
553 The following keywords are allowed:
556 followed by the title of the locale document
557 (e.g., "Maori language locale for New Zealand").
560 followed by the name of the organization that maintains this document.
563 followed by the address of the organization that maintains this document.
566 followed by the name of the contact person at
567 the organization that maintains this document.
570 followed by the email address of the person or
571 organization that maintains this document.
574 followed by the telephone number (in international format)
575 of the organization that maintains this document.
578 followed by the fax number (in international format)
579 of the organization that maintains this document.
582 followed by the name of the language to which this document applies.
585 followed by the name of the country/geographic extent
586 to which this document applies.
589 followed by a description of the audience for which this document is intended.
592 followed by a description of any special application
593 for which this document is intended.
596 .\" as far as I can tell... (mtk)
597 followed by the short name for this document.
600 followed by the revision number of this document.
603 followed by the revision date of this document.
605 In addition, for each of the categories defined by the document,
606 there should be a line starting with the keyword
610 a string that identifies this locale category definition,
620 definition ends with the string
621 .IR "END LC_IDENTIFICATION" .
623 The definition starts with the string
627 The following keywords are allowed:
630 followed by a regular expression that describes possible
634 followed by a regular expression that describes possible
638 followed by the output string corresponding to "yes".
641 followed by the output string corresponding to "no".
645 definition ends with the string
646 .IR "END LC_MESSAGES" .
648 The definition starts with the string
652 The following keywords are allowed:
655 followed by number identifying the standard used for measurement.
656 The following values are recognized:
663 US customary measurements.
668 definition ends with the string
669 .IR "END LC_MEASUREMENT" .
671 The definition starts with the string
676 .IR int_curr_symbol ,
677 .IR currency_symbol ,
678 .IR mon_decimal_point ,
679 .IR mon_thousands_sep ,
683 are defined as Unicode code points, the others as plain numbers.
685 The following keywords are allowed:
688 followed by the international currency symbol.
690 4-character string containing the international currency symbol as
691 defined by the ISO 4217 standard (three characters) followed by a
695 followed by the local currency symbol.
698 followed by the string that will be used as the decimal delimiter
699 when formatting monetary quantities.
702 followed by the string that will be used as a group separator
703 when formatting monetary quantities.
706 followed by a sequence of integers separated by semicolons that
707 describe the formatting of monetary quantities.
713 followed by a string that is used to indicate a positive sign for
717 followed by a string that is used to indicate a negative sign for
721 followed by the number of fractional digits that should be used when
723 .IR int_curr_symbol .
726 followed by the number of fractional digits that should be used when
728 .IR currency_symbol .
731 followed by an integer that indicates the placement of
733 for a nonnegative formatted monetary quantity:
737 the symbol succeeds the value.
740 the symbol precedes the value.
744 followed by an integer that indicates the separation of
745 .IR currency_symbol ,
746 the sign string, and the value for a nonnegative formatted monetary quantity.
747 The following values are recognized:
751 No space separates the currency symbol and the value.
754 If the currency symbol and the sign string are adjacent,
755 a space separates them from the value;
756 otherwise a space separates the currency symbol and the value.
759 If the currency symbol and the sign string are adjacent,
760 a space separates them from the value;
761 otherwise a space separates the sign string and the value.
765 followed by an integer that indicates the placement of
767 for a negative formatted monetary quantity.
768 The same values are recognized as for
772 followed by an integer that indicates the separation of
773 .IR currency_symbol ,
774 the sign string, and the value for a negative formatted monetary quantity.
775 The same values are recognized as for
779 followed by an integer that indicates where the
781 should be placed for a nonnegative monetary quantity:
785 Parentheses enclose the quantity and the
788 .IR int_curr_symbol .
791 The sign string precedes the quantity and the
794 .IR int_curr_symbol .
797 The sign string succeeds the quantity and the
800 .IR int_curr_symbol .
803 The sign string precedes the
806 .IR int_curr_symbol .
809 The sign string succeeds the
812 .IR int_curr_symbol .
816 followed by an integer that indicates where the
818 should be placed for a negative monetary quantity.
819 The same values are recognized as for
823 followed by an integer that indicates the placement of
824 .I int_currency_symbol
825 for a nonnegative internationally formatted monetary quantity.
826 The same values are recognized as for
830 followed by an integer that indicates the placement of
831 .I int_currency_symbol
832 for a negative internationally formatted monetary quantity.
833 The same values are recognized as for
836 .I int_p_sep_by_space
837 followed by an integer that indicates the separation of
838 .IR int_currency_symbol ,
840 and the value for a nonnegative internationally formatted monetary quantity.
841 The same values are recognized as for
844 .I int_n_sep_by_space
845 followed by an integer that indicates the separation of
846 .IR int_currency_symbol ,
848 and the value for a negative internationally formatted monetary quantity.
849 The same values are recognized as for
853 followed by an integer that indicates where the
855 should be placed for a nonnegative
856 internationally formatted monetary quantity.
857 The same values are recognized as for
861 followed by an integer that indicates where the
863 should be placed for a negative
864 internationally formatted monetary quantity.
865 The same values are recognized as for
870 definition ends with the string
871 .IR "END LC_MONETARY" .
873 The definition starts with the string
877 Various keywords are allowed, but only
880 Other keywords are needed only if there is common convention to
881 use the corresponding salutation in this locale.
882 The allowed keywords are as follows:
885 followed by a string containing field descriptors that define
886 the format used for names in the locale.
887 The following field descriptors are recognized:
888 .\" From localedata/locales/uk_UA:
895 Family names in uppercase.
904 First given name with Latin letters.
910 Additional given name(s).
913 Initials for additional given name(s).
919 Salutation, such as "Doctor".
922 Abbreviated salutation, such as "Mr." or "Dr.".
925 Salutation, using the FDCC-sets conventions.
926 .\" 1 for the name_gen
927 .\" In glibc 2.19, %d1 is used in only:
928 .\" /home/mtk/ARCHIVE/GLIBC/glibc-2.19/localedata/locales/bem_ZM
929 .\" /home/mtk/ARCHIVE/GLIBC/glibc-2.19/localedata/locales/zh_HK
930 .\" In glibc 2.19, %d[2-5] appear to be not used at all
937 If the preceding field descriptor resulted in an empty string,
938 then the empty string, otherwise a space character.
942 followed by the general salutation for any gender.
945 followed by the salutation for men.
948 followed by the salutation for married women.
951 followed by the salutation for unmarried women.
954 followed by the salutation valid for all women.
958 definition ends with the string
961 The definition starts with the string
965 The following keywords are allowed:
968 followed by the string that will be used as the decimal delimiter
969 when formatting numeric quantities.
972 followed by the string that will be used as a group separator
973 when formatting numeric quantities.
976 followed by a sequence of integers as plain numbers separated by
977 semicolons that describe the formatting of numeric quantities.
979 Each integer specifies the number of digits in a group.
980 The first integer defines the size of the group immediately
981 to the left of the decimal delimiter.
982 Subsequent integers define succeeding groups to the
983 left of the previous group.
984 If the last integer is not \-1, then the size of the previous group
985 (if any) is repeatedly used for the remainder of the digits.
986 If the last integer is \-1, then no further grouping is performed.
990 definition ends with the string
991 .IR "END LC_NUMERIC" .
993 The definition starts with the string
997 Values in this category are defined as plain numbers.
999 The following keywords are allowed:
1002 followed by the height, in millimeters, of the standard paper format.
1005 followed by the width, in millimeters, of the standard paper format.
1009 definition ends with the string
1010 .IR "END LC_PAPER" .
1012 The definition starts with the string
1014 in the first column.
1016 The following keywords are allowed:
1019 followed by a string that contains field descriptors that identify
1020 the format used to dial international numbers.
1021 The following field descriptors are recognized:
1022 .\" From localedata/locales/uk_UA
1026 Area code without nationwide prefix (the prefix is often "00").
1029 Area code including nationwide prefix.
1032 Local number (within area code).
1035 Extension (to local number).
1041 Alternate carrier service code used for dialing abroad.
1044 If the preceding field descriptor resulted in an empty string,
1045 then the empty string, otherwise a space character.
1049 followed by a string that contains field descriptors that identify
1050 the format used to dial domestic numbers.
1051 The recognized field descriptors are the same as for
1055 followed by the prefix used to call international phone numbers.
1058 followed by the prefix used from other countries to dial this country.
1062 definition ends with the string
1063 .IR "END LC_TELEPHONE" .
1065 The definition starts with the string
1067 in the first column.
1069 The following keywords are allowed:
1070 .\" FIXME The following LC_TIME keywords are not documented:
1077 followed by a list of abbreviated names of the days of the week.
1078 The list starts with the first day of the week
1081 (Sunday by default).
1085 followed by a list of names of the days of the week.
1086 The list starts with the first day of the week
1089 (Sunday by default).
1093 followed by a list of abbreviated month names.
1096 followed by a list of month names.
1099 followed by the appropriate date and time format
1104 followed by the appropriate date format
1109 followed by the appropriate time format
1114 followed by the appropriate representation of the
1119 This should be left empty for locales not using AM/PM convention.
1122 followed by the appropriate time format
1125 when using 12h clock format.
1126 This should be left empty for locales not using AM/PM convention.
1129 followed by the alternative digits used for date and time in the locale.
1132 followed by a list of three values as plain numbers:
1133 The number of days in a week (by default 7),
1134 a date of beginning of the week (by default corresponds to Sunday),
1135 and the minimal length of the first week in year (by default 4).
1136 Regarding the start of the week,
1138 shall be used for Sunday and
1140 shall be used for Monday.
1143 .IR first_weekday " (since glibc 2.2)"
1144 followed by the number of the first day from the
1146 list to be shown in calendar applications.
1147 The default value of
1149 (plain number) corresponds to either Sunday or Monday depending
1150 on the value of the second
1155 .IR first_workday " (since glibc 2.2)"
1156 followed by the number of the first working day from the
1159 The default value is
1165 .\" from localedata/locales/uk_UA
1166 followed by a plain number value that indicates the direction for the
1167 display of calendar dates, as follows:
1171 Left-right from top.
1177 Right-left from top.
1181 followed by the appropriate date representation for
1188 definition ends with the string
1192 .I /usr/lib/locale/locale-archive
1193 Usual default locale archive location.
1195 .I /usr/share/i18n/locales
1196 Usual default path for locale definition files.
1198 POSIX.2, ISO/IEC TR 14652.
1200 The collective GNU C library community wisdom regarding
1208 https://sourceware.org/glibc/wiki/Locales
1211 The value of the second
1213 list item specifies the base of the
1220 specifies the offset of the first day-of-week in the
1226 For compatibility reasons, all glibc locales should set the value of the
1231 (Sunday) and base the
1235 lists appropriately, and set
1243 depending on whether the week and work week actually starts on Sunday or
1244 Monday for the locale.
1246 This manual page isn't complete.
1248 .\" Jochen Hein (Hein@Student.TU-Clausthal.de)