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 88670 - Pan ignores charset setting for article body
Pan ignores charset setting for article body
Status: RESOLVED FIXED
Product: Pan
Classification: Other
Component: general
pre-0.13.0 betas
Other Linux
: High major
: 0.13.0
Assigned To: Charles Kerr
Charles Kerr
Depends on:
Blocks:
 
 
Reported: 2002-07-20 06:49 UTC by Martin Tomasek
Modified: 2006-06-18 04:56 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
bad headers (404 bytes, text/plain)
2002-07-21 00:25 UTC, Martin Tomasek
Details

Description Martin Tomasek 2002-07-20 06:49:23 UTC
(I'm using CVS version)

Pan ignores charset setting for article body. Headers are set correcty like
this:

MIME-Version: 1.0                                                         
     
Content-Type: text/plain; charset=ISO-8859-2 

But body is still in utf-8.
Comment 1 Christophe Lambin 2002-07-20 12:15:50 UTC
I can't work out what you mean here. Are you reading an article ? Or
writing a new article ?  If reading, could you give me a group +
message id where you're seeing this ?
Comment 2 Martin Tomasek 2002-07-21 00:23:10 UTC
I'm writing new article. It contains some czech characters.
Comment 3 Martin Tomasek 2002-07-21 00:25:33 UTC
Created attachment 9985 [details]
bad headers
Comment 4 Martin Tomasek 2002-07-21 00:36:24 UTC
I attached one example. Charset is set to iso-8859-2 in pan, which is
reflected in header. Article body uses utf-8. (btw, in attached file
comment: replace/bad headers/bad body charset example/ :-)
Comment 5 Charles Kerr 2002-07-23 05:39:30 UTC
When creating the GMimeMessage in message-header.c, we should
convert the article body before passing it to gmime.
Comment 6 Charles Kerr 2002-07-23 17:47:06 UTC
Marking this as depending on 85289: they are variations of the same
bug, but 88670 will need extra testing to verify it's working.

The core problem is that messages coming out of the Compose window
are kept in utf8, rather than encoded into the user-specified
charset.
Comment 7 Charles Kerr 2002-07-28 04:05:25 UTC
Prioritizing remaining 0.13.0 tasks
Comment 8 Charles Kerr 2002-07-28 04:10:33 UTC
marking crashers & other server problems as "major" severity
Comment 9 Jeffrey Stedfast 2002-07-30 01:32:06 UTC
or just give a filtered-stream to GMime (with a charset filter to do
the conversion from UTF-8 to iso-8859-2 in this case).
Comment 10 Charles Kerr 2002-07-30 22:07:44 UTC
<chris_> I think you can really only do the conversion from utf-8 to
charset
<chris_> just before you send it: it gets put in pan.sendlater first.
<chris_> so, it needs to be edited from there, we'd need to reconvert
<chris_> from charset to utf-8.
<charles> task-post.c::build_nntp_message() builds the char* we pass
to the server, from a GMimeMessage
<charles> That looks like a good candidate, s.t. it doesn't affect the
original GMimeMessage
<chris_> so, you just need to make sure the charset is available there.
&#65533; chris_/#pan curses signals.
<charles> working on that in gui-headers, too.  I probably should
write a pan_g_mime_message_get_group s.t. it's just in one place
Comment 11 Charles Kerr 2002-08-02 21:07:48 UTC
Fixed in cvs head.