ANSI INCITS ISO IEC 10646 AMD 2-2006 Information technology Universal Multiple-Octet Coded Character Set (UCS) AMENDMENT 2 N'Ko Phags-pa Phoenician and other characters.pdf

《ANSI INCITS ISO IEC 10646 AMD 2-2006 Information technology Universal Multiple-Octet Coded Character Set (UCS) AMENDMENT 2 N'Ko Phags-pa Phoenician and other characters.pdf》由会员分享，可在线阅读，更多相关《ANSI INCITS ISO IEC 10646 AMD 2-2006 Information technology Universal Multiple-Octet Coded Character Set (UCS) AMENDMENT 2 N'Ko Phags-pa Phoenician and other characters.pdf（86页珍藏版）》请在麦多课文档分享上搜索。

1、 iiiForeword ISO (the International Organization 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 te

2、chnical committees established by the respective 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

3、part in the work. In the field of information technology, 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 2. The main task of the joint technical committee is to prepare In

4、ternational Standards. Draft International Standards 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 so

5、me of the elements of this document may be the subject of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights. Amendment 2 to ISO/IEC 10646:2003 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 2, Code

6、d character sets. INCITS/ISO/IEC 10646:2003/Amd.2:20062008 ITIC 2008 All rights reservedInformation technology Universal Multiple-Octet Coded Character Set (UCS) Page 1, Clause 1 Scope In the note, update the Unicode Standard version from 4.1 to 5.0. Page 2, Clause 3 Normative references Update the

7、reference to the Unicode Bidirectional Algorithm and the Unicode Normalization Forms as follows: Unicode Standard Annex, UAX#9, The Unicode Bidi-rectional Algorithm, Version 5.0.0, March 2006. Unicode Standard Annex, UAX#15, Unicode Nor-malization Forms, Version 5.0.0, March 2006. Page 6, Figure 1 -

8、 Entire coding space of the Universal Multiple-Octet Coded Character set Remove the note. Page 7, Figure 2 Group 00 of the Universal Mul-tiple-Octet Coded Character set Remove the second note and rename the first note “NOTE” instead of “NOTE 1”. Page 8, Sub-clause 6.4 Naming of characters In the lis

9、t item c), remove unified in front of ideo-graphs. Replace last paragraph starting with “Guidelines to be used” with the following text: Additional rules to be used for constructing the names of characters are given in clause 28.1. Page 9, Clause 7 General requirement for the UCS Make the second not

10、e normative by removing the “NOTE 2” term and by setting it as requirement b. The first note is renamed “NOTE” and the following requirements become c. and d. Page 10, Sub-clause 9.2 Other Planes reserved for future standardization Replace text and note by the following: Planes 11 to FF in Group 00

11、and all planes in any other groups (i.e. Planes 00 to FF in Groups 01 to 7F) are permanently reserved. Code positions in these planes do not have a map-ping to the UTF-16 form (see annex C). Page 13, Clause 18 Block names Replace title with “Block and Collection names”. Add a sub-clause “18.1 Block

12、names”. Add the following paragraph after last. Rules to be used for constructing the names of blocks are given in clause 28.1. Add the following sub-clause: 18.2 Collection names Collections are shown in Annex A. Rules to be used for constructing the names of col-lections are given in clause 28.1.

13、Page 14, Clause 19 Characters in bidirectional context In the Note, replace “Unicode Standard Version 4.1” with “Unicode Standard”. Page 14, Sub-clause 20.3 Format characters In the list of format characters, remove the following entry: 1D159 MUSICAL SYMBOL NULL NOTEHEAD Page 15, Sub-clause 20.4 Var

14、iation selectors In the paragraph before Note 2, replace “table” with “list”, and remove the side borders around the de-scription of the variant appearances for mathemati-cal symbols. Page 16, Sub-clause 20.4 Variation selectors In the paragraph before Note 3, replace “table” with “list”, remove the

15、 last sentence “These combinations table”, and remove the side borders around the 1AMENDMENT 2: NKo, Phags-pa, Phoenician and other characters INCITS/ISO/IEC 10646:2003/Amd.2:20062008 ITIC 2008 All rights reserveddescription of the variant appearances for Mongo-lian. Page 17, Sub-clause 20.4 Variati

16、on selectors Insert the following text after the list describing the Mongolian variation sequences: The following list provides a description of the vari-ant appearances corresponding to the use of appro-priate variation selectors with all allowed base Phags-pa characters. These variation selector s

17、e-quences do not select fixed visual representation; rather, they select a representation that is reversed from the normal form predicted by the preceding character. Sequence (UID notation)Description of variant appearancePHAGS-PA LETTER reversed shaping SMALL A PHAGS-PA LETTER reversed shaping HA P

18、HAGS-PA LETTER reversed shaping I PHAGS-PA LETTER reversed shaping U PHAGS-PA LETTER reversed shaping E PHAGS-PA SUBJOINED LETTER re-versed shaping YA Page 23, Clause 28 Character names and annota-tions, sub-clause 28.1 General Replace paragraph with following new sub-clauses 28.1.1 to 28.1.4 28.1.1

19、 Entity names This standard specifies names for the following en-tity types: characters named UCS sequence identifiers (clause 29) blocks (clause 18 and A.2) collections (clause A.1) The names given by this standard to these entities shall follow the rules for name formation and name uniqueness spec

20、ified in this clause. This specifica-tion applies to the entity names in the English lan-guage version of this standard. NOTE 1 In a version of such a standard in another language: a) these rules may be amended to permit names to be generated using words and syntax that are considered appropriate wi

21、thin that language; b) the entity names from this version of the standard may be replaced by equivalent unique names con-structed according to the rules amended as in a) above. NOTE 2 Additional guidelines for constructing entity names are given in annex L for information. 28.1.2 Name formation An e

22、ntity names shall consist only of the following characters: LATIN CAPITAL LETTER A through LATIN CAPITAL LETTER Z, DIGIT ZERO through DIGIT NINE, SPACE, HYPHEN-MINUS, and FULL STOP if the entity being named is a collection. The first character in an entity name shall be a Latin capital letter. The l

23、ast character in an entity name shall be either a Latin capital letter or a Digit. An entity name shall not contain two or more con-secutive SPACE characters or consecutive HYPHEN-MINUS characters. A collection name shall not contain two or more consecutive FULL STOP characters. A sequence of a SPAC

24、E followed by a HYPHEN-MINUS or a sequence of a HYPHEN-MINUS fol-lowed by a SPACE may appear only in character names or named UCS sequence identifiers. EXAMPLE Each of the following two character names contains a consecutive SPACE and HY-PHEN-MINUS: TIBETAN LETTER -A TIBETAN MARK BKA- SHOG YIG MGO F

25、ULL STOP may appear only in between two alpha-numeric characters (LATIN CAPITAL LETTER A through LATIN CAPITAL LETTER Z, DIGIT ZERO through DIGIT NINE) in a collection name. EXAMPLE 1 The following collection name contains FULL STOP in between two Digits, DIGIT FOUR and DIGIT ONE: UNICODE 4.1 EXAMPL

26、E 2 The following collection name contains FULL STOP in between one Latin letter, LATIN CAPITAL LETTER D, and a Digit, DIGIT SEVEN: BMP-AMD.7 28.1.3 Single name Each entity named in this standard shall be given only one name. NOTE This does not preclude the informative use of name aliases or acronym

27、s for the sake of clarity. However, the normative entity name will be unique. 28.1.4 Name uniqueness Each entity name must also be unique within an ap-propriate name space, as specified here. 2 INCITS/ISO/IEC 10646:2003/Amd.2:20062008 ITIC 2008 All rights reserved28.1.5 Block names Block names const

28、itute a name space. Each block name shall be unique and distinct from all other block names specified in the standard. 28.1.6 Collection names Collection names constitute a name space. Each collection name shall be unique and distinct from all other collection names specified in the standard. 28.1.7

29、 Character names and named UCSsequence identifiers Character names and named UCS sequence identi-fiers, taken together, constitute a name space. Each character name or named UCS sequence identifier shall be unique and distinct from all other character names or named UCS sequence identifiers. 28.1.8

30、Determining uniqueness For block names and collection names, two names shall be considered unique and distinct if they are different even when SPACE and medial HYPHEN-MINUS characters are ignored in comparison of the names. NOTE 1 A medial HYPHEN-MINUS is a HYPHEN-MINUS character that occurs immedia

31、tely after a character other than SPACE and immediately before a character other than SPACE. EXAMPLE 1 The following hypothetical block names would be unique and distinct: LATIN-A LATIN-B EXAMPLE 2 The following hypothetical block names would not be unique and distinct: LATIN-A LATIN A LATINA For ch

32、aracter names and named UCS sequence identifiers, two names shall be considered unique and distinct if they are different even when SPACE and medial HYPHEN-MINUS characters are ignored and even when the words “LETTER“, “CHARACTER“, and “DIGIT“ are ignored in com-parison of the names. EXAMPLE 1 The f

33、ollowing hypothetical character names would not be unique and distinct: MANICHAEAN CHARACTER A MANICHAEAN LETTER A EXAMPLE 2 The following two actual character names are unique and distinct, because they differ by a HYPHEN-MINUS that is not a medial HYPHEN-MINUS: TIBETAN LETTER A TIBETAN LETTER -A T

34、he following two character names shall be consid-ered unique and distinct: HANGUL JUNGSEONG OE HANGUL JUNGSEONG O-E NOTE 2 These two character names are explicitly handled as an exception, because they were defined in an earlier version of this International Standard be-fore the introduction of the

35、name uniqueness require-ment. This pair is, has been, and will be the only ex-ception to the uniqueness rule in this International Standard. 28.1.9 Annotations A character name or a named UCS sequence identi-fier may be followed by an additional explanatory statement not part of the name, and separa

36、ted by a single SPACE character. These statements are in parentheses and use the Latin lower case letters a-z, digits 0-9, SPACE and HYPHEN-MINUS. A capi-tal Latin letter A-Z may be used for word initials where required. Such parenthetical annotations are not part of the entity names themselves, and

37、 the characters used in the annotations are not subject to the name unique-ness requirements. A character name may also be followed by a single ASTERISK separated from the name by a single SPACE. If a parenthetical annotation is present, the ASTERISK follows the annotation and is separated from the

38、closing parenthesis by a single SPACE. The presence of the ASTERISK notes that additional information on the character is available in annex P of this standard. Page 23, sub-clause 28.3 Character names and annotations for Hangul syllables Replace the ending note as follows: NOTE The annex R provides

39、 the names of Hangul syllables in two formats: syllable-name and full name/annotation, both available through linked files. Page 25, New Clause 29 Insert this new clause after Clause 28 and renumber following clauses as appropriate. 29 Named UCS Sequence Identifiers A named UCS Sequence Identifier (

40、USI) is a USI associated to a name following the same construc-tion rules as for character names. These rules are given in Clause 28. NOTE The purpose of these named USIs is to spec-ify sequences of characters that may be treated as single units, either in particular types of processing, in referenc

41、e by standards, in listing of repertoires (such as for fonts or keyboards). The following list provides a description of these named UCS sequence identifiers. 3INCITS/ISO/IEC 10646:2003/Amd.2:20062008 ITIC 2008 All rights reservedUSI USI nameLATIN CAPITAL LETTER A WITH MACRON AND GRAVE LATIN SMALL L

42、ETTER A WITH MACRON AND GRAVE LATIN SMALL LETTER A WITH ACUTE AND OGONEK LATIN CAPITAL LETTER E WITH VERTICAL LINE BELOW LATIN SMALL LETTER E WITH VERTICAL LINE BELOW LATIN CAPITAL LETTER E WITH VERTICAL LINE BELOW AND GRAVE LATIN SMALL LETTER E WITH VERTICAL LINE BELOW AND GRAVE LATIN CAPITAL LETTE

43、R E WITH VERTICAL LINE BELOW AND ACUTE LATIN SMALL LETTER E WITH VERTICAL LINE BELOW AND ACUTE LATIN CAPITAL LETTER E WITH CIRCUMFLEX AND MACRON LATIN SMALL LETTER E WITH CIRCUMFLEX AND MACRON LATIN CAPITAL LETTER E WITH CIRCUMFLEX AND CARON LATIN SMALL LETTER E WITH CIRCUMFLEX AND CARON LATIN CAPIT

44、AL LETTER I WITH MACRON AND GRAVE LATIN SMALL LETTER I WITH MACRON AND GRAVE LATIN SMALL LETTER I WITH DOT ABOVE AND ACUTE LATIN SMALL LETTER NG WITH TILDE ABOVE LATIN CAPITAL LETTER O WITH VERTICAL LINE BELOW LATIN SMALL LETTER O WITH VERTICAL LINE BELOW LATIN CAPITAL LETTER O WITH VERTICAL LINE BE

45、LOW AND GRAVE LATIN SMALL LETTER O WITH VERTICAL LINE BELOW AND GRAVE LATIN CAPITAL LETTER O WITH VERTICAL LINE BELOW AND ACUTE LATIN SMALL LETTER O WITH VERTICAL LINE BELOW AND ACUTE LATIN CAPITAL LETTER S WITH VERTICAL LINE BELOW LATIN SMALL LETTER S WITH VERTICAL LINE BELOW LATIN CAPITAL LETTER U

46、 WITH MACRON AND GRAVE LATIN SMALL LETTER U WITH MACRON AND GRAVE GEORGIAN LETTER U-BRJGU KHMER CONSONANT SIGN COENG KA KHMER CONSONANT SIGN COENG KHA KHMER CONSONANT SIGN COENG KO KHMER CONSONANT SIGN COENG KHO KHMER CONSONANT SIGN COENG NGO KHMER CONSONANT SIGN COENG CA KHMER CONSONANT SIGN COENG

47、CHA KHMER CONSONANT SIGN COENG CO KHMER CONSONANT SIGN COENG CHO KHMER CONSONANT SIGN COENG NYO KHMER CONSONANT SIGN COENG DA KHMER CONSONANT SIGN COENG TTHA KHMER CONSONANT SIGN COENG DO KHMER CONSONANT SIGN COENG TTHO KHMER CONSONANT SIGN COENG NA KHMER CONSONANT SIGN COENG TA KHMER CONSONANT SIGN

48、 COENG THA KHMER CONSONANT SIGN COENG TO KHMER CONSONANT SIGN COENG THO KHMER CONSONANT SIGN COENG NO KHMER CONSONANT SIGN COENG BA KHMER CONSONANT SIGN COENG PHA KHMER CONSONANT SIGN COENG PO KHMER CONSONANT SIGN COENG PHO KHMER CONSONANT SIGN COENG MO KHMER CONSONANT SIGN COENG YO KHMER CONSONANT

49、SIGN COENG RO KHMER CONSONANT SIGN COENG LO KHMER CONSONANT SIGN COENG VO KHMER CONSONANT SIGN COENG SHA KHMER CONSONANT SIGN COENG SSA KHMER CONSONANT SIGN COENG SA KHMER CONSONANT SIGN COENG HA KHMER CONSONANT SIGN COENG LA KHMER VOWEL SIGN COENG QA KHMER INDEPENDENT VOWEL SIGN COENG QU KHMER INDEPENDENT VOWEL SIGN COENG RY KHMER INDEPENDENT VOWEL SIGN COENG RYY KHMER INDEPENDENT VOWEL SIGN COENG QE KHMER VOWEL SIGN OM KHMER VOWEL SIGN AAM KATAKANA LETTER AINU P MODIFIER LETTER EXTRA-HIGH EXTRA-LOW CONTOUR TONE BAR All the