[90-M1] Motion: Approve the minutes of UTC 89/L2 186 as documented in L2/01-405R.
Moved by V.S. Umamaheswaran, seconded by Sandra Martin O'Donnell
10 for (Adobe, Apple, Compaq, IBM, Justsystem, Microsoft, PeopleSoft, Sybase, Trigeminal, Unisys)
2 abstain ( NCR, Sun)
[90-M2] Motion: Fix the mapping error for U+F951 in UnicodeData.txt as part of Unicode 3.2. Change the mapping from U+96FB to U+964B. [L2/02-054]
Moved by Ken Whistler, seconded by Sandra Martin O'Donnell
12 for (Adobe, Apple, Basis, Compaq, IBM, Justsystem, Microsoft, NCR, PeopleSoft, Sun, Sybase, Trigeminal)
1 abstain (Unisys)
[90-C3] Consensus: Change the mapping of the upper case Turkish I as described in L2/02-046, with the typo corrected (U+0407 should be U+0307).
[90-C4] Consensus: Publish a proposed draft technical report on default word boundaries based on L2/02-047R3, -071, and feedback from discussion. In Unicode 3.2 document that the guidelines in the standard will be superseded by the PDUTR.
[90-C5] Consensus: Do not change the canonical mappings of the new Japanese compatibility ideographs at FA30..FA6A. [L2/02-44]
[90-C6] Consensus: Add to Unicode 3.2 the tables 4-7 and 4-8 from document L2/02-018 to Unihan.txt (primary numeric and accounting values).
[90-C7] Consensus: Add U+200B and four Hangul fillers (U+115F, U+1160, U+3164, U+FFA0) to the default ignorable code point property for Unicode 3.2 and add more explanatory text to Proplist.txt. [L2/02-080, 081]
[90-C9] Consensus: Advance Proposed Draft Unicode Technical Report #25 Unicode Support for Mathematics to Draft Unicode Technical Report #25 Unicode Support for Mathematics, after removing the section on mathematics in plain text, and adding a description of the properties. [L2/02-077]
[90-C10] Consensus: The UTC accepts the additional six Limbu characters:
1909 LIMBU LETTER JHA
190A LIMBU LETTER YAN
191A LIMBU LETTER SSA
1932 LIMBU SMALL LETTER ANUSVARA
1940 LIMBU SIGN LOO
1944 LIMBU EXCLAMATION MARK
requests a rearrangement of the vowel signs, appending the letter "A" to 1930..1938 and moving LIMBU QUESTION MARK from U+193F to U+1945. [L2/02-106]
[90-M3] Motion: Add to the text of Unicode 3.2, the following guidelines for the handling of variation selectors: [L2/01-478, L2/02-002]
1) If a variation selector sequence is not available, the variation selector should be ignored.
2) The standardization or support of a particular variation selector does not limit the set of glyphs that can be used to represent the character alone.
3) If you want to have distinction between a character and a character plus a variation selector, you must have a font available that supports that distinction.
Moved by Mark Davis, seconded by Asmus Freytag
7 for (Apple, Basis, IBM, NCR, Sun, Sybase, Unisys)
3 against (Adobe, Compaq, Trigeminal)
3 abstain (Justsystem, Microsoft, PeopleSoft )
[90-C11] Consensus: The UTC congratulates Julie Allen on her recent, well deserved promotion to Senior Editor. Her contributions to Unicode publishing are very much appreciated.
[90-C12] Consensus: The UTC accepts the 13 Arabic characters with the names and code locations as documented in L2/02-061, with the character properties to be finished later. The representative glyphs for 0600..0602 will be updated.
0600 ARABIC NUMBER SIGN
0601 ARABIC YEAR SIGN
0602 ARABIC FOOTNOTE
060D ARABIC POETIC VERSE SIGN
060E ARABIC DATE SEPARATOR
0610 ARABIC SIGN SALLALLAHOU ALAYHE WASALLAM
0611 ARABIC SIGN ALAYHE ASSALAM
0612 ARABIC SIGN RAHMATULLAH ALAYHE
0613 ARABIC SIGN RADI ALLAHOUN ANHU
0614 ARABIC SIGN NOM DE PLUME
0656 ARABIC SUBSCRIPT ALEF
0657 ARABIC TURNED DAMMA
0658 ARABIC BREVE
[90-M4] Motion: The UTC adopts position B from L2/02-010, as the fix to Hangul ordering.Moved by Ken Whistler, seconded by Umamaheswaran[90-C13] Consensus: The UTC endorses voting no on 16451 unless collation is synchronized with the Unicode Collation Algorithm.
11 for (Adobe, Apple, Compaq, IBM, Justsystem, Microsoft, Oracle, PeopleSoft, RLG, Sybase, Unisys)
2 abstain (NCR, Sun )
[90-C14] Consensus: The UTC is in support of having the compatibility Jamo sort according to user expectations.
[90-C15] Consensus: The UTC does not object to the introduction of more explanatory information on pre-handling, but would object to changes to the algorithm that would negatively impact performance or memory requirements.
[90-C17] Consensus: Adopt the behavior of grapheme cluster boundaries as described in L2/02-043 with the following changes: 1) use behavior described in 4' and 5' for join controls, 2) add a rule that indicates that combining marks are ignored in the sequence, 3) add a rule which breaks before the start of text.
[90-M5] Motion: Advance Draft Unicode Technical Report #26 Compatibility Encoding Scheme for UTF-16: 8-Bit (CESU-8) to Unicode Technical Report #26 Compatibility Encoding Scheme for UTF-16: 8-Bit (CESU-8), after adding suggested highlighting, a modification section, and with the final IANA status noted. [L2/02-088R]
Moved by Toby Phipps, seconded by Jianping Yang
12 for (Adobe, Apple, Basis, IBM, Justsystem, Microsoft, Oracle, PeopleSoft, RWS, SAP, Sybase, Unisys)
2 against (NCR, Trigeminal)
1 abstain (Compaq)
[90-M6] FAILED Motion: Strike the text after the first sentence from paragraph two, section Elimination of Irregular Sequences. [L2/02-074]Moved by Sandra Martin O'Donnell, seconded by Michael Kaplan[90-M7] Motion: Change the second sentence of paragraph two, section Elimination of Irregular Sequences, to say: "Note: Some Implementations of UTF-8 might still interpret irregular sequences; for those, a separate compatibility encoding scheme, to be distinguished from UTF-8 may be used. [L2/02-074]
4 for (Compaq, Microsoft, NCR, Trigeminal)
7 against (Adobe, Basis, IBM, Oracle, PeopleSoft, Sybase, Unisys)
5 abstain (Apple, Justsystem, RLG, RWS, SAP)Moved by Ken Whistler, seconded by Eric Muller
10 for (Adobe, Apple, Basis, IBM, Justsystem, Microsoft, Oracle, PeopleSoft, Sybase, Unisys)
3 against (Compaq, NCR, Trigeminal)
3 abstain (RLG, RWS, SAP)
[90-M8] Motion: Remove the section Addition of the Word Joiner from 3.1 Conformance Requirements (revision), which means the clause C10 will remain unchanged. [L2/02-074]
Moved by Ken Whistler, seconded by Eric Muller[90-C18] Consensus: Change the term compatibility composite in D21, section 3.6 Decomposition (revision), to compatibility decomposable character and add aliases in D18. [L2/02-074]
[90-C19] Consensus: Accept the definition of D23a Canonical composite as given in L2/02-035, with a change in term from canonical composite to canonical decomposable. Include an explanatory diagram along with the new definition in Unicode 3.2.
[90-C21] Consensus: In Unicode 3.2, add a chart, similar to the chart given in L2/02-096, that describe extended Cambodian characters with appropriate annotations and properties.
[90-M9] Motion: The UTC formally identifies six Khmer characters as candidates for deprecation. These characters will be annotated and documented as such in Unicode 3.2 [L2/02-097]
17A3 KHMER INDEPENDENT VOWEL QAQ
17A4 KHMER INDEPENDENT VOWEL QAA
17B4 KHMER VOWEL INHERENT AQ
17B5 KHMER VOWEL INHERENT AA
17D3 KHMER VOWEL INHERENT AQ
17D8 KHMER SIGN BEYYALMoved by Asmus Freytag, seconded by Joan Aliprand
10 for (Adobe, Basis, Compaq, IBM, Justsystem, Microsoft, Oracle, PeopleSoft, RLG, Sun)
5 abstain (Apple, NCR, Sybase, Trigeminal, Unisys)
[90-C22] Consensus: The UTC requests the officers to issue a liaison communication to the Cambodian national body, with the intent to clarify issues, strengthen cooperation, and invite future participation.
[90-C23] Consensus: The UTC accepts 45 new Khmer characters: [L2/02-099, 100, 101]
17DD KHMER SIGN ATTHACAN
17EA KRUNG VOICING OR PREGLOTTALIZATION SIGN
17EB KRUNG VOICING AND PREGLOTTALIZATION SIGN
17F0 KHMER SYMBOL LEK ATTAK SON
17F1 KHMER SYMBOL LEK ATTAK MUOY
17F2 KHMER SYMBOL LEK ATTAK PII
17F3 KHMER SYMBOL LEK ATTAK BEI
17F4 KHMER SYMBOL LEK ATTAK BUON
17F5 KHMER SYMBOL LEK ATTAK PRAM
17F6 KHMER SYMBOL LEK ATTAK PRAM-MUOY
17F7 KHMER SYMBOL LEK ATTAK PRAM-PII
17F8 KHMER SYMBOL LEK ATTAK PRAM-BEI
17F9 KHMER SYMBOL LEK ATTAK PRAM-BUON
19E0 KHMER SYMBOL PATHAMASAT
19E1 KHMER SYMBOL MUOY KOET
19E2 KHMER SYMBOL PII KOET
19E3 KHMER SYMBOL BEI KOET
19E4 KHMER SYMBOL BUOM KOET
19E5 KHMER SYMBOL PRAM KOET
19E6 KHMER SYMBOL PRAM-MUOY KOET
19E7 KHMER SYMBOL PRAM-PII KOET
19E8 KHMER SYMBOL PRAM-BEI KOET
19E9 KHMER SYMBOL PRAM-BUON KOET
19EA KHMER SYMBOL DAP KOET
19EB KHMER SYMBOL DAP-MUOY KOET
19EC KHMER SYMBOL DAP-PII KOET
19ED KHMER SYMBOL DAP-BEI KOET
19EE KHMER SYMBOL DAP-BUON KOET
19EF KHMER SYMBOL DAP-PRAM KOET
19F0 KHMER SYMBOL TUTEY ASAT
19F1 KHMER SYMBOL MUOY ROC
19F2 KHMER SYMBOL PII ROC
19F3 KHMER SYMBOL BEI ROC
19F4 KHMER SYMBOL BUOM ROC
19F5 KHMER SYMBOL PRAM ROC
19F6 KHMER SYMBOL PRAM-MUOY ROC
19F7 KHMER SYMBOL PRAM-PII ROC
19F8 KHMER SYMBOL PRAM-BEI ROC
19F9 KHMER SYMBOL PRAM-BUON ROC
19FA KHMER SYMBOL DAP ROC
19FB KHMER SYMBOL DAP-MUOY ROC
19FC KHMER SYMBOL DAP-PII ROC
19FD KHMER SYMBOL DAP-BEI ROC
19FE KHMER SYMBOL DAP-BUON ROC
19FF KHMER SYMBOL DAP-PRAM ROC
[90-C24] Consensus: The Editorial Committee should update the technical reports for consistency with Unicode 3.2 and post as proposed updates.
[90-C25] Consensus: Add text to Unicode Standard Annex #21 Case Mappings stating that to preserve canonical equivalence in case mapping operations, the input text should be normalized. Add further explanatory text as necessary.
[90-C28] Consensus: Accept the new text on variation selectors given in L2/02-104 with change made in committee.
[90-M10] FAILED Motion: The UTC rescinds its earlier decision to correct the error in the canonical mapping of U+F951.Moved by Rick McGowan, seconded by Lee Collins
1 for (Apple)
8 against (Adobe, IBM, Justsystem, Microsoft, PeopleSoft, Sun, Sybase, Trigeminal)
5 abstain (Basis, NCR, Oracle, RLG, Unisys)
[90-C29] Consensus: The UTC approves Unicode 3.2 as documented in L2/02-074 and amended during the meeting, for public release.
[90-C30] Consensus: Remove the compatibility mappings for 23B4..23B6 from the Unicode 3.2 datafile.
[90-M11] Motion: The Editorial Committee has the responsibility for the technical notes web page, process, and approval of technical notes. It can delegate the selection process for technical notes to a subcommittee, which may include members who are not on the Editorial Committee. [L2/02-075, 076]Moved by Mark Davis, seconded by Asmus Freytag
9 for (Apple, Basis, IBM, Microsoft, Oracle, PeopleSoft, RLG, Sun, Trigeminal)
1 against (Sybase)
4 abstain (Adobe, Justsystem, NCR, Unisys)