1# $FreeBSD$
2
3TYPE		ROWCOL
4NAME		GURMUKHI/UCS
5SRC_ZONE	0x00-0xFA
6OOB_MODE	ILSEQ
7DST_ILSEQ	0xFFFE
8DST_UNIT_BITS	16
9#=======================================================================
10#   File name:  GURMUKHI.TXT
11#
12#   Contents:   Map (external version) from Mac OS Gurmukhi
13#               encoding to Unicode 2.1 and later.
14#
15#   Copyright:  (c) 1997-2002, 2005 by Apple Computer, Inc., all rights
16#               reserved.
17#
18#   Contact:    charsets@apple.com
19#
20#   Changes:
21#
22#       c02  2005-Apr-05    Update header comments. Matches internal xml
23#                           <c1.1> and Text Encoding Converter 2.0.
24#      b3,c1 2002-Dec-19    Change mappings for 0x91, 0xD5 based on
25#							new decomposition rules. Update URLs,
26#                           notes. Matches internal utom<b2>.
27#       b02  1999-Sep-22    Update contact e-mail address. Matches
28#                           internal utom<b1>, ufrm<b1>, and Text
29#                           Encoding Converter version 1.5.
30#       n02  1998-Feb-05    First version; matches internal utom<n5>,
31#                           ufrm<n6>.
32#
33# Standard header:
34# ----------------
35#
36#   Apple, the Apple logo, and Macintosh are trademarks of Apple
37#   Computer, Inc., registered in the United States and other countries.
38#   Unicode is a trademark of Unicode Inc. For the sake of brevity,
39#   throughout this document, "Macintosh" can be used to refer to
40#   Macintosh computers and "Unicode" can be used to refer to the
41#   Unicode standard.
42#
43#   Apple Computer, Inc. ("Apple") makes no warranty or representation,
44#   either express or implied, with respect to this document and the
45#   included data, its quality, accuracy, or fitness for a particular
46#   purpose. In no event will Apple be liable for direct, indirect,
47#   special, incidental, or consequential damages resulting from any
48#   defect or inaccuracy in this document or the included data.
49#
50#   These mapping tables and character lists are subject to change.
51#   The latest tables should be available from the following:
52#
53#   <http://www.unicode.org/Public/MAPPINGS/VENDORS/APPLE/>
54#
55#   For general information about Mac OS encodings and these mapping
56#   tables, see the file "README.TXT".
57#
58# Format:
59# -------
60#
61#   Three tab-separated columns;
62#   '#' begins a comment which continues to the end of the line.
63#     Column #1 is the Mac OS Gurmukhi code or code sequence
64#       (in hex as 0xNN or 0xNN+0xNN)
65#     Column #2 is the corresponding Unicode or Unicode sequence
66#       (in hex as 0xNNNN or 0xNNNN+0xNNNN).
67#     Column #3 is a comment containing the Unicode name or sequence
68#       of names. In some cases an additional comment follows the
69#       Unicode name(s).
70#
71#   The entries are in two sections. The first section is for pairs of
72#   Mac OS Gurmukhi code points that must be mapped in a special way.
73#   The second section maps individual code points.
74#
75#   Within each section, the entries are in Mac OS Gurmukhi code order.
76#
77#   Control character mappings are not shown in this table, following
78#   the conventions of the standard UTC mapping tables. However, the
79#   Mac OS Gurmukhi character set uses the standard control characters
80#   at 0x00-0x1F and 0x7F.
81#
82# Notes on Mac OS Gurmukhi:
83# -------------------------
84#
85#   This is a legacy Mac OS encoding; in the Mac OS X Carbon and Cocoa
86#   environments, it is only supported via transcoding to and from
87#   Unicode.
88#
89#   Mac OS Gurmukhi is based on IS 13194:1991 (ISCII-91), with the
90#   addition of several punctuation and symbol characters. However,
91#   Mac OS Gurmukhi does not support the ATR (attribute) mechanism of
92#   ISCII-91.
93#
94# 1. ISCII-91 features in Mac OS Gurmukhi include:
95#
96#  a) Explicit halant and soft halant
97#
98#     A double halant (0xE8 + 0xE8) constitutes an "explicit halant",
99#     which will always appear as a halant instead of causing formation
100#     of a ligature or half-form consonant.
101#
102#     Halant followed by nukta (0xE8 + 0xE9) constitutes a "soft
103#     halant", which prevents formation of a ligature and instead
104#     retains the half-form of the first consonant.
105#
106#  b) Invisible consonant
107#
108#     The byte 0xD9 (called INV in ISCII-91) is an invisible consonant:
109#     It behaves like a consonant but has no visible appearance. It is
110#     intended to be used (often in combination with halant) to display
111#     dependent forms in isolation, such as the RA forms or consonant
112#     half-forms.
113#
114#  c) Extensions for Vedic, etc.
115#
116#     The byte 0xF0 (called EXT in ISCII-91) followed by any byte in
117#     the range 0xA1-0xEE constitutes a two-byte code point which can
118#     be used to represent additional characters for Vedic (or other
119#     extensions); 0xF0 followed by any other byte value constitutes
120#     malformed text. Mac OS Gurmukhi supports this mechanism, but
121#     does not currently map any of these two-byte code points to
122#     anything.
123#
124# 2. Mac OS Gurmukhi additions
125#
126#   Mac OS Gurmukhi adds characters using the code points
127#   0x80-0x8A and 0x90-0x94 (the latter are some Gurmukhi additions).
128#
129# 3. Unused code points
130#
131#   The following code points are currently unused, and are not shown
132#   here: 0x8B-0x8F, 0x95-0xA1, 0xA3, 0xAA-0xAB, 0xAE-0xAF, 0xB2,
133#   0xC7, 0xCE, 0xD0, 0xD2-0xD3, 0xD6, 0xDF-0xE0, 0xE3-0xE4, 0xE7,
134#   0xEB-0xEF, 0xFB-0xFF. In addition, 0xF0 is not shown here, but it
135#   has a special function as described above.
136#
137# Unicode mapping issues and notes:
138# ---------------------------------
139#
140# 1. Mapping the byte pairs
141#
142#   If the byte value 0xE8 is encountered when mapping Mac OS
143#   Gurmukhi text, then the next byte (if there is one) should be
144#   examined. If the next byte is 0xE8 or 0xE9, then the byte pair
145#   should be mapped using the first section of the mapping table
146#   below. Otherwise, each byte should be mapped using the second
147#   section of the mapping table below.
148#
149#   - The Unicode Standard, Version 2.0, specifies how explicit
150#     halant and soft halant should be represented in Unicode;
151#     these mappings are used below.
152#
153#   If the byte value 0xF0 is encountered when mapping Mac OS
154#   Gurmukhi text, then the next byte should be examined. If there
155#   is no next byte (e.g. 0xF0 at end of buffer), the mapping
156#   process should indicate incomplete character. If there is a next
157#   byte but it is not in the range 0xA1-0xEE, the mapping process
158#   should indicate malformed text. Otherwise, the mapping process
159#   should treat the byte pair as a valid two-byte code point with no
160#   mapping (e.g. map it to QUESTION MARK, REPLACEMENT CHARACTER,
161#   etc.).
162#
163# 2. Mapping the invisible consonant
164#
165#   It has been suggested that INV in ISCII-91 should map to ZERO
166#   WIDTH NON-JOINER in Unicode. However, this causes problems with
167#   roundtrip fidelity: The ISCII-91 sequences 0xE8+0xE8 and 0xE8+0xD9
168#   would map to the same sequence of Unicode characters. We have
169#   instead mapped INV to LEFT-TO-RIGHT MARK, which avoids these
170#   problems.
171#
172# 3. Mappings using corporate characters
173#
174#   Mapping the GURMUKHI LETTER SHA 0xD5 presents an interesting
175#   problem. At first glance, we could map it to the single Unicode
176#   character 0x0A36.
177#
178#   However, our goal is that the mappings provided here should also
179#   be able to generate the mappings to maximally decomposed Unicode
180#   by simple recursive substitution of the canonical decompositions
181#   in the Unicode database. We want mapping tables derived this way
182#   to retain full roundtrip fidelity.
183#
184#   Since the canonical decomposition of 0x0A36 is 0x0A38+0x0A3C,
185#   the decomposition mapping for 0xD5 would be identical with the
186#   decomposition mapping for 0xD7+0xE9, and roundtrip fidelity would
187#   be lost.
188#
189#   We solve this problem by using a grouping hint (one of the set of
190#   transcoding hints defined by Apple).
191#
192#   Apple has defined a block of 32 corporate characters as "transcoding
193#   hints." These are used in combination with standard Unicode characters
194#   to force them to be treated in a special way for mapping to other
195#   encodings; they have no other effect. Sixteen of these transcoding
196#   hints are "grouping hints" - they indicate that the next 2-4 Unicode
197#   characters should be treated as a single entity for transcoding. The
198#   other sixteen transcoding hints are "variant tags" - they are like
199#   combining characters, and can follow a standard Unicode (or a sequence
200#   consisting of a base character and other combining characters) to
201#   cause it to be treated in a special way for transcoding. These always
202#   terminate a combining-character sequence.
203#
204#   The transcoding coding hint used in this mapping table is:
205#     0xF860 group next 2 characters
206#
207#   Then we can map 0x91 as follows:
208#     0xD5 -> 0xF860+0x0A38+0x0A3C
209#
210#   We could also have used a variant tag such as 0xF87F and mapped it
211#   this way:
212#     0xD5 -> 0x0A36+0xF87F
213#
214# 4. Additional loose mappings from Unicode
215#
216#   These are not preserved in roundtrip mappings.
217#
218#   0A59 -> 0xB4+0xE9   # GURMUKHI LETTER KHHA
219#   0A5A -> 0xB5+0xE9   # GURMUKHI LETTER GHHA
220#   0A5B -> 0xBA+0xE9   # GURMUKHI LETTER ZA
221#   0A5E -> 0xC9+0xE9   # GURMUKHI LETTER FA
222#
223#   0A70 -> 0xA2    # GURMUKHI TIPPI
224#
225#   Loose mappings from Unicode should also map U+0A71 (GURMUKHI ADDAK)
226#   followed by any Gurmukhi consonant to the equivalent ISCII-91
227#   consonant plus halant plus the consonant again. For example:
228#
229#   0A71+0A15 -> 0xB3+0xE8+0xB3
230#   0A71+0A16 -> 0xB4+0xE8+0xB4
231#   ...
232#
233# Details of mapping changes in each version:
234# -------------------------------------------
235#
236#   Changes from version b02 to version b03/c01:
237#
238#   - Change mapping of 0x91 from 0xF860+0x0A21+0x0A3C to 0x0A5C GURMUKHI
239#     LETTER RRA, now that the canonical decomposition of 0x0A5C to
240#     0x0A21+0x0A3C has been deleted
241#
242#   - Change mapping of 0xD5 from 0x0A36 GURMUKHI LETTER SHA to
243#     0xF860+0x0A38+0x0A3C, now that a canonical decomposition of 0x0A36
244#     to 0x0A38+0x0A3C has been added.
245#
246##################
247BEGIN_MAP
2480x00 - 0x7F = 0x0000 -
2490x80 = 0x00D7
2500x81 = 0x2212
2510x82 = 0x2013
2520x83 = 0x2014
2530x84 = 0x2018
2540x85 = 0x2019
2550x86 = 0x2026
2560x87 = 0x2022
2570x88 = 0x00A9
2580x89 = 0x00AE
2590x8A = 0x2122
2600x90 = 0x0A71
2610x91 = 0x0A5C
2620x92 = 0x0A73
2630x93 = 0x0A72
2640x94 = 0x0A74
2650xA2 = 0x0A02
2660xA4 = 0x0A05
2670xA5 = 0x0A06
2680xA6 = 0x0A07
2690xA7 = 0x0A08
2700xA8 = 0x0A09
2710xA9 = 0x0A0A
2720xAC = 0x0A0F
2730xAD = 0x0A10
2740xB0 = 0x0A13
2750xB1 = 0x0A14
2760xB3 = 0x0A15
2770xB4 = 0x0A16
2780xB5 = 0x0A17
2790xB6 = 0x0A18
2800xB7 = 0x0A19
2810xB8 = 0x0A1A
2820xB9 = 0x0A1B
2830xBA = 0x0A1C
2840xBB = 0x0A1D
2850xBC = 0x0A1E
2860xBD = 0x0A1F
2870xBE = 0x0A20
2880xBF = 0x0A21
2890xC0 = 0x0A22
2900xC1 = 0x0A23
2910xC2 = 0x0A24
2920xC3 = 0x0A25
2930xC4 = 0x0A26
2940xC5 = 0x0A27
2950xC6 = 0x0A28
2960xC8 = 0x0A2A
2970xC9 = 0x0A2B
2980xCA = 0x0A2C
2990xCB = 0x0A2D
3000xCC = 0x0A2E
3010xCD = 0x0A2F
3020xCF = 0x0A30
3030xD1 = 0x0A32
3040xD4 = 0x0A35
305#0xD5 = 0xF860+0x0A38+0x0A3C
3060xD7 = 0x0A38
3070xD8 = 0x0A39
3080xD9 = 0x200E
3090xDA = 0x0A3E
3100xDB = 0x0A3F
3110xDC = 0x0A40
3120xDD = 0x0A41
3130xDE = 0x0A42
3140xE1 = 0x0A47
3150xE2 = 0x0A48
3160xE5 = 0x0A4B
3170xE6 = 0x0A4C
3180xE8 = 0x0A4D
319#0xE8+0xE8 = 0x0A4D+0x200C
320#0xE8+0xE9 = 0x0A4D+0x200D
3210xE9 = 0x0A3C
3220xEA = 0x0964
3230xF1 = 0x0A66
3240xF2 = 0x0A67
3250xF3 = 0x0A68
3260xF4 = 0x0A69
3270xF5 = 0x0A6A
3280xF6 = 0x0A6B
3290xF7 = 0x0A6C
3300xF8 = 0x0A6D
3310xF9 = 0x0A6E
3320xFA = 0x0A6F
333END_MAP
334