UTC/1999-010


From: kenw@sybase.com
Sent: Tuesday, May 11, 1999 7:09 PM
To: Multiple Recipients of Unicore
Cc: kenw@sybase.com
Subject: Summary of WG2 actions in Fukuoka requiring UTC ratification

The WG2 meeting in Fukuoka, March 9 - 15, took a number of
actions which will require UTC ratification at the UTC meeting
in June. I will prepare a consent docket document for that UTC
meeting, to make it easier to get through the list of
required changes.

First, however, here is the summary of what happened regarding
the amendments to 10646-1, plus a few auxiliary items.

Those who want all the details can refer to JTC 1/SC 2 N3291
(= WG 2 N2004), available at:
http://wwwold.dkuug.dk/JTC1/SC2/open/dr.htm

Amendments 22 (Keyboard Symbols), 24 (Thaana), 25 (Khmer), and
27 (Syriac) progressed to FDAM ballotting, with no changes.

Amendment 26 (Myanmar) pregressed to FDAM ballotting, with only
a minor glyph change requested by the U.K.

There was discussion at the meeting regarding a number of issues
for Khmer and Myanmar, but all objections were resolved by agreements
to add annotations or to consider future additions. No changes to
the characters in the ballot resulted

Amendment 14 (Yi syllables and Yi radicals) underwent some major
changes in the Yi radicals to resolve the FPDAM ballot comments.
This amendment progressed to FDAM ballotting. The impact for
Unicode is the net removal of 7 Yi radicals and the
reordering of the block of Yi radicals. This will have to be
approved.

Amendment 15 (KangXi radicals and CJK radicals supplement). There
were a number of changes to resolve PDAM ballot comments. U+239A was
removed, and the names of 8 other CJK radicals were changed.
These changes will have to be approved by UTC. This amendment
progressed to FPDAM ballotting (SC 2 N3311), with a closing date of
August 13.

Amendment 28 (Ideographic description characters). No changes
were required. This amendment progressed to FPDAM ballotting
(SC 2 N3312), with a closing date of August 13.

Amendment 29 (Mongolian). There were a number of changes in character
names as a result of the resolution of PDAM ballot comments or
editorial fixes. In particular, all characters with "AG" in their
names had that expression expanded to "ALI GALI", and characters
with "PERIOD" were changed to use "FULL STOP". These changes
will have to be ratified by UTC. This amendment progressed to
FPDAM ballotting (SC 2 N3308), with a closing date of August 13.

Amendment 30 (Additional Latin and other characters). There were
a number of changes--both deletions and additions--as a result
of ballot comments. U+204F SOFT SPACE was deleted. That already
accords with UTC requirements. U+048C/U+048D CYRILLIC LETTER
C/S SEMISOFT SIGN were added for Kildin Sami. U+20AF DRACHMA SIGN
was added for Greece. These 3 additions will have to be ratified
by UTC. This amendment progressed to FPDAM ballotting (SC 2 N3309),
with a closing date of August 13. There is an additional, late-breaking
problem with this ballot: 6 more characters are being pulled
(04C5, 04C6, 04C9, 04CA, 04CD, 04CE) because of inconsistencies
between the ballotted glyphs and names and information obtained
from the Kildin Sami experts. This change must also be ratified by
UTC, and must be rolled in to UTC (and L2) comments on the FPDAM
ballot, to ensure that Unicode 3.0 and 10646-1 stay in synch here.

Amendment 31 (Tibetan extension). A number of clarificatory notes
were added during the resolution of the PDAM comments. Similar
clarifications are being rolled into the names list for Unicode 3.0,
but no normative changes for Unicode 3.0 were involved. This
amendment progressed to FPDAM ballotting (SC 2 N3310), with
a closing date of August 13.

Other issues:

Draft Technical Corrigendum No. 3 was prepared, and SC2 issued it,
with a ballot closing date of June 30. The contents of this DCOR
is mostly of relevance to 10646-1, but during its preparation, the
editor turned up an error in the normative table of Jamo Short
Names (Table 4.4) in the Unicode Standard. The correction of that
error needs to be ratified by the UTC.

A bucket #36 was created, and U+20E4 COMBINING ENCLOSING UPWARD
POINTING TRIANGLE was added to it. This finally deals with the
disconnect for this character that UTC has already accepted. However,
this character is not yet in any SC2 ballot, so cannot be included
in the Unicode 3.0 repertoire. It joins other characters (such
as the Gothic or Deseret scripts) that UTC has accepted, but which are waiting
for a future edition.

One additional WG2 resolution is of relevance to the Unicode Consortium:
Resolution M36.25: "WG2 requests the Unicode Consortium to act as
the backup to AFII, if necessary, for preparing the camera ready copy
of the non-Unified CJK glyph charts and list of names of the second
edition of ISO/IEC 10646-1 on schedule." This request from WG2 was
to ensure that they would be covered for the printing of 10646-1.
This is not a technical issue for UTC, but it does have a bearing
on resources and schedule for the publication of the Unicode Standard
and 10646-1 second edition.

--Ken