ISO/IEC JTC 1/SC 2 N 3368/WG2 N2129

DATE: 1999-09-20

 

ISO/IEC JTC 1/SC 2

Coded Character Sets

Secretariat: Japan (JISC)

 

DOC TYPE:  

Disposition of Comments
 

TITLE:

Disposition of Comments Report on SC 2 N 3310, ISO/IEC 10646-1/FPDAM 31, Universal Multiple-Octet Coded Character Set (UCS) -- Part 1: Architecture and Basic Multilingual Plane -- AMENDMENT 31: Tibetan extension
 

SOURCE:

ISO/IEC JTC 1/SC 2/WG 2
 

PROJECT:

JTC 1.02.18.01.30
 

STATUS:

Disposition of Comments approved at the 37th SC 2/WG 2 Meeting held in Copenhagen, Denmark, 1999-09-13/16.
 

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:

2

ACCESS LEVEL:

Defined

WEB ISSUE #:

062

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

Report on JTC1/SC2 letter ballot on FPDAM.31, Tibetan extension
to ISO/IEC 10646-1: 1993 (E)

Disposition of Comments
The FPDAM appears in JTC1/SC2 N 3310 (also WG2 N 2022)
Responses to the letter ballot appear in JTC1/SC2 N 3351 (also WG2 N 2070).
National bodies that submitted comments are listed below.

China

General:

  1. Noted. No action required.
  2. Noted. No action required.
    The FPDAM added some new characters but these do not require any change in the structure of the implementing method.
  3. Noted. No action required. The new characters are needed by some specialist texts, and must be accommodated in the standard. Existing implementations are not required to change if they do not need these characters.

Technical comments:

  1. Noted. No action required.
  2. Noted. No action required.
  3. Not accepted.
    To output a combining character it should appear after SPACE (U+0020) in the data stream and will then combine with it, see 23.1 in the First Edition of the IS. The proposed new character FORM is not needed.
  4. Noted. No action required.
    The new characters were put in 0FBE - 0FCC & 0FCF, rather than 0FC0 - 0FCF.
  5. Not accepted.
    The character LINK was not in AMD.6 in any position, and thus it has not been removed by this FPDAM.


---------------------------------------