- From: Mark Buer via GitHub <sysbot+gh@w3.org>
- Date: Wed, 18 May 2016 00:30:31 +0000
- To: public-annotation@w3.org
I'd like to bring to this issues attention a [recent query against the EPUBCFI specification](https://github.com/IDPF/epub-revision/issues/555), which may be used as fragment identifiers within this spec, where it was (tentatively?) decided that character positions be defined in terms of UTF-16 code units. It might be confusing if this spec chooses unicode code points but the EPUBCFI spec chooses UTF-16 code units... Is this specification in danger of being too difficult to implement atop the current state of deployed ECMAScript and browser DOM APIs (where UTF-16 code units are the lingua franca)? Are changes to browser DOM APIs (for example allowing unicode code point indexing within DOM Ranges and others) imminent? -- GitHub Notification of comment by mark-buer Please view or discuss this issue at https://github.com/w3c/web-annotation/issues/206#issuecomment-219893634 using your GitHub account
Received on Wednesday, 18 May 2016 00:30:33 UTC