L2/06-035

Open Issues for Public Review, January 27, 2006


75	Proposed Update UTR #25, Unicode Support for Mathematics	2005.10.28
UTR #25, Unicode Support for Mathematics, is being updated to account for recent and pending additions to the character repertoire of mathematical characters in the Unicode Standard.

77	Proposed Draft UTS #39 and Proposed Update UTR #36	2005.10.28
The sections of UTR #36: Unicode Security Considerations that pertain to security functions have been split off into a new proposed draft UTS #39: Unicode Security Mechanisms. In addition, a section on some of the problems with language-based security has been added to UTR #36. We would appreciate feedback on the proposed changes, and comments on the security issues highlighted in UTR #36. See: http://www.unicode.org/reports/tr36/tr36-4.html http://www.unicode.org/reports/tr39/tr39-1.html

80	Proposed Update to UAX #9: The Bidirectional Algorithm	2006.01.30
The Unicode Bidi algorithm has allowed for a great deal of flexibility in determining which characters are to be mirrored (see HL6 http://www.unicode.org/reports/tr9/tr9-16.html#HL6). Unfortunately, that means that text that originates with one person may show up with the wrong graphic to another, thus causing the text to be misinterpreted. The proposal is to tighten up conformance by eliminating overriding of bidi mirroring, and at the same time extending the characters with the Bidi_Mirrored property. The UTC would like public feedback on whether to make this change, and which characters should have the Bidi_Mirrored property. The proposed change is to retain the set of characters currently having Bidi_Mirrored property, and add some additional characters with similar properties. For further information and character lists, see the background document for this issue.

81	Proposed Update to UAX #34: Unicode Named Character Sequences	2006.01.30
A provisional process for the approval of named character sequences has been added to the text of this UAX. A data file containing provisional named character sequences is now available, separate from the list of approved named character sequences. See: http://www.unicode.org/reports/tr34/tr34-4.html Please review the provisional entries in NamedSequencesProv.txt, as well as the proposed text of the update.

82	Representation of Gurmukhi Double Vowels	2006.01.30
In older Gurmukhi, some texts use two vowel signs on a single consonant; for example, one can find ga with both the oo and u vowel signs. A priori, this can be represented in Unicode using two different sequences. Details of a proposal regarding this situation is found in the background document.

83	Changing Glyph for U+047C/U+047D Cyrillic Omega with Titlo	2006.01.30
UTC has received information indicating that the glyphs for U+047C and U+047D should be changed. In the accompanying figure below, the current shape is shown on the left. The proposed new shape is shown on the right. UTC will move to implement this change if no information to the contrary is received by the end of the review period.

84	Proposed Update to UAX #29: Text Boundaries	2006.01.30
A number of changes have been made to simplify implementations and cover edge cases in the rules.

85	Proposed Update to UAX #31: Identifier and Pattern Syntax	2006.01.30
Clarifying text has been added for ideographs and the use of additional characters in identifiers.

86	Proposed Update to UAX #15: Unicode Normalization Forms	2006.01.30
There are no substantive changes in this version of UAX #15. Sections were added to clarify stability and versioning issues, and to make some formatting changes for Unicode 5.0.

87	Proposed Update to UAX #24: Script Names	2006.01.30
This proposed update contains a proposed change in default script value for unassigned characters from Common to a new value Unknown, and a correction for the contents of the Script=Inherited value.

88	Proposed Update to UAX #14: Line Breaking Properties	2006.01.30
The UTC has modified the conformance clauses of UAX #14 and the text they reference. These changes clarify precisely what is tailorable in conformant implementations and what is not. The non-tailorable results are limited to interactions among a small set of well-defined core characters, such as CR, LF, NBSP, SP, and so on, where the semantics of the characters is bound up in how they linebreak. Please see the background document for details of other changes and items to review.

Note: for constraints on proposed changes, see the Unicode Stability Policies.