2 ! *****************************************************************
4 ! * Copyright (c) Digital Equipment Corporation, 1991, 1995 *
6 ! * All Rights Reserved. Unpublished rights reserved under *
7 ! * the copyright laws of the United States. *
9 ! * The software contained on this media is proprietary to *
10 ! * and embodies the confidential technology of Digital *
11 ! * Equipment Corporation. Possession, use, duplication or *
12 ! * dissemination of the software and media is authorized only *
13 ! * pursuant to a valid written license from Digital Equipment *
17 ! * THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS *
18 ! * OR IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE *
19 ! * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A *
20 ! * PARTICULAR PURPOSE. *
23 ! * RESTRICTED RIGHTS LEGEND Use, duplication, or disclosure *
24 ! * by the U.S. Government is subject to restrictions as set *
25 ! * forth in Subparagraph (c)(1)(ii) of DFARS 252.227-7013, *
26 ! * or in FAR 52.227-19, as applicable. *
28 ! *****************************************************************
33 ! @(#)$XConsortium: OSF1.lcx /main/4 1996/10/28 13:57:14 drk $
35 !!!!!!!!!!!!!! OSF1 Locale-Related Translations !!!!!!!!!!!!!!
37 ! Default location: /usr/dt/config/svc/OSF1.lcx
39 ! Define the OSF1-specific set of locale-related translations.
41 ! This file contains the set of all locale-related translations
42 ! that can occur during _DtLcxXlateOpToStd() and _DtLcxStdToOp()
43 ! calls on OSF1 platforms. Note that platform-specific tables may
44 ! include more than one translation to and from CDE standard
45 ! strings if they can be distinguished by version, operation, or
48 ! It is important that additional CDE standard strings only
49 ! be created by the CDE owner of the _DtLcx translation service
50 ! and NOT be created by an individual vendor or user. This be because
51 ! the purpose of adopting a set of CDE standard strings is to
52 ! support interoperability across platforms. If individual vendors
53 ! add their own "standard" strings and these strings are not
54 ! known on other platforms, then the goal of interoperability
57 ! If you feel that a new CDE standard string is needed,
58 ! contact your CDE representative/vendor with a specific
59 ! proposal and justification and have them forward it to
60 ! the owner of the CDE _DtLcx service.
62 ! Note that it is allowed for vendors and users to add new
63 ! operations for which translations are specified and which
64 ! utilize the standard strings. If the operations are of
65 ! general utility, please bring them to the attention of
66 ! your CDE representative/vendor for forwarding to the
69 ! This table is used by the _DtLcx translation service
71 ! Revision: $XConsortium: OSF1.lcx /main/4 1996/10/28 13:57:14 drk $
73 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
75 !!!!!!!!!!!!!!!! translation specification syntax !!!!!!!!!!!!!!!!!!!
76 ! Introductory fields:
77 ! ====================
78 ! The _DtLcx translation specifications have a fixed number of
79 ! introductory fields followed by a several standard value
80 ! fields and the operation-specific value.
81 ! The introductory fields are:
82 ! <platform>.<version range>.<operation(s)>.<kind>
84 ! Platform generally is the same string as uname(1) -s.
85 ! Version range utilizes normalized version numbers that
86 ! are acquired using the 'version' translations.
87 ! Operations are one or more comma-separated strings that
88 ! uniquely identify the operation associated with the
89 ! operation-specific value. This string is specified
90 ! as part of the request for a translation.
92 ! Kinds of translations allow the mechanism to support several modes
93 ! of operation, each useful for different purposes. When
94 ! reading or writing a specification, pay particular attention
95 ! to the kind of specification, as this guides the usage of it.
97 ! Specification kinds:
98 ! .=. means a valid bi-directional translation requiring the op-value
99 ! in the translation specification to exactly match the op-value of
100 ! the call to _DtLcxXlateOpToStd(), e.g. foo matches only foo
101 ! .~. means a valid bi-directional translation requiring the op-value
102 ! in the translation specification to match the beginning of the
103 ! op-value of the call to _DtLcxXlateOpToStd(), e.g. foo matches
104 ! foo@bar. This is often useful, e.g. for operation-specific
105 ! locale strings that may also contain modifier suffixes.
106 ! .>. means only from standard to op-specific (generally a
107 ! compatibility translation, meaning on op-specific value
108 ! that will work for the standard, although that is not
109 ! the straight mapping)
110 ! .<. means only from op-specific to standard (generally a
111 ! regex in the op-value which is used to map a class of
112 ! op values to a standard value)
113 ! .0. means that translation is not supported and if a translation
114 ! request matches the specification, the request will fail.
118 ! _DtLcx defines the order of the standard values in the
119 ! translations it utilizes. All translation specifications
120 ! must adhere to this order.
121 ! <std lang_terr>.<std codeset>.<std modifier>
122 ! In CDE 1.0, no modifiers are standard and that
123 ! portion of the table is unspecified. This means
124 ! that no CDE standard modifiers are available across
125 ! platforms. Operations that use only the <std codeset>
126 ! should specify the wildcard character ("?") for the
127 ! <std lang_terr> value.
129 ! Operation-specific value:
130 ! =========================
131 ! The operation-specific value is a string that is used
132 ! according to the kind of translation. The syntax is
134 ! or : "<op-string>", if it contains white space
136 ! Filling in the table of translations:
137 ! =====================================
138 ! The person preparing the translation table should know
139 ! the minimum version of the target platform that is
140 ! be supported. For example, assume that we must
141 ! complete the table for all versions 9.00 and higher.
143 ! The objective is then to provide two sets of translations:
144 ! a full set of translations from CDE standard locales to
145 ! valid platform locales, and a full set of translations
146 ! from valid platform locales to some or all CDE standard
149 ! Translations from CDE standard locales to valid platform
150 ! locales must use the .~. .=. or .>. mappings. When there
151 ! is a 1:1 mapping between a CDE locale and a platform locale,
152 ! use the .~. or .=. mapping. See the comment below to
153 ! decide which to use. When there is no 1:1 mapping between
154 ! CDE locale and platform locale, use the .>. mapping. This
155 ! provides a valid translation from the CDE locale to the
156 ! best-suitable platform locale, but never translates from
157 ! that platform locale to the CDE locale.
159 ! Translations from every platform locale to the appropriate
160 ! CDE locale must use the .~. .=. or .<. mappings.
161 ! When there is a 1:1 mapping between a platform locale and
162 ! a CDE standard locale, use the .~. or .=. mapping. See the
163 ! comment below to decide which to use. If there is a 1:1
164 ! mapping, but the platform locale pattern uses a regular
165 ! expression, or if more than one platform locale can
166 ! be translated to one CDE standard locale, the .<. mapping must
169 ! If no appropriate CDE standard locale can be found, you have
170 ! identified the need for a new CDE standard locale. Refer to
171 ! the instructions at the head of this file for how to go about
172 ! registering a new CDE standard locale. You should not create
173 ! a new "standard" locale (the left hand side of the translation
174 ! specification) without registering it with CDE, because this
175 ! will hinder the free exchange of information across locales
178 ! The .=. and .~. mappings are similar. The difference is
179 ! that the .=. mapping requires an exact string match between
180 ! the platform locale and the string provided to the
181 ! translation routine. Generally speaking, this mapping
182 ! is risky unless exact matchings can be guaranteed in
183 ! all DtLcx clients for the particular operation in question.
184 ! The .~. mapping is to be preferred, but the .=. translation
185 ! is useful in limited situations, where similar strings may
188 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
190 ! define this resource to dump debug/test info
193 !!!!!!!!!!!!!!!! OSF1 Version Identificaton !!!!!!!!!!!!!!!!!
194 ! These translations are used by the _DtXlateGetXlateEnv()
195 ! call to determine the version number to use.
197 ! To understand the translation, realize that the
198 ! operation-specific regexp(5) pattern on the right
199 ! hand side is matched against the strings returned
200 ! by uname(2). The best match determines the "normalized"
201 ! version number of the platform, which should range from
202 ! 001 and up. By convention, major release numbers
203 ! map to centuries and minor release numbers to within
206 ! To determine the string that the regular expression on the
207 ! right hand side is matching against, use uname(1) and run
208 ! 'uname -r' and 'uname -v' and note the strings. During execution,
209 ! the strings returned by this command are retrieved and
210 ! concatenated "rv"--in that order, no extra spaces.
211 ! This is the string that the pattern must match.
213 ! Sometimes this string may not be intuitive. For example,
214 ! note that AIX 3.2 returns 2 for 'uname -r' and 3 for 'uname -v'.
215 ! So the pattern string must be 23, not 32. Do not go by
216 ! the order of 'uname -rv' or 'uname -vr', as that is not used.
218 ! Define string for OSF/1 Platinum
219 OSF1.?.version.<.400: "[A-Z]4\\..*"
220 ! Define string for OSF/1 Gold minor
221 OSF1.?.version.<.320: "[A-Z]3\\.2.*" !! any OSF/1 GM version
222 ! Define string for OSF/1 Gold
223 OSF1.?.version.<.300: "[A-Z]3\\..*"
225 !!!!!!!!!!!!!!!! OSF1-specific setlocale translations !!!!!!!!!!!!!!!!!!!
226 ! These translations are for the string returned by the
227 ! getlocale() or setlocale(LC_xxx,NULL) operations, but not
228 ! setlocale(LC_ALL,NULL) operation.
230 ! It provides translations from OSF1 operation-specific
231 ! to CDE standard strings and back again.
233 ! Some language,territory combinations have the following comments:
234 ! (1) These ISO territory names may be subject to change
235 ! However, their CDE names will continue to be supported
236 ! (2) No ISO "territory" name exists for the Arabic-speaking regions of the
237 ! world as a whole. Vendors have sometimes supplied their own.
238 ! Those names, when conformant to the ISO model, will be adopted for CDE.
240 !Platform Operation Lang_Terr Op-Value Language,Territory Who has
241 !--- --------- ----- -------- ------------------ -------
242 ! Version Kind Codeset
246 ! setlocales Compliance
247 OSF1.400+.setlocale.~.C.ISO-8859-1: C ! setlocales compliance ,IBM, HP, Sun , USL
248 OSF1.400+.setlocale.~.POSIX.ISO-8859-1: POSIX ! setlocales compliance ,IBM, HP, Sun , USL
250 ! W European/Americas, Latin 1 codeset
251 OSF1.400+.setlocale.~.da_DK.ISO-8859-1: da_DK.ISO8859-1 ! Danish, Denmark XoJIG,IBM, HP, , USL ("da")
252 OSF1.400+.setlocale.>.de_AT.ISO-8859-1: de_DE.ISO8859-1 ! German,Austria XoJIG, , , , USL
253 OSF1.400+.setlocale.~.de_CH.ISO-8859-1: de_CH.ISO8859-1 ! German,Switzerland XoJIG,IBM, , , USL
254 OSF1.400+.setlocale.~.de_DE.ISO-8859-1: de_DE.ISO8859-1 ! German, Germany XoJIG,IBM, HP, Sun ("de"), USL ("de")
255 OSF1.400+.setlocale.>.en_AU.ISO-8859-1: en_GB.ISO8859-1 ! English,Australia , , , , USL
256 OSF1.400+.setlocale.>.en_CA.ISO-8859-1: en_US.ISO8859-1 ! English,Canada XoJIG, , , , USL
257 OSF1.400+.setlocale.>.en_DK.ISO-8859-1: en_GB.ISO8859-1 ! English, Denmark XoJIG, , , , USL
258 OSF1.400+.setlocale.~.en_GB.ISO-8859-1: en_GB.ISO8859-1 ! English, U.K. XoJIG,IBM, HP, , USL ("en")
259 OSF1.400+.setlocale.>.en_JP.ISO-8859-1: en_US.ISO8859-1 ! English, Japan XoJIG,IBM, , ,
260 OSF1.400+.setlocale.>.en_IE.ISO-8859-1: en_GB.ISO8859-1 ! English, Ireland XoJIG, , , , USL
261 OSF1.400+.setlocale.>.en_MY.ISO-8859-1: en_US.ISO8859-1 ! English,Malaysia , , , , USL
262 OSF1.400+.setlocale.>.en_NZ.ISO-8859-1: en_GB.ISO8859-1 ! English,New Zealand , , , , USL
263 OSF1.400+.setlocale.>.en_KR.ISO-8859-1: en_US.ISO8859-1 ! English,Korea , , , , USL
264 OSF1.400+.setlocale.>.en_TW.ISO-8859-1: en_US.ISO8859-1 ! English,Taiwan , , , , USL
265 OSF1.400+.setlocale.~.en_US.ISO-8859-1: en_US.ISO8859-1 ! English, USA XoJIG,IBM, HP, Sun , USL
266 OSF1.400+.setlocale.>.es_AR.ISO-8859-1: es_ES.ISO8859-1 ! Spanish, Argentina , , , Sun , USL
267 OSF1.400+.setlocale.>.es_BO.ISO-8859-1: es_ES.ISO8859-1 ! Spanish, Bolivia , , , Sun
268 OSF1.400+.setlocale.>.es_CL.ISO-8859-1: es_ES.ISO8859-1 ! Spanish, Chile , , , Sun , USL
269 OSF1.400+.setlocale.>.es_CO.ISO-8859-1: es_ES.ISO8859-1 ! Spanish, Columbia , , , Sun
270 OSF1.400+.setlocale.>.es_CR.ISO-8859-1: es_ES.ISO8859-1 ! Spanish, Costa Rica , , , Sun
271 OSF1.400+.setlocale.>.es_EC.ISO-8859-1: es_ES.ISO8859-1 ! Spanish, Ecuador , , , Sun
272 OSF1.400+.setlocale.~.es_ES.ISO-8859-1: es_ES.ISO8859-1 ! Spanish, Spain XoJIG,IBM, HP, Sun , USL
273 OSF1.400+.setlocale.~.ca_ES.ISO-8859-1: ca_ES.ISO8859-1 ! Catalan, Spain XoJIG,IBM, HP, Sun , USL, DEC
274 OSF1.400+.setlocale.>.es_GT.ISO-8859-1: es_ES.ISO8859-1 ! Spanish, Guatemala , , , Sun
275 OSF1.400+.setlocale.>.es_MX.ISO-8859-1: es_ES.ISO8859-1 ! Spanish, Mexico , , , Sun , USL
276 OSF1.400+.setlocale.>.es_PE.ISO-8859-1: es_ES.ISO8859-1 ! Spanish, Peru , , , Sun
277 OSF1.400+.setlocale.>.es_UY.ISO-8859-1: es_ES.ISO8859-1 ! Spanish, Uruguay , , , Sun
278 OSF1.400+.setlocale.>.es_VE.ISO-8859-1: es_ES.ISO8859-1 ! Spanish, Venezuela , , , Sun , USL
279 ! OSF1.400+.setlocale.>.et_EE.ISO-8859-1: ! Estonian, Estonia XoJIG,
280 OSF1.400+.setlocale.~.fi_FI.ISO-8859-1: fi_FI.ISO8859-1 ! Finnish, Finland XoJIG,IBM, HP, , USL ("fi")
281 ! OSF1.400+.setlocale.>.fo_FO.ISO-8859-1: ! Faroese, Faeroe Island XoJIG,
282 OSF1.400+.setlocale.~.fr_BE.ISO-8859-1: fr_BE.ISO8859-1 ! French,Belgium XoJIG, , , , USL
283 OSF1.400+.setlocale.~.fr_CA.ISO-8859-1: fr_CA.ISO8859-1 ! French, Canada XoJIG,IBM, HP, , USL
284 OSF1.400+.setlocale.~.fr_CH.ISO-8859-1: fr_CH.ISO8859-1 ! French, Switzerland XoJIG,IBM, , , USL
285 OSF1.400+.setlocale.~.fr_FR.ISO-8859-1: fr_FR.ISO8859-1 ! French, France XoJIG,IBM, HP, Sun ("fr"), USL ("fr")
286 OSF1.400+.setlocale.~.is_IS.ISO-8859-1: is_IS.ISO8859-1 ! Icelandic, Iceland XoJIG,IBM, HP, , USL ("is")
287 OSF1.400+.setlocale.>.it_CH.ISO-8859-1: it_IT.ISO8859-1 ! Italian,Switzerland , , , , USL
288 OSF1.400+.setlocale.~.it_IT.ISO-8859-1: it_IT.ISO8859-1 ! Italian, Italy XoJIG,IBM, HP, Sun ("it"), USL ("it")
289 ! OSF1.400+.setlocale.>.kl_GL.ISO-8859-1: ! Greenlandic, Greenland XoJIG,
290 ! OSF1.400+.setlocale.>.lt_LT.ISO-8859-1: ! Lithuanian, Lithuania XoJIG,
291 ! OSF1.400+.setlocale.>.lv_LV.ISO-8859-1: ! Latvian, Latvia XoJIG,
292 OSF1.400+.setlocale.~.nl_BE.ISO-8859-1: nl_BE.ISO8859-1 ! Dutch, Belgium XoJIG,IBM, , , USL
293 OSF1.400+.setlocale.~.nl_NL.ISO-8859-1: nl_NL.ISO8859-1 ! Dutch, The Netherlands XoJIG,IBM, HP, , USL ("nl")
294 OSF1.400+.setlocale.~.no_NO.ISO-8859-1: no_NO.ISO8859-1 ! Norwegian, Norway XoJIG,IBM, HP, , USL ("no")
295 OSF1.400+.setlocale.>.pt_BR.ISO-8859-1: pt_PT.ISO8859-1 ! Portuguese,Brazil , , , , USL
296 OSF1.400+.setlocale.~.pt_PT.ISO-8859-1: pt_PT.ISO8859-1 ! Portuguese, Portugal XoJIG,IBM, HP, , USL
297 OSF1.400+.setlocale.>.sv_FI.ISO-8859-1: sv_SE.ISO8859-1 ! Swedish, Finland XoJIG,
298 OSF1.400+.setlocale.~.sv_SE.ISO-8859-1: sv_SE.ISO8859-1 ! Swedish, Sweden XoJIG,IBM, HP, Sun ("sv"), USL ("sv")
301 OSF1.400+.setlocale.~.cs_CS.ISO-8859-2: cs_CZ.ISO8859-2 ! Czech(1) ,IBM, HP
302 ! OSF1.400+.setlocale.>.hr_HR.ISO-8859-2: ! Croatian, Croatia ,IBM
303 OSF1.400+.setlocale.~.hu_HU.ISO-8859-2: hu_HU.ISO8859-2 ! Hungarian, Hungry XoJIG,IBM, HP
304 OSF1.400+.setlocale.~.pl_PL.ISO-8859-2: pl_PL.ISO8859-2 ! Polish, Poland XoJIG,IBM, HP
305 ! OSF1.400+.setlocale.>.ro_RO.ISO-8859-2: ! Rumanian, Romania XoJIG,IBM, HP
306 ! OSF1.400+.setlocale.>.sh_YU.ISO-8859-2: ! Serbocroatian, Yugoslavia(1) ,IBM, HP
307 OSF1.400+.setlocale.>.sl_CS.ISO-8859-2: sl_SI.ISO8859-2 ! Slovenian , , HP, , , DEC
308 OSF1.400+.setlocale.~.si_SI.ISO-8859-2: sl_SI.ISO8859-2 ! Slovenian ,IBM, , , , DEC
309 OSF1.400+.setlocale.~.sk_SK.ISO-8859-2: sk_SK.ISO8859-2 ! Slovak ,IBM
312 OSF1.400+.setlocale.~.lt_LT.ISO-8859-4: lt_LT.ISO8859-4 ! Lithuanian, Lithuania , , , , , DEC
315 ! OSF1.400+.setlocale.>.bg_BG.ISO-8859-5: ! Bulgarian, Bulgaria ,IBM, HP
316 ! OSF1.400+.setlocale.>.mk_MK.ISO-8859-5: ! Macedonian ,IBM
317 OSF1.400+.setlocale.~.ru_RU.ISO-8859-5: ru_RU.ISO8859-5 ! Russian(1) ,IBM,
318 OSF1.400+.setlocale.>.ru_SU.ISO-8859-5: ru_RU.ISO8859-5 ! Russian(1) , , HP
319 ! OSF1.400+.setlocale.>.sp_YU.ISO-8859-5: ! Serbian,Yugoslavia(1) ,IBM
322 ! OSF1.400+.setlocale.>.ar_DZ.ISO-8859-6: ! Arabic(2) , , HP
323 ! OSF1.400+.setlocale.>.ar_SA.ISO-8859-6: ! Arabic(2) ,IBM, HP
326 OSF1.400+.setlocale.~.iw_IL.ISO-8859-8: iw_IL.ISO8859-8 ! Hebrew, Israel ,IBM, HP
329 OSF1.400+.setlocale.~.el_GR.ISO-8859-7: el_GR.ISO8859-7 ! Greek, Greece ,IBM, HP
332 OSF1.400+.setlocale.~.tr_TR.ISO-8859-9: tr_TR.ISO8859-9 ! Turkish, Turkey ,IBM, HP
335 OSF1.400+.setlocale.~.ja_JP.EUC-JP: ja_JP ! Japanese, Japan ,IBM, HP, Sun ("ja"), USL
336 OSF1.400+.setlocale.~.ja_JP.IBM-932: ja_JP.SJIS ! Japanese, Japan ,IBM
337 OSF1.400+.setlocale.>.ja_JP.HP-SJIS: ja_JP.SJIS ! Japanese, Japan aka japanese 15 , , HP,
338 OSF1.400+.setlocale.~.ja_JP.DEC-KANJI: ja_JP.deckanji ! Japanese, Japan , , , , , DEC
339 OSF1.400+.setlocale.~.ja_JP.DEC-SKANJI: ja_JP.sdeckanji ! Japanese, Japan , , , , , DEC
340 OSF1.400+.setlocale.~.ko_KR.EUC-KR: ko_KR ! Korean, Korea , , , , , DEC
341 OSF1.400+.setlocale.~.zh_CN.EUC-CN: zh_CN ! Chinese, China ,IBM, , Sun ("zh"), USL
342 OSF1.400+.setlocale.>.zh_CN.HP-15CN: zh_CN ! Chinese, China , , HP
343 OSF1.400+.setlocale.~.zh_TW.DEC-HANYU: zh_TW ! Chinese, Taiwan , , , , , DEC
344 OSF1.400+.setlocale.~.zh_TW.DEC-BIG5: zh_TW.big5 ! Chinese, Taiwan , , , , , DEC
345 OSF1.400+.setlocale.~.zh_TW.EUC-TW: zh_TW.eucTW ! Chinese, Taiwan ,IBM, HP, Sun , USL
346 OSF1.400+.setlocale.~.zh_HK.EUC-CN: zh_HK.dechanzi ! Chinese, Hong Kong , , , , , DEC
347 OSF1.400+.setlocale.~.zh_HK.DEC-HANYU: zh_HK.dechanyu ! Chinese, Hong Kong , , , , , DEC
348 OSF1.400+.setlocale.~.zh_HK.DEC-BIG5: zh_HK.big5 ! Chinese, Hong Kong , , , , , DEC
349 OSF1.400+.setlocale.~.zh_HK.EUC-TW: zh_HK.eucTW ! Chinese, Hong Kong , , , , , DEC
350 ! OSF1.400+.setlocale.>.zh_TW.HP-BIG5: ! Chinese, Taiwan , , HP, ,
351 ! OSF1.400+.setlocale.>.zh_TW.HP-CCDC: ! Chinese, Taiwan , , HP, ,
352 ! OSF1.400+.setlocale.>.ja_JP.HP-KANA8: ! Japanese, Japan , , HP, ,
355 OSF1.400+.setlocale.~.th_TH.TIS-620: th_TH ! Thai, Thailand ,IBM, HP
357 ! codesets supported for iconv(1,3) & nl_langinfo and above
358 OSF1.400+.iconv1,iconv3,nl_langinfo(CODESET).=.?.ISO-8859-1: ISO8859-1
359 OSF1.400+.iconv1,iconv3,nl_langinfo(CODESET).=.?.ISO-8859-2: ISO8859-2
360 OSF1.400+.iconv1,iconv3,nl_langinfo(CODESET).=.?.ISO-8859-4: ISO8859-4
361 OSF1.400+.iconv1,iconv3,nl_langinfo(CODESET).=.?.ISO-8859-5: ISO8859-5
362 OSF1.400+.iconv1,iconv3,nl_langinfo(CODESET).=.?.ISO-8859-6: ISO8859-6
363 OSF1.400+.iconv1,iconv3,nl_langinfo(CODESET).=.?.ISO-8859-7: ISO8859-7
364 OSF1.400+.iconv1,iconv3,nl_langinfo(CODESET).=.?.ISO-8859-8: ISO8859-8
365 OSF1.400+.iconv1,iconv3,nl_langinfo(CODESET).=.?.ISO-8859-9: ISO8859-9
366 OSF1.400+.iconv1,iconv3.=.?.EUC-KR: eucKR
367 OSF1.400+.nl_langinfo(CODESET).=.?.EUC-KR: KSC5601
368 OSF1.400+.iconv1,iconv3,nl_langinfo(CODESET).=.?.EUC-JP: eucJP
369 OSF1.400+.iconv1,iconv3,nl_langinfo(CODESET).=.?.DEC-KANJI: deckanji
370 OSF1.400+.iconv1,iconv3,nl_langinfo(CODESET).=.?.DEC-SKANJI: sdeckanji
371 OSF1.400+.iconv1,iconv3,nl_langinfo(CODESET).=.?.EUC-TW: eucTW
372 OSF1.400+.iconv1,iconv3,nl_langinfo(CODESET).=.?.DEC-HANYU: dechanyu
373 OSF1.400+.iconv1,iconv3,nl_langinfo(CODESET).=.?.DEC-BIG5: big5
374 OSF1.400+.iconv1,iconv3,nl_langinfo(CODESET).=.?.EUC-CN: dechanzi
375 OSF1.400+.iconv1,iconv3,nl_langinfo(CODESET).>.?.HP-15CN: dechanzi
376 OSF1.400+.iconv1,iconv3,nl_langinfo(CODESET).=.?.IBM-932: SJIS
377 OSF1.400+.iconv1,iconv3,nl_langinfo(CODESET).>.?.HP-SJIS: SJIS
378 OSF1.400+.iconv1,iconv3,nl_langinfo(CODESET).=.?.TIS-620: TACTIS
380 ! codesets supported for iconv(1,3) only
381 OSF1.400+.iconv1,iconv3.=.?.ISO-2022-JP: ISO-2022-JP
382 OSF1.400+.iconv1,iconv3.=.?.ISO-2022-KR: ISO-2022-KR
384 ! codesets not supported for either iconv(1,3) or nl_langinfo
385 ! OSF1.?.iconv1,iconv3.~.?.UCS-2:
386 ! OSF1.?.iconv1,iconv3.~.?.UTF-8:
387 ! OSF1.?.iconv1,iconv3.~.?.HP-ARABIC8:
388 ! OSF1.?.iconv1,iconv3.~.?.HP-GREEK8:
389 ! OSF1.?.iconv1,iconv3.~.?.HP-HEBREW8
390 ! OSF1.?.iconv1,iconv3.~.?.HP-ROMAN8:
391 ! OSF1.?.iconv1,iconv3.~.?.HP-TURKISH8:
392 ! OSF1.?.iconv1,iconv3.~.?.HP-KANA8:
393 ! OSF1.?.iconv1,iconv3.~.?.ISO-2022-TW:
394 ! OSF1.?.iconv1,iconv3.~.?.HP-CCDC:
395 ! OSF1.?.iconv1,iconv3.~.?.HP-BIG5:
396 ! OSF1.?.iconv1,iconv3.~.?.ISO-2022-CN:
397 ! OSF1.?.iconv1,iconv3.~.?.IBM-437:
398 ! OSF1.?.iconv1,iconv3.~.?.IBM-850:
399 ! OSF1.?.iconv1,iconv3.~.?.IBM-856:
400 ! OSF1.?.iconv1,iconv3.~.?.IBM-1046:
403 ! This translation provides an alternative to a call to
404 ! using setlocale() and MB_CUR_MAX to determine this.
405 OSF1.?.multibyte.=.?.EUC-KR: 3
406 OSF1.?.multibyte.=.?.HP-SJIS: 2
407 OSF1.?.multibyte.=.?.IBM-932: 2
408 OSF1.?.multibyte.=.?.EUC-JP: 3
409 OSF1.?.multibyte.=.?.DEC-KANJI: 2
410 OSF1.?.multibyte.=.?.DEC-SKANJI: 3
411 ! OSF1.?.multibyte.~.?.HP-CCDC: 2
412 ! OSF1.?.multibyte.~.?.HP-BIG5: 2
413 OSF1.?.multibyte.=.?.EUC-TW: 4
414 OSF1.?.multibyte.=.?.DEC-HANYU: 4
415 OSF1.?.multibyte.=.?.DEC-BIG5: 2
416 OSF1.?.multibyte.=.?.EUC-CN: 2
417 OSF1.?.multibyte.=.?.HP-15CN: 2
419 ! Translations from predefined CCDF-locales to CDE Standard Locales
420 OSF1.?.ccdf.=.?.HP-ROMAN8: hp-roman8
421 OSF1.?.ccdf.=.?.ISO-8859-1: ISO8859-1
422 OSF1.?.ccdf.=.ko_KR.EUC-KR: hp-korean15
423 OSF1.?.ccdf.=.ko_KR.EUC-KR: eucKR
424 OSF1.?.ccdf.=.ja_JP.HP-SJIS: hp-japanese15
425 OSF1.?.ccdf.=.ja_JP.EUC-JP: eucJP
426 OSF1.?.ccdf.=.?.DT-SYMBOL-1: symbol !!! standard Dt symbol font
428 ! These CDE standard locales may have CCDF-locales, but they are defined by localizers
429 ! OSF1.?.ccdf.=.ar_SA.HP-ARABIC8: arabic8
430 ! OSF1.?.ccdf.=.el_GR.HP-GREEK8: greek8
431 ! OSF1.?.ccdf.=.iw_IL.HP-HEBREW8: hebrew8
432 ! OSF1.?.ccdf.=.tr_TR.HP-TURKISH8: turkish8
433 ! OSF1.?.ccdf.<.ja_JP.HP-SJIS: sjis
434 ! OSF1.?.ccdf.=.ja_JP.HP-KANA8: kana8
435 ! OSF1.?.ccdf.<.ja_JP.EUC-JP: ujis
436 ! OSF1.?.ccdf.=.zh_CN.HP-CCDC: roc15
438 ! Codesets that require multibyte parsing to avoid confusion with shell special chars
439 OSF1.?.dtkshSpecialParse.=.ja_JP.HP-JIS: True
440 OSF1.?.dtkshSpecialParse.=.ja_JP.HP-SJIS: True
441 OSF1.?.dtkshSpecialParse.=.ja_JP.IBM-932: True
442 OSF1.?.dtkshSpecialParse.=.zh_TW.HP-BIG5: True
443 OSF1.?.dtkshSpecialParse.=.zh_TW.HP-CCDC: True
444 OSF1.?.dtkshSpecialParse.=.zh_TW.EUC-TW: True
445 OSF1.?.dtkshSpecialParse.=.?.DEC-KANJI: True
446 OSF1.?.dtkshSpecialParse.=.?.DEC-SKANJI: True
447 OSF1.?.dtkshSpecialParse.=.?.DEC-HANYU: True
448 OSF1.?.dtkshSpecialParse.=.?.DEC-BIG5: True
450 !! When content is exchanged with other platforms, the interchange codeset
451 !! may be different that the codeset used locally. In CDE1, these translations
452 !! are used by dtmail, but other clients may use the same translations
453 !! in the future. For example, to improve interoperability of 8-bit mail,
454 !! the mail messages of users working in codesets such as HP-ROMAN8 or IBM-850
455 !! are translated to the interchangeCodeset (in this case, ISO-8859-1) before
456 !! they are sent. Similarly, the mail of Japanese users is translated to JIS
457 !! before it is sent.
458 OSF1.?.interchangeCodeset.~.?.ISO-8859-1: ISO-8859-1 ! ISO Latin 1
459 ! OSF1.?.interchangeCodeset.>.?.HP-ROMAN8: ISO-8859-1 ! HP Roman8
460 ! OSF1.?.interchangeCodeset.>.?.IBM-437: ISO-8859-1 ! PC (US)
461 ! OSF1.?.interchangeCodeset.>.?.IBM-850: ISO-8859-1 ! PC (Multi-lingual)
462 OSF1.?.interchangeCodeset.~.?.ISO-8859-2: ISO-8859-2 ! ISO Latin 2
463 OSF1.?.interchangeCodeset.~.?.ISO-8859-4: ISO-8859-4 ! ISO Latin 4
464 OSF1.?.interchangeCodeset.~.?.ISO-8859-5: ISO-8859-5 ! ISO Latin/Cyrillic
465 OSF1.?.interchangeCodeset.~.?.ISO-8859-6: ISO-8859-6 ! ISO Latin/Arabic
466 ! OSF1.?.interchangeCodeset.>.?.HP-ARABIC8: ISO-8859-6 ! HP Arabic8
467 ! OSF1.?.interchangeCodeset.>.?.IBM-1046: ISO-8859-6 ! PC Arabic Code Set
468 OSF1.?.interchangeCodeset.~.?.ISO-8859-8: ISO-8859-8 ! ISO Latin/Hebrew
469 ! OSF1.?.interchangeCodeset.>.?.HP-HEBREW8: ISO-8859-8 ! HP Hebrew8
470 ! OSF1.?.interchangeCodeset.>.?.IBM-856: ISO-8859-8 ! PC Hebrew
471 OSF1.?.interchangeCodeset.~.?.ISO-8859-7: ISO-8859-7 ! ISO Latin/Greek
472 ! OSF1.?.interchangeCodeset.>.?.HP-GREEK8: ISO-8859-7 ! HP Greek8
473 OSF1.?.interchangeCodeset.~.?.ISO-8859-9: ISO-8859-9 ! ISO Latin 5
474 ! OSF1.?.interchangeCodeset.>.?.HP-TURKISH8: ISO-8859-9 ! HP Turkish8
475 OSF1.?.interchangeCodeset.~.?.EUC-JP: ISO-2022-JP ! Japanese EUC
476 ! OSF1.?.interchangeCodeset.>.?.HP-SJIS: ISO-2022-JP ! HP Japanese Shift JIS
477 OSF1.?.interchangeCodeset.>.?.IBM-932: ISO-2022-JP ! PC Japanese Shift JIS
478 ! OSF1.?.interchangeCodeset.>.?.HP-KANA8: ISO-2022-JP ! HP Japanese Katakana8
479 OSF1.?.interchangeCodeset.~.?.DEC-KANJI: ISO-2022-JP ! Japanese DEC Kanji
480 OSF1.?.interchangeCodeset.~.?.DEC-SKANJI: ISO-2022-JP ! Japanese Super DEC Kanji
481 OSF1.?.interchangeCodeset.~.?.EUC-KR: ISO-2022-KR ! Korean EUC
482 ! comment when ISO-2022-CN is supported by iconv
483 OSF1.?.interchangeCodeset.~.?.EUC-CN: EUC-CN ! China Chinese EUC
484 ! OSF1.?.interchangeCodeset.>.?.HP-15CN: EUC-CN ! HP Chinese EUC
485 ! uncomment when ISO-2022-CN is supported by iconv
486 ! OSF1.?.interchangeCodeset.~.?.EUC-CN: ISO-2022-CN ! China Chinese EUC
487 ! ! OSF1.?.interchangeCodeset.>.?.HP-15CN: ISO-2022-CN ! HP Chinese EUC
488 ! comment when ISO-2022-TW is supported by iconv
489 OSF1.?.interchangeCodeset.~.?.EUC-TW: EUC-TW ! Taiwan Chinese EUC
490 OSF1.?.interchangeCodeset.~.?.DEC-HANYU: DEC-HANYU ! Taiwan Chinese DEC Hanyu
491 OSF1.?.interchangeCodeset.~.?.DEC-BIG5: DEC-BIG5 ! Taiwan Chinese DEC Big5
492 ! OSF1.?.interchangeCodeset.>.?.HP-BIG5: EUC-TW ! HP Big5 Chinese
493 ! OSF1.?.interchangeCodeset.>.?.HP-CCDC: EUC-TW ! HP CCDC Chinese
494 ! uncomment when ISO-2022-TW is supported by iconv
495 ! OSF1.?.interchangeCodeset.~.?.EUC-TW: ISO-2022-TW ! Taiwan Chinese EUC
496 ! ! OSF1.?.interchangeCodeset.>.?.HP-BIG5: ISO-2022-TW ! HP Big5 Chinese
497 ! ! OSF1.?.interchangeCodeset.>.?.HP-CCDC: ISO-2022-TW ! HP CCDC Chinese
498 OSF1.?.interchangeCodeset.~.?.TIS-620: TIS-620 ! Thai
499 OSF1.?.interchangeCodeset.>.?.UCS-2: UTF-8 ! Unicode
500 OSF1.?.interchangeCodeset.~.?.UTF-8: UTF-8 ! multibyte Unicode
502 !! Codeset identifiers for use with MIME messages. The .~. translations
503 !! are used by dtmail and adhere to the MIME standard, RFC 1521.
504 !! Note that the MIME standard states that codeset identifiers are
505 !! case-insensitive. The operation-specific values on the right-hand-side
506 !! of the translations below, however, ARE case sensitive. Before
507 !! doing a OpToStd translation, first convert the MIME codeset identifier
508 !! to uppercase. Alternatively, one could provide lower-case versions
509 !! of the translations (right-hand-side only should be in lower-case).
510 OSF1.?.mime.~.?.ISO-8859-1: ISO-8859-1 ! ISO Latin 1
511 OSF1.?.mime.~.?.HP-ROMAN8: X-HP-ROMAN8 ! HP Roman8
512 OSF1.?.mime.~.?.IBM-437: X-IBM-437 ! PC (US)
513 OSF1.?.mime.~.?.IBM-850: X-IBM-850 ! PC (Multi-lingual)
514 OSF1.?.mime.~.?.ISO-8859-2: ISO-8859-2 ! ISO Latin 2
515 OSF1.?.mime.~.?.ISO-8859-4: ISO-8859-4 ! ISO Latin 4
516 OSF1.?.mime.~.?.ISO-8859-5: ISO-8859-5 ! ISO Latin/Cyrillic
517 OSF1.?.mime.~.?.ISO-8859-6: ISO-8859-6 ! ISO Latin/Arabic
518 OSF1.?.mime.~.?.HP-ARABIC8: X-HP-ARABIC8 ! HP Arabic8
519 OSF1.?.mime.~.?.IBM-1046: X-IBM-1046 ! PC Arabic Code Set
520 OSF1.?.mime.~.?.ISO-8859-8: ISO-8859-8 ! ISO Latin/Hebrew
521 OSF1.?.mime.~.?.HP-HEBREW8: X-HP-HEBREW8 ! HP Hebrew8
522 OSF1.?.mime.~.?.IBM-856: X-IBM-856 ! PC Hebrew
523 OSF1.?.mime.~.?.ISO-8859-7: ISO-8859-7 ! ISO Latin/Greek
524 OSF1.?.mime.~.?.HP-GREEK8: X-HP-GREEK8 ! HP Greek8
525 OSF1.?.mime.~.?.ISO-8859-9: ISO-8859-9 ! ISO Latin 5
526 OSF1.?.mime.~.?.HP-TURKISH8: X-HP-TURKISH8 ! HP Turkish8
527 OSF1.?.mime.~.?.EUC-JP: X-EUC-JP ! Japanese EUC
528 OSF1.?.mime.~.?.ISO-2022-JP: ISO-2022-JP ! Japanese JIS with 7-bit encoding per ISO-2022-JP
529 OSF1.?.mime.~.?.HP-SJIS: X-HP-SJIS ! HP Japanese Shift JIS
530 OSF1.?.mime.~.?.IBM-932: X-IBM-932 ! PC Japanese Shift JIS
531 OSF1.?.mime.~.?.HP-KANA8: X-HP-KANA8 ! HP Japanese Katakana8
532 OSF1.?.mime.~.?.EUC-KR: X-EUC-KR ! Korean EUC
533 OSF1.?.mime.~.?.ISO-2022-KR: ISO-2022-KR ! Korean with 7-bit encoding per ISO-2022-KR
534 OSF1.?.mime.~.?.EUC-CN: X-EUC-CN ! China Chinese EUC
535 OSF1.?.mime.~.?.ISO-2022-CN: ISO-2022-CN ! China Chinese with 7-bit encoding per ISO-2022-CN
536 OSF1.?.mime.~.?.HP-15CN: X-HP-15CN ! HP China Chinese EUC
537 OSF1.?.mime.~.?.EUC-TW: X-EUC-TW ! Taiwan Chinese EUC
538 OSF1.?.mime.~.?.ISO-2022-TW: ISO-2022-TW ! Taiwan Chinese with 7-bit encoding per ISO-2022-TW
539 OSF1.?.mime.~.?.DEC-HANYU: X-DEC-HANYU ! Taiwan Chinese DEC Hanyu
540 OSF1.?.mime.~.?.DEC-BIG5: X-DEC-BIG5 ! Taiwan Chinese DEC Big5
541 OSF1.?.mime.~.?.HP-BIG5: X-HP-BIG5 ! HP Big5 Taiwan Chinese
542 OSF1.?.mime.~.?.HP-CCDC: X-HP-CCDC ! HP CCDC Taiwan Chinese
543 OSF1.?.mime.~.?.TIS-620: X-TIS-620 ! Thai
544 OSF1.?.mime.~.?.UCS-2: X-UCS-2 ! Unicode; group 0, plane 0 of ISO-10646
545 OSF1.?.mime.~.?.UCS-4: X-UCS-4 ! ISO-10646
546 OSF1.?.mime.~.?.UTF-7: X-UTF-7 ! multibyte encoding of Unicode
547 OSF1.?.mime.~.?.UTF-8: X-UTF-8 ! multibyte encoding of Unicode
548 OSF1.?.mime.~.?.UTF-16: X-UTF-16 ! multibyte encoding of Unicode
550 !! If other mailers are using other codeset identifiers in their MIME
551 !! messages, dtmail will not be able to process them correctly.
552 !! To correct this, additional .<. translations for these identifiers
553 !! can be added to a <platform>.lcx file in the /etc/dt/config/svc
554 !! or $HOME/.dt/config/svc directories. Such translations should read:
555 !! <platform>.?.mime.<.?.<CDE std codeset>: <mailer identifier for the codeset>
557 !! ***NEVER*** use a .~. translation, such as we use above, as this could
558 !! cause dtmail to send unexpected identifier strings by overriding the
559 !! above definition. Further, never use .=. or .>. translations.
561 !! These two identifiers are in common usage, as they derive from RFC1521.
562 OSF1.?.mime.<.?.ISO-8859-1: us-ascii ! ISO Latin 1
563 OSF1.?.mime.<.?.ISO-8859-1: US-ASCII ! ISO Latin 1
projects / oweals / cde.git / blob