##Adobe File Version: 1.000 #======================================================================= # FTP file name: CORPCHAR.TXT # # Contents: Registry (external version) of Apple use of # Unicode corporate-zone characters. # # Copyright: (c) 1994-1999 by Apple Computer, Inc., all rights # reserved. # # Contact: charsets@apple.com # # Changes: # # b03 1999-Sep-22 Update contact e-mail address. Matches # internal registry <b3> and Text Encoding # Converter version 1.5. # b02 1998-Aug-18 Expanded usage of 0xF8A0. Matches internal # registry <b3>. # n11 1998-Feb-05 Minor update to header comments # n09 1997-Dec-14 Update to match internal registry <n23>: # Add source hint 0xF850, transcoding hints # 0xF860-0xF86B and 0xF870-0xF872, deprecate # almost all other non-hint corporate # characters. # n08 1997-Jul-17 Update to match internal registry <n13>: # Add characters for Mac OS Chinese, Korean & # Farsi. Add CJK source hints. Deprecate some # characters in favor of combinations of # standard characters and transcoding hints. # Change header format. # n04 1995-Nov-15 Update to match internal registry <n8>: # Add characters for Mac OS Hebrew and Thai. # n02 1995-Apr-18 First version. Matches internal registry # <n5>. # # Standard header: # ---------------- # # Apple, the Apple logo, and Macintosh are trademarks of Apple # Computer, Inc., registered in the United States and other countries. # Unicode is a trademark of Unicode Inc. For the sake of brevity, # throughout this document, "Macintosh" can be used to refer to # Macintosh computers and "Unicode" can be used to refer to the # Unicode standard. # # Apple makes no warranty or representation, either express or # implied, with respect to these tables, their quality, accuracy, or # fitness for a particular purpose. In no event will Apple be liable # for direct, indirect, special, incidental, or consequential damages # resulting from any defect or inaccuracy in this document or the # accompanying tables. # # These mapping tables and character lists are subject to change. # The latest tables should be available from the following: # # <ftp://ftp.unicode.org/Public/MAPPINGS/VENDORS/APPLE/> # <ftp://dev.apple.com/devworld/Technical_Documentation/Misc._Standards/> # # For general information about Mac OS encodings and these mapping # tables, see the file "README.TXT". # # Format: # ------- # # Two tab-separated columns; # '#' begins a comment which continues to the end of the line. # Column #1 is the Unicode corporate character code point # (in hex as 0xNNNN) # Column #2 is a comment containing: # 1) an informal name describing the Unicode corporate character, # or if it is deprecated, information about what to use # instead. # 2) optionally, another '#', followed by information on which # Mac OS encodings use the Unicode corporate character, and - # if relevant - the Mac OS code points that correspond to the # corporate character. # # The entries are in Unicode order. #_______________________________________________________________________ # The block of 16 characters 0xF850-0xF85F is for source hint characters. # These have no display (like zero-width no-break space). If they appear # in text, they can only be mapped to tables that include them. If a run # of Unicode characters such as Han characters could otherwise be mapped # to any of several encodings, including one of these hint characters can # force the text to be mapped only to an encoding whose mapping table # includes the hint character. Once they have forced mapping to a particular # encoding, they no longer apply (they don't need to be cancelled); if a # subsequent character cannot be mapped to that encoding, it may be mapped # to another encoding. Currently source hints are mainly defined for CJK # source disambiguation. # NOTE: These are only defined for application developers who have requested # them. The Mac OS Text Encoding Converter does not generate these when # converting from other CJK encodings to Unicode. However, it will handle # these characters correctly when converting from Unicode to other encodings. 0xF850 # source hint: Reset, try all candidate encodings in preferred order. 0xF85C # source hint: Chinese simplified 0xF85D # source hint: Chinese traditional 0xF85E # source hint: Japanese 0xF85F # source hint: Korean # The block of 32 characters 0xF860-0xF87F is for transcoding hints. # These are used in combination with standard Unicode characters to force # them to be treated in a special way for mapping to other encodings; # they have no other effect. # # 0xF870-0xF87F are "variant tags" - they are like combining characters, # and can follow a standard Unicode (or a sequence consisting of a base # character and other combining characters) to tag it so that it will be # unique, treated in a special way for transcoding. These always terminate # a sequence of combining characters. # # 0xF860-0xF86B are "grouping hints" - they precede a group of two to # four standard Unicode characters to indicate that they are treated as a # group for transcoding. This grouping overrides any other combining # behavior. # # Here are the ones defined so far: 0xF860 # transcoding hint: group next 2 characters # Japanese,Korean 0xF861 # transcoding hint: group next 3 characters # Japanese,Korean 0xF862 # transcoding hint: group next 4 characters # Japanese,Korean 0xF863 # transcoding hint: group next 4 characters, alt1 # Korean 0xF864 # transcoding hint: group next 4 characters, alt2 # Korean 0xF865 # transcoding hint: group next 4 characters, alt3 # Korean 0xF866 # transcoding hint: group next 4 characters, alt4 # Korean 0xF867 # transcoding hint: group next 2 characters, alt1 # Korean 0xF868 # transcoding hint: group next 2 characters, alt2 # Korean 0xF869 # transcoding hint: group next 2 characters, alt3 # Korean 0xF86A # transcoding hint: group next 2 characters, RL # Hebrew 0xF86B # transcoding hint: group next 4 characters, RL # Farsi variant # 0xF870 # transcoding hint: variant tag 16 # Symbol, Korean 0xF871 # transcoding hint: variant tag 15 # Symbol, Korean 0xF872 # transcoding hint: variant tag 14 # Symbol 0xF873 # transcoding hint: variant tag 13 # Korean, Thai 0xF874 # transcoding hint: variant tag 12 # Korean, Thai 0xF875 # transcoding hint: variant tag 11 # Korean, Thai 0xF876 # transcoding hint: variant tag 10 # Korean 0xF877 # transcoding hint: variant tag 9 # Korean 0xF878 # transcoding hint: variant tag 8 # Korean 0xF879 # transcoding hint: variant tag 7 # Korean 0xF87A # transcoding hint: variant tag 6 # Korean 0xF87B # transcoding hint: variant tag 5 # Korean 0xF87C # transcoding hint: variant tag 4 # ChineseTrad, Korean, Dingbats 0xF87D # transcoding hint: variant tag 3 # ChineseTrad 0xF87E # transcoding hint: variant tag 2 # Chinese,Japanese 0xF87F # transcoding hint: variant tag 1 # CJK,Symbol,Dingbats,Hebrew # The following (2) are metrics "characters" so applications can get the # height and width of double-byte character glyphs by measuring the glyph of a # one-byte character (e.g. calling CharWidth for character 0x82 in a Chinese # Traditional font); this approach assumes that the glyphs for all double-byte # characters in a font have the same metrics, which is currently true. Note # that the width-metric character glyphs are used differently for TrueType and # old-style bitmap fonts; for TrueType fonts the metric glyph width is equal # to the full width of a double-byte character glyph, while for FBIT/FDEF # bitmap fonts the metric glyph width is half the width of a double-byte # character glyph. 0xF880 # height-metric character for double-byte fonts # Chinese Simp&Trad-0x81 0xF881 # width-metric character for double-byte fonts # Chinese Simp&Trad-0x82 # The following (2) are for the TrueType variant of Mac OS Farsi. # NOTE: 0xF883 is deprecated in favor of a combination of standard # characters and transcoding hint. The deprecated character will still # be loosely mapped to the appropriate Mac OS Farsi character. 0xF882 # Arabic ligature "peace on him" # Farsi(TrueType variant)-0x8B 0xF883 # deprecated, use 0xF86B+0x0631+0x064A+0x0627+0x0644 # Farsi(TrueType variant)-0xA4 # The following (22) are for the Mac OS Thai encoding. # In this encoding, positional variants of upper vowels, tone marks, # and other marks are normally handled automatically by WorldScript I. # However, the Thai-DTP keyboard allows the codes for the positional # variants to be entered directly, so they must be treated as # characters. When the abstract character is treated as a positional # variant, it has the right (and high, if relevant) position. # NOTE: These are now all deprecated in favor of combinations of standard # characters and transcoding hints. The deprecated characters will still # be loosely mapped to the appropriate Mac OS Thai character. 0xF884 # deprecated, use 0x0E31+0xF874 # Thai-0x92 0xF885 # deprecated, use 0x0E34+0xF874 # Thai-0x94 0xF886 # deprecated, use 0x0E35+0xF874 # Thai-0x95 0xF...
wendy6