Bug 4577 - Fancy plugin with GTK3 seems to ignore content encoding
Summary: Fancy plugin with GTK3 seems to ignore content encoding
Status: RESOLVED FIXED
Alias: None
Product: Claws Mail
Classification: Unclassified
Component: Plugins/Fancy (show other bugs)
Version: 4.0.0
Hardware: PC Linux
: P3 normal
Assignee: users
URL:
Depends on:
Blocks:
 
Reported: 2022-03-23 00:37 UTC by Shai Berger
Modified: 2022-03-23 12:52 UTC (History)
0 users

See Also:


Attachments
Message that Fancy/GTK2 handles well but Fancy/GTK3 doesnt (23.10 KB, text/plain)
2022-03-23 00:37 UTC, Shai Berger
Details
Broken rendering with Fancy/GTK3 (Claws 4.0.0) (17.43 KB, image/png)
2022-03-23 00:39 UTC, Shai Berger
Details
Correct rendering with Fancy/GTK2 (claws 3.17.8+) (38.76 KB, image/png)
2022-03-23 00:40 UTC, Shai Berger
Details

Description Shai Berger 2022-03-23 00:37:32 UTC
Created attachment 2274 [details]
Message that Fancy/GTK2 handles well but Fancy/GTK3 doesnt

Hello,

I have received a message which uses windows-1255, which is a single-byte encoding for Hebrew. The message uses multipart/alternative, with both plaintext and HTML. The plaintext part is handled well with GTK3, but the HTML (Fancy) is broken, and seems to want to interpret it as UTF-8 -- even though the encoding is given both in the part header:

    Content-Type: text/html; charset="windows-1255"

and inside the HTML:

    <meta http-equiv="Content-Type" content="text/html; charset=windows-1255">

I'm attaching the mail itself, a picture of what current Fancy does to it, and a picture taken with an older (GTK2) version where it is rendered correctly.

Thanks, 
Shai.
Comment 1 Shai Berger 2022-03-23 00:39:29 UTC
Created attachment 2275 [details]
Broken rendering with Fancy/GTK3 (Claws 4.0.0)
Comment 2 Shai Berger 2022-03-23 00:40:58 UTC
Created attachment 2276 [details]
Correct rendering with Fancy/GTK2 (claws 3.17.8+)
Comment 3 Paul 2022-03-23 12:52:37 UTC
This is now fixed in git. Thanks for the report.

Note You need to log in before you can comment on or make changes to this bug.