L2/15-033

PRI and Reporting Form Feedback Brought Forward From Prior Meetings


Feedback on Encoding Proposals

MOVE FORWARD to feedback for next meeting Date/Time: Wed Aug 20 11:25:16 CDT 2014
Name: John Cowan
Report Type: Error Report
Opt Subject: L2/14-192: Preliminary Proposal to Encode the Turkestani Script

Given the repeated statements in the proposal that Tocharian and Khotanese
writing are mutually illegible, and the need for different treatment of
certain letters in the two writing systems, I believe that they should not be
unified.  The precedent is the severance of the various 22-character West
Semitic abjads, which are completely isomorphic (unlike this case), on the
grounds of mutual illegibility.

I therefore propose that the Khotanese characters be removed and the script
renamed to "Tocharian".

MOVE FORWARD to feedback for next meeting  Date/Time: Wed Aug 20 11:18:45 CDT 2014
Name: John Cowan
Report Type: Feedback on an Encoding Proposal
Opt Subject: L2/14-200: Don't use U+E01EF VARIATION SELECTOR-256

I strongly support this; indeed, I think that U+E01EF should be formally
deprecated.  Nobody should be using it now, and nobody should use it in
future.

MOVE FORWARD to feedback for next meeting  Date/Time: Wed Aug 20 11:17:09 CDT 2014
Name: John Cowan
Report Type: Feedback on an Encoding Proposal
Opt Subject: L2/14-202: Additional proposal to encode Latin characters for theta and delta

I have no problem with the proposed capital letters.

I am concerned that the introduction of a Latin small theta will disrupt the
standard encoding of IPA with the Greek small theta.  IPA is complicated
enough without introducing multiple spellings of a very common character.
Strong provisions would have to be made to ensure that IPA continued to be
encoded with Greek theta.

Other Reports

MOVE FORWARD to feedback for next meeting Date/Time: Thu Sep 18 15:11:28 CDT 2014
Name: Roozbeh Pournader
Report Type: Error Report
Opt Subject: Behavior of music format character underspecified

The music format characters at U+1D173..1D17A are underspecified. For example, it 
is not clear if they can nest like the bidi formatting characters.

Making them nestable would make their implementation in plain text environments very 
hard, I suggest the standard clearly mentions that they are nestable, or that different 
kinds of format may nest, but not more than one of each, etc.