- From: Brendan Eich <brendan@mozilla.com>
- Date: Sun, 19 Feb 2012 15:18:08 -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 2:44 PM, Brendan Eich wrote: >> Thanks. We have a confusing transposition of terms between Unicode and ECMA-262, it seems. Should we fix? > > The ES5.1 spec.is ok because it always uses (as defined in section 6) the term "Unicode character" when it means exactly that and uses "character" when talking about the elements of String values. It says that both "code unit" and "character" refer to a 16-bit unsigned value. That is still pretty confusing. I hope we can stop abusing "character" by overloading it in ECMA-262 in this way. > 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. /be
Received on Sunday, 19 February 2012 23:18:38 UTC