Debian Codegraph @

upstream/debian-unstable/man5/locale.5

raw
1 .\" Copyright 1994, Jochen Hein <[email protected]>
2 .\" Copyright 2008, Petr Baudis <[email protected]>
3 .\" Copyright 2014, Michael Kerrisk <[email protected]>
4 .\" Copyright, the authors of the Linux man-pages project
5 .\"
6 .\" SPDX-License-Identifier: GPL-2.0-or-later
7 .\"
8 .TH locale 5 2026-02-08 "Linux man-pages 6.18"
9 .SH NAME
10 locale \- describes a locale definition file
11 .SH DESCRIPTION
12 The
13 .B locale
14 definition file contains all the information that the
15 .BR localedef (1)
16 command needs to convert it into the binary locale database.
17 .P
18 The definition files consist of sections which each describe a
19 locale category in detail.
20 See
21 .BR locale (7)
22 for additional details for these categories.
23 .SS Syntax
24 The locale definition file starts with a header that may consist
25 of the following keywords:
26 .TP
27 .I escape_char
28 is followed by a character that should be used as the
29 escape-character for the rest of the file to mark characters that
30 should be interpreted in a special way.
31 It defaults to the backslash (\[rs]).
32 .TP
33 .I comment_char
34 is followed by a character that will be used as the
35 comment-character for the rest of the file.
36 It defaults to the number sign (#).
37 .P
38 The locale definition has one part for each locale category.
39 Each part can be copied from another existing locale or
40 can be defined from scratch.
41 If the category should be copied,
42 the only valid keyword in the definition is
43 .I copy
44 followed by the name of the locale in double quotes which should be
45 copied.
46 The exceptions for this rule are
47 .B LC_COLLATE
48 and
49 .B LC_CTYPE
50 where a
51 .I copy
52 statement can be followed by locale-specific rules and selected overrides.
53 .P
54 When defining a locale or a category from scratch, an existing system-
55 provided locale definition file should be used as a reference to follow
56 common glibc conventions.
57 .SS Locale category sections
58 The following category sections are defined by POSIX:
59 .IP \[bu] 3
60 .B LC_CTYPE
61 .IP \[bu]
62 .B LC_COLLATE
63 .IP \[bu]
64 .B LC_MESSAGES
65 .IP \[bu]
66 .B LC_MONETARY
67 .IP \[bu]
68 .B LC_NUMERIC
69 .IP \[bu]
70 .B LC_TIME
71 .P
72 In addition, since glibc 2.2,
73 the GNU C library supports the following nonstandard categories:
74 .IP \[bu] 3
75 .B LC_ADDRESS
76 .IP \[bu]
77 .B LC_IDENTIFICATION
78 .IP \[bu]
79 .B LC_MEASUREMENT
80 .IP \[bu]
81 .B LC_NAME
82 .IP \[bu]
83 .B LC_PAPER
84 .IP \[bu]
85 .B LC_TELEPHONE
86 .P
87 See
88 .BR locale (7)
89 for a more detailed description of each category.
90 .SS LC_ADDRESS
91 The definition starts with the string
92 .I LC_ADDRESS
93 in the first column.
94 .P
95 The following keywords are allowed:
96 .TP
97 .I postal_fmt
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 .RS
102 .TP
103 %n
104 Person's name, possibly constructed with the
105 .B LC_NAME
106 .I name_fmt
107 keyword (since glibc 2.24).
108 .TP 4
109 %a
110 Care of person, or organization.
111 .TP
112 %f
113 Firm name.
114 .TP
115 %d
116 Department name.
117 .TP
118 %b
119 Building name.
120 .TP
121 %s
122 Street or block (e.g., Japanese) name.
123 .TP
124 %h
125 House number or designation.
126 .TP
127 %N
128 Insert an end-of-line
129 if the previous descriptor's value was not an empty string;
130 otherwise,
131 ignore.
132 .TP
133 %t
134 Insert a space if the previous descriptor's value was not an empty string;
135 otherwise,
136 ignore.
137 .TP
138 %r
139 Room number, door designation.
140 .TP
141 %e
142 Floor number.
143 .TP
144 %C
145 Country designation, from the
146 .I country_post
147 keyword.
148 .TP
149 %l
150 Local township within town or city (since glibc 2.24).
151 .TP
152 %z
153 Zip number, postal code.
154 .TP
155 %T
156 Town, city.
157 .TP
158 %S
159 State, province, or prefecture.
160 .TP
161 %c
162 Country, as taken from data record.
163 .P
164 Each field descriptor may have an \[aq]R\[aq] after
165 the \[aq]%\[aq] to specify that the
166 information is taken from a Romanized version string of the
167 entity.
168 .RE
169 .TP
170 .I country_name
171 followed by the country name in the language of the current document
172 (e.g., "Deutschland" for the
173 .B de_DE
174 locale).
175 .TP
176 .I country_post
177 followed by the abbreviation of the country
178 (for example, CEPT-MAILCODE codes).
179 .TP
180 .I country_ab2
181 followed by the two-letter abbreviation of the country (ISO\~3166).
182 .TP
183 .I country_ab3
184 followed by the three-letter abbreviation of the country (ISO\~3166).
185 .TP
186 .I country_num
187 followed by the numeric country code (ISO\~3166).
188 .TP
189 .I country_car
190 followed by the international license plate country code.
191 .TP
192 .I country_isbn
193 followed by the ISBN code (for books).
194 .TP
195 .I lang_name
196 followed by the language name in the language of the current document.
197 .TP
198 .I lang_ab
199 followed by the two-letter abbreviation of the language (ISO\~639).
200 .TP
201 .I lang_term
202 followed by the three-letter abbreviation of the language (ISO\~639-2/T).
203 .TP
204 .I lang_lib
205 followed by the three-letter abbreviation of the language for library
206 use (ISO\~639-2/B).
207 Applications should in general prefer
208 .I lang_term
209 over
210 .IR lang_lib .
211 .P
212 The
213 .B LC_ADDRESS
214 definition ends with the string
215 .IR "END LC_ADDRESS" .
216 .SS LC_CTYPE
217 The definition starts with the string
218 .I LC_CTYPE
219 in the first column.
220 .P
221 The following keywords are allowed:
222 .TP
223 .I upper
224 followed by a list of uppercase letters.
225 The letters
226 .B A
227 through
228 .B Z
229 are included automatically.
230 Characters also specified as
231 .BR cntrl ,
232 .BR digit ,
233 .BR punct ,
234 or
235 .B space
236 are not allowed.
237 .TP
238 .I lower
239 followed by a list of lowercase letters.
240 The letters
241 .B a
242 through
243 .B z
244 are included automatically.
245 Characters also specified as
246 .BR cntrl ,
247 .BR digit ,
248 .BR punct ,
249 or
250 .B space
251 are not allowed.
252 .TP
253 .I alpha
254 followed by a list of letters.
255 All character specified as either
256 .B upper
257 or
258 .B lower
259 are automatically included.
260 Characters also specified as
261 .BR cntrl ,
262 .BR digit ,
263 .BR punct ,
264 or
265 .B space
266 are not allowed.
267 .TP
268 .I digit
269 followed by the characters classified as numeric digits.
270 Only the
271 digits
272 .B 0
273 through
274 .B 9
275 are allowed.
276 They are included by default in this class.
277 .TP
278 .I space
279 followed by a list of characters defined as white-space
280 characters.
281 Characters also specified as
282 .BR upper ,
283 .BR lower ,
284 .BR alpha ,
285 .BR digit ,
286 .BR graph ,
287 or
288 .B xdigit
289 are not allowed.
290 The characters
291 .BR <space> ,
292 .BR <form-feed> ,
293 .BR <newline> ,
294 .BR <carriage-return> ,
295 .BR <tab> ,
296 and
297 .B <vertical-tab>
298 are automatically included.
299 .TP
300 .I cntrl
301 followed by a list of control characters.
302 Characters also specified as
303 .BR upper ,
304 .BR lower ,
305 .BR alpha ,
306 .BR digit ,
307 .BR punct ,
308 .BR graph ,
309 .BR print ,
310 or
311 .B xdigit
312 are not allowed.
313 .TP
314 .I punct
315 followed by a list of punctuation characters.
316 Characters also
317 specified as
318 .BR upper ,
319 .BR lower ,
320 .BR alpha ,
321 .BR digit ,
322 .BR cntrl ,
323 .BR xdigit ,
324 or the
325 .B <space>
326 character are not allowed.
327 .TP
328 .I graph
329 followed by a list of printable characters, not including the
330 .B <space>
331 character.
332 The characters defined as
333 .BR upper ,
334 .BR lower ,
335 .BR alpha ,
336 .BR digit ,
337 .BR xdigit ,
338 and
339 .B punct
340 are automatically included.
341 Characters also specified as
342 .B cntrl
343 are not allowed.
344 .TP
345 .I print
346 followed by a list of printable characters, including the
347 .B <space>
348 character.
349 The characters defined as
350 .BR upper ,
351 .BR lower ,
352 .BR alpha ,
353 .BR digit ,
354 .BR xdigit ,
355 .BR punct ,
356 and the
357 .B <space>
358 character are automatically included.
359 Characters also specified as
360 .B cntrl
361 are not allowed.
362 .TP
363 .I xdigit
364 followed by a list of characters classified as hexadecimal
365 digits.
366 The decimal digits must be included followed by one or
367 more set of six characters in ascending order.
368 The following
369 characters are included by default:
370 .B 0
371 through
372 .BR 9 ,
373 .B a
374 through
375 .BR f ,
376 .B A
377 through
378 .BR F .
379 .TP
380 .I blank
381 followed by a list of characters classified as
382 .BR blank .
383 The characters
384 .B <space>
385 and
386 .B <tab>
387 are automatically included.
388 .TP
389 .I charclass
390 followed by a list of locale-specific character class names
391 which are then to be defined in the locale.
392 .TP
393 .I toupper
394 followed by a list of mappings from lowercase to uppercase
395 letters.
396 Each mapping is a pair of a lowercase and an uppercase letter
397 separated with a
398 .B ,
399 and enclosed in parentheses.
400 .TP
401 .I tolower
402 followed by a list of mappings from uppercase to lowercase
403 letters.
404 If the keyword tolower is not present, the reverse of the
405 toupper list is used.
406 .TP
407 .I map totitle
408 followed by a list of mapping pairs of
409 characters and letters
410 to be used in titles (headings).
411 .TP
412 .I class
413 followed by a locale-specific character class definition,
414 starting with the class name followed by the characters
415 belonging to the class.
416 .TP
417 .I charconv
418 followed by a list of locale-specific character mapping names
419 which are then to be defined in the locale.
420 .TP
421 .I outdigit
422 followed by a list of alternate output digits for the locale.
423 .TP
424 .I map to_inpunct
425 followed by a list of mapping pairs of
426 alternate digits and separators
427 for input digits for the locale.
428 .TP
429 .I map to_outpunct
430 followed by a list of mapping pairs of
431 alternate separators
432 for output for the locale.
433 .TP
434 .I translit_start
435 marks the start of the transliteration rules section.
436 The section can contain the
437 .I include
438 keyword in the beginning followed by
439 locale-specific rules and overrides.
440 Any rule specified in the locale file
441 will override any rule
442 copied or included from other files.
443 In case of duplicate rule definitions in the locale file,
444 only the first rule is used.
445 .IP
446 A transliteration rule consist of a character to be transliterated
447 followed by a list of transliteration targets separated by semicolons.
448 The first target which can be presented in the target character set
449 is used, if none of them can be used the
450 .I default_missing
451 character will be used instead.
452 .TP
453 .I include
454 in the transliteration rules section includes
455 a transliteration rule file
456 (and optionally a repertoire map file).
457 .TP
458 .I default_missing
459 in the transliteration rules section
460 defines the default character to be used for
461 transliteration where none of the targets cannot be presented
462 in the target character set.
463 .TP
464 .I translit_end
465 marks the end of the transliteration rules.
466 .P
467 The
468 .B LC_CTYPE
469 definition ends with the string
470 .IR "END LC_CTYPE" .
471 .SS LC_COLLATE
472 Note that glibc does not support all POSIX-defined options,
473 only the options described below are supported (as of glibc 2.23).
474 .P
475 The definition starts with the string
476 .I LC_COLLATE
477 in the first column.
478 .P
479 The following keywords are allowed:
480 .TP
481 .I coll_weight_max
482 followed by the number representing used collation levels.
483 This keyword is recognized but ignored by glibc.
484 .TP
485 .I collating\-element
486 followed by the definition of a collating-element symbol
487 representing a multicharacter collating element.
488 .TP
489 .I collating\-symbol
490 followed by the definition of a collating symbol
491 that can be used in collation order statements.
492 .TP
493 .I define
494 followed by
495 .B string
496 to be evaluated in an
497 .I ifdef
498 .B string
499 /
500 .I else
501 /
502 .I endif
503 construct.
504 .TP
505 .I reorder\-after
506 followed by a redefinition of a collation rule.
507 .TP
508 .I reorder\-end
509 marks the end of the redefinition of a collation rule.
510 .TP
511 .I reorder\-sections\-after
512 followed by a script name to reorder listed scripts after.
513 .TP
514 .I reorder\-sections\-end
515 marks the end of the reordering of sections.
516 .TP
517 .I script
518 followed by a declaration of a script.
519 .TP
520 .I symbol\-equivalence
521 followed by a collating-symbol to be equivalent to another defined
522 collating-symbol.
523 .P
524 The collation rule definition starts with a line:
525 .TP
526 .I order_start
527 followed by a list of keywords chosen from
528 .BR forward ,
529 .BR backward ,
530 or
531 .BR position .
532 The order definition consists of lines that describe the collation
533 order and is terminated with the keyword
534 .IR order_end .
535 .P
536 The
537 .B LC_COLLATE
538 definition ends with the string
539 .IR "END LC_COLLATE" .
540 .SS LC_IDENTIFICATION
541 The definition starts with the string
542 .I LC_IDENTIFICATION
543 in the first column.
544 .P
545 The following keywords are allowed:
546 .TP
547 .I title
548 followed by the title of the locale document
549 (e.g., "Maori language locale for New Zealand").
550 .TP
551 .I source
552 followed by the name of the organization that maintains this document.
553 .TP
554 .I address
555 followed by the address of the organization that maintains this document.
556 .TP
557 .I contact
558 followed by the name of the contact person at
559 the organization that maintains this document.
560 .TP
561 .I email
562 followed by the email address of the person or
563 organization that maintains this document.
564 .TP
565 .I tel
566 followed by the telephone number (in international format)
567 of the organization that maintains this document.
568 As of glibc 2.24, this keyword is deprecated in favor of
569 other contact methods.
570 .TP
571 .I fax
572 followed by the fax number (in international format)
573 of the organization that maintains this document.
574 As of glibc 2.24, this keyword is deprecated in favor of
575 other contact methods.
576 .TP
577 .I language
578 followed by the name of the language to which this document applies.
579 .TP
580 .I territory
581 followed by the name of the country/geographic extent
582 to which this document applies.
583 .TP
584 .I audience
585 followed by a description of the audience for which this document is
586 intended.
587 .TP
588 .I application
589 followed by a description of any special application
590 for which this document is intended.
591 .TP
592 .I abbreviation
593 followed by the short name for provider of the source of this document.
594 .TP
595 .I revision
596 followed by the revision number of this document.
597 .TP
598 .I date
599 followed by the revision date of this document.
600 .P
601 In addition, for each of the categories defined by the document,
602 there should be a line starting with the keyword
603 .IR category ,
604 followed by:
605 .IP (1) 5
606 a string that identifies this locale category definition,
607 .IP (2)
608 a semicolon, and
609 .IP (3)
610 one of the
611 .B LC_*
612 identifiers.
613 .P
614 The
615 .B LC_IDENTIFICATION
616 definition ends with the string
617 .IR "END LC_IDENTIFICATION" .
618 .SS LC_MESSAGES
619 The definition starts with the string
620 .I LC_MESSAGES
621 in the first column.
622 .P
623 The following keywords are allowed:
624 .TP
625 .I yesexpr
626 followed by a regular expression that describes possible
627 yes-responses.
628 .TP
629 .I noexpr
630 followed by a regular expression that describes possible
631 no-responses.
632 .TP
633 .I yesstr
634 followed by the output string corresponding to "yes".
635 .TP
636 .I nostr
637 followed by the output string corresponding to "no".
638 .P
639 The
640 .B LC_MESSAGES
641 definition ends with the string
642 .IR "END LC_MESSAGES" .
643 .SS LC_MEASUREMENT
644 The definition starts with the string
645 .I LC_MEASUREMENT
646 in the first column.
647 .P
648 The following keywords are allowed:
649 .TP
650 .I measurement
651 followed by number identifying the standard used for measurement.
652 The following values are recognized:
653 .RS
654 .TP 4
655 .B 1
656 Metric.
657 .TP
658 .B 2
659 US customary measurements.
660 .RE
661 .P
662 The
663 .B LC_MEASUREMENT
664 definition ends with the string
665 .IR "END LC_MEASUREMENT" .
666 .SS LC_MONETARY
667 The definition starts with the string
668 .I LC_MONETARY
669 in the first column.
670 .P
671 The following keywords are allowed:
672 .TP
673 .I int_curr_symbol
674 followed by the international currency symbol.
675 This must be a
676 4-character string containing the international currency symbol as
677 defined by the ISO\~4217 standard (three characters) followed by a
678 separator.
679 .TP
680 .I currency_symbol
681 followed by the local currency symbol.
682 .TP
683 .I mon_decimal_point
684 followed by the single-character string that will be used as the
685 decimal delimiter when formatting monetary quantities.
686 .TP
687 .I mon_thousands_sep
688 followed by the single-character string that will be used as a group
689 separator when formatting monetary quantities.
690 .TP
691 .I mon_grouping
692 followed by a sequence of integers separated by semicolons that
693 describe the formatting of monetary quantities.
694 See
695 .I grouping
696 below for details.
697 .TP
698 .I positive_sign
699 followed by a string that is used to indicate a positive sign for
700 monetary quantities.
701 .TP
702 .I negative_sign
703 followed by a string that is used to indicate a negative sign for
704 monetary quantities.
705 .TP
706 .I int_frac_digits
707 followed by the number of fractional digits that should be used when
708 formatting with the
709 .IR int_curr_symbol .
710 .TP
711 .I frac_digits
712 followed by the number of fractional digits that should be used when
713 formatting with the
714 .IR currency_symbol .
715 .TP
716 .I p_cs_precedes
717 followed by an integer that indicates the placement of
718 .I currency_symbol
719 for a nonnegative formatted monetary quantity:
720 .RS
721 .TP 4
722 .B 0
723 the symbol succeeds the value.
724 .TP
725 .B 1
726 the symbol precedes the value.
727 .RE
728 .TP
729 .I p_sep_by_space
730 followed by an integer that indicates the separation of
731 .IR currency_symbol ,
732 the sign string, and the value for a nonnegative formatted monetary quantity.
733 The following values are recognized:
734 .RS
735 .TP 4
736 .B 0
737 No space separates the currency symbol and the value.
738 .TP
739 .B 1
740 If the currency symbol and the sign string are adjacent,
741 a space separates them from the value;
742 otherwise a space separates the currency symbol and the value.
743 .TP
744 .B 2
745 If the currency symbol and the sign string are adjacent,
746 a space separates them from the value;
747 otherwise a space separates the sign string and the value.
748 .RE
749 .TP
750 .I n_cs_precedes
751 followed by an integer that indicates the placement of
752 .I currency_symbol
753 for a negative formatted monetary quantity.
754 The same values are recognized as for
755 .IR p_cs_precedes .
756 .TP
757 .I n_sep_by_space
758 followed by an integer that indicates the separation of
759 .IR currency_symbol ,
760 the sign string, and the value for a negative formatted monetary quantity.
761 The same values are recognized as for
762 .IR p_sep_by_space .
763 .TP
764 .I p_sign_posn
765 followed by an integer that indicates where the
766 .I positive_sign
767 should be placed for a nonnegative monetary quantity:
768 .RS
769 .TP 4
770 .B 0
771 Parentheses enclose the quantity and the
772 .I currency_symbol
773 or
774 .IR int_curr_symbol .
775 .TP
776 .B 1
777 The sign string precedes the quantity and the
778 .I currency_symbol
779 or the
780 .IR int_curr_symbol .
781 .TP
782 .B 2
783 The sign string succeeds the quantity and the
784 .I currency_symbol
785 or the
786 .IR int_curr_symbol .
787 .TP
788 .B 3
789 The sign string precedes the
790 .I currency_symbol
791 or the
792 .IR int_curr_symbol .
793 .TP
794 .B 4
795 The sign string succeeds the
796 .I currency_symbol
797 or the
798 .IR int_curr_symbol .
799 .RE
800 .TP
801 .I n_sign_posn
802 followed by an integer that indicates where the
803 .I negative_sign
804 should be placed for a negative monetary quantity.
805 The same values are recognized as for
806 .IR p_sign_posn .
807 .TP
808 .I int_p_cs_precedes
809 followed by an integer that indicates the placement of
810 .I int_curr_symbol
811 for a nonnegative internationally formatted monetary quantity.
812 The same values are recognized as for
813 .IR p_cs_precedes .
814 .TP
815 .I int_n_cs_precedes
816 followed by an integer that indicates the placement of
817 .I int_curr_symbol
818 for a negative internationally formatted monetary quantity.
819 The same values are recognized as for
820 .IR p_cs_precedes .
821 .TP
822 .I int_p_sep_by_space
823 followed by an integer that indicates the separation of
824 .IR int_curr_symbol ,
825 the sign string,
826 and the value for a nonnegative internationally formatted monetary quantity.
827 The same values are recognized as for
828 .IR p_sep_by_space .
829 .TP
830 .I int_n_sep_by_space
831 followed by an integer that indicates the separation of
832 .IR int_curr_symbol ,
833 the sign string,
834 and the value for a negative internationally formatted monetary quantity.
835 The same values are recognized as for
836 .IR p_sep_by_space .
837 .TP
838 .I int_p_sign_posn
839 followed by an integer that indicates where the
840 .I positive_sign
841 should be placed for a nonnegative
842 internationally formatted monetary quantity.
843 The same values are recognized as for
844 .IR p_sign_posn .
845 .TP
846 .I int_n_sign_posn
847 followed by an integer that indicates where the
848 .I negative_sign
849 should be placed for a negative
850 internationally formatted monetary quantity.
851 The same values are recognized as for
852 .IR p_sign_posn .
853 .P
854 The
855 .B LC_MONETARY
856 definition ends with the string
857 .IR "END LC_MONETARY" .
858 .SS LC_NAME
859 The definition starts with the string
860 .I LC_NAME
861 in the first column.
862 .P
863 Various keywords are allowed, but only
864 .I name_fmt
865 is mandatory.
866 Other keywords are needed only if there is common convention to
867 use the corresponding salutation in this locale.
868 The allowed keywords are as follows:
869 .TP
870 .I name_fmt
871 followed by a string containing field descriptors that define
872 the format used for names in the locale.
873 The following field descriptors are recognized:
874 .RS
875 .TP 4
876 %f
877 Family name(s).
878 .TP
879 %F
880 Family names in uppercase.
881 .TP
882 %g
883 First given name.
884 .TP
885 %G
886 First given initial.
887 .TP
888 %l
889 First given name with Latin letters.
890 .TP
891 %o
892 Other shorter name.
893 .TP
894 %m
895 Additional given name(s).
896 .TP
897 %M
898 Initials for additional given name(s).
899 .TP
900 %p
901 Profession.
902 .TP
903 %s
904 Salutation, such as "Doctor".
905 .TP
906 %S
907 Abbreviated salutation, such as "Mr." or "Dr.".
908 .TP
909 %d
910 Salutation, using the FDCC-sets conventions.
911 .\" 1 for the name_gen
912 .\" In glibc 2.19, %d1 is used in only:
913 .\" /home/mtk/ARCHIVE/GLIBC/glibc-2.19/localedata/locales/bem_ZM
914 .\" /home/mtk/ARCHIVE/GLIBC/glibc-2.19/localedata/locales/zh_HK
915 .\" In glibc 2.19, %d[2-5] appear to be not used at all
916 .\" 2 for name_mr
917 .\" 3 for name_mrs
918 .\" 4 for name_miss
919 .\" 5 for name_ms
920 .TP
921 %t
922 If the preceding field descriptor resulted in an empty string,
923 then the empty string, otherwise a space character.
924 .RE
925 .TP
926 .I name_gen
927 followed by the general salutation for any gender.
928 .TP
929 .I name_mr
930 followed by the salutation for men.
931 .TP
932 .I name_mrs
933 followed by the salutation for married women.
934 .TP
935 .I name_miss
936 followed by the salutation for unmarried women.
937 .TP
938 .I name_ms
939 followed by the salutation valid for all women.
940 .P
941 The
942 .B LC_NAME
943 definition ends with the string
944 .IR "END LC_NAME" .
945 .SS LC_NUMERIC
946 The definition starts with the string
947 .I LC_NUMERIC
948 in the first column.
949 .P
950 The following keywords are allowed:
951 .TP
952 .I decimal_point
953 followed by the single-character string that will be used as the
954 decimal delimiter when formatting numeric quantities.
955 .TP
956 .I thousands_sep
957 followed by the single-character string that will be used as a group
958 separator when formatting numeric quantities.
959 .TP
960 .I grouping
961 followed by a sequence of integers separated by semicolons
962 that describe the formatting of numeric quantities.
963 .IP
964 Each integer specifies the number of digits in a group.
965 The first integer defines the size of the group immediately
966 to the left of the decimal delimiter.
967 Subsequent integers define succeeding groups to the
968 left of the previous group.
969 If the last integer is not \-1, then the size of the previous group
970 (if any) is repeatedly used for the remainder of the digits.
971 If the last integer is \-1, then no further grouping is performed.
972 .P
973 The
974 .B LC_NUMERIC
975 definition ends with the string
976 .IR "END LC_NUMERIC" .
977 .SS LC_PAPER
978 The definition starts with the string
979 .I LC_PAPER
980 in the first column.
981 .P
982 The following keywords are allowed:
983 .TP
984 .I height
985 followed by the height, in millimeters, of the standard paper format.
986 .TP
987 .I width
988 followed by the width, in millimeters, of the standard paper format.
989 .P
990 The
991 .B LC_PAPER
992 definition ends with the string
993 .IR "END LC_PAPER" .
994 .SS LC_TELEPHONE
995 The definition starts with the string
996 .I LC_TELEPHONE
997 in the first column.
998 .P
999 The following keywords are allowed:
1000 .TP
1001 .I tel_int_fmt
1002 followed by a string that contains field descriptors that identify
1003 the format used to dial international numbers.
1004 The following field descriptors are recognized:
1005 .RS
1006 .TP 4
1007 %a
1008 Area code without nationwide prefix (the prefix is often "00").
1009 .TP
1010 %A
1011 Area code including nationwide prefix.
1012 .TP
1013 %l
1014 Local number (within area code).
1015 .TP
1016 %e
1017 Extension (to local number).
1018 .TP
1019 %c
1020 Country code.
1021 .TP
1022 %C
1023 Alternate carrier service code used for dialing abroad.
1024 .TP
1025 %t
1026 If the preceding field descriptor resulted in an empty string,
1027 then the empty string, otherwise a space character.
1028 .RE
1029 .TP
1030 .I tel_dom_fmt
1031 followed by a string that contains field descriptors that identify
1032 the format used to dial domestic numbers.
1033 The recognized field descriptors are the same as for
1034 .IR tel_int_fmt .
1035 .TP
1036 .I int_select
1037 followed by the prefix used to call international phone numbers.
1038 .TP
1039 .I int_prefix
1040 followed by the prefix used from other countries to dial this country.
1041 .P
1042 The
1043 .B LC_TELEPHONE
1044 definition ends with the string
1045 .IR "END LC_TELEPHONE" .
1046 .SS LC_TIME
1047 The definition starts with the string
1048 .I LC_TIME
1049 in the first column.
1050 .P
1051 The following keywords are allowed:
1052 .TP
1053 .I abday
1054 followed by a list of abbreviated names of the days of the week.
1055 The list starts with the first day of the week
1056 as specified by
1057 .I week
1058 (Sunday by default).
1059 See NOTES.
1060 .TP
1061 .I day
1062 followed by a list of names of the days of the week.
1063 The list starts with the first day of the week
1064 as specified by
1065 .I week
1066 (Sunday by default).
1067 See NOTES.
1068 .TP
1069 .I abmon
1070 followed by a list of abbreviated month names.
1071 .TP
1072 .I mon
1073 followed by a list of month names.
1074 .TP
1075 .I d_t_fmt
1076 followed by the appropriate date and time format
1077 (for syntax, see
1078 .BR strftime (3)).
1079 .TP
1080 .I d_fmt
1081 followed by the appropriate date format
1082 (for syntax, see
1083 .BR strftime (3)).
1084 .TP
1085 .I t_fmt
1086 followed by the appropriate time format
1087 (for syntax, see
1088 .BR strftime (3)).
1089 .TP
1090 .I am_pm
1091 followed by the appropriate representation of the
1092 .B am
1093 and
1094 .B pm
1095 strings.
1096 This should be left empty for locales not using AM/PM convention.
1097 .TP
1098 .I t_fmt_ampm
1099 followed by the appropriate time format
1100 (for syntax, see
1101 .BR strftime (3))
1102 when using 12h clock format.
1103 This should be left empty for locales not using AM/PM convention.
1104 .TP
1105 .I era
1106 followed by semicolon-separated strings that define how years are
1107 counted and displayed for each era in the locale.
1108 Each string has the following format:
1109 .RS
1110 .P
1111 .IR direction ":" offset ":" start_date ":" end_date ":" era_name ":" era_format
1112 .P
1113 The fields are to be defined as follows:
1114 .TP 4
1115 .I direction
1116 Either
1117 .B +
1118 or
1119 .BR \- .
1120 .B +
1121 means the years closer to
1122 .I start_date
1123 have lower numbers than years closer to
1124 .IR end_date .
1125 .B \-
1126 means the opposite.
1127 .TP
1128 .I offset
1129 The number of the year closest to
1130 .I start_date
1131 in the era, corresponding to the
1132 .I %Ey
1133 descriptor (see
1134 .BR strptime (3)).
1135 .TP
1136 .I start_date
1137 The start of the era in the form of
1138 .IR yyyy/mm/dd .
1139 Years prior AD 1 are represented as negative numbers.
1140 .TP
1141 .I end_date
1142 The end of the era in the form of
1143 .IR yyyy/mm/dd ,
1144 or one of the two special values of
1145 .B \-*
1146 or
1147 .BR +* .
1148 .B \-*
1149 means the ending date is the beginning of time.
1150 .B +*
1151 means the ending date is the end of time.
1152 .TP
1153 .I era_name
1154 The name of the era corresponding to the
1155 .I %EC
1156 descriptor (see
1157 .BR strptime (3)).
1158 .TP
1159 .I era_format
1160 The format of the year in the era corresponding to the
1161 .I %EY
1162 descriptor (see
1163 .BR strptime (3)).
1164 .RE
1165 .TP
1166 .I era_d_fmt
1167 followed by the format of the date in alternative era notation,
1168 corresponding to the
1169 .I %Ex
1170 descriptor (see
1171 .BR strptime (3)).
1172 .TP
1173 .I era_t_fmt
1174 followed by the format of the time in alternative era notation,
1175 corresponding to the
1176 .I %EX
1177 descriptor (see
1178 .BR strptime (3)).
1179 .TP
1180 .I era_d_t_fmt
1181 followed by the format of the date and time in alternative era notation,
1182 corresponding to the
1183 .I %Ec
1184 descriptor (see
1185 .BR strptime (3)).
1186 .TP
1187 .I alt_digits
1188 followed by the alternative digits used for date and time in the locale.
1189 .TP
1190 .I week
1191 followed by a list of three values separated by semicolons:
1192 The number of days in a week (by default 7),
1193 a date of beginning of the week (by default corresponds to Sunday),
1194 and the minimal length of the first week in year (by default 4).
1195 Regarding the start of the week,
1196 .B 19971130
1197 shall be used for Sunday and
1198 .B 19971201
1199 shall be used for Monday.
1200 See NOTES.
1201 .TP
1202 .IR first_weekday " (since glibc 2.2)"
1203 followed by the number of the day from the
1204 .I day
1205 list to be shown as the first day of the week in calendar applications.
1206 The default value of
1207 .B 1
1208 corresponds to either Sunday or Monday depending
1209 on the value of the second
1210 .I week
1211 list item.
1212 See NOTES.
1213 .TP
1214 .IR first_workday " (since glibc 2.2)"
1215 followed by the number of the first working day from the
1216 .I day
1217 list.
1218 The default value is
1219 .BR 2 .
1220 See NOTES.
1221 .TP
1222 .I cal_direction
1223 followed by a number value that indicates the direction for the
1224 display of calendar dates, as follows:
1225 .RS
1226 .TP 4
1227 .B 1
1228 Left-right from top.
1229 .TP
1230 .B 2
1231 Top-down from left.
1232 .TP
1233 .B 3
1234 Right-left from top.
1235 .RE
1236 .TP
1237 .I date_fmt
1238 followed by the appropriate date representation for
1239 .BR date (1)
1240 (for syntax, see
1241 .BR strftime (3)).
1242 .P
1243 The
1244 .B LC_TIME
1245 definition ends with the string
1246 .IR "END LC_TIME" .
1247 .SH FILES
1248 .TP
1249 .I /usr/lib/locale/locale\-archive
1250 Usual default locale archive location.
1251 .TP
1252 .I /usr/share/i18n/locales
1253 Usual default path for locale definition files.
1254 .SH STANDARDS
1255 POSIX.2.
1256 .SH NOTES
1257 The collective GNU C library community wisdom regarding
1258 .IR abday ,
1259 .IR day ,
1260 .IR week ,
1261 .IR first_weekday ,
1262 and
1263 .I first_workday
1264 states at
1265 https://sourceware.org/glibc/wiki/Locales
1266 the following:
1267 .IP \[bu] 3
1268 The value of the second
1269 .I week
1270 list item specifies the base of the
1271 .I abday
1272 and
1273 .I day
1274 lists.
1275 .IP \[bu]
1276 .I first_weekday
1277 specifies the offset of the first day-of-week in the
1278 .I abday
1279 and
1280 .I day
1281 lists.
1282 .IP \[bu]
1283 For compatibility reasons, all glibc locales should set the value of the
1284 second
1285 .I week
1286 list item to
1287 .B 19971130
1288 (Sunday) and base the
1289 .I abday
1290 and
1291 .I day
1292 lists appropriately, and set
1293 .I first_weekday
1294 and
1295 .I first_workday
1296 to
1297 .B 1
1298 or
1299 .BR 2 ,
1300 depending on whether the week and work week actually starts on Sunday or
1301 Monday for the locale.
1302 .\" .SH AUTHOR
1303 .\" Jochen Hein ([email protected])
1304 .SH SEE ALSO
1305 .BR iconv (1),
1306 .BR locale (1),
1307 .BR localedef (1),
1308 .BR localeconv (3),
1309 .BR newlocale (3),
1310 .BR setlocale (3),
1311 .BR strftime (3),
1312 .BR strptime (3),
1313 .BR uselocale (3),
1314 .BR charmap (5),
1315 .BR charsets (7),
1316 .BR locale (7),
1317 .BR unicode (7),
1318 .BR utf\-8 (7)