[Webkit-unassigned] [Bug 51035] UCS2 encoding aliases should be defaulted to Big Endian

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Dec 16 10:43:42 PST 2010


--- Comment #40 from Yong Li <yong.li.webkit at gmail.com>  2010-12-16 10:43:42 PST ---
(In reply to comment #39)
> (In reply to comment #38)
> > The currently preferred way to resolve such differences is via standardization in HTML5. In fact, HTML5 already sides with IE/WebKit:
> > ---------------------------
> > When a user agent is to use the UTF-16 encoding but no BOM has been found, user agents must default to UTF-16LE.
> > Note: The requirement to default UTF-16 to LE rather than BE is a willful violation of RFC 2781, motivated by a desire for compatibility with legacy content. [RFC2781]
> > ---------------------------
> > The tests added here are very good, and I suggest landing those. But it doesn't seem like we should be changing behavior.
> Tend to agree. But probably we still want to handle 'ISO-10646-UCS-2' and 'UCS-2' as BE?

As IE also uses BE for 'ISO-10646-UCS-2'

Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the webkit-unassigned mailing list