1 # $NetBSD: UCS%JISX0212.src,v 1.2 2003/07/12 16:11:11 tshiozak Exp $
5 SRC_ZONE 0x0000 - 0x9FFF
12 # This mapping data is made from the mapping data provided by Unicode, Inc.
15 # Name: JIS X 0212 (1990) to Unicode
16 # Unicode version: 1.1
18 # Table format: Format A
21 # Copyright (c) 1991-1994 Unicode, Inc. All Rights reserved.
23 # This file is provided as-is by Unicode, Inc. (The Unicode Consortium).
24 # No claims are made as to fitness for any particular purpose. No
25 # warranties of any kind are expressed or implied. The recipient
26 # agrees to determine applicability of information provided. If this
27 # file has been provided on magnetic media by Unicode, Inc., the sole
28 # remedy for any claim will be exchange of defective media within 90
31 # Recipient is granted the right to make copies in any form for
32 # internal distribution and to freely use the information supplied
33 # in the creation of products supporting Unicode. Unicode, Inc.
34 # specifically excludes the right to re-distribute this file directly
35 # to third parties or other organizations whether for profit or not.
40 # This table contains one set of mappings from JIS X 0212 into Unicode.
41 # Note that these data are *possible* mappings only and may not be the
42 # same as those used by actual products, nor may they be the best suited
43 # for all uses. For more information on the mappings between various code
44 # pages incorporating the repertoire of JIS X 0212 and Unicode, consult the
45 # VENDORS mapping data. Normative information on the mapping between
46 # JIS X 0212 and Unicode may be found in the Unihan.txt file in the
47 # latest Unicode Character Database.
49 # If you have carefully considered the fact that the mappings in
50 # this table are only one possible set of mappings between JIS X 0212 and
51 # Unicode and have no normative status, but still feel that you
52 # have located an error in the table that requires fixing, you may
53 # report any such error to errata@unicode.org.
56 # Format: Three tab-separated columns
57 # Column #1 is the JIS X 0212 code (in hex as 0xXXXX)
58 # Column #2 is the Unicode (in hex as 0xXXXX)
59 # Column #3 the Unicode name (follows a comment sign, '#')
60 # The official names for Unicode characters U+4E00
61 # to U+9FA5, inclusive, is "CJK UNIFIED IDEOGRAPH-XXXX",
62 # where XXXX is the code point. Including all these
63 # names in this file increases its size substantially
64 # and needlessly. The token "<CJK>" is used for the
65 # name of these characters. If necessary, it can be
66 # expanded algorithmically by a parser or editor.
68 # The entries are in JIS X 0212 order
70 # The following algorithms can be used to change the hex form
71 # of JIS 0212 to other standard forms:
73 # To change hex to EUC form, add 0x8080
74 # To change hex to kuten form, first subtract 0x2020. Then
75 # the high and low bytes correspond to the ku and ten of
76 # the kuten form. For example, 0x2121 -> 0x0101 -> 0101;
77 # 0x6D63 -> 0x4D43 -> 7767
79 # The kanji mappings are a normative part of ISO/IEC 10646. The
80 # non-kanji mappings are provisional, pending definition of
81 # official mappings by Japanese standards bodies
83 # Any comments or problems, contact <John_Jenkins@taligent.com>
87 # 1. JIS X 0212 apparently unified the following two symbols
88 # into a single character at 0x2922:
90 # LATIN CAPITAL LETTER D WITH STROKE
91 # LATIN CAPITAL LETTER ETH
93 # However, JIS X 0212 maintains the distinction between
94 # the lowercase forms of these two elements at 0x2942 and 0x2943.
95 # Given the structre of these JIS encodings, it is clear that
96 # 0x2922 and 0x2942 are intended to be a capital/small pair.
97 # Consequently, in the Unicode mapping, 0x2922 is treated as
98 # LATIN CAPITAL LETTER D WITH STROKE.