[Webkit-unassigned] [Bug 28760] New: Make the canonical names (of TextEncoding) robust to changes in ICU's alias table

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=28760

           Summary: Make the canonical names (of TextEncoding) robust to
                    changes in ICU's alias table
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Platform
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: jshin at chromium.org
                CC: ap at webkit.org, eric at webkit.org, darin at apple.com


In ICU 4.2, the gb18030 entry in convertrs.txt changed to 

gb18030 { IANA* }       ibm-1392 { IBM* } windows-54936 { WINDOWS* } GB18030 {
MIME* }


from

gb18030 { IANA* }       ibm-1392 { IBM* } windows-54936 { WINDOWS* }

Note that 'GB18030' (uppercase) was added as the MIME name for gb18030. Because
Webkit gives a higher precedence to MIME, it picks up GB18030 as the canonical
name. 

Chromium has some tests that do the case-sensitive comparison of charset names
(Webkit layout tests have some, too. e.g. 'EUC-JP'). Chromium also has some
unit tests  (dom serialization) and ui tests (encoding menu test) that compare
the textual contents of two files which include 'meta charset' label generated
by dom serializer which uses the canonical name of TextEncoding for meta
charset generation. 

It's possible to track down all the cases where TextEncoding::name() is used
and lowercases the return value in Webkit 'clients', but it may be better to
make the canonical name of TextEncoding be always lowercase. When we do, we
have to change the expected results of a few layout tests.

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