ISO/IEC JTC/1 SC/2 WG/2 N2095
1999-09-08

ISO/IEC JTC/1 SC/2 WG/2
Universal Multiple-Octet Coded Character Set (UCS)
Secretariat: ANSI

Title: Addition of CJK ideographs which are already “unified”
Doc. Type: National Body contribution
Source:Japan, (JSC2, JCS, )Project:

UCS

Status:For Information

tksandFor initiation of a discussion at #37/38 meetingDate:

1990-09-08

Distribution: SC/2 WG/2
Reference:

Annex T (CJK unification rule)

Medium:Attached please find a addition requirement of CJK ideographs.

National body of Japan for the SC2 is forwarding this for an information.

The originator of the requirement is new coded character JIS development team.
The CJK ideographs in the requirement are ideographs which are already unified withexisting UCS ideographs per unification rule in annex T. Thus, in principle of the UCS,
those ideographs should not be requested for addition to the 10646.

However, the practical world (in some of legal application in Japan) need to recognize thoseideographs as a separated ideograph from the ideographs which are already shown in
10646 as sample glyph shape.

One of possible reaction on this requirement is rejection. Those ideographs are out of10646 principle. In this case, 10646 should give up “round trip conversion with JIS”, andfurther more, 10646 may loose a marketability in Japan.

12nd idea of the solution is to make them as a compatibility characters (with JIS), This quick
and easy solution may invite other issues.
1.

The origin of those ideographs (new JIS) is aiming a limited application, when extendinga scope of application, there will be more of the same kind of requirement may appearin Japan.

2.

Can we keep adding the compatibility characters

This is not only a matter of Japanese unique, it is common thing through out
ideographic region. Taiwan and Hong Kong are already indicating the same kind ofrequirements at IRG.

3.

Then, question is “do we want to unify them?”. May be some countries say “thoseshould not be separated for my market”.

4.

Then, will those be a country (or origin) dependent compatibility ideographs?

5.

May be, more issues to come3rd choice would be a revision of the “unification rule”, but it is not clear whether if it ispossible or not.
The 4th would be to give up the CJK unification.

Since Taiwan already presented the same kind of requirement in the last IRG (with muchlarger number of characters), Discussion about this issue is on the agenda of next IRG,
But Japan believes that this might not be a limited issue within IRG, it might be a muchbroader 10646 principle issue.

Thus, before the IRG discussion, it would be better to let

the issue known to wider members of the WG2 and give as much as possible input to IRG.

------end----attachment:2

1999-08-23

Universal Multiple-Octet Coded Character Set
International Organization for StandardizationDoc Type: Working Group Document
Title:
Source:Addition of fifty six KANJIs for compatibility
JCS committee, JSA

Status:Date:

Working Document
1999-08-23

This document proposes fifty six (56) KANJIs defined in the final draft Japanese Industrial Standard, JIS X0213, anddiscusses the rationale for their inclusion.
The new Japanese Industrial Standard for a coded character set, JIS X0213, is being developed in Japan, and will be
published by the end of this year. The new standard will include all characters in this proposal, so the adoption of them iscrucial in the view to keep upward compatibility with the Japanese products.
The proposed KANJI characters are defined and described in the Japanese legal directives for compilation of family
registers, and every public office of Japan is under obligation to treat these characters distinctly in compiling registers.
The characters proposed here have been under unification in the existing coded character sets such as JIS X0208, ISO
10646-1, and will be newly dis-unified under the new standard JIS X0213, which makes it appropriate to treat them asCJK COMPATIBILITY IDEOGRAPHS.
The characters proposed to be added here are given below, with proposed code positions, The proposal summary form
is appended thereafter.

FA30(CJK COMPATIBILITY IDEOGRAPH-FA30)

FA3B(CJK COMPATIBILITY IDEOGRAPH-FA3B)

FA31(CJK COMPATIBILITY IDEOGRAPH-FA31)FA3C(CJK COMPATIBILITY IDEOGRAPH-FA3C)

FA32(CJK COMPATIBILITY IDEOGRAPH-FA32)

FA3D(CJK COMPATIBILITY IDEOGRAPH-FA3D)

FA33(CJK COMPATIBILITY IDEOGRAPH-FA33)

FA3E(CJK COMPATIBILITY IDEOGRAPH-FA3E)

FA34(CJK COMPATIBILITY IDEOGRAPH-FA34)

FA3F(CJK COMPATIBILITY IDEOGRAPH-FA3F)

FA35(CJK COMPATIBILITY IDEOGRAPH-FA35)

FA40(CJK COMPATIBILITY IDEOGRAPH-FA40)

FA36(CJK COMPATIBILITY IDEOGRAPH-FA36)

FA41(CJK COMPATIBILITY IDEOGRAPH-FA41)

FA37(CJK COMPATIBILITY IDEOGRAPH-FA37)

FA42(CJK COMPATIBILITY IDEOGRAPH-FA42)FA38(CJK COMPATIBILITY IDEOGRAPH-FA38)FA43(CJK COMPATIBILITY IDEOGRAPH-FA43)

FA39(CJK COMPATIBILITY IDEOGRAPH-FA39)FA44(CJK COMPATIBILITY IDEOGRAPH-FA44)

FA3A(CJK COMPATIBILITY IDEOGRAPH-FA3A)

FA45(CJK COMPATIBILITY IDEOGRAPH-FA45)

1FA46(CJK COMPATIBILITY IDEOGRAPH-FA46)

FA57(CJK COMPATIBILITY IDEOGRAPH-FA57)

FA47(CJK COMPATIBILITY IDEOGRAPH-FA47)

FA58(CJK COMPATIBILITY IDEOGRAPH-FA58)

FA48(CJK COMPATIBILITY IDEOGRAPH-FA48)

FA59(CJK COMPATIBILITY IDEOGRAPH-FA59)

FA49(CJK COMPATIBILITY IDEOGRAPH-FA49)

FA5A(CJK COMPATIBILITY IDEOGRAPH-FA5A)

FA4A(CJK COMPATIBILITY IDEOGRAPH-FA4A)

FA5B(CJK COMPATIBILITY IDEOGRAPH-FA5B)

FA4B(CJK COMPATIBILITY IDEOGRAPH-FA4B)

FA5C(CJK COMPATIBILITY IDEOGRAPH-FA5C)

FA4C(CJK COMPATIBILITY IDEOGRAPH-FA4C)

FA5D(CJK COMPATIBILITY IDEOGRAPH-FA5D)

FA4D(CJK COMPATIBILITY IDEOGRAPH-FA4D)

FA5E(CJK COMPATIBILITY IDEOGRAPH-FA5E)

FA4E(CJK COMPATIBILITY IDEOGRAPH-FA4E)

FA5F(CJK COMPATIBILITY IDEOGRAPH-FA5F)

FA4F(CJK COMPATIBILITY IDEOGRAPH-FA4F)

FA60(CJK COMPATIBILITY IDEOGRAPH-FA60)

FA50(CJK COMPATIBILITY IDEOGRAPH-FA50)

FA61(CJK COMPATIBILITY IDEOGRAPH-FA61)

FA51(CJK COMPATIBILITY IDEOGRAPH-FA51)

FA62(CJK COMPATIBILITY IDEOGRAPH-FA62)

FA52(CJK COMPATIBILITY IDEOGRAPH-FA52)

FA63(CJK COMPATIBILITY IDEOGRAPH-FA63)

FA53(CJK COMPATIBILITY IDEOGRAPH-FA53)

FA64(CJK COMPATIBILITY IDEOGRAPH-FA64)

FA54(CJK COMPATIBILITY IDEOGRAPH-FA54)

FA65(CJK COMPATIBILITY IDEOGRAPH-FA65)

FA55(CJK COMPATIBILITY IDEOGRAPH-FA55)

FA66(CJK COMPATIBILITY IDEOGRAPH-FA66)

FA56(CJK COMPATIBILITY IDEOGRAPH-FA56)

FA67(CJK COMPATIBILITY IDEOGRAPH-FA67)

2

A. Administrative
1. Title
Addition of fifty six KANJIs for compatibility
2. Requester’s name
JCS Committee, JSA
3. Requester type (Member body/Liaison/Individual contribution)
Individual contribution
4. Submission date1999-08-23
5. Requester’s reference (if applicable)
the final draft Japanese Industrial Standard, JIS X0213
6. This is a complete proposal
Yes

B. Technical - General
1a. This proposal is for a new script ? Name ?
No.
1b. The proposal is for addition of characters(s) to an existing block? Name?
Yes.
CJK COMPATIBILITY IDEOGRAPHS
2. Number of characters in proposal
56
3. Proposed categoryA
4. Proposed level of implementation and rationale
1Is a rationale provided for the choice ?
Yes
If Yes, reference:
Enclosed
5. Is a repertoire including character names provided ?
Yes
5a. Are the names in accordance with the ‘character naming guidelines’ in Annex K of ISO/IEC 10646-1 ?
Yes
5b. Are the character shapes attached in a review-able form ?
Yes
6. Who will provide the appropriate computerized font for publishing the standard ?
JCS Committee, JSA
If available now, identify source(s) for the font and indicate the tools used.
396 dots bitmap
7a. Are references (to other character sets, dictionaries, descriptive texts, etc.) provided ?
Yes
7b. Are published examples (such as samples from newspapers, magazines, or other sources) of use of
proposed characters attached ?
Yes
8. Does the proposal address other aspects of character data processing (if applicable) such as input,presentation, sorting searching, indexing, transliteration etc ?
Specification enclosed

C. Technical - Justification
1. Has this proposal for addition of character(s) been submitted before ?
No
2. Has contact been made to members of the user community ?
Yes
If yes, with whom ?
JCS committee, JSA.
If yes, available relevant documents?
the final draft JIS X0213
3. Information on the user community for the proposed characters is included ?
Yes
Reference
JCS committee, JSA.
4. The context of use for the proposed characters
Common5. Are the proposed characters in current use by the user community?
Yes
If yes, where ? Reference
Enclosed
6. After giving due considerations to the principles in “Principles and Procedures” documents must theproposed characters be entirely in the BMP ?
Yes
If Yes, is a rationale provided ?
Yes
If Yes, Reference
Enclosed
7. Should the proposed characters be kept together in a contiguous range (rather than being scattered) ?
Yes
8. Can any of the proposed characters be considered a presentation form of an existing character orcharacter sequence ?
4No
9. Can any of the proposed characters(s) be considered to be similar (in appearance or function) to an
existing character ?
No
10. Does the proposal include use of combining characters and/or use of composite sequences ?
No
11. Does the proposal contain characters with any special properties such as control function or similar
semantics ?
No

D. SC2/WG2 Administrative
To be completed by SC2/WG2
1. Relevant SC2/WG2 document numbers:

2. Status (list of meeting number and corresponding action or disposition

3. Additional contact to user communities, liaison organizations etc.

4. Assigned category and assigned priority/time frame

Other Comments5.