Re: [web-annotation] (model) vague definition of charactor position for text position selector

I prefer code unit. IIRC Maciej pointed out in the last TPAC that Find
 Text should be compatible with DOM Range. I can't agree more.

I understand code point looks safe, but when it points the middle of a
 grapheme cluster, it looks to me that the problems are similar to 
when it points the middle of a code point. Assuming we all want 
grapheme to be handed properly, I see little benefits in code point.

The use of grapheme has benefits, but UAX#29 allows tailoring, which 
can make the pointer ambiguous.

Each spec then should require to adjust appropriately. Recently we 
 to handle grapheme correctly. It's true that needing to fix all such 
is troublesome, but code point doesn't save us from doing it anyway.

GitHub Notification of comment by kojiishi
Please view or discuss this issue at
 using your GitHub account

Received on Thursday, 19 May 2016 09:48:20 UTC