L2/00-125

ISO/IEC JTC 1/SC 2 N 3421

DATE: 2000-03-24


 

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 JTC 1 N 5999, Proposal for a New Work Item, Amendment to the part concerning Korean characters in ISO/IEC 10646-1:1993 (JTC 1 N 6106)
 

SOURCE:

Secretariat, ISO/IEC JTC 1 
 

PROJECT:

 

STATUS:

This proposal has failed to meet the criteria for acceptance into the JTC 1 Programme of Work. 
 

ACTION ID:

FYI
 

DUE DATE:


 

DISTRIBUTION:

P, O and L Members of ISO/IEC JTC 1/SC 2
WG Conveners, Secretariats
ISO/IEC JTC 1 Secretariat
ISO/IEC ITTF
 

NO. OF PAGES:

15

ACCESS LEVEL:

Defined

WEB ISSUE #:

081

Secretariat ISO/IEC JTC 1/SC 2 - Toshiko KIMURA
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 105 JAPAN
Tel: +81 3 3431 2808; Fax: +81 3 3431 6493; E-mail: kimura@itscj.ipsj.or.jp; http://www.dkuug.dk/jtc1/sc2
*A Standard Organization accredited by JISC
 



JTC 1 Reports

Votes on a Ballot

Committee : 

JTC 1 - Information Technology

Ballot Number : 

JTC 1 N5999

Ballot Title : 

Proposal for a New Work Item, Amendment to the part concerning Korean characters in ISO/IEC 10646-1:1993

Source:

JTC 1 Secretariat

Distribution:

JTC 1 P-members

Related SC

SC 2

 

Questions for this Ballot

 

Do you accept the proposal in document JTC 1 N 5999 as a sufficient definition of the new work item?

Answers

Votes

 

Not Yet Voted

 

YES

10 

 

NO

 

ABSTAIN

Do you support the addition of the work item to the programme of work of the joint technical committee?

Answers

Votes

 

Not Yet Voted

 

YES

10 

 

NO

 

ABSTAIN

Do you commit yourself to participate the development of this new work item?

Answers

Votes

 

Not Yet Voted

 

YES

 

NO

15 

 

ABSTAIN

Are you able to offer a project editor who will dedicate his/her efforts to the advancement and maintenance of this project? (If "YES," please identify)

Answers

Votes

 

Not Yet Voted

 

YES

 

NO

18 

 

ABSTAIN

Do you have a major contribution or a reference document ready for submittal?

Answers

Votes

 

Not Yet Voted

 

YES

 

NO

17 

 

ABSTAIN

Will you have such a contribution in ninety days?

Answers

Votes

 

Not Yet Voted

 

YES

 

NO

16 

 

ABSTAIN

 

Organization

Q.1

Q.2

Q.3

Q.4

Q.5

Q.6

Comment

Australia

YES

YES

NO

NO

NO

ABST.

 

Austria

ABST.

ABST.

ABST.

Not Yet Voted

Not Yet Voted

Not Yet Voted

 

Belgium

YES

YES

NO

NO

NO

NO

 

Brazil

YES

YES

NO

NO

NO

NO

 

Canada

NO

NO

NO

NO

NO

NO

Canada does not support this NWI and instead suggests to DPR of Korea to follow the steps in the resolution from WG2 quoted below:
 

M37.12 (Feedback to D.P.R of Korea): With reference to the NP in document SC2/WG2N2056 (?) to amend the Korean encoding of Amendment 5, WG 2 instructs its convener to inform SC 2 to respond to the Committee for Standardization of the D.P.R. of Korea:
- that WG 2 cannot support this NP because any reordering of the standardized Korean Hangul characters would harm existing implementations that are using the standard including its Amendment 5
- that existing standardized character names cannot be changed because character names are normative in the standard and changing them would harm existing users of these standardized character names 
- invite them to make concrete proposals to add any missing characters following the existing WG 2 Procedures and Guidelines document (JTC 1/SC 2/WG 2 N2002), and the conventions for naming of characters in the standard, for future consideration by WG 2, and,
- invite them to participate in the IRG regarding any Hanja character requirements they may have, and, draw their attention to FCD-3 of ISO/IEC 14651 -- international ordering under ballot in SC 22.

Canada should supports the above position / decision made by SC2/WG2. Unicode standard 2.0 and soon to be published 3.0
-- is kept in synch from characters and their allocated positions. 10646 (Unicode) have been widely implemented in many systems -- including MS Windows NT, Windows 2000, Java etc. Any changes to code position allocations would be very harmful to the users of these systems / standard. Also, ordering / sorting of characters is not a primary concern of SC2 but that of JTC1/SC22/WG20 (DIS 14651 under development) and is independent of the coding of characters in any standard.

China

YES

YES

YES

NO

NO

NO

 

Denmark

YES

YES

NO

NO

NO

NO

 

Egypt

Not Yet Voted

Not Yet Voted

Not Yet Voted

Not Yet Voted

Not Yet Voted

Not Yet Voted

 

Finland

NO

NO

NO

NO

NO

NO

Finland/SFS cannot accept this NWI because we already participated on the approval of the resolution M37.12 of SC2/WG2 Copenhagen meeting. (JTC1/SC2/WG2 N 2104r)

France

ABSTAIN

Not Yet Voted

Not Yet Voted

Not Yet Voted

Not Yet Voted

Not Yet Voted

 

Germany

Not Yet Voted

Not Yet Voted

Not Yet Voted

Not Yet Voted

Not Yet Voted

Not Yet Voted

 

Hungary

YES

YES

NO

NO

NO

NO

 

Ireland

NO

NO

NO

NO

NO

NO

Comments sent separately by e.mail.

Italy

ABSTAIN

ABSTAIN

ABSTAIN

ABSTAIN

ABSTAIN

ABSTAIN

 

Japan

YES

YES

NO

NO

NO

NO

The national body of Japan notes that the most of the proposals in the NP are "incompatible changes in the ISO/IEC 10646" or "out of principle of the ISO/IEC 10646". Those proposals should not be accepted by the SC2 even if the NP itself is passed.

However, the national body of Japan also recognized that following proposals might include meaningful characters to be added onto the ISO/IEC 10646 (yes, there are many which can not be included into the ISO/IEC 10646 in them). Thus the following requirement should be reviewed by SC2 WG2:

- addition of Korean combining characters
- addition of special symbolic characters
- Korean Hanja (some may be CJK unified ideographs, and some may be CJK compatibility ideographs)

The most of the incompatible change requests are typical "correction requests for cultural correctness" which the WG2 has received too many times, someone should explain to D.P.R.K why the requests are not accommodated by the ISO/IEC 10646.

Netherlands

YES

YES

ABSTAIN

NO

NO

NO

 

New Zealand

NO

NO

NO

NO

NO

NO

The feedback provided to DPR of Korea by JTC1/SC2/WG2 in its document N210r, resolution M37.12 details the reasons why the NWIP is not acceptable in its present form.

Norway

NO

NO

NO

NO

NO

NO

The proposed characters are already coded in 10646

Republic of Korea

NO

NO

NO

NO

YES

YES

Republic of Korea disapprove on JTC1N5999 document with the same reasons as presented in Resolution M37.12(Feedback to D.P.R of Korea) determined in the JTC1/SC2/WG2 meeting 37 held in Copenhagen, Denmark from 13 to 16 September, 1999.

Romania

Not Yet Voted

Not Yet Voted

Not Yet Voted

Not Yet Voted

Not Yet Voted

Not Yet Voted

 

Slovenia

YES

YES

NO

NO

NO

NO

 

South Africa

Not Yet Voted

Not Yet Voted

Not Yet Voted

Not Yet Voted

Not Yet Voted

Not Yet Voted

 

Sweden

NO

NO

NO

NO

NO

NO

Sweden votes NO to the 10646-1 New Work Item Proposal (NP) in JTC1 N 5999, and objects to most of the points in the NP. Some of the suggestions 
can be accomodated within the present Program of Work for WG 2. An expert contribution has been sent to WG 2 about these items (see SC 2/WG 2 
N 2167). 

Clause 1 
The Hangul characters have already assigned code points, and these code point assignments are being used in more and more implementations. It is much too late to change them now. Only new code points for missing characters may be allocated. 

Clause 2 
Unicode technical report 10 and ISO/IEC DIS 14651 specifies methods for tailoring of the ordering of Hangul Jamo and Hangul syllables (as well as any other characters). 

Clause 3 
Part of  Annex B appears to suggest a rearrangement of the Hangul Compatibility Jamo (U+3130-U+318F) code points. These have been allocated in 10646 since many years. It is unacceptable to change the code points now. Again see UTR 10 and ISO/IEC DIS 14651 on how to tailor 
their ordering. 

Clause 4 
Adding cross references to KPS 9566-97 in 10646 itself is not needed, and not helpful. A machine readable mapping table, however, would be helpful. 

Clause 5 
Character name changes for already assigned characters cannot be accepted, since the names in 10646 itself are normative and already in use by implementations.

Switzerland

ABSTAIN

ABSTAIN

ABSTAIN

ABSTAIN

ABSTAIN

ABSTAIN

Switzerland has no interest.

United Kingdom

YES

YES

YES

NO

NO

NO

(See Attached File)
UK vote on question 2 is conditional upon the  comments in the attached file (00640669.PDF) being addressed. 
UK comments

USA

NO

NO

NO

NO

NO

NO

Q. 1. See document L2/99-382