1 .\" Copyright (c) 1993, 1994
2 .\" The Regents of the University of California. All rights reserved.
4 .\" This code is derived from software contributed to Berkeley by
5 .\" Paul Borman at Krystal Technologies.
7 .\" Redistribution and use in source and binary forms, with or without
8 .\" modification, are permitted provided that the following conditions
10 .\" 1. Redistributions of source code must retain the above copyright
11 .\" notice, this list of conditions and the following disclaimer.
12 .\" 2. Redistributions in binary form must reproduce the above copyright
13 .\" notice, this list of conditions and the following disclaimer in the
14 .\" documentation and/or other materials provided with the distribution.
15 .\" 3. All advertising materials mentioning features or use of this software
16 .\" must display the following acknowledgement:
17 .\" This product includes software developed by the University of
18 .\" California, Berkeley and its contributors.
19 .\" 4. Neither the name of the University nor the names of its contributors
20 .\" may be used to endorse or promote products derived from this software
21 .\" without specific prior written permission.
23 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
24 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
25 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
26 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
27 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
28 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
29 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
30 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
31 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
32 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
35 .\" @(#)mklocale.1 8.2 (Berkeley) 4/18/94
43 .Nd make LC_CTYPE locale files
48 .Ar "> language/LC_CTYPE"
59 source file from standard input and produces a
61 binary file on standard output suitable for placement in
62 .Pa /usr/share/locale/ Ns Ar language Ns Pa /LC_CTYPE .
67 It consists of a series of lines which start with a keyword and have
68 associated data following.
69 C style comments are used
70 to place comments in the file.
72 Following options are available:
73 .Bl -tag -width indent
75 Turns on debugging messages.
80 Besides the keywords which will be listed below,
81 the following are valid tokens in
83 .Bl -tag -width ".Ar literal"
87 may be any of the following:
88 .Bl -tag -width ".Ar 0x[0-9a-z]*"
107 A hexadecimal number representing a rune code.
109 An octal number representing a rune code.
111 A decimal number representing a rune code.
114 A string enclosed in double quotes (").
120 Used to indicate ranges.
122 The follow characters are taken literally:
123 .Bl -tag -width ".Dv <\|\|(\|\|["
125 Used to start a mapping.
128 Used to end a mapping.
131 Used as a delimiter in mappings.
135 Key words which should only appear once are:
136 .Bl -tag -width ".Dv PHONOGRAM"
140 which indicates the encoding mechanism to be used for this locale.
141 The current encodings are:
142 .Bl -tag -width ".Dv MSKanji"
149 encoding as used by several
154 PRC national standard for encoding of Chinese text.
156 Older PRC national standard for encoding Chinese text.
158 A widely used encoding method for Chinese text,
159 backwards compatible with GB\ 2312-1980.
161 The method of encoding Japanese used by Microsoft,
162 loosely based on JIS.
168 No translation and the default.
172 transformation format of
175 as defined by RFC 2279.
178 This keyword must be followed by a single tab or space character,
179 after which encoding specific data is placed.
182 encoding requires variable data.
190 follows and is used as the invalid rune for this locale.
193 The following keywords may appear multiple times and have the following
195 .Bl -tag -width ".Dv <RUNE1 THRU RUNEn : RUNE2>" -offset indent
200 .It Dv <RUNE1 THRU RUNEn : RUNE2>
211 .Bl -tag -width ".Dv PHONOGRAM"
213 Defines the tolower mappings.
215 is the lower case representation of
218 Defines the toupper mappings.
220 is the upper case representation of
223 Defines a map from runes to their digit value.
225 is the integer value represented by
227 For example, the ASCII character
229 would map to the decimal value 0.
230 Only values up to 255
234 The following keywords may appear multiple times and have the following
236 .Bl -tag -width ".Dv RUNE1 THRU RUNEn" -offset indent
238 This rune has the property defined by the keyword.
239 .It Dv "RUNE1 THRU RUNEn"
240 All the runes between and including
244 have the property defined by the keyword.
246 .Bl -tag -width ".Dv PHONOGRAM"
248 Defines runes which are alphabetic, printable and graphic.
250 Defines runes which are control characters.
252 Defines runes which are decimal digits, printable and graphic.
254 Defines runes which are graphic and printable.
256 Defines runes which are lower case, printable and graphic.
258 Defines runes which are punctuation, printable and graphic.
260 Defines runes which are spaces.
262 Defines runes which are upper case, printable and graphic.
264 Defines runes which are hexadecimal digits, printable and graphic.
266 Defines runes which are blank.
268 Defines runes which are printable.
270 Defines runes which are ideograms, printable and graphic.
272 Defines runes which are special characters, printable and graphic.
274 Defines runes which are phonograms, printable and graphic.
276 Defines runes with display width 0.
278 Defines runes with display width 1.
280 Defines runes with display width 2.
282 Defines runes with display width 3.
285 If no display width explicitly defined, width 1 assumed
286 for printable runes by default.
301 utility first appeared in
306 utility is overly simplistic.