L2/07-353
Title: WG2 Consent Docket
Source: Ken Whistler
Date: October 10, 2007
Following my usual procedure, I have rolled up all items from the
latest WG2 meeting (WG2 #51, Hangzhou, China, September 17-21, 2007)
for which there is a synchronization issue that the UTC needs to
address.
This WG2 meeting progressed 3 amendments:
Amendment 4: The disposition of comments was completed for the FPDAM 4,
and FDAM 4 will be issued soon.
Amendment 5: The disposition of comments was completed for the PDAM 5,
and FPDAM 5 will be issued soon.
Amendment 6: A new amendment was started, and PDAM 6 will be issued
soon.
In the consent docket this time, I have organized the issues
in part by which amendment they are associated with, to help
keep things straight. Note that as of current plans, the repertoires
for Amendments 3 and 4 together will be the eventual repertoire
added for Unicode 5.1. The new repertoire for Amendments 5 and 6 will
likely be targeted for a future version of Unicode past Version 5.1.
Note also that for changes specific to FDAM 4, the UTC really
just has to approve things at this point, as there is no
chance now to reconsider the decisions by WG2; the FDAM vote
is an up or down vote, with no technical changes allowed.
================================================================
A. Lanna (FDAM 4 and FPDAM 5)
WG2 removed Lanna from Amendment 4, based on significant comments
from China that indicated that there were still unresolved
issues in the encoding.
The removal from Amendment 4, per se, has no consequence for
the approval of Lanna by the UTC; it simply means that Lanna
will not be part of the repertoire to be published as
Unicode 5.1.
However, there is more to deal with. WG2 moved Lanna *into*
Amendment 5, with significant changes. So the UTC needs to
consider resynching its approval of Lanna to reflect those
changes. In particular:
1. The script name is changed from "Lanna" to "Tai Tham".
2. The block stays at 1A20..1AAF, but the block name is
changed from "LANNA" to "TAI THAM".
3. Because of the script name change, all character names
have been changed from "LANNA XYZ..." to "TAI THAM XYZ..."
4. Additional character approved:
1A5A TAI THAM SIGN LOLA HOY KONGNOT
5. Characters moved:
1A5F --> 1A7E TAI THAM LETTER GREAT SA
(Plus some shifting due to the insertion of 1A5A.)
Recommendation: approve the script, block, and character name
changes, addition of one character, and changed code points.
================================================================
B. Myanmar (FDAM 4)
WG2 approved the Irish request to add a few more Shan characters,
as well as Shan digits, to the Myanmar additions already in
Amendment 4. The UTC has already seen and approved this
request, so is in synch with the results for Amendment 4.
The thing to note is that the UTC requested character moves
consistent with these approvals for Amendment 4, but assumed
(and requested) that the other Shan additions be ballotted in
a subsequent amendment. This distinction is now moot, as
all Myanmar additions were handled in the disposition of
comments for Amendment 4.
There was one name correction:
108E MYANMAR VOWEL SIGN RUMAI PALAUNG FA
-->
108E MYANMAR LETTER RUMAI PALAUNG FA
Recommendation: Accept the name correction. Otherwise, simply
note the outcome of Amendment 4, for updating
of the pipeline re Myanmar character additions.
================================================================
C. Supplemental Punctuation (FDAM 4)
WG2 approved 3 name changes for the supplemental punctuation,
as well as a reorganization of the approved code points, to
compact the additions.
The name changes reverse the UTC expressed preference for
"SWUNG DASH" over "TILDE" in 3 dictionary punctuation marks:
2E1B SWUNG DASH WITH RING ABOVE
2E1E SWUNG DASH WITH DOT ABOVE
2E1F SWUNG DASH WITH DOT BELOW
-->
2E1B TILDE WITH RING ABOVE
2E1E TILDE WITH DOT ABOVE
2E1F TILDE WITH DOT BELOW
The reorganization of the approved characters to compact the
chart was as follows:
2E40..2E49 --> 2E20..2E29
2E2C --> 2E2B
2E2E..2E2F --> 2E2C..2E2D
2E34 --> 2E2E
2E3B --> 2E2F
2E38 --> 2E30
Recommendation: Accept the 3 name changes and the updated
code points for supplemental punctuation.
==============================================================
D. Bamum (FPDAM 5)
WG2 removed Bamum from Amendment 5, pending feedback from
the stakeholder community in Cameroon.
This doesn't impact the UTC approval of the encoding of the
Bamum script -- it merely postpones ISO ballotting of the
script for now.
Recommendation: Note the disposition for Bamum.
===============================================================
E. Meitei Mayek (FPDAM 5)
WG2 was unable to resolve the dispute about the status of
danda punctuation for Meitei Mayek. It created an action item
to come up with a general position on dandas for the Principles
and Procedures document, but in the meantime removed Meitei Mayek
from Amendment 5, pending a principled resolution of the danda
issue.
This decision doesn't impact the UTC approval of the encoding
of the Meitei Mayek script -- it merely postpones ISO ballotting
of the script.
Recommendation: Note the disposition for Meitei Mayek for now.
The UTC should be prepared to contribute to the development of
a position on the dandas, so that the ISO ballotting of this
script can resume at some point in the near future.
===============================================================
F. CJK Extension C (FPDAM 5)
WG2 kept CJK Extension C in Amendment 5, with extensive revisions
requested by China, the U.S., the U.K., and Japan. This included
67 removals, reordering of the remaining repertoire to remove
holes, plus modifications to mappings. This results in a
revised repertoire:
2A700..2B731 (4146 additions) CJK Unified Ideographs Extension C
Given that this collection is now headed for its FPDAM ballot,
and that the U.S. comments on it have been accomodated, I think
it is probably time for the UTC to go on record as approving
the repertoire for addition to Unicode.
Recommendation: Approve the CJK Unified Ideographs Extension C
repertoire and block.
=================================================================
G. Avestan Separation Point (FPDAM 5)
WG2 declined to accomodate the U.S. request to remove
U+10B38 AVESTAN SEPARATION POINT from Amendment 5, in the
face of a determined requirement from the Irish NB that it
stay in the amendment. This despite the addition of the
WORD SEPARATOR MIDDLE DOT, which the UTC encoded to serve
for this.
Recommendation: Decline to resynch in this particular case,
and instead prepare more forceful ballot comments on this for
FPDAM 5.
==================================================================
H. WORD SEPARATOR MIDDLE DOT (FPDAM 5)
As a result of the compacting of supplemental punctuation for
the disposition of comments for Amendment 4, WG2 changed
the code point for the WORD SEPARATOR MIDDLE DOT, when it was
accepted for addition to Amendment 5.
2E37 WORD SEPARATOR MIDDLE DOT
-->
2E31 WORD SEPARATOR MIDDLE DOT
Recommendation: Approve revised code point.
=================================================================
I. Egyptian Hieroglyphs (FPDAM 5)
In response to the Irish NB comment, WG2 removed one character
as a duplicate, and added 9 others. 4 of the additions are
variants of other hieroglyphs, and 5 of them are additional
number forms.
No block range change was required for this.
Recommendation: Accept the revised repertoire, as shown in
WG2 N3349 (= L2/07-322).
==================================================================
J. Additional CJK Compatibility Ideographs (FPDAM 5)
Japan requested the encoding of 6 additional ideographs,
as proposed in WG2 N3318. (These are identified as
Japanese ARIB ideographs.) WG2 encoded 2 unified
ideographs:
9FC4..9FC5
and 4 compatibility ideographs:
FA6B..FA6E
Recommendation: Accept the 6 additional CJK ideographs.
Ensure that appropriate source mapping data is available
for the 2 unified ideographs and that the equivalence
mapping data is available for the 4 compatibility ideographs.
===================================================================
K. PDAM 6 Issues
Amazingly, there are none! Only scripts and sets of symbols
that had already been approved by the UTC were included for
ballot in Amendment 6 as of now, with no technical changes.
So there are no new synchronization issues posed by Amendment 6.
===================================================================