Bug 4676 - claws-mail-4.1.1: incorrect html decoding
Summary: claws-mail-4.1.1: incorrect html decoding
Status: RESOLVED INVALID
Alias: None
Product: Claws Mail
Classification: Unclassified
Component: Other (show other bugs)
Version: 4.1.1
Hardware: PC Linux
: P3 normal
Assignee: users
URL:
Depends on:
Blocks:
 
Reported: 2023-05-25 10:34 UTC by Yoric C°
Modified: 2023-09-12 09:08 UTC (History)
0 users

See Also:


Attachments
raw-body letter (30.89 KB, message/rfc822)
2023-05-25 10:34 UTC, Yoric C°
Details
false decoding (102.10 KB, image/jpeg)
2023-05-25 10:35 UTC, Yoric C°
Details
true decoding (184.54 KB, image/jpeg)
2023-05-25 10:35 UTC, Yoric C°
Details

Description Yoric C° 2023-05-25 10:34:00 UTC
Created attachment 2325 [details]
raw-body letter

Hello, sorry my bad English.
From the beginning of the message there are only dashes, then it is normally visible. I attach a screenshot of the incorrect and correct display and the letter itself.
Comment 1 Yoric C° 2023-05-25 10:35:03 UTC
Created attachment 2326 [details]
false decoding
Comment 2 Yoric C° 2023-05-25 10:35:43 UTC
Created attachment 2327 [details]
true decoding
Comment 3 Paul 2023-05-25 10:44:51 UTC
Looks like the part which is dashes does not use UTF-8 encoding as declared, but the rest does.
Comment 4 Paul 2023-05-25 10:50:51 UTC
When viewing the message, if you change /View/Decode/Auto-detect to /View/Decode/Quoted-printable you will see the dashs displayed correctly.

It /appears/ that the auto-detection of message in encoding is failing in Claws Mail, (but only for the opening section). However, I cannot rule out a problem with the message itself at this point.
Comment 5 Paul 2023-09-12 09:01:50 UTC
Sorry for the tardy response.

The problem is caused by invalid UTF-8 in the header of the html attachment:

  <!--[if !mso]><!--><meta http-equiv="X-UA-Compatible" content="IE�ge" /><!--<![endif]-->
  <meta name="viewport" content="width�vice-width" />
Comment 6 Paul 2023-09-12 09:08:10 UTC
In fact, I should also have said that the paragraphs which are displayed as underscores/dashes also contain invalid UTF-8, hence the reason that those sections cannot be displayed

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