The sections below contain links to permanent feedback documents for the open Public Review Issues as well as other public feedback as of January 29,2014, since the previous cumulative document was issued prior to UTC #138 (November 2013). This document does not include feedback on moderated Public Review Issues from the forum that have been digested by the forum moderators; those are in separate documents for each of the PRIs. Grayed-out items in the Table of Contents do not have feedback here.
The links below go to directly to open PRIs and to feedback documents for them, as of November 1, 2013.
Issue Name (+ feedback links) 265 Proposed Update UAX #29, Unicode Text Segmentation (no feedback) 264 Proposed Update UTS #46, Unicode IDNA Compatibility Processing (feedback) 263 Sequences to Select From Multiple C2-Conjoining Forms in Malayalam (feedback) 262 Proposed Update UAX #44, Unicode Character Database (no feedback) 261 Proposed Update UAX #15, Unicode Normalization Forms (no feedback) 260 Proposed Update UTS #10, Unicode Collation Algorithm (no feedback)
The links below go to locations in this document for feedback.
Date/Time: Mon Jan 20 11:56:36 CST 2014
Contact: jamadagni@gmail.com
Name: Shriramana Sharma
Report Type: Feedback on an Encoding Proposal
Opt Subject: Cibu Johny's proposal to encode MALAYALAM MEASUREMENT SYMBOL PARA
Dear Rick, I didn't think this warrants a separate document/number, but I wanted it to go into the record nevertheless and should be considered at the upcoming UTC. Since Cibu submitted the proposal before waiting for my feedback while I was away at a conference, this could not be included in his original submission. So I am sending this via the reporting form: In his recent submission, Cibu asks for a character to be encoded: MALAYALAM MEASUREMENT SYMBOL PARA. As per Indic naming practices, this should be changed to MALAYALAM SIGN PARA. Shriramana Sharma.
Per action 137-A46, this feedback was copied forward from L2/13-202 at the last meeting.
Also required is a pointer to
CLDR Ticket #6736
Date/Time: Fri Oct 4 16:01:36 CDT 2013
Contact: jungshik@google.com
Name: Jungshik Shin
Report Type: Error Report
Opt Subject: Case mapping for U+0587
Hello, This is not a bug report per se, but is just to bring an issue we came across about the uppercase of U+0587 at Google to the UTC's attention. U+0587 (Armenian Small letter Ligature ECH YIWN) is currently case-mapped to a sequence of U+0535 (Amernian Capital Letter ECH) and U+0552 (Capital letter YIWN). There's a report from Armenian speakers in Armenia that the latest Armenian orthography as used in Rep. of Armenia uppercases it to a sequence of U+0535 and U+054E ( (Armenian Capital letter VEW). OTOH, Armenian diaspora and "Western Armenian" speakers follow the current Unicode standard. A comment from Google's Armenian speaker: "That form was used in Armenia before "spelling reform of the Armenian language" at the beginning of the 20th century (1922–1924 - according to Wikipedia). There is a variation of Armenian language currently used by Armenian diaspora, who still use the old version. But everyone in Armenia (including official documents and media) are using the new form." Another comment from a linguistics professor at Yerevan : <quote> So I asked this guy http://www.ysu.am/science/en/4Kg4l3vuxYoueJU5nAWSsH9JAT/type/1/page/1 who is friend of mine. His comment was "Ev is a ligature, same as &, and as such it is not a full first class citizen letter and it cannot have a capital. In Eastern Armenian it is usually "ԵՎ" although it is logically wrong, as the ligature is ligature of "եւ". To cut things short - it is illogical and historically incorrect to write ԵՎ in his opinion, but that is the way it is done, so we shall write ԵՎ in Eastern Armenian and ԵՒ in Western. </quote>
Date/Time: Fri Nov 15 20:35:03 CST 2013
Contact: liancu@microsoft.com
Name: Laurentiu Iancu
Report Type: Error Report
Opt Subject: UTS #18: Add Unicode_Radical_Stroke to Table 2.7
In UTS #18 (Revision 16 draft 1), Table 2.7 appears to enumerate all UCD properties which are not deprecated, obsolete, or provisional. Unicode_Radical_Stroke is an informative property and is missing from Table 2.7, so from that perspective it seems that it should be added to the CJK section of the table.
Date/Time: Mon Dec 9 21:00:36 CST 2013
Contact: roozbeh@google.com
Name: Roozbeh Pournader
Report Type: Error Report
Opt Subject: North Indic Number forms also used in Mahajani, Maithili and Modi
Currently, ScriptExtensions.txt defines the following scripts as using the North Indic number forms: Deva Gujr Guru Kthi Takr According to the proposal encoding the North Indic number forms at http://www.unicode.org/L2/L2007/07139r-north-indian-acctg-signs.pdf, the North Indic numbers forms are also used in Mahajani, Tirhuta (Maithili), and Modi scripts. Samples and explanation are provided in that document. This means that those scripts should be added to the Script_Extension property for the characters in Unicode 7.0, changing the properties to: Deva Gujr Guru Kthi Mahj Modi Takr Tirh
Date/Time: Tue Feb 4 13:34:21 CST 2014
Contact: roozbeh@unicode.org
Name: Roozbeh Pournader
Report Type: Error Report
Opt Subject: Incorrect properties for Ornate Parentheses
The general category and the line breaking property of U+FD3E and U+FD3F appear to imply that the LEFT character is opening (gc=Ps, lb=OP), while the RIGHT character is closing (gc=Pe, lb=CL). That is incorrect. The characters, which are still very frequently used as quotation marks with the Arabic script especially in religious text, are the other way around. The RIGHT character is opening, while the LEFT one is closing. The characters are special in the way that since they are not bidi mirroring, so they would need to break with the normal treatment of LEFT and RIGHT pairs.
None at this time.