Content not rendering correctly (even when "Repair Text Encoding" is clicked)
Categories
(Thunderbird :: Message Reader UI, defect)
Tracking
(Not tracked)
People
(Reporter: github, Unassigned)
Details
Attachments
(1 file)
95.90 KB,
image/png
|
Details |
Steps to reproduce:
Open an email and view it
Actual results:
The message is rendered with symbols (unicode replacement characters)
Expected results:
The message should get rendered properly. In this case, a double whitespace causes the encoding to not render properly. This was tested against Gmail and Forward Email services, and in both cases this is a client bug.
Here is the raw test email file that you can reproduce this with:
https://gist.github.com/titanism/2ee57f52f2e02c7d2c5e94e5bb6c672b
Comment 2•1 year ago
|
||
Renders fine to me (on linux/trunk). Maybe the font you're using doesn't have a (good) char for that...
In Support Forum, I would usually advise you try this:
- Settings > General
- Scroll down to bottom and clickon 'Config Editor'
- In search type: mime
- look for : mail.strictly_mime
- Click on far right toggle icon to change it from "false" to true.
Does this fix the problem?
In general, all spaces but the last space in a multi-space sequence are replaced by a NBSP. Unless that gets mangled on the way, it will render properly. Your message from the ZIP file, when imported into TB, renders properly. Look at it in a hex editor, between well.
and We
there are three ASCII spaces. So the message you submitted is not the message that displays badly for you.
@github: Any update here? The message in the ZIP is 100% ASCII and displays fine when imported.
@Anje: Pref mail.strictly_mime affects the CTE when a message is sent (if forces quoted-printable which can avoid encoding issues), it doesn't affect or repair message display.
Updated•11 months ago
|
Resolved per whiteboard
Description
•