L2/01-376

DATE:  2001-10-6

 

DOC TYPE:	National Body Contribution
TITLE:	Guideline to correct fatal error on UCS
SOURCE:	Japan T. L. Kobayashi
PROJECT:	JTC 1.02.18 – ISO/IEC 10646
STATUS:	Input to proposed AMD1 – 10646-1:2000
ACTION ID:	For review by WG2
DUE DATE:	2001-01-31
DISTRIBUTION:	SC2/WG2 members and Liaison organizations
MEDIUM:	Electronic
NO. OF PAGES:	2

 

This contribution paper proposes some guideline for the correctionprocedure of fatal errors found in ISO/IEC 10646 especially in CJKUnified Ideographs part. And also this contribution paper proposes somerecommendation/request to maintain mapping information between ISO/IEC10646 and several domestic/private coded character sets.

Related documents and action item are as follows.

N2271: Propose to amend two source code changes in BMP CJK Unified Ideographs block (TCA)

N2294: Feedback from Japan on N2271 – Proposal by TCA to amend two source code changes in BMP CJK Unified Ideographs block (Japan)

AI-39-9b: To examine the proposal in document N2271 -- Proposal to amend two source code changes in BMP CJK Unified Ideographs block; TCA; 2000-09-19 – and advise WG2 on a possible corrigendum to 10646-1 for the T-Column entries in the CJK tables.

 

Principles:

*Code position and printed shape of ISO/IEC 10646 should not be changeddefinitely in principle.

*If there found fatal error, it should be changed as earlier as possibleto minimize confusion and loss.

 

Consideration of impact on standard itself and implementation:

*Arbitrary and shortsighted change may make some inconsistency instandard itself.

*Arbitrary and shortsighted change may make some confusion and loss foralready implemented systems and products.

*Especially, if correction of error causes some change on mappinginformation between ISO/IEC 10646 and existing domestic/private codedcharacter sets, best effort to avoid change of mapping information shouldbe done.

 

Guideline for correction of fatal error:

*Change of code position should not be done definitely. If needed, new code position assignment is preferable.

*Change of printed shape of character, which causes mapping information between

ISO/IEC 10646 and existing domestic/private coded character sets, should

be minimized.

*If change of shape of character is inevitable, information of change should

be widely announced as earlier as possible.

*Also history of changes should be kept consistent and widely open.

 

Note:

*Primarily owners of mapping information between ISO/IEC 10646 and current domestic/privatecoded character sets are developer of each character sets except domestic/private coded character sets are quoted in ISO/IEC 10646 as source information.

 

Recommendation/request:

*Although mapping information between ISO/IEC 10646 and existingdomestic/private coded character sets is out of SC2/WG2's scope, it iswelcomed that some organization collects mapping information and maintain it consistently as volunteer.

*And it is also welcomed that this information is widely disclosed.