Updates:
Owner: [email protected]
Labels: -Area-WebKit
Comment #7 on issue 3301 by [email protected]: Run zh-CN Chrome: Non-ASCII
album name showing as garbage on PicasaWeb
http://code.google.com/p/chromium/issues/detail?id=3301
Firefox (and any browser when the default encoding is set to GB18030)
suffers from
this issue. Rebang also used to suffer from this, but now fixed.
Basically, when 'Accept-Charset' has gb18030 as the 1st charset, Picasa web
sends a
part of the page encoded in gb18030 while the rest of the page is encoded
in UTF-8
and the page is declared to be in UTF-8.
http://www.google.cn/hp?sp=china (icafe) has the same problem.
I'll just go ahead and switch SC Chrome's default encoding to GBK. Because
it only
happens with gb18030. Needless to say, Google has to fix this and icafe bug.
Google internal bugs related to this: b/1435844, b/1668772, b/1680999.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---
