DR 11-0033, "WML: Positioning of Emphasis Marks" still not quite resolved to China's satisfaction

[Alex Brown]

Dear all,

 

We shouldn't make a breaking change by altering attribute names without
exceptionally good reason; I'm not seeing one here.

 

- Alex.

 

From: Rex Jaeschke [mailto:rex at RexJaeschke.com] 
Sent: 13 February 2013 16:56
To: SC 34 WG4
Subject: DR 11-0033, "WML: Positioning of Emphasis Marks" still not quite
resolved to China's satisfaction

 

Some time ago, we closed this DR and then re-opened it. Then last week we
closed it again. However, China still has some concerns. See below an
extract from private mail to me.

 

While I sympathize with China's concerns, I think that their proposal to
change several enumerations' short names is a breaking change for
implementers. That said, standards are allowed to have breaking changes.

 

Comments please.

 

Rex

 

 

 

 

From: Li Ning [mailto:lining at bistu.edu.cn] 
Sent: Wednesday, February 13, 2013 10:58 AM
To: 'Rex Jaeschke'

 

Dear Rex,

 

I have read your draft minutes. I have a slight different opinion how to
explain the emphasis mark. As it may appear at different positions(top,
bottom, left, right), it is not a good idea to name it as "underDot". I
prefer to name it as "type-1" or "type-2". I made some changes in the table
in track mode, I think that you can understand me well.

 

Best regards,

Ning

 


______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.vse.cz/pipermail/sc34wg4/attachments/20130213/b6985b65/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6089 bytes
Desc: not available
URL: <http://mailman.vse.cz/pipermail/sc34wg4/attachments/20130213/b6985b65/attachment.bin>