- From: Brendan Eich <brendan@mozilla.com>
- Date: Sun, 19 Feb 2012 15:31:11 -0800
- To: Allen Wirfs-Brock <allen@wirfs-brock.com>
- CC: Anne van Kesteren <annevk@opera.com>, "public-script-coord@w3.org" <public-script-coord@w3.org>, mranney@voxer.com, es-discuss <es-discuss@mozilla.org>
Allen Wirfs-Brock wrote: > On Feb 19, 2012, at 3:18 PM, Brendan Eich wrote: > >> Allen Wirfs-Brock wrote: >> ... >>> Your proposal would change that equivalence. In one sense, the BSR >>> would be a switch that controls whether a ES "character" corresponds >>> to "code unit" or a "code point" >> >> Yes, and we might rather have a different word on that basis too. >> >> How about "character element"? "Element" to capture indexing as the >> means of accessing the thing in question. > > I generally try to use "element" in informal contexts for exactly that > reason. However, shouldn't it be "string element" and we could let > "character" and "Unicode character" mean the same thing? Yes, see my es-discuss+you followup -- should have measured twice and cut once. I like this much better than anything overloading "character". To hope to make this sideshow beneficial to all the cc: list, what do DOM specs use to talk about uint16 units vs. code points? /be
Received on Sunday, 19 February 2012 23:31:41 UTC