Lines Matching +full:mac +full:- +full:only
4 SRC_ZONE 0x00-0xFF
13 # Contents: Map (external version) from Mac OS Farsi
16 # Copyright: (c) 1997-2002, 2005 by Apple Computer, Inc., all rights
23 # c02 2005-Apr-05 Update header comments. Matches internal xml
25 # b3,c1 2002-Dec-19 Add comments about character display and
28 # b02 1999-Sep-22 Update contact e-mail address. Matches
31 # n04 1998-Feb-05 Show required Unicode character
38 # n01 1997-Jul-17 First version. Matches internal utom<n1>,
42 # ----------------
63 # For general information about Mac OS encodings and these mapping
67 # -------
69 # Three tab-separated columns;
71 # Column #1 is the Mac OS Farsi code (in hex as 0xNN)
77 # The entries are in Mac OS Farsi code order.
81 # Mac OS Farsi character set uses the standard control characters at
82 # 0x00-0x1F and 0x7F.
84 # Notes on Mac OS Farsi:
85 # ----------------------
87 # This is a legacy Mac OS encoding; in the Mac OS X Carbon and Cocoa
88 # environments, it is only supported via transcoding to and from
93 # The Mac OS Farsi character set is based on the Mac OS Arabic
94 # character set. The main difference is in the right-to-left digits
95 # 0xB0-0xB9: For Mac OS Arabic these correspond to right-left
96 # versions of the Unicode ARABIC-INDIC DIGITs 0660-0669; for
97 # Mac OS Farsi these correspond to right-left versions of the
98 # Unicode EXTENDED ARABIC-INDIC DIGITs 06F0-06F9. The other
102 # Mac OS Arabic.
104 # Mac OS Farsi characters 0xEB-0xF2 are non-spacing/combining marks.
108 # The Mac OS Arabic character set (on which Mac OS Farsi is based)
109 # was developed in 1986-1987. At that time the bidirectional line
110 # layout algorithm used in the Mac OS Arabic system was fairly simple;
111 # it used only a few direction classes (instead of the 19 now used in
114 # characters were encoded twice, one with a left-right direction
115 # attribute and the other with a right-left direction attribute. This
116 # is the case in Mac OS Farsi too.
118 # For example, plus sign is encoded at 0x2B with a left-right
119 # attribute, and at 0xAB with a right-left attribute. However, there
120 # is only one PLUS SIGN character in Unicode. This leads to some
121 # interesting problems when mapping between Mac OS Farsi and Unicode;
125 # encoded only once in Mac OS Farsi, it may have a different
128 # For example, the Mac OS Farsi character at 0x93 is HORIZONTAL
129 # ELLIPSIS with strong right-left direction. However, the Unicode
132 # 3. Behavior of ASCII-range numbers in WorldScript
134 # Mac OS Farsi also has two sets of digit codes.
136 # The digits at 0x30-0x39 may be displayed using either European
139 # side of a sequence consisting of digits 0x30-0x39 and possibly comma
145 # decimal separator. In any case, 0x2C, 0x2E, and 0x30-0x39 are always
146 # left-right.
148 # The digits at 0xB0-0xB9 are always displayed using Persian digit
149 # shapes, and moreover, these digits always have strong right-left
156 # Mac OS Farsi encoding. This encoding is supported by the Tehran font
161 # variants in Mac OS Arabic). For these nine code points the standard
162 # Mac OS Farsi encoding has the following mappings:
163 # 0x8B -> 0x06BA ARABIC LETTER NOON GHUNNA (Urdu)
164 # 0xA4 -> <RL>+0x0024 DOLLAR SIGN, right-left
165 # 0xAA -> <RL>+0x002A ASTERISK, right-left
166 # 0xC0 -> <RL>+0x274A EIGHT TEARDROP-SPOKED PROPELLER ASTERISK,
167 # right-left
168 # 0xF4 -> 0x0679 ARABIC LETTER TTEH (Urdu)
169 # 0xF7 -> 0x06A4 ARABIC LETTER VEH (for transliteration)
170 # 0xF9 -> 0x0688 ARABIC LETTER DDAL (Urdu)
171 # 0xFA -> 0x0691 ARABIC LETTER RREH (Urdu)
172 # 0xFF -> 0x06D2 ARABIC LETTER YEH BARREE (Urdu)
177 # 0x8B -> 0xF882 Arabic ligature "peace on him" (corporate char.)
178 # 0xA4 -> 0xFDFC RIAL SIGN (added in Unicode 3.2)
179 # 0xAA -> <RL>+0x00D7 MULTIPLICATION SIGN, right-left
180 # 0xC0 -> <RL>+0x002A ASTERISK, right-left
181 # 0xF4 -> <RL>+0x00B0 DEGREE SIGN, right-left
182 # 0xF7 -> 0xFDFA ARABIC LIGATURE SALLALLAHOU ALAYHE WASALLAM
183 # 0xF9 -> <RL>+0x25CF BLACK CIRCLE, right-left
184 # 0xFA -> <RL>+0x25A0 BLACK SQUARE, right-left
185 # 0xFF -> <RL>+0x25B2 BLACK UP-POINTING TRIANGLE, right-left
188 # ---------------------------------
190 # 1. Matching the direction of Mac OS Farsi characters
192 # When Mac OS Farsi encodes a character twice but with different
193 # direction attributes for the two code points - as in the case of
194 # plus sign mentioned above - we need a way to map both Mac OS Farsi
196 # With the plus sign, for example, mapping one of the Mac OS Farsi
202 # and direction-dependent mappings. When mapping from Mac OS Farsi
208 # must have a strong left-right context, and a tag of <RL> indicates
209 # a right-left context.
214 # indicates LEFT-RIGHT OVERRIDE, PDF indicates POP DIRECTION
217 # 0x2B -> 0x202D (LRO) + 0x002B (PLUS SIGN) + 0x202C (PDF)
220 # forcing, the overrides need only be used at the beginning and end.
223 # 0x24 0x20 0x28 0x29 -> 0x202D 0x0024 0x0020 0x0028 0x0029 0x202C
226 # between strong-direction characters with matching directionality,
228 # always needed to map the right-left digits at 0xB0-0xB9.
230 # When mapping from Unicode to Mac OS Farsi, the Unicode
233 # Mac OS Farsi can then be disambiguated by the use of the resolved
236 # Unicode 0x002B -> Mac OS Farsi 0x2B (if L) or 0xAB (if R)
239 # be discarded when mapping from Unicode to Mac OS Farsi (after
244 # fidelity, they are sometimes used when mapping Mac OS Farsi
246 # the resulting Unicode text. For example, the single Mac OS Farsi
247 # ellipsis character has direction class right-left,and there is no
248 # left-right version. However, the Unicode HORIZONTAL ELLIPSIS
250 # with a resolved direction of left-right if surrounded by left-right
251 # characters). When mapping the Mac OS Farsi ellipsis to Unicode, it
254 # mapping the Unicode HORIZONTAL ELLIPSIS back to Mac OS Farsi.
256 # 2. Mapping the Mac OS Farsi digits
259 # strict round-trip fidelity is required. However, for numeric
261 # that may appear different than the Mac OS Farsi text displayed on
262 # a Mac OS system using WorldScript. This is because WorldScript
263 # uses context-dependent display for the 0x30-0x39 digits.
266 # alternate mappings should be used when a sequence of 0x30-0x39
267 # digits - possibly including 0x2C and 0x2E - occurs in an Arabic
273 # 0x30 0x06F0 # EXTENDED ARABIC-INDIC DIGIT ZERO
274 # 0x31 0x06F1 # EXTENDED ARABIC-INDIC DIGIT ONE
275 # 0x32 0x06F2 # EXTENDED ARABIC-INDIC DIGIT TWO
276 # 0x33 0x06F3 # EXTENDED ARABIC-INDIC DIGIT THREE
277 # 0x34 0x06F4 # EXTENDED ARABIC-INDIC DIGIT FOUR
278 # 0x35 0x06F5 # EXTENDED ARABIC-INDIC DIGIT FIVE
279 # 0x36 0x06F6 # EXTENDED ARABIC-INDIC DIGIT SIX
280 # 0x37 0x06F7 # EXTENDED ARABIC-INDIC DIGIT SEVEN
281 # 0x38 0x06F8 # EXTENDED ARABIC-INDIC DIGIT EIGHT
282 # 0x39 0x06F9 # EXTENDED ARABIC-INDIC DIGIT NINE
284 # 3. Use of corporate-zone Unicodes (mapping the TrueType variant)
292 # -------------------------------------------
296 # - Update mapping of 0xA4 in TrueType variant to use new Unicode
301 # - Change mapping of 0xA4 in TrueType variant (just described in
307 0x00 - 0x7F = 0x0000 -