ISO/IEC JTC 1/SC 2 N

3412/WG2 N2181
Date: 2000-03-02

ISO/IEC JTC 1/SC 2
CODED CHARACTER SETS
SECRETARIAT: JAPAN (JISC)

DOC TYPE:

Summary of Voting/Table of Replies

TITLE:

Summary of Voting on SC 2 N 3393, ISO/IEC CD 10646-2, Information
Technology -- Universal Multiple-Octet Coded Character Set (UCS) -Part 2: Secondary Multilingual Plane for scripts and symbols
Supplementary Plane for CJK Ideographs
Special Purpose Plane

SOURCE:

Secretariat, ISO/IEC JTC 1/SC 2

PROJECT:

JTC 1.02.18.02

STATUS:This document is forwarded to WG 2 for consideration. WG 2 is requested toprepare a disposition of comments report, revised text and a recommendation on
further processing.

ACTION ID:

ACTDUE DATE:
DISTRIBUTION: P, O and L Members of ISO/IEC JTC 1/SC 2
WG Conveners and Secretariats
Secretariat, ISO/IEC JTC 1
ISO/IEC ITTF
NO. OF PAGES:

39

ACCESS LEVEL: Defined
WEB ISSUE #:078

Contact: Secretariat ISO/IEC JTC 1/SC 2 - Toshiko KIMURAIPSJ/ITSCJ (Information Processing Society of Japan/Information Technology Standards Commission of Japan)*Room 308-3, Kikai-Shinko-Kaikan Bldg., 3-5-8, Shiba-Koen, Minato-ku, Tokyo 105-0011 JAPAN
Tel: +81 3 3431 2808; Fax: +81 3 3431 6493; E-mail: kimura@itscj.ipsj.or.jp*A Standard Organization accredited by JISC

Summary of Voting on SC 2 N 3393
Approve

P-member
Armenia
Austria
BelgiumBrazilCanadaChina
Denmark
Egypt
FinlandFranceGermany
GreeceIceland
India
Iran, Islamic
Republic of
IrelandIsraelItaly
Japan
Korea Rep. ofMongolia
MoroccoNetherlands
NorwayPolandRomania
Russian Federation
Singapore
Slovenia
SwedenThailandTunisia
TurkeyUK
USA
Yugoslavia

Disapprove

AbstainNo
response

Comments

X
X

X
X
X
X

Attachment 1

X
X*

X
Attachment 2

X

X
X

Attachment 3
Attachment 4

X
X
X
X

To be
submitted

X

X
X

X
X

Attachment 5

X
X
X
X

X

Lack of
Expertise

X
X*

Attachment 6

X

X*

Attachment 7

X
X
X
X
X
9

Total (36)O-member (if responding)Australia
Portugal

Approvewithcomments

5
14

Attachment 8
Attachment 9

5
5

2
2
X
X

X
15
15
Lack of
Expertise*=Acceptance of these reasons and appropriate changes in the text will change our vote to approval.

Attachment 1 – China
China is in favour of ISO/IEC/JTC1/SC2 N3393 with comments on Plane 2,
Supplementary Plane for CJK Ideographs (CJK Unified Ideographs Extension B). And
we will attach the comments to the accessory.

Attachment 2 – Finland
We are aware of and agree in principle with the initiative to split the CJK Extension B
into two parts and move one part (consisting of JIS 0213, the Korean set and possibly theHong Kong set) into the BMP, i.e. 10646-1. Thus, we believe that the current CD should
be used as the basis for future work only after the initiative has been duly acted upon, at
which stage our ballot for the remaining content of the CD will change to Approve.

Attachment 3 - Germany

German comments on CD 10646-2
Vote
Approval with comments.

Coding of characters (§4)
It is prefereable to use the six-digit form throughout to have a uniform mechanism to address all
characters, including those in the Private Use plane.

Etruscan
Major
This table contains not only Etruscan characters, but also characters from other Italic languages
such as Umbrian (e. g. 031C), Faliscan (e. g. 0317) and Oscan (e. g. 031D). This stresses theimportance to seek not only an isolated solution for Etruscan, based upon less than authoritative
sources,a targetbutthat
to is
aim
quite
for a comprehensive solutions for all Italic languages
possible to attain.
More detailed information and further assistance can be made available upon request.

Minor
All Etruscan glyphs and also the Umbrian character 031C need to be reversed, for Etruscan wasusually written leftwards.
Note: A few characters such as the Oscian-Umbrian letter 031B are already in correct order.

Gothic
Major
Gothic letter "EIS WITH DIAERESIS" (033A) should not be encoded as a separate character.
The diaeresis on the eis is used primarily to indicate boundaries between morphemes; thecharacter as such does not carry any additional meaning, is unified with the eis for ordering
purposes and also does not figure as a numeral sign (eis: 10, kusma: 20, etc) as all the other
Gothic characters do. It is therefore a perfect example of a precomposed character, to use
Unicode terminology.

Minor
A few glyphs are not quite correct (e. g. bairkan and qairthra). For more details on more suitable
glyphs please cf. Wilhelm Braune: Gotische Grammatik. Mit Lesestücken undWörterverzeichnis. Neubearbeitet von Ernst A. Ebbinghaus. Tübingen: Niemeyer, 1981,
especially p. 14, or any good reproduction of the Codex Argenteus. For more information please
see the Gothic link list (in German) http://www.sfb441.uni-tuebingen.de/~reimar/gotisch.html

Deseret
Germany objects to the encoding of this sort of artificial scripts such as Deseret as a matter ofprinciple. It requests that Table 3 be removed.

Western Musical Symbols
Tables 7 and 8 fill a gap in an important area of typesetting, the typesetting of musical symbols.
While our experts are full of praise for this proposal in general, there are a number of open
issues. First of all, there are a few missing characters that should be taken account of:Secondly, Annex E is insufficiently clear as to how a practical encoding of musical scores shouldwork. It would be immensely helpful if one or two brief concrete examples could be given on
how this is to function in detail.
Especially, Annex E should strongly point out that encoding musical pitch is outside the scope ofwhat tables 7 and 8 aim to attain.

Some questions which need still further discussion:•

Should there be precomposed notes with downward stem?

•

Should a mechnanism (e. g. number-like symbols) to indicate the beat? (e. g. 3/4 beat) be
defined? If so, how would such a mechanism look like?

Mathematical Alphanumeric Symbols
We acknowledge that typography can mark a semantic difference in mathematical typesetting.
This is true, however, for typographic distinctions (italic, bold, etc.) in many fields ofapplication, including, e. g., the humanities.
For good reasons, SC2/WG2 refuses to take typographic distinctions into account. The
mathematical alphanumeric symbols break this rule, introducing potential data exchange
problems which are likely to arise from misuse of these symbols. Germany therefore objects tothe inclusion of these characters.
Should the need for a solution in this area be found to be compelling, then it might beworthwhile to investigate solutions in the spirit of §10.3.

Annex D: Tag characters
This approach should be closely harmonized with relevant groups such as the W3C. At least a
note should inform the reader about the use, potential benefits and pitfalls of the tag characters in
an SGML/XML environment.

Annex F
Care should be taken to find authoritative sources and the consent of eminent experts in the fields
concerned.

The national body of Japan approves the registration of ISO/IEC CD 10646-2.

The national body of Japan disapproves the ISO/IEC CD 10646-2 with following comments.
The national body of Japan requests to proceed to 2nd CD as a next step.

Comments
J-1: Clause 10.3: This clause describes two independent things. One is a structure of theplane-14, and the other is a characteristic of TAG block.

Separate them into two sub-clauses.

Note: This is one example that the several clauses of the CD have multiple unrelated information.
They should be separated.

J-2: Clause 10.3: Insert following text between “represented in the character code table bydotted box” and “ A possible use….”“A functionality of TAGS for their use is not defined in thisinternational standard, it shall be defined in separated standards”

J-3: Clause 10.2: Japan strongly requests the source information of CJK ideographs (either
unified and compatibility) in plane-2 should be “normative ”. Therefore, it should be a part of thisinternational standard. The source information should not be an information somewhere else.
If it is separated, it should be another ISO/IEC standard (and to be described in clause 3).
The clause 10.2 does not describe those clearly.

If the idea is a “normative” electronic data stored in a defined place (and to be accessed byelectronic means by public), the method should be approved by ISO and/or IEC (at least by
JTC1 and supported by ITTF in written form).

J-4: Clause 10.2:

The format information of the source data should be in a sub clauseseparated from the clause 10.2. (again clause 10.2 has too much of information)
And current text (last part of clause 10.2) is not clear enough for the user. At least, “whichcorresponds to G, which for T……of the part-1 kind of information to be added.

J-5: Most of the user may not understand the differences among Hanzi, Hanja, Kanji……,
Use much clear explanation.

J-6: Clause 10.2

kanji from JPNxxx should be changed to:Japanese source (do not describe as Kanji):

JIS X 0213:2000

Also, 48-54 octet: Kanji(JPNddd) is very questionable. Why not be same as others?

J-7: Clause 1: remove NOTE. This note is not necessary as a JTC1 international standard.

J-8

Clause 2: Does this clause really necessary?

The conformance clause of the part-1 isdescribes that the conformance of ISO/IEC 10646 (not only part-1).

J-9: Clause 3: add ISO/IEC 10646-1:2000? As a normative reference. This standard is not
in ISO/IEC 10646-1 as this CD expecting.

J-10:

Clause 4:

2nd paragraph 1st line, Change “within planes 01 to 0F” to “within planes 01,

02 and 0E”.

Comment on the editor’s note: Japan does not care the number of digits.

J-11: Clause 5: Japan supports the idea to refer to the definitions of ISO/IEC 10646-1.
However, there is a conflict with the definition clause of the part-1. Clause 1 SCOPE of thepart-1 describes as “the part-1 defines terms used in ISO/IEC 10646”,

And the SCOPE of

the part-2 does not say any on the definition. Therefore, the definition clauses should be moved
to the part-1 (in theory).

However, it would be better to change the part-1 so that clause 5 ofthe part-5 can be used as it is now.

J-12: Clause 6 SMP: Clarification of the last bullet of the NOTE: Does “Symbol set” include“ideographic symbol”?
ideographic symbols.

Note that clause 7 SIP does not describe that SIP includes theThen what for 00-0F of the plane-2?

Japan believes that all symbols (include ideographic symbols) to be in plane-1, and 00-0F of theplane-2 should be used for CJK unified ideograph. Thus, the current text itself is acceptablewith Japan, but it is conflicting with WG2 decision at Copenhagen.

J-13:

Clause 710646-1.

J-14:

SIP:

Clarification:

In 3r d paragraph 3rd line.

Clause 4.13 of ISO/IEC

Is this ISO/IEC 10646-1:1993 or 2000? They are different terms. It may be 2000.

Clause 8

SPP:

Delete “Some of these characters….do not have printable graphic

symbols”.
Rationale: It will not be a case only for the SPP, it may be happened on any plane.
Thus this kind of information should be added (if needed) character by character in principle.

J-15

Clause 10.2: Note: Beginning text of annex R of the part-1 is not applicable for thepart-2 (plane-2). Add more explanation.

J-16:

Clause 10.3: Note does mean nothing, delete all text of the note.

J-17:

Clause A.1: Add a collection for plane-1, plane-2 and plane-14 just like collection 300

and 301 of the BMP.

This might make sub-setting easier.

Note: Conformance clause of the part-1 is covering all parts of the ISO/IEC 10646.

J-18: Clause A.1: Note: Change “The CJK Ext-B collection includes characters form the CJKCOMPATIBILITY….” To “ The CJK Ext-B collection includes (real number to be here) charactersfrom the CJK COMPATIBILITY…..” .

J-19: Table-8 Row 00: TAGS: Change title to “table 16 Row 00 TAGS”

J-20: Clause B.2: Change text to “The following characters are not allowed in implementationlevel 2” then describe “none”.
Rationale: Thus addition of the level 2 characters in future is easier.

J-21: Clause C.2: Add code range for CJK Unified ideograph Ext-B.
Add CJK compatibility ideograph with empty code range. (or add in later).

J-22: Clause D.5: Change U-XXXX short ID to CODE VALUE in HEX.
Rationale: to be consistent with other portion of ISO/IEC 10646 series of standards.

J-23:

Extension B

See Attachment.

Extra comment on AMD-1 for ISO/IEC 10646-1.2: Annex R: Is this really annex R? It would
be annex S. Confirm these characters with final version of Ext-B with CJK editor. If the FAXX
characters here are all correct, then add annex P equivalent to this international standard. And
also source information should be provided for those characters.

------end of comments-----

Attachment

UCS code ofthecharacter
that
to
be
removedforunification
2-144F
2-18F82-210E
2-24392-25672-259E
2-274C
2-28632-2CAB
2-2DEC
2-2EEA
2-32F62-33732-35F92-3655
2-39CE
2-3A672-3E01
2-3E872-3FD42-42B3
2-42C82-442B
2-46ED
2-47982-48AA
2-4BBD
2-4C742-4D5D
2-51932-580B
2-5BE82-5BEA
2-5CEA
2-5E27
2-5EAD
2-61F9SuperCJK9.0
number of thecharacter thatto be removed
for unification
08099
10171
13336
14550
14978
15055
15793
16359
18222
18852
19231
20818
21022
22396
22545
24098
24342
25808
26132
26857
28105
28171
28800
29784
30041
30464
31865
32144
32504
34150
36802
38311
38314
38809
39336
39515
40952

UCS code ofthecharacter
that
to
be
unified with
0-578B
0-36FC
0-5DE2
0-5EFE
0-38C7
0-5F620-60810-60C70-62FC
0-63A90-6477
2-32F60-3B080-681F
0-69142-3A18
0-3C4E
0-6CBF
0-6D85
0-3D330-70700-707D
2-438D
0-72500-72802-48620-7485
0-3F1B
0-753E
0-3F1B
0-798F
2-5BE3
0-7AEE
2-5CEB
0-4227
2-5DC00-7DC7

SuperCJK9.0
number of thecharacter thatto be unified
with
07798
10062
13332
14549
14972
15040
15922
16101
17889
18270
18841
20744
20962
21973
22419
24223
24345
25701
26042
26770
28093
28119
28537
29816
30028
30328
31671
32102
32483
34102
36736
38306
38290
38810
38960
39168
40777

2-62EA
2-6474
2-6F452-72252-74CA
2-74F02-88972-8906
2-8CE42-9101
2-A176
2-A401
2-A6762-4703
2-60CF
2-6CF3
2-7D6E
2-87092-0CC32-2ADE
2-42322-5890
2-6D8F
2-0956
2-14392-2FB62-3FD42-6EC2
2-92B92-A1C2
2-A31A
2-A48D
2-A4AF
2-A63A
2-0CDB
2-29142-2617
2-5C0E
2-24EA
2-1E0C

41355
42074
46664
47819
48926
48991
57229
57386
59306
61143
67722
68796
69658
29809
40320
45601
52748
56626
04924
17327
27909
36985
45929
03641
08074
19535
26857
46469
61737
67853
68410
68997
69039
69568
04983
16668
15250
38360
14798
12058

0-7E45
0-7F7A
0-84F12-70F40-87280-87792-887B
0-911B
0-9145
0-96C30-9CFD
2-A3E90-9F162-47072-60C90-83BD
0-8CFF
2-86E00-54060-621B
0-701B
0-79C40-83FB
0-52C7
2-1438
2-2FB5
0-3D330-45442-92BD
2-A1AE
2-A31C
2-A48C
2-A4AD
0-9F000-54480-614C
0-5F9A
0-8D11
2-0BF3
0-5C6E

41133
42017
46369
47365
48701
48904
57184
57250
59100
61097
67530
68761
69650
29814
40314
45822
52747
56580
04886
17322
27789
36984
45928
03637
08073
19534
26770
46901
61741
67815
68412
68996
69037
69562
05018
16509
15317
53525
04614
12055

2-255E(JPN 073) was withdrawn by Japan and should be removed from Ext. B.
2-2914 (KXI 0401.310; T6-5D26; SCJK9.0 16668) is unified to 0-614C (KXI
0398.090; T1-637D; SCJK9.0 16509) and is suggested to be put into the suggested
CJK Compatibility Zone in Plane 2.

The following glyphs found in Extension B are wrong.
Ext. Number

SCJK90
Number

2-063402410

2-040301565

2-0AC404183

2-399524016

2-7ED853288

2-09DC03855

2-5E6039402

2-675C

43173

2-7E3D

53044

2-A7DB

70160

2-69FB

44328

2-0A7304072

2-37B523285

Wrong Glyph

Right GlyphThe following characters should be added in Extension B for disunification.
Character
to be
added

Counerpart’s
UCS code

Corresponding pairs inSuperCJK9.0

Suggested KXIIndex of new
character

2-02790089.201

2-126A

0215.271

2-20E70323.1412-308B

0474.131

2-3A9B

0474.131

2-31020475.321

2-3AD90578.131

2-4BEC0745.051

2-660A

0961.131

2-6D2C1036.401

2-82061338.081

2-8E9D

1338.081

2-086C

0142.281

More comments

Character
to be
added

Counerpart’s
UCS code

Corresponding pairs inSuperCJK9.0

Suggested KXIIndex of new
character2-093A

0147.071

2-156A

0240.301

2-24BD0357.100

2-2D930582.351

2-35670526.210

2-07B30137.301

0-365C0274.1710-37360274.171

0-37AF

0307.271

0-3ABF0479.151

0-3DD70678.130

0-4CF91498.400

2-11510211.400

2-42640663.191

More comments

KXI index of 224BD shouldbe
0357.101

KXI index of 23567 should be0526.211KXI index of 03DD7 should be
0678.161

KXI index of 21151 should be0211.121Character
to be
added

Counerpart’s
UCS code

Corresponding pairs inSuperCJK9.0

Suggested KXIIndex of new
character

2-48490704.351

0-67470513.011

0-93F8More comments

The following characters’ source information are incorrect or missing.
Extension SCJK9.0
Wrong / Missing
Source Code to be Added /B CodeNo
Source Codechanged
2-2BAB
17661
T6-2722
Change to T6-2772.
(Wrong source)(Font no change)
2-735E
48231
Add T7-5C24 source
2-108906601
Add T7-2149 source
2-115D
06895
Add T7-3732 source
2-126507234
Add T7-5752 source
2-12D107400
Add T6-2D34 source
2-168D
09000
Add T6-2265 source
2-1A0810614
Add T7-4650 source
2-1C7611524
Add T6-3032 source
2-1E0C
12058
Add T4-2135 source
2-212913371
Add T5-237C source
2-21B813603
Add T6-3060 source
2-21BB
13606
Add T6-3066 source
2-21C713622
Add T6-372A source
2-238A
14301
Add TF-3A66 source
2-245114584
Add T6-3073 source
2-246614606
Add T6-3F4E source
2-255314949
Add T5-6C26 source
2-26C015491
Add T6-2326 source
2-26EA
15602
Add T3-257E source
2-274815777
Add T6-3759 source
2-278B
15944
Add T6-3F6B source
2-2AE717339
Add T4-375C source
2-2B3617445
Add T7-472D source
2-2B8E
17593
Add T5-226F source
2-2C8018128
Add T6-4028 source
2-2EA019124
Add T7-2E35 source
2-2FE4
19598
Add T4-2D3E source
2-319F
20210
Add T6-495C source
2-31AE
20234
Add T4-5F6C source
2-31D820298
Add T3-4731 source
2-33C021156
Add T4-5055 source
2-34DC
21591
Add T6-2522 source
2-35CE
22274
Add T6-4060 source
2-371622954
Add T3-474B source
2-396423954
Add T7-5B61 source
2-3A2524244
Add T6-5D76 source
2-3A8E
24397
Add T5-2835 source
2-3BFA
24909
Add T7-4031 source
2-3BFE
24914
Add T7-474C source
2-3C3F
24998
Add T5-214A source2-3D3A
2-40442-404C
2-4161
2-41E52-434D
2-45CD
2-48302-48FD
2-4908
2-49D92-4B3E
2-4B67
2-4BC1
2-4C53
2-4D01
2-4D11
2-4D3A
2-50E92-511D
2-52072-5888
2-59DA
2-5A6B
2-5B8E
2-5C5A
2-5C782-5CB02-5CEB
2-5D53
2-5DD2
2-5F262-5FAF
2-604B
2-60A92-60C92-612F
2-61B52-65F72-6621
2-67272-673F
2-67FF
2-68E2
2-6D5D
2-6E2A
2-6EA6

25330
27088
27105
27600
27787
28404
29428
30255
30617
30633
30954
31648
31719
31875
32078
32367
32385
32443
33914
33984
34302
36969
37556
37749
38167
38514
38588
38690
38810
38989
39203
39678
39902
40138
40263
40314
40544
40818
42640
42706
43105
43134
43510
43919
45792
46232
46396

Add T7-386B source
Add T6-5E3C source
Add T6-5E38 source
Add T3-553A source
Add T7-475B source
Add T5-2E4D source
Add T5-7043 source
Add T7-4E3F source
Add T6-4B38 source
Add T5-3A28 source
Add T7-3935 source
Add T3-4826 source
Add T7-253D source
Add T4-6028 source
Add T7-623B source
Add T7-4066 source
Add T6-3479 source
Add T6-395D source
Add T7-4E4F source
Add T6-4B6F source
Add T7-5C24 source
Add T4-217E source
Add T7-3978 source
Add T3-2A45 source
Add T5-7934 source
Add T6-427B source
Add T6-4C5D source
Add T6-5631 source
Add T6-6024 source
Add T4-5240 source
Add T7-3A29 source
Add T7-5C34 source
Add T6-4C62 source
Add T7-3A35 source
Add T7-5857 source
Add T6-2D52 source
Add T6-4C6D source
Add T6-6035 source
Add T7-5863 source
Add T7-2729 source
Add T3-5863 source
Add T7-4877 source
Add T6-3B2F source
Add T6-606A source
Add T5-3528 source
Add T6-5765 source
Add T6-6133 source2-7235
0-85C42-771E
2-798D
2-7DA72-8867
2-88C62-898F
2-8A47
2-8A8F
2-8AB3
2-8C23
2-8C6C
2-8CFE
2-8F652-90412-92972-955C
0-4AA3
2-97C4
2-9AD82-9BFD
2-9DB02-9EAC
2-A0A3
0-4D56
2-A57C
2-A652
2-A6F12-34862-5890
2-6D8F
2-6031
2-05F5
2-19FF
2-1BA72-7ED8
2-20FC
2-225E
2-239E
2-25AE
2-39FC
2-72B82-893C
2-8E2C
2-A391
2-27C4

47836
49385
49792
50870
52832
57156
57306
57614
57889
58002
58120
58973
59115
59336
60496
60869
61691
62715
62721
63692
64999
65477
66072
66385
67266
69265
69309
69597
69828
21446
36985
45929
40095
02328
10600
11255
53288
13301
13859
14329
15079
24179
48004
57457
59989
68557
16047

KXI index 0505.041

V3-083DT6-6267

Add T7-5876 source
Add T7-496B source
Add T7-547A source
Add T6-623B source
Add T5-5133 source
Add T6-4F62 source
Add T7-297E source
Add T6-6349 source
Add T7-5D27 source
Add T6-3C64 source
Add T6-4F77 source
Add T5-6A34 source
Add T7-5071 source
Add T7-5965 source
Add T6-255D source
Add T4-4829 source
Add T5-6A48 source
Add T7-4B6B source
Add T7-5148 source
Add T6-3C75 source
Add T7-5A41 source
Add T7-5D61 source
Add T7-5D70 source
Add T5-4B63 source
Add T7-6331 source
Add T5-6F54 source
Add T7-2C35 source
Add T7-5B2D source
Add T7-3670 source
KXI index 0084.201
Add T4-2755 source
Add T6-4D7C source
V2-803D
Add T6-5064 source
Add T7-3F41 source
Add T6-6267 source
Change to T4-4757
Add T6-216D source
Add T7-2D52 Source
Add T6-5248 source
Add T6-3F5B source
Add T5-3946 source
Add T7-613D source
Add T7-5F6B source
Add T3-3F6D source
Add T7-6630 source
Add T6-3766 source2-69FB
2-6A102-34F52-9AC7

44328
44354
21667
64973

T4-6A6E

T7-544F
Add T4-6A6E source
Add J-source JPN092
Add T7-564E source

The following characters are missing in Extension B.
Glyph
Source information

Kangxi Index

TF-394A

0134.351

T6-29750157.041

T7-66330163.191

G-KX, T5-417B

0990.060

G-KX, T5-5731

0994.170

G-KX, T5-6D2B

0998.140

TF-2D2D

0980.141

T6-616F

1088.341

T6-25560083.011

TF-642C

1267.191

TF-5D2E

1316.111

Attachment 6 - Singapore
There are about 60 Singapore HanZi, some of them are frequently used in Singapore. However, noneof them have been encoded un CD 10646-2yet. It is very important to encode these Singapore Hanzi in
CD 10646-2 because of various reasons.

Attachment 7 - Sweden
Swedish Comments to CD 10646-2:
Our No vote can be turned to a Yes only if points SE2 and SE3 below are accepted.
SE 1.

[General] The CD for 10646-2 concerns three planes: plane 1, plane 2, and plane 14.
Plane 1 and plane 2 are planned to become almost filled. It is more logical to haveone part per plane, rather than having part 1 covering plane zero, and part 2 covering
more than one plane. Therefore we suggest that the current part 2 is split into part 2
for plane 1 and part 3 for plane 2 (regarding plane 14, see below).
Regarding plane 2 (supplementary ideographs plane), the content on this plane must
be approved by experts on East Asian ideographs for us to accept it.
Regarding Etruscan, Gothic, Deseret, Byzantine musical symbols and ‘western’musical symbols, experts on these scripts (or symbol sets, respectively) must approvethe content on these for us to accept them.

SE 2.

[All text and tables referring to plane 14; including annex D] The “language tag”
characters (a kind of control characters) in the “special purpose plane” must all be
removed. Encoding these as separate characters is highly objectionable. Language
tagging is not a plain text issue, and should not become one. Language tagging as
such has its place and is useful, but the plane 14 tag characters approach is highly
inappropriate. For a more detailed explanation on why these characters are
objectionable, and a possible alternative proposal, see document SC2/WG2 N 2169.

SE 3.

[pages 20-35 of the CD] The “Math Alphanumeric” preformatted letters/digits (in plane1) must be removed. Encoding these as separate characters is highly objectionable.
Preformatted letters (and digits) have not been needed for math before, and there isno need, nor any advantage, to introduce them now. For a more detailed explanation
on why these characters are objectionable, and a possible alternative solution for
MathML, see document SC2/WG2 N 2168.

SE 4.

For clarity, the plane indication should be given in each table heading.

SE 5.

For combining characters (preliminarily listed in Annex B), the way each of them
combines with preceding character(s) should be indicated by dotted circles in the‘typical’ glyph tables, just as in part 1.

SE 6.

For characters that don’t have a typical glyph, a dotted box should surround thedescriptive text for those characters in the glyph tables, just as in part 1. (This applies
in particular to some western musical symbols; see Annex E.)

SE 7.

GOTHIC LETTER HAGL looks very much like GOTHIC LETTER URUS. Should they
really be so similar glyphs?

SE 8.

Western musical note head names: It is not clear that a “NULL” note head is different
from a “VOID” note head, and these two names may be easily confused. Since there
is also a “BLACK” note head, maybe the “VOID” note head should be renamed to“WHITE-INNER” note head, or some such.

Filnamn: 10646-2CDComments.doc

SE 9.

The identity of the characters in plane 2 depend very much on the given sample
glyphs, since there are no supporting names, so these glyphs must be clear.
Occasionally, a bit smaller glyphs are used, or (apparent) bold/semibold. We suggest
using the same light actual font weight and the same large actual glyph size
consistently if possible.

SE 11.

In our printout for plane 2, some code points are not given any sample glyph, while thebox for the sample glyph is not grey-shaded (see in plane 2’s row 33, row 65, row 97,
and row A8). Is that just missing glyphs, or is it unused code positions? The sample
glyphs for 0002 9D32 and 0002 9E68 appear damaged.

SE 12.

Typo on page iv: 10646 will consist of “parts”, not just a “part”.

Filnamn: 10646-2CDComments.doc

Attachment 8 - UK
UK COMMENTS ACCOMPANYING VOTE OF APPROVAL ON CD 10646-2(JTC1/SC2 N 3393)
Technical comments on CD 10646-2
This CD should not proceed to the Final CD stage until Plane 01 is populated with a substantial number of
additional characters - it is at present less than 5% filled. A target of at least 10-15% fill would be more
appropriate, and would present a better “image” to users at the time of publication of the First Edition.

Editorial comments on CD 10646-2
1.

Clause 4, last para., line 3 should read "..represent characters from all planes specified ..."

2.

Clause 6, line 1: replace "shall be" by "is".
Justification: The use of "shall be" is not appropriate in a sentence describing facts about the arrangementof the standard. It should only be used for requirements on coded information interchange, or on devices, towhich conformance applies.

3.

Clause 6, para. 2, 1st sentence: similar comment to 2 above. The "shall not" is here merely an instruction
to WG2 not to do it, not a requirement on coded interchange !
2nd sentence: replace "slated" by "proposed" or "scheduled".

4.

Clause 7 & Clause 8: similar comment to 2 above.

5.

Clause 8: Add here the statement that defines positions 000E 0000 to 000E 0FFF as reserved for Alternate
format characters. At present this statement is proposed (on page 386) for Clause 8 of 10646-1, but it would
there be out of scope since the title of that clause is “The Basic Multilingual Plane”.

6.

Clause 9, Note: The term "unaware process" is not defined.

7.

Clause 10, Title: The title is completely wrong - the clause is not an "overview".
It should be as clause 26 of 10646-1, i.e. "Code tables and lists of character names".

8.

Clause 10.1, 2nd sentence: replace "the planes are" by "this plane is".

9.

Clause 10.2: This needs an extra first sentence stating what this clause is, e.g.:"Code tables for the block CJK UNIFIED IDEOGRAPHS EXTENSION B are shown on the following pages."
In para. 1, 2nd sentence, replace "source reference" by "source references".

10. Annex B.1: Although this Annex lists combining characters in the block WESTERN MUSICAL SYMBOLS,
the corresponding code tables do not show dotted circles for these characters, contrary to the statement in
24.2 of clause 24 of 10646-1 which is referred to at the start of the Annex. An statement is required toresolve this conflict, probably somewhere in clause 10.

11. Annex C, introductory paragraph: The last two sentences do not belong here, they already appear in Annex
F.
In the first sentence after "CJK Ideographs" add "in Plane 02".
12. Annex D. Para 1, line 2; replace "sequence" by "string" [for consistency].
Para 2, line 1: after "spell out" add "a character string in" [for accuracy].
D.3, line 3: the meaning of "text itself goes out of scope" is quite obscure, and should be amended.
Perhaps it means "the end of the cc-data-element is reached".
13. Page 386: [The SC2 Secretariat has instructed National Bodies to ignore this page during the CD ballot.
However the following comments are given here to assist the Project Editor.]a. The page heading, and all title information, should be deleted, and replaced by text such as the following.
EDITOR’S NOTE: The following items will be included in a future PDAM for ISO/IEC 10646-1.
b. Clause 8: See comment 5 above. Also Annex F of 10646-1 defining Alternate Format Characters
includes many that are not within any of the ranges listed here. This should be clarified.
c. Annex A.1: The change for collection 81 is superfluous, it is already included in 2nd Edition.
d. The new collection 208 is technically incorrect, as there are many other such characters outside therange quoted, see Annex F of 10646-1 2nd Edition. Maybe the collection name should be adjusted.

BSI
24/02/2000

Date: February 2, 2000

Title:

Comments accompanying the US positive vote on the CD ISO/IEC 10646-2

Source:Action:U.S.
Forward to JTC 1/SC 2

The US is voting YES on the Committee Draft ISO/IEC 10646-2 with the following comments:

Technical Comments:
Secondary Multilingual Plane for scripts and symbols: Western Musical Symbols
T.1 The list of combining characters as specified by the Annex B.1 is incorrect; it should be amended as follows(encoding within Plane 1): D110-D117, D11A-D120, D134-D135, D157-D15A.
Furthermore the chart pages should show a dotted circle as customary for these characters.
T.2 The Annex E (Usage of musical symbols) illustrates ‘equivalence’ between pre-composed note values andprimitives from which complete notes may be constructed. However these characters and sequences are notstrictly equivalent. We suggest replacing the last phrase of the first column by:‘Although these characters are not formally equivalent, in practice conforming devices may not want todistinguish among the following sequence pairs:’
The ‘=’ symbol used in the following lists should be replaced by a symbol reflecting a looser association than anequivalence. The character ‘˜ ’ is suggested.
Supplementary Plane for CJK Ideographs:
T.3 The CD should reflect the changes suggested in the IRG editors report following the 14th IRG meeting in
Singapore.
Collections
Annex A (page 368) or a possible Amendment to part 1
T.4 A new collection needs to be added to cover all planes from 0 to 16. The collection number, name andpositions (character range) are suggested as follows:
10646 UNICODE
0000 0000 - 0010 FFFFAs the collection spans many plane, it is suggested that the text should be added to the part 1 of the standard. As
the formal introduction of the part 2 within ISO/IEC 10646 will require a change in the first part of the standard,
it could be part of the necessary amendment.
Although the US understands that the text appearing at the very end of the CD ballot (page 386) looking like apart 1 amendment is not part of the CD ballot itself, it is nevertheless an informative document to be used as atemplate for the eventual amendment to part 1.
T.5 The clause A.1 contains a definition for CJK UNIFIED IDEOGRAPHS EXTENSION B specifying
characters from Part 1 (like 0FA0E, 0FA0F,…FA29). These characters should not be part of Extension B but
documented as being part of a larger collection including all CJK UNIFIED IDEOGRAPHS from all planes. The
intent is to make sure that these 10 ideographic characters are part of that collection. The US asks that thesecharacters be removed from collection 1006 and be added to a new collection in the amendment to part 1
specified above. Source information for these 10 characters should also be provided in the same amendment.

Editorial Comments:
Secondary Multilingual Plane for scripts and symbols: Western Musical Symbols
Clause 6 (page 2)

E.1 The end of the last sentence (the SMP cannot be used as a two-octet coded character set) is confusing, areference to UCS-2 should be used instead.
E.2 In the first sentence of the 2nd paragraph, replace ‘them’ by ‘CJK Ideographs’.
Clause 9 (page 3)
E.3 The note is unclear. Please clarify.
Annex E (page 383 and 384):
E.4 Remove the numbering in all lists in the Annex clauses E.2 and E.3.
Supplementary Plane for CJK Ideographs:
Clause 7 (page 3)
E.5 The end of the last sentence (the SIP cannot be used as a two-octet coded character set) is confusing, areference to UCS-2 should be used instead.
Clause 10.2 (page 36)
E.6 The clause is imprecise in many cases about the correlation between the sources as described in the first partand as described in the explanation of the text file source document. For example, it is unclear to which source
the Unique Hanzi abbreviated names (like G_4K, G_BK, etc.) refers to. The descriptive section (first part)should mention explicitly these abbreviated names in correlation with the full name (like G_CY for Ci Yuan).
E.7 The Hong Kong Hanzi source should be updated to reflect the new naming for the sources: Government
Common Character Set (GCCS) and Hong Kong Supplementary Character Set (HKSCS) instead of GCCS_1 and
GCCS_2.
E.8 Furthermore, the Hong Kong Hanzi source specifies two groups (GCCS) and Industry Collection. But thesource document only references Industry Collection (HA-, HB-, HC-). It should be made clear whether or not
the GCCS and HSCS collections are fully contained within the Industry Collection.
E.9 The Kanji source should explicitly refer to the newly adopted JIS-x-213, as it is now known as the official
source for these characters.
E.10 The second Editor’s note can be addressed by developing the explanation of the plain text file. The
explanation basis should be based on the following: The Kangxi Dictionary is really used for two purposes: true
entries using the ‘dddd.dd0’ notation (‘dddd’ is the page number, and ‘dd’ is the order within the page indecimal notation), and duplicates noted as ‘dddd.dd1’. The duplicates are ordered within the single ‘dddd.dd1’
entry as determined by the IRG committee. That internal order bears no significance.
End of US comments