[Webkit-unassigned] [Bug 14475] Text encoding of frames cannot be detected nor changed

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Sat Jun 30 08:15:45 PDT 2007


http://bugs.webkit.org/show_bug.cgi?id=14475





------- Comment #3 from tomyun at gmail.com  2007-06-30 08:15 PDT -------
(In reply to comment #2)
> I have tried, and choosing Korean (Mac OS) from the menu works for me in r23841
> nightly (running with Safari 3.0.2 beta). I'm wondering what is different in
> your case. Do you have any Safari enhancers installed?
> 

I missed that one. Actually, I (and maybe many Korean users) usually play with
'Korean (Windows, DOS)', not 'Korean (Mac OS)'. They are slightly different
variants of EUC-KR encoding, though I'm not sure which parts are exactly
different. Since Windows platforms are prevalent in Korea, the former would be
more commonly found on the web.

Anyway, choosing 'Korean (Windows, DOS)' should show the same result as 'Korean
(Mac OS)' in most cases. Web pages rendered correctly in Safari 2 starts broken
in Safari 3.

Also, automatic encoding detection feature in Safari 3 seems to be somewhat
broken when the page does not specify one.

PS: I don't have any enhancer installed. Once I had SafariStand, but
uninstalled it right after Safari 3 beta came out.


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



More information about the webkit-unassigned mailing list