Summary: | [GTK] [Windows] baidu.com [charset gb2312] didn't rendered correctly | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Bakhtiar Hasmanan <mr.tiar> | ||||||||||||
Component: | Text | Assignee: | Nobody <webkit-unassigned> | ||||||||||||
Status: | RESOLVED FIXED | ||||||||||||||
Severity: | Normal | CC: | cgarcia, mrobinson, mr.tiar | ||||||||||||
Priority: | P2 | ||||||||||||||
Version: | 528+ (Nightly build) | ||||||||||||||
Hardware: | PC | ||||||||||||||
OS: | Windows XP | ||||||||||||||
Attachments: |
|
Created attachment 82557 [details]
google.com.hk [glib+freetype]
Created attachment 82559 [details]
Expected rendering in chromium
works if charset was utf-8 or gbk failed if gb2312 Seems to work fine on Linux, so I'm adding the Windows tag. Works with ICU 4.6 backend Created attachment 85176 [details]
baidu.com webkit-1.2.7 with ICU4.6
Ccing Carlos since he's the one who knows the most about the current state of the GLib unicode backend. Created attachment 85314 [details]
baidu.com with glib unicode backend
This is what I get with current webkit built with the glib unicode backend.
(In reply to comment #8) > Created an attachment (id=85314) [details] > baidu.com with glib unicode backend > > This is what I get with current webkit built with the glib unicode backend. in Linux My first screenshot is with glib-2.22.5 (since I use older gtk 2.16) It'd be interesting to hear if this still fails with trunk. Already works with 1.8.x |
Created attachment 82555 [details] baidu.com webkitgtk+ 1.2.7 in all combination of icu, glib, pango, freetype. baidu.com : Chinese largest search engine baidu.com use <meta http-equiv="Content-Type" content="text/html;charset=gb2312"> google.com.hk use <meta http-equiv="content-type" content="text/html; charset=UTF-8">