W3C home > Mailing lists > Public > public-script-coord@w3.org > April to June 2014

[Bug 24581] Fix ByteString type & [EnsureUTF16] flag story

From: <bugzilla@jessica.w3.org>
Date: Mon, 23 Jun 2014 16:50:11 +0000
To: public-script-coord@w3.org
Message-ID: <bug-24581-3890-TEjyIRltH9@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24581

Brendan Eich <brendan@mozilla.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |brendan@mozilla.org

--- Comment #4 from Brendan Eich <brendan@mozilla.org> ---
ScalarValueString is Not Great. It uses a Unicode phrase out of context, so
does not connote Unicode -- in particular does not suggest that lone surrogates
are replaced by U+FFFD -- and also sounds grandiosely general ("scalar value"
in what domain? String theory? :-P).

Concrete beats abstract when something very concrete such as U+FFFD replacement
is going on under the hood. Any of UnicodeString or UniString or UCString would
be better.

A bikeshedding symposium is in order. I don't have a particular favorite but
can provide beverages if nearby.

The big-picture point is: we can do better than ScalarValueString, and we
should. The future is bigger than the past. Let's get this right soon, before
ScalarValueString spreads widely and we can't change it.

/be

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Monday, 23 June 2014 16:50:12 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:22 UTC