1# $FreeBSD$ 2 3TYPE ROWCOL 4NAME UCS/DEVANAGA 5SRC_ZONE 0x0000-0x2212 6OOB_MODE INVALID 7DST_INVALID 0x100 8DST_UNIT_BITS 16 9#======================================================================= 10# File name: DEVANAGA.TXT 11# 12# Contents: Map (external version) from Mac OS Devanagari 13# encoding to Unicode 2.1 and later. 14# 15# Copyright: (c) 1995-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; add section on 23# roundtrip considerations. Matches internal 24# xml <c1.1> and Text Encoding Converter 2.0. 25# b3,c1 2002-Dec-19 Update URLs. Matches internal utom<b1>. 26# b02 1999-Sep-22 Update contact e-mail address. Matches 27# internal utom<b1>, ufrm<b1>, and Text 28# Encoding Converter version 1.5. 29# n04 1998-Feb-05 First version; matches internal utom<n9>, 30# ufrm<n15>. 31# 32# Standard header: 33# ---------------- 34# 35# Apple, the Apple logo, and Macintosh are trademarks of Apple 36# Computer, Inc., registered in the United States and other countries. 37# Unicode is a trademark of Unicode Inc. For the sake of brevity, 38# throughout this document, "Macintosh" can be used to refer to 39# Macintosh computers and "Unicode" can be used to refer to the 40# Unicode standard. 41# 42# Apple Computer, Inc. ("Apple") makes no warranty or representation, 43# either express or implied, with respect to this document and the 44# included data, its quality, accuracy, or fitness for a particular 45# purpose. In no event will Apple be liable for direct, indirect, 46# special, incidental, or consequential damages resulting from any 47# defect or inaccuracy in this document or the included data. 48# 49# These mapping tables and character lists are subject to change. 50# The latest tables should be available from the following: 51# 52# <http://www.unicode.org/Public/MAPPINGS/VENDORS/APPLE/> 53# 54# For general information about Mac OS encodings and these mapping 55# tables, see the file "README.TXT". 56# 57# Format: 58# ------- 59# 60# Three tab-separated columns; 61# '#' begins a comment which continues to the end of the line. 62# Column #1 is the Mac OS Devanagari code or code sequence 63# (in hex as 0xNN or 0xNN+0xNN) 64# Column #2 is the corresponding Unicode or Unicode sequence 65# (in hex as 0xNNNN or 0xNNNN+0xNNNN). 66# Column #3 is a comment containing the Unicode name or sequence 67# of names. In some cases an additional comment follows the 68# Unicode name(s). 69# 70# The entries are in two sections. The first section is for pairs of 71# Mac OS Devanagari code points that must be mapped in a special way. 72# The second section maps individual code points. 73# 74# Within each section, the entries are in Mac OS Devanagari code order. 75# 76# Control character mappings are not shown in this table, following 77# the conventions of the standard UTC mapping tables. However, the 78# Mac OS Devanagari character set uses the standard control characters 79# at 0x00-0x1F and 0x7F. 80# 81# Notes on Mac OS Devanagari: 82# --------------------------- 83# 84# This is a legacy Mac OS encoding; in the Mac OS X Carbon and Cocoa 85# environments, it is only supported via transcoding to and from 86# Unicode. 87# 88# Mac OS Devanagari is based on IS 13194:1991 (ISCII-91), with the 89# addition of several punctuation and symbol characters. However, 90# Mac OS Devanagari does not support the ATR (attribute) mechanism of 91# ISCII-91. 92# 93# 1. ISCII-91 features in Mac OS Devanagari include: 94# 95# a) Overloading of nukta 96# 97# In addition to using the nukta (0xE9) like a combining dot below, 98# nukta is overloaded to function as a general character modifier. 99# In this role, certain code points followed by 0xE9 are treated as 100# a two-byte code point representing a character which may be 101# rather different than the characters represented by either of 102# the code points alone. For example, the character DEVANAGARI OM 103# (U+0950) is represented in ISCII-91 as candrabindu + nukta. 104# 105# b) Explicit halant and soft halant 106# 107# A double halant (0xE8 + 0xE8) constitutes an "explicit halant", 108# which will always appear as a halant instead of causing formation 109# of a ligature or half-form consonant. 110# 111# Halant followed by nukta (0xE8 + 0xE9) constitutes a "soft 112# halant", which prevents formation of a ligature and instead 113# retains the half-form of the first consonant. 114# 115# c) Invisible consonant 116# 117# The byte 0xD9 (called INV in ISCII-91) is an invisible consonant: 118# It behaves like a consonant but has no visible appearance. It is 119# intended to be used (often in combination with halant) to display 120# dependent forms in isolation, such as the RA forms or consonant 121# half-forms. 122# 123# d) Extensions for Vedic, etc. 124# 125# The byte 0xF0 (called EXT in ISCII-91) followed by any byte in 126# the range 0xA1-0xEE constitutes a two-byte code point which can 127# be used to represent additional characters for Vedic (or other 128# extensions); 0xF0 followed by any other byte value constitutes 129# malformed text. Mac OS Devanagari supports this mechanism, but 130# does not currently map any of these two-byte code points to 131# anything. 132# 133# 2. Mac OS Devanagari additions 134# 135# Mac OS Devanagari adds characters using the code points 136# 0x80-0x8A and 0x90-0x91 (the latter are some Devanagari additions 137# from Unicode). 138# 139# 3. Unused code points 140# 141# The following code points are currently unused, and are not shown 142# here: 0x8B-0x8F, 0x92-0xA0, 0xEB-0xEF, 0xFB-0xFF. In addition, 143# 0xF0 is not shown here, but it has a special function as described 144# above. 145# 146# Unicode mapping issues and notes: 147# --------------------------------- 148# 149# 1. Mapping the byte pairs 150# 151# If one of the following byte values is encountered when mapping 152# Mac OS Devanagari text - 0xA1, 0xA6, 0xA7, 0xAA, 0xDB, 0xDC, 0xDF, 153# 0xE8, or 0xEA - then the next byte (if there is one) should be 154# examined. If the next byte is 0xE9 - or also 0xE8, if the first 155# byte was 0xE8 - then the byte pair should be mapped using the 156# first section of the mapping table below. Otherwise, each byte 157# should be mapped using the second section of the mapping table 158# below. 159# 160# - The Unicode Standard, Version 2.0, specifies how explicit 161# halant and soft halant should be represented in Unicode; 162# these mappings are used below. 163# 164# If the byte value 0xF0 is encountered when mapping Mac OS 165# Devanagari text, then the next byte should be examined. If there 166# is no next byte (e.g. 0xF0 at end of buffer), the mapping 167# process should indicate incomplete character. If there is a next 168# byte but it is not in the range 0xA1-0xEE, the mapping process 169# should indicate malformed text. Otherwise, the mapping process 170# should treat the byte pair as a valid two-byte code point with no 171# mapping (e.g. map it to QUESTION MARK, REPLACEMENT CHARACTER, 172# etc.). 173# 174# 2. Mapping the invisible consonant 175# 176# It has been suggested that INV in ISCII-91 should map to ZERO 177# WIDTH NON-JOINER in Unicode. However, this causes problems with 178# roundtrip fidelity: The ISCII-91 sequences 0xE8+0xE8 and 0xE8+0xD9 179# would map to the same sequence of Unicode characters. We have 180# instead mapped INV to LEFT-TO-RIGHT MARK, which avoids these 181# problems. 182# 183# 3. Additional loose mappings from Unicode 184# 185# These are not preserved in roundtrip mappings. 186# 187# U+0958 0xB3+0xE9 # DEVANAGARI LETTER QA 188# U+0959 0xB4+0xE9 # DEVANAGARI LETTER KHHA 189# U+095A 0xB5+0xE9 # DEVANAGARI LETTER GHHA 190# U+095B 0xBA+0xE9 # DEVANAGARI LETTER ZA 191# U+095C 0xBF+0xE9 # DEVANAGARI LETTER DDDHA 192# U+095D 0xC0+0xE9 # DEVANAGARI LETTER RHA 193# U+095E 0xC9+0xE9 # DEVANAGARI LETTER FA 194# 195# 4. Roundtrip considerations when mapping to decomposed Unicode 196# 197# Both ISCII-91 (hence Mac OS Devanagari) and Unicode provide multiple 198# ways of representing certain Devanagari consonants. For example, 199# DEVANAGARI LETTER NNNA can be represented in Unicode as the single 200# character 0x0929 or as the sequence 0x0928 0x093C; similarly, this 201# consonant can be represented in Mac OS Devanagari as 0xC7 or as the 202# sequence 0xC6 0xE9. This leads to some roundtrip problems. First 203# note that we have the following mappings without such problems: 204# 205# ISCII/ standard decomposition of reverse mapping 206# Mac OS Unicode mapping standard mapping of decomposition 207# ------ ----------------------- ---------------- ---------------- 208# 0xC6 0x0928 ... LETTER NA 0x0928 (same) 0xC6 209# 0xCD 0x092F ... LETTER YA 0x092F (same) 0xCD 210# 0xCF 0x0930 ... LETTER RA 0x0930 (same) 0xCF 211# 0xD2 0x0933 ... LETTER LLA 0x0933 (same) 0xD2 212# 0xE9 0x093C ... SIGN NUKTA 0x093C (same) 0xE9 213# 214# However, those mappings above cause roundtrip problems for the 215# the following mappings if they are decomposed: 216# 217# ISCII/ standard decomposition of reverse mapping 218# Mac OS Unicode mapping standard mapping of decomposition 219# ------ ----------------------- ---------------- ---------------- 220# 0xC7 0x0929 ... LETTER NNNA 0x0928 0x093C 0xC6 0xE9 221# 0xCE 0x095F ... LETTER YYA 0x092F 0x093C 0xCD 0xE9 222# 0xD0 0x0931 ... LETTER RRA 0x0930 0x093C 0xCF 0xE9 223# 0xD3 0x0934 ... LETTER LLLA 0x0933 0x093C 0xD2 0xE9 224# 225# One solution is to use a grouping transcoding hint with the four 226# decompositions above to mark the decomposed sequence for special 227# treatment in transcoding. This yields the following mappings to 228# decomposed Unicode: 229# 230# ISCII/ decomposed 231# Mac OS Unicode mapping 232# ------ ---------------- 233# 0xC7 0xF860 0x0928 0x093C 234# 0xCE 0xF860 0x092F 0x093C 235# 0xD0 0xF860 0x0930 0x093C 236# 0xD3 0xF860 0x0933 0x093C 237# 238# Details of mapping changes in each version: 239# ------------------------------------------- 240# 241################## 242# Section 1: Map the following byte pairs as indicated: 243# (ZWNJ means ZERO WIDTH NON-JOINER, ZWJ means ZERO WIDTH JOINER) 244# (Also see note about 0xF0 in comments above) 245# Section 2: Map the remaining bytes as follows: 246# 247# 248# 249# 250BEGIN_MAP 2510x0000 - 0x007F = 0x00 - 2520x00A9 = 0x88 2530x00AE = 0x89 2540x00D7 = 0x80 2550x0901 = 0xA1 2560x0902 = 0xA2 2570x0903 = 0xA3 2580x0905 = 0xA4 2590x0906 = 0xA5 2600x0907 = 0xA6 2610x0908 = 0xA7 2620x0909 = 0xA8 2630x090A = 0xA9 2640x090B = 0xAA 265#0x090C = 0xA6+0xE9 2660x090D = 0xAE 2670x090E = 0xAB 2680x090F = 0xAC 2690x0910 = 0xAD 2700x0911 = 0xB2 2710x0912 = 0xAF 2720x0913 = 0xB0 2730x0914 = 0xB1 2740x0915 = 0xB3 2750x0916 = 0xB4 2760x0917 = 0xB5 2770x0918 = 0xB6 2780x0919 = 0xB7 2790x091A = 0xB8 2800x091B = 0xB9 2810x091C = 0xBA 2820x091D = 0xBB 2830x091E = 0xBC 2840x091F = 0xBD 2850x0920 = 0xBE 2860x0921 = 0xBF 2870x0922 = 0xC0 2880x0923 = 0xC1 2890x0924 = 0xC2 2900x0925 = 0xC3 2910x0926 = 0xC4 2920x0927 = 0xC5 2930x0928 = 0xC6 2940x0929 = 0xC7 2950x092A = 0xC8 2960x092B = 0xC9 2970x092C = 0xCA 2980x092D = 0xCB 2990x092E = 0xCC 3000x092F = 0xCD 3010x0930 = 0xCF 3020x0931 = 0xD0 3030x0932 = 0xD1 3040x0933 = 0xD2 3050x0934 = 0xD3 3060x0935 = 0xD4 3070x0936 = 0xD5 3080x0937 = 0xD6 3090x0938 = 0xD7 3100x0939 = 0xD8 3110x093C = 0xE9 312#0x093D = 0xEA+0xE9 3130x093E = 0xDA 3140x093F = 0xDB 3150x0940 = 0xDC 3160x0941 = 0xDD 3170x0942 = 0xDE 3180x0943 = 0xDF 319#0x0944 = 0xDF+0xE9 3200x0945 = 0xE3 3210x0946 = 0xE0 3220x0947 = 0xE1 3230x0948 = 0xE2 3240x0949 = 0xE7 3250x094A = 0xE4 3260x094B = 0xE5 3270x094C = 0xE6 3280x094D = 0xE8 329#0x094D+0x200C = 0xE8+0xE8 330#0x094D+0x200D = 0xE8+0xE9 331#0x0950 = 0xA1+0xE9 3320x095F = 0xCE 333#0x0960 = 0xAA+0xE9 334#0x0961 = 0xA7+0xE9 335#0x0962 = 0xDB+0xE9 336#0x0963 = 0xDC+0xE9 3370x0964 = 0xEA 3380x0965 = 0x90 3390x0966 = 0xF1 3400x0967 = 0xF2 3410x0968 = 0xF3 3420x0969 = 0xF4 3430x096A = 0xF5 3440x096B = 0xF6 3450x096C = 0xF7 3460x096D = 0xF8 3470x096E = 0xF9 3480x096F = 0xFA 3490x0970 = 0x91 3500x200E = 0xD9 3510x2013 = 0x82 3520x2014 = 0x83 3530x2018 = 0x84 3540x2019 = 0x85 3550x2022 = 0x87 3560x2026 = 0x86 3570x2122 = 0x8A 3580x2212 = 0x81 359END_MAP 360