Incorrect encoded subject line in New message window and in Message pane
Categories
(Thunderbird :: Mail Window Front End, defect)
Tracking
(Not tracked)
People
(Reporter: blomman, Unassigned)
Details
Attachments
(1 file)
|
53.91 KB,
image/png
|
Details |
may2023-Thunderbird-mail-subject-bug.png
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/113.0
Steps to reproduce:
Sending mail from a PHP script saved as ANSI (Western European 1252).
The mail has Content-Type text/plain; charset=ISO-8859-1
The mail contains the german and swedish characters åäöÅÄÖ öäüß,
both in the mail body and in the subject line.
NOTE: this works in all tested mail software EXCEPT Thunderbird.
(See attached screen dump).
Actual results:
The subject line in Message pane, AND in New message window, is incorrect.
The characters åäöÅÄÖ öäüß are not viewed.
BUT subject lines in the Folder panes are fine.
(See attached screen dump).
Expected results:
The subject line in Message pane and in New message window
should be viewed correctly encoded,
as they do in the Folder panes of Thunderbird.
|
||
Comment 1•2 years ago
|
||
Most likely the MIME encoding is missing in the subject header.
If in doubt, please upload a example email.
Yes, but the subject lines are correct in the Thunderbird Folder panes.
So why not in the Message pane as well? (and the New message window).
It looks like someone at Mozilla started to fix this, but only got halfway through.
It's much easier to fix this issue in ONE place (Thunderbird), than modify all affected scripts around the world.
|
|
||
Comment 3•2 years ago
|
||
(In reply to David2023 from comment #2)
Yes, but the subject lines are correct in the Thunderbird Folder panes.
Not in all cases. See Bug 1779070 comment #10.
It looks like someone at Mozilla started to fix this, but only got halfway through.
It's the other way around. TB has changed the charset handling to UTF-8. An individual presetting of the charset is no longer supported.
It's much easier to fix this issue in ONE place (Thunderbird), than modify all affected scripts around the world.
8-bit characters in the header have never been allowed. If this requirement is ever dropped, it will only be in favor of UTF-8. Anything else is out of date.
So if you can't put MIME encoding in your scripts, use UTF-8.
THE FACT is that every other tested e-mail client works fine
except Thunderbird.
Other e-mail clients are fully compatible with other character encoding than utf-8.
But Thunderbird is not.
So if Thunderbird can't fix this, we'll use another e-mail client. That's the easiest solution.
Description
•