W3C home > Mailing lists > Public > www-international@w3.org > January to March 2014

[Bug 24104] Clarify how encoders should deal with lone surrogates

From: <bugzilla@jessica.w3.org>
Date: Fri, 28 Mar 2014 18:05:34 +0000
To: www-international@w3.org
Message-ID: <bug-24104-4285-1RFamLFHEV@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24104

--- Comment #8 from Anne <annevk@annevk.nl> ---
Well, as shown in comment 2 currently the behavior is different for encodings
other than utf-8 and utf-16le/be. Chrome will emit lone surrogates escaped
(meaning its encoders take code points) where as Firefox emits lone surrogates
as U+FFFD escaped.

Other than that it is mostly a layer and debugging question I suppose, yes, but
also affects whether e.g. IDL needs [EnsureUTF16] or some such or not.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Friday, 28 March 2014 18:05:36 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 21 September 2016 22:37:36 UTC