[Webkit-unassigned] [Bug 14475] REGRESSION: Korean (DOS) encoding doesn't work
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Sat Jun 30 09:02:25 PDT 2007
http://bugs.webkit.org/show_bug.cgi?id=14475
ap at webkit.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Component|New Bugs |WebKit API
Ever Confirmed|0 |1
Keywords| |NeedsRadar, Regression
Priority|P2 |P1
Summary|Text encoding of frames |REGRESSION: Korean (DOS)
|cannot be detected nor |encoding doesn't work
|changed |
------- Comment #4 from ap at webkit.org 2007-06-30 09:02 PDT -------
> Anyway, choosing 'Korean (Windows, DOS)' should show the same result as 'Korean
> (Mac OS)' in most cases
Yes, I also see this now. Confirming that 'Korean (Windows, DOS)' no longer
works, renaming the bug to make clear that it tracks this specific problem.
As for automatic detection, there are two issues in fact:
1) Firefox has true encoding auto-detection (using the actual page text to
guess what the correct encoding is). WebKit only has it for Japanese at the
moment, although other languages could also benefit from it. I suggest adding
examples of sites that need auto-detection to bug 4120.
2) In your test case, the index document explicitly specifies an encoding,
while its subframes do not. WebKit used to propagate the encoding from main
frame to subframes in such case, but we stopped doing so because of many sites
that were broken by this approach. If you have examples of real-life sites that
are broken because of this change, please file a new bug; maybe we could find a
safer solution.
--
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