[Webkit-unassigned] [Bug 15914] [GTK] Implement Unicode functionality using GLib

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=15914





------- Comment #20 from dominik.roettsches at access-company.com  2008-08-27 08:01 PDT -------
Created an attachment (id=23031)
 --> (https://bugs.webkit.org/attachment.cgi?id=23031&action=view)
Overview and Comparison of Text Codecs in Safari Win/Mac and libiconv

Libiconv becomes a less favorable choice for enumerating the available
encodings given the fact that glib does not rely on libiconv on all platforms
but uses the standard libc iconv on a number of Unices or win32 functions on
Windows.

I have created an overview of Safari Win & Mac encodings compared to the ones
supported by libiconv (and most likely supported by standard libc iconv, too,
as from what I understand, these implementations are often very similar). This
table shows that almost all Safari encodings can be covered by using these
encoding names.

The table does not yet list all the aliases for each canonical encoding. For a
start, a list of typical MIME encoding names could be extracted from:
http://www.iana.org/assignments/character-sets.

The canonical encoding names in the libiconv column of this table could be used
for probing whether glib's g_iconv_open supports this encoding on a particular
platform. 

Otherwise, the only way out would be to redesign WebCore's text codecs part, as
Alexey pointed out in comment #16.


-- 
Configure bugmail: https://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.