ISO/IEC JTC 1/SC 2 N 3641- WG2 N 2520
DATE: 2002-11-15

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 ISO/IEC JTC 1/SC 2 N 3624, ISO/IEC 10646-1:
2000/FPDAM 2, Information technology -- Universal Multiple-Octet
Coded Character Set (UCS) -- Part 1: Architecture and Basic Multilingual
Plane AMENDMENT 2: Limbu, Tai Le, Yijing and other characters

SOURCESC 2 Secretariat

PROJECT

JTC 1.02.18.01.02.00.02

STATUSThis document is forwarded to WG 2 for consideration. WG 2 is requested
to prepare a dispostion of comments report, revised text and arecommendation for further processing.

ACTION ID

FYIDUE DATE
DISTRIBUTION

P, O and L Members of ISO/IEC JTC 1/SC 2 ; ISO/IEC JTC 1 Secretariat;
ISO/IEC ITTFACCESS LEVEL Def
ISSUE NO.

FILE

NAME
SIZE(KB)
PAGES

15102n3641.pdf
10Secretariat ISO/IEC JTC 1/SC 2 - IPSJ/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 1050011 Japan *Standard Organization Accredited by JISC
Telephone: +81-3-3431-2808; Facsimile: +81-3-3431-6493; E-mail: kimura@itscj.ipsj.or.jp

Summary of Voting on
ISO/IEC JTC 1/SC 2 N 3624 :ISO/IEC 10646-1: 2000/FPDAM 2, Information technology -- Universal Multiple-Octet
Coded Character Set (UCS) -- Part 1: Architecture and Basic Multilingual Plane
AMENDMENT 2: Limbu, Tai Le, Yijing and other characters
Q1 : FPDAM Consideration
Q1
Not yetComments
voted
Reasons
Approve Disapprove
Abstention
P-Member
Armenia
X
AustriaX
BelgiumXCanadaX*Attachment 1
ChinaXDenmark
X
Egypt
X
FinlandX
FranceX
Germany
X
GreeceX
IcelandX
India
X
Iran, Islamic Republic ofX#
Attachment 2
IrelandX#
Attachment 3
Israel
X
Italy
X
Japan
X
Korea, Democratic People's
X
Republic
Korea, Republic ofX#
Attachment 4
Mongolia
X
MoroccoX
Netherlands
X
NorwayX
PolandX
Romania
X
Russian Federation
X
Singapore
X
Slovenia
X
SwedenX
ThailandX
Tunisia
X
TurkeyX
USA
X
Attachment 5
Yugoslavia
X
Total (35)94517*: Approve with comments#: Acceptance of the reasons and appropriate changes in the text will change the vote to approval.

Netherlands
No expertise available
NorwayNo expertise in this area.

Attachement 1

Recommended response from CAC SC2:======================================
Accept with following editorial comments:
a. Page 1: Italicized 'change xxx by xxx' under Page 13 items.. does notread right..
Please change to 'replace xxx with xxx'etc.
b.

Page 3, new entries for collections:

104 and 105 have both LTR ALPHABETIC PRESENTATION FORMS. One of these (wethink it is 105) must be RTL ALPHABETIC PRESENTATION FORMS.
============
Regards....Roz
Roz Waddell
Standards Council of Canadarwaddell@scc.ca

Attachment 2

Title:
Source:Action:Comments accompanying Iran’s negative vote on theFPDAM 2 to ISO/IEC 10646-1:2000
ISIRI (Institute of Standards & Industrial Research of Iran)To be considered by JTC 1/SC 2/WG 2

Iran votes NO on FPDAM 2 to ISO/IEC 10646-1:2000, disapproving the draft in its current form.
The negative vote will cease if the following comments get accepted and incorporated in the text,
changing Iran’s vote to YES.
In the following text, the P+ABCD notation is used to refer to character proposed to be encodedat the position ABCD.

Technical
T1. Pages 18 and 19: Iran requests the names (or the glyphs) for the proposed characters P+060Dand P+060E be interchanged, as the current names are clearly wrong. Iran also requests a
review of other characters names and shapes which are new to the Arabic block be done by theeditors, to make sure there is no other such error.
T2. Pages 18 and 19: Iran requests that the character P+0659 be moved to the position 0615, since
it’s a combining character that, unlike the other characters in the range U+064B to U+0655,
but like the characters P+0610 to P+0614, applies to the whole word (or a word ending), andnot to a single letter. This will help consistency in the new characters proposed to be encodedin the Arabic block.
T3. Pages 18 and 19: Iran requests the character P+0603 to be moved to the position 060B, orsome other position in the range 061C to 061E, to help group the characters with similiar
functionality near each other.
T4. Page 75: Iran requests the character P+FDFD to be renamed to have a name more consistent
with the other characters in the range U+FDF0 to U+FDFB. As current transliterations done forthe names of those characters recommend the letter E for Arabic Kasra, and since the vowels
connecting the words are also Kasra (and not Fatha), the name for the new character should
be changed to ‘ARABIC LIGATURE BESMELLAH ERRAHMAN ERRAHIM’ or ‘ARABIC
LIGATURE BESMELLAHERRAHMANERRAHIM’.

Editorial
E1. Pages 18 and 20: Iran requests the glyphs for the following proposed characters be revised tobe consistent with the rest of the Arabic block:P+0656 The representative glyph should be similiar in shape and size to U+0670 ARABICLETTER SUPERSCRIPT ALEF. The Alef-shaped part of the glyph is currently muchlarger.
P+0657 The representative glyph should be similiar in shape and size to U+064F ARABICDAMMA. It is currently smaller and comma-shaped instead of being Damma-shaped.
P+0659 The representative glyph should change to Naskhi style which is the style of all othercharacters in the Arabic block. The current glyph is in Nastaliq style. See also T2.
P+06EE, P+06EF, and P+06FF The representative glyphs should become larger in size (compare P+06EE with U+062F, for example) and have their “Inverted V” part consistent withthe glyph for U+06C9.

1

Attachment
Subject: Irish vote on SC2 N3624 (ISO-IEC 10646-1:2000/FPDAM 2)
Importance: HighSC 2 N 3624:
ISO/IEC 10646-1: 2000/FPDAM 2, Information technology -- Universal
Multiple-Octet Coded Character Set (UCS) -- Part 1: Architecture andBasic Multilingual Plane AMENDMENT 2: Limbu, Tai Le, Yijing and othercharacters[Closing date: 2002-11-09]
Ireland DISAPPROVES the draft with the technical and editorialcomments given below. Acceptance of these comments and appropriatechanges in the text will change our vote to approval.
10646-1 FPDAM2
Technical Comments:
T.1 Change the character name for U+0658 to ARABIC MARK NOON GHUNNA-- note that it should not be "NOON-GHUNNA" as was seen in someearlier documentation.
T.2 In the note to be added at clause 25.3, it should say "When thenormalization forms are applied" not "When the normalizations forms
are applied"
T.3. Change the character name for U+FDFD to ARABIC LIGATURE
BISMILLAH AL-RAHMAN AL-RAHIM. This transliteration better shows theunderlying text, where the transcription ARRAHMAN ARRAHIM hides it
due to the assimilation of the article as written.
Editorial Comments:
E.1 The glyph for the hot beverage at U+2615 should be changed to one
which is more conventional.
-Michael Everson * * Everson Typography * * http://www.evertype.com

3

Attachment 4

Subject: Letter Ballot on SC2 N 3624 (ISO/IEC 10646-1:2000/FPDAM2)
Date: 2002-11-08
NB: KATS
1. We vote "no" due to the following two reasons.
2. reason 1
We used ISO TS 11941:1996 for naming Korean Hangul letters and syllables.
However, the transliteration used for naming the following characters in PDAM2 isdifferent from TS 11941.
[p. 63, Table 104]
U+0321D OJEON
U+0321E OHU
U+0327C CHAMKO
U+0327D JUEUIConsidering that, in the future, we may add more Korean Hangul letters in addition tothe above characters, we suggest that we set up a transliteration rule for naming Korean
Hangul letters and syllables and adhere to that rule.
3. reason 2
Normalization forms for Hangeul letters/syllables are not appropriate for handlingHangeul properly.
[on page 1] Page 2, clause 3 Normative references
Add the following reference:
Unicode Standard Annex, UAX#15, Unicode
Normalization Forms, Version 3.2.0, 2002-03-27. ...
[on page 2]
Page 13, after clause 23 Order of characters
Insert a new clause 24 between the current clause
23 and 24 (the following clauses are incremented byone):
24 Normalization forms
Normalization forms are the mechanisms allowing
the selection of a unique coded representation
among alternative, but equivalent coded text repre-sentationsof the same text. Normalization forms foruse with ISO/IEC 10646 are specified in the UnicodeStandard UAX#15. ...

Attachment 5

INCITS/L2/02- 408

Date: November 7, 2002

Title:
Source:Action:Comments accompanying the US negative vote on the FPDAM2 toISO/IEC 10646-1:2000
INCITS/L2
Forward to INCITSThe US National body is voting NO on the FPDAM2 to ISO/IEC 10646-1:2000. It will change its vote to YES if
the technical comment T.8 is accepted.

Technical Comments:
T.1 Normative ReferencesUpdate the reference to the Unicode Bidirectional Algorithm to version 3.2
T.2 Greek
Add the following characters:
GREEK CAPITAL LUNATE SIGMA (proposed code position: 03F9) as documented by INCITS L2 02/314R,
GREEK CAPITAL LETTER SAN (proposed code position: 03FA) as documented by INCITS L2/313R,
GREKK SMALL LETTER SAN (proposed code position: 03FB) as documented by INCITS L2/313R
T.3 Arabic
Change the character name for U+0658 to ARABIC MARK NOON GHUNNA
T.4 Symbols
Add the character VERTICAL LINE EXTENSION (proposed code position: 23D0) as documented by WG2
N2508. The character addition would complement the existing HORIZONTAL LINE EXTENSION at codeposition 23AF.
T.5 Annex A.1 Collections of coded graphic charactersa) Change the entry 105 to read:
105 RTL ALPHABETIC PRESENTATION FORMSb) The code range for collection 110 should read 2B00-2B7F.
c) To complete the change for collection 63, the first entry for collection 63 in annex A.1 (between 62 and 64)
should read:63 (Collection specified as union of other collections)d) Collection 251 SCRIPT-SPECIFIC FORMAT CHARACTERS should not contain the collection 207e) After the collection 381, a new collection should be added as follows:
382 CJK COMPATIBILITY IDEOGRAPHS-2003 * described as Collection 381 with the addition of U+FA70FAE9. This is only required if the addition of the range FA70-FAE9 is maintained in this proposed amendment.
Note that the US is asking for its removal in comment T8.
f) In the alphabetically list in Note 3, add collections 98 and 99 to the ‘Arrows’ entry and 380, 381, 382 (asappropriate, see above) to the ‘Ideographs’ entry.

T.6 Annex A.2 Block listsModify the code position range for MISCELLANEOUS SYMBOLS AND ARROWS to 2B00-2B7F
T.7 Annex Q and R
In the context of merging the two parts of ISO 10646, the US is asking for an overhaul of Annex Q and R of Part
1 by making the code mapping for Hangul Syllables (Annex Q) and the Names of Hangul Syllables (Annex R)
available as separate text files. This will make the information much more usable.
T.8 DPRK Compatibility characters
The US asks for removal of characters from FA70 to FAE9.
Rationale:
The US has found many discrepancies in the list of characters (incorrect mapping). For example, the reference
mapping for characters FA9D to FAE9 is shifted by one position, leaving the proposed code position FA9D
without reference mapping to a CJK Unified character. Some characters like FA8C and FA90 and many others
seem to have incorrect mappings. Furthermore, it looks like not enough research has been done to look forexisting variants in the CJK repertoire that could have been used for encoding the KP1 characters. Given theseissues, the US does not see these proposed additions as mature enough for encoding and is therefore asking fortheir removal pending further study.
T.9 Syriac
Change the glyph for 070F SYRIAC ABBREVIATION MARK to include a default rendering in addition to thecurrent picture, suggested new glyph:

SAM
T.10 Annex F, Soft Hyphen format character
The SOFT HYPHEN entry in clause F.1.1 should be reworded as follows:
SOFT HYPHEN (00AD): SOFT HYPHEN (SHY) is a format character that indicates a preferred intra-wordline-break opportunity. If the line is broken at that point, then whatever mechanism is appropriate for intraword line-breaks should be invoked, just as if the line break had been triggered by another mechanism, suchas a dictionary lookup. Depending on the language and the word, that may produce different visible results,
such as:•inserting a graphic symbol indicating the hyphenation and breaking the line after it,•
inserting a graphic symbol indicating the hyphenation, breaking the line after the symbol and changing
spelling in the divided word parts,•
not showing any visible change and simply breaking the line at that point.
The inserted graphic symbol, if any, can be take a wide variety of shapes, such as HYPHEN (2010),
ARMENIAN HYPHEN (058A), MONGOLIAN TODO SOFT HYPHEN (1806), as appropriate for the situation.
When encoding text that includes explicit line breaking opportunities, including actual hyphenations,characters such as HYPHEN, ARMENIAN HYPHEN, and MONGOLIAN TODO SOFT HYPHEN may beused, depending on the language.
When a SOFT HYPHEN is used to represent a possible hyphenation point, the spelling is that of the word
without hyphenation (for example: "tug<00AD>gumi"). When encoding text that includes hard line breaks,
including actual hyphenations, the spelling must reflect the changes due to hyphenation (for example:"tugg<2010>" / "gumi").

Editorial Comments:
E.1 Clause 25.3 Alternate coded representations
In the 6th line add a ‘s’ at the word ‘representation’ (after multiple).
E.2 Clause 27 CJK Unified Ideographs
Add a mention that the clause number is now 28 (following the insertion of clause 24).
---End of US comments