ANSI INCITS ISO IEC 10646-1-2000 Information technology Universal Multiple-Octet Coded Character Set (UCS) Part 1 Architecture and Basic Multilingual Plane AMENDMENT 1 Mathematical.pdf

1、 Reference numberISO/IEC 10646-1:2000/Amd.1:2002(E)ISO/IEC 2002INTERNATIONAL STANDARD ISO/IEC10646-1Second edition2000-09-15AMENDMENT 12002-07-15Corrected version2002-12-15Information technology Universal Multiple-Octet Coded Character Set (UCS) Part 1: Architecture and Basic Multilingual Plane AMEN

2、DMENT 1: Mathematical symbols and other characters Technologies de linformation Jeu universel de caractres cods sur plusieurs octets (JUC) Partie 1: Architecture et plan multilingue de base AMENDEMENT 1: Symboles mathmatiques et autres caractres Adopted by INCITS (InterNational Committee for Informa

3、tion Technology Standards) as an American National Standard.Date of ANSI Approval: 12/24/2002Published by American National Standards Institute,25 West 43rd Street, New York, New York 10036Copyright 2002 by Information Technology Industry Council (ITI).All rights reserved.These materials are subject

4、 to copyright claims of International Standardization Organization (ISO), InternationalElectrotechnical Commission (IEC), American National Standards Institute (ANSI), and Information Technology Industry Council(ITI). Not for resale. No part of this publication may be reproduced in any form, includi

5、ng an electronic retrieval system, withoutthe prior written permission of ITI. All requests pertaining to this standard should be submitted to ITI, 1250 Eye Street NW,Washington, DC 20005.Printed in the United States of AmericaISO/IEC 10646-1:2000/Amd.1:2002(E) PDF disclaimer This PDF file may conta

6、in embedded typefaces. In accordance with Adobes licensing policy, this file may be printed or viewed but shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In downloading this file, parties accept therein the responsibil

7、ity of not infringing Adobes licensing policy. The ISO Central Secretariat accepts no liability in this area. Adobe is a trademark of Adobe Systems Incorporated. Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation para

8、meters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below. ISO/IEC 2002 All rights reserved. Unless oth

9、erwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or ISOs member body in the country of the requester. ISO copyrig

10、ht office Case postale 56 CH-1211 Geneva 20 Tel. + 41 22 749 01 11 Fax + 41 22 749 09 47 E-mail copyrightiso.ch Web www.iso.ch Printed in Switzerland ii ISO/IEC 2002 All rights reserved ISO/IEC 10646-1:2000/Amd.1:2002(E) ISO/IEC 2002 All rights reserved iiiForeword ISO (the International Organizatio

11、n for Standardization) and IEC (the International Electrotechnical Commission) form the specialized system for worldwide standardization. National bodies that are members of ISO or IEC participate in the development of International Standards through technical committees established by the respectiv

12、e organization to deal with particular fields of technical activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other international organizations, governmental and non-governmental, in liaison with ISO and IEC, also take part in the work. In the field of information t

13、echnology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1. International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 3. The main task of the joint technical committee is to prepare International Standards. Draft International Stan

14、dards adopted by the joint technical committee are circulated to national bodies for voting. Publication as an International Standard requires approval by at least 75 % of the national bodies casting a vote. Attention is drawn to the possibility that some of the elements of this Amendment may be the

15、 subject of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights. Amendment 1 to International Standard ISO/IEC 10646-1:2000 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 2, Coded character sets. Thi

16、s corrected version of ISO/IEC 10646-1:2000/Amd.1:2002 includes the electronic attachments that were omitted in the original version. ISO/IEC 10646-1:2000/Amd.1:2002 (E) ISO/IEC 2002 All rights reserved 1Information technology Universal Multiple-Octet Coded Character Set (UCS) Part 1: Architecture a

17、nd Basic Multilingual Plane AMENDMENT 1: Mathematical symbols and other characters Page v, Foreword Replace: Part 2: Secondary Multilingual Plane for scripts and symbols, Supplementary Plane for CJK Ideographs, Special Purpose Plane by: Part 2: Supplementary Planes Remove the text “Additional parts

18、will specify other planes”. Page 2, clause 3 Append the following references: ISO/IEC 10646-2:2001, Information Technology Universal Multiple-Octet Coded Character Set (UCS) Part 2: Supplementary Planes. Unicode Standard Annex, UAX#9, The Unicode Bidi-rectional Algorithm, Version 3.1.0, 2001-03-23.

19、Page 6, figure 2 In the legend “Private use planes 0F, 10, E0-FF” de-lete “E0-FF”, and delete the upward arrows pointing to planes E0 to FF. Page 7, clause 6 Change “four-digit form” and “4-digit form” to “four-to-six-digit form” throughout. In clause 6.5, replace title, first paragraph and add note

20、 as follows: 6.5 Short identifiers for code positions (UIDs) ISO/IEC 10646 defines short identifiers for each code position, including code positions that are re-served. A short identifier for any code position is dis-tinct from a short identifier for any other code posi-tion. If a character is allo

21、cated at a code position, a short identifier for that code position can be used to refer to the character allocated at that code position. NOTE 1 For instance, U+DC00 identifies a code position that is permanently reserved for UTF-16, and U+FFFF identifies a code position that is permanently reserve

22、d. U+0025 identifies a code position to which a character is allocated; U+0025 also identifies that character (named PERCENT SIGN). Rename the existing note to NOTE 2, and increment all other note numbers of the sub-clause by one (NOTE 3 and 4). In clause 6.5.b change “It is not defined if the first

23、 four digits of the eight-digit form are not all zeros” to “It is not defined if the eight-digit form is greater than 0010FFFF” and append at the end of the text “Lead-ing zeros beyond four digits are suppressed.”. Change “+xxxx” in the BNF form to “+(xxxx | xxxxx | xxxxxx)”. Add a clause 6.5f: f. F

24、or the 8 digit forms, the characters SPACE or NO-BREAK SPACE may optionally be inserted before the four last digits. Page 8, clause 6 After clause 6.5, add a new clause 6.6 (UCS Se-quence Identifiers) and a note: “ISO/IEC 10646 defines an identifier for any se-quence of code positions taken from the

25、 standard. Such an identifier is known as a UCS Sequence Identifier (USI). For a sequence of n code positions it has the following form: where UID1, UID2, etc. represent the short identifiers of the corresponding code positions, in the same order as those code positions appear in the se-quence. If e

26、ach of the code positions in such a se-quence has a character allocated to it, the USI can ISO/IEC 10646-1:2000/Amd.1:2002 (E) ISO/IEC 2002 All rights reserved 2 be used to identify the sequence of characters allo-cated at those code positions. The syntax for UID1, UID2, etc. is specified in clause

27、6.5. A COMMA character (optionally followed by a SPACE character) separates the UIDs. The UCS Sequence Identifier shall include at least two UIDs; it shall begin with a LESS-THAN SIGN and be terminated by a GREATER-THAN SIGN.” NOTE UCS Sequences Identifiers cannot be used for specification of subset

28、 and collection content. They may be used outside this standard to identify: composite sequences for mapping purposes, font repertoire, etc. Page 8, clause 7 Remove the note. Page 8, Clause 8 Insert the following note after the first paragraph which ends “UCS-2 (see 13.1)”. NOTE 1 Since UCS-2 only c

29、ontains the repertoire of the BMP it is not fully interoperable with UCS-4, UTF-8 and UTF-16. Insert the following paragraph and note after the second paragraph which ends “reserved for control characters.” Code positions 0000 2060 to 0000 206F, 0000 FFF0 to 0000 FFFC, and 000E 0000 to 000E 0FFF are

30、 reserved for Alternate Format Characters (see annex F). NOTE 2 Unassigned code positions in those ranges may be ignored in normal processing and display. Replace the last paragraph as follows: Code positions 0000 FDD0 to 0000 FDEF, 0000 FFFE, and 0000 FFFF are permanently re-served. NOTE 3 Code pos

31、ition 0000 FFFE is reserved for “signature” (see annex H). Code positions 0000 FDD0 to 0000 FDEF, and 0000 FFFF can be used for inter-nal processing uses requiring numeric values which are guaranteed not to be coded characters, such as in terminating tables, or signaling end-of-text. Further-more, s

32、ince 0000 FFFF is the largest BMP value, it may also be used as the final value in binary or se-quential searching index within the context of UCS-2 or UTF-16.” NOTE 4 A “permanently reserved” code position cannot be changed by future amendments. Page 8, clause 9 Replace clause 9 to read as follows:

33、 9. Other planes 9.1 Planes reserved for future standardization Planes 11 to FF in Group 00 and all planes in any other groups (i.e. Planes 00 to FF in Groups 01 to 7F) are reserved for future standardization, and thus those code positions shall not be used for any other purpose. Code positions in t

34、hese planes do not have a map-ping to the UTF-16 form (see Annex C). NOTE To ensure continued interoperability between the UTF-16 form and other coded representations of the UCS, it is intended that no characters will be allo-cated to code positions in Planes 11 to FF in Group 00 or any planes in an

35、y other groups. 9.2 Planes accessible by UTF-16 Each code position in Planes 01 to 10 of Group 00 has a unique mapping to a four-octet sequence in accordance with the UTF-16 form of coded repre-sentation (see annex C). This form is compatible with the two-octet BMP form of UCS-2 (see 13.1). Page 8,

36、clause 10 Replace sub-clause 10.2 to read as follows: 10.2 Code positions for private use characters The code positions of Plane 0F and Plane 10 of Group 00 shall be for private use. The 6400 code positions E000 to F8FF of the Basic Multilingual Plane shall be for private use. The contents of these

37、code positions are not speci-fied in ISO/IEC 10646 (see 10.1). Page 9, clause 14 In the first paragraph, change the text “listed in an-nex B” to “listed in annex B of each part of ISO/IEC 10646”. Page 9, clause 14.1 Change the text “(see clause B.1)” to “(see clause B.1 of each part of ISO/IEC 10646

38、)”. Page 9, clause 14.2 Change the text “listed in clause B.2” to “listed in clause B.2 of each part of ISO/IEC 10646”. Page 12, clause 19 Add a new clause 19.1 at the end of clause 19. 19.1 Directional of bi-directional text The Unicode Bidirectional Algorithm describes the algorithm used to determ

39、ine the directionality for bidi-rectional text. ISO/IEC 10646-1:2000/Amd.1:2002 (E) ISO/IEC 2002 All rights reserved 3Page 13, Clause 22 Compatibility characters Add the following sub-clauses: 22.1 Compatibility Ideographs The CJK compatibility ideographs (characters part of the CJK COMPATIBILITY ID

40、EOGRAPHS-2001 col-lection) are ideographs that should have been unified with one of the CJK unified ideographs (characters part of the CJK UNIFIED IDEOGRAPHS-2001 col-lection), per the unification rule described in Annex S of this International Standard. However, they are included in this Internatio

41、nal Standard as separate characters, because, based on various national, cultural, or historical reason for some specific country and region, some national and regional standards assign separate code positions for them. NOTE For this reason, compatibility ideographs should only be used for maintaini

42、ng and guarantee-ing a round trip conversion with the specific national, regional, or other standard. Other usage is strongly discouraged. 22.2 Source references for CJK Compatibility Ideographs ISO/IEC 10646-1 provides the source reference for CJK Compatibility Ideographs included in the Basic Mult

43、ilingual Plane. ISO/IEC 10646-2 provides the source reference for CJK Compatibility Ideographs included in the Supplementary Planes. The source references for the CJK Compatibility Ideographs included in the BMP are provided in a machine-readable format that is accessible as a link to this document.

44、 The content pointed to by this link is also normative. NOTE 1 The referenced file is only available to us-ers who obtain their copy of the standard in a ma-chine-readable form. However, the file format makes it printable. The Kanji J sources are: J3 JIS X 213:2000 level-3 J4 JIS X 213:2000 level-4

45、The Hanja K source is: K0 KS C 5601-1987 The Unicode U source is: U0 The Unicode Standard 3.0-2000 The content linked to is a plain text file that specifies, after a 8-line header, as many lines as CJK Com-patibility Ideographs; each containing the following information organized in fixed width fiel

46、ds: 01-06 octet: BMP code value (0hhhh ) 07-12 octet: Corresponding CJK Unified Ideo-graph (0hhhh ). 13-20 octet: Kanji J sources (J3-hhhh ), (J4-hhhh ). 21-28 octet: Hanja K sources (K0-hhhh ). 29-36 octet : Unicode U sources (U0-hhhh ) The format definition uses h as a hexadecimal unit. Uppercase

47、characters and all other symbols includ-ing the space character between parentheses ap-pear as shown. Click on this highlighted text to access the reference file. NOTE 2 The content is also available as a separate viewable file in the same file directory as this docu-ment. The file is named: “CJKC0S

48、R.txt”. Page 13, clause 24 In the first paragraph, change the text “clause B.1” to “clause B.1 of each part of ISO/IEC 10646”, and change the text “clause B.2” to “clause B.2 of each part of ISO/IEC 10646”. Page 14, clause 24 A sub-clause 24.5 is added to the clause 24 Combin-ing Characters as follo

49、ws: 24.5 Variation selectors Variation selectors are combining characters follow-ing immediately a specific base character to indicate a specific variant form of graphic symbol for that character. Some variation selectors are specific to a script, such as the Mongolian free variation selec-tors, others are used with various other base charac-ters such as the mathematical symbols. Variations selectors following other characters have no effect on the selection of the graphic symbol for that char-acter. No se