After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 74854 - We need to respect the charset content in received headers
We need to respect the charset content in received headers
Status: RESOLVED DUPLICATE of bug 53465
Product: Pan
Classification: Other
Component: general
0.11.2.90
Other All
: Normal normal
: 0.12.0
Assigned To: Charles Kerr
Charles Kerr
Depends on:
Blocks:
 
 
Reported: 2002-03-15 22:14 UTC by Charles Kerr
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Charles Kerr 2002-03-15 22:14:14 UTC
This should be earmarked for Pan 0.12.0.

<charles> about charsets
<charles> someone posts a message with a mime header specifying a charset.
<fejj> right
<fejj> that's the charset for the particular mime part
<charles> To convert that text to utf8 for GtkTextView, I should _not_ use
          g_locale_to_utf8, because it converts from the wrong charset,
          right?
<fejj> right
<fejj> you want to convert using the charset specified in the mime part
       header as the base
<fejj> s/base/source charset
<fejj> dest charset being UTF-8
<fejj> you may also want to get the content-object from the mime-part
       and then write that to a filtered stream that will convert from
       src charset to UTF-8
<fejj> this will cut down a lot on memory usage
<fejj> since it won't have to equivalently strdup the message
<charles> so I want to go through g_mime_iconv() rather than g_convert()
          for these, right?
<fejj> for mime-part content, yes
<charles> (or the filter, which goes through g_mime_iconv())
<fejj> right
Comment 1 Charles Kerr 2002-04-05 20:14:13 UTC
gmime is doing this now.
Comment 2 Charles Kerr 2002-06-11 16:15:24 UTC

*** This bug has been marked as a duplicate of 53465 ***