Bug 6046 - Need to cleanup charset aliases support
Summary: Need to cleanup charset aliases support
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: DOM (show other bugs)
Version: 420+
Hardware: Mac OS X 10.4
: P2 Enhancement
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-12-11 22:14 PST by Alexey Proskuryakov
Modified: 2007-03-31 11:45 PDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Alexey Proskuryakov 2005-12-11 22:14:34 PST 
With a fix to bug 5932 in place, WebCore uses both its own and ICU's tables for charset names. There are 
a lot of redundant entries that should be removed (I'm not even sure if any aliases known to WebCore are 
missing from ICU).

Also, ICU works directly with charset names, so it's unnecessary to convert them to CFStringEncodings and 
back.
Comment 1 Darin Adler 2005-12-18 14:25:37 PST 
Note that WebCore's lookup ignores case and all non-alphanumeric characters. So that if WebCore lists 
"UTF-8", then "u<t>f-8-" will also work.

Since ICU does not have this property, we'd need to do something if we want to preserve this behavior.
Comment 2 Alexey Proskuryakov 2005-12-19 03:38:15 PST 
(In reply to comment #1)
ICU does something similar: it ignores case, dashes, spaces and underscores. Dunno whether ignoring 
other non-alphanumeric symbols is useful.
Comment 3 Alexey Proskuryakov 2007-03-31 11:45:27 PDT 
Charset handling has been refactored, this bug doesn't appear useful anymore.