6046 2005-12-11 22:14:34 -0800 Need to cleanup charset aliases support 2007-03-31 11:45:27 -0700 1 1 1 Unclassified WebKit DOM 420+ Mac OS X 10.4 RESOLVED FIXED P2 Enhancement --- 1 ap webkit-unassigned ian oldest_to_newest 25847 0 ap 2005-12-11 22:14:34 -0800 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. 26138 1 darin 2005-12-18 14:25:37 -0800 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. 26172 2 ap 2005-12-19 03:38:15 -0800 (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. 16041 3 ap 2007-03-31 11:45:27 -0700 Charset handling has been refactored, this bug doesn't appear useful anymore.