"�(U+FFFD)" is inserted in the subject line of the email.
Categories
(Thunderbird :: Mail Window Front End, defect)
Tracking
(Not tracked)
People
(Reporter: tamatsuna, Unassigned)
References
()
Details
Attachments
(1 file)
|
22.21 KB,
image/png
|
Details |
2020-07-13_14h48_03.png
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.116 Safari/537.36
Steps to reproduce:
I just received an email from someone else.
Actual results:
" (U+FFFD)" is inserted in the subject line.
For example, like this
testtesttest → testtesttest
Expected results:
It's been discussed (and wrangled :) ) on Japanese forums
for quite some time now, but There seems to be a bug
in the mail decoding of IS-2022-JP.
Apparently it's not so good for security.
Japanese users are having a lot of trouble,
so I want you to do something about it.
|
||
Comment 2•5 years ago
|
||
Bug 1508136? ISO-2022-JP text is displayed with a replacement character <?> if it contains a zero-length ASCII run due to concatenation
(In reply to Wayne Mery (:wsmwk) from comment #2)
Bug 1508136? ISO-2022-JP text is displayed with a replacement character <?> if it contains a zero-length ASCII run due to concatenation
I know about that.
But it's just very inconvenient to
have strange characters added.
We wish it will be fixed.
(In reply to Magnus Melin [:mkmelin] from comment #4)
So this is the same as bug 1508136?
I think so, too.
However, it doesn't matter where the email is sent from, it inserts strange characters.
This only happens in Thunderbird.
The bug has been neglected for a long time, which is one of the reasons why Thunderbird is not used in Japan.
|
|
||
Comment 6•5 years ago
|
||
Thanks for the feedback.
... is one of the reasons why Thunderbird is not used in Japan.
Actually, IIRC Japanese locale is in the top 10 of translations used.
|
||
Comment 7•5 years ago
|
||
In the past, I noticed examples of Japanese file name of an attachment
having a strange 0xFFFD in the middle of its pathnames.
Some of them might be caused by the same underlying problem.
(Not all of them.: I distinctively recall that some composition sequence used by Apple did not produce desired visual display on Windows.)
I can't find the bugzilla entry handy, but I now feel at least some issues I saw might be quite similar to the issue here (aside from Apple's composition sequence problem.)
|
|
||
Comment 8•5 years ago
|
||
(In reply to ISHIKAWA, Chiaki from comment #7)
In the past, I noticed examples of Japanese file name of an attachment
having a strange 0xFFFD in the middle of its pathnames.
Some of them might be caused by the same underlying problem.
(Not all of them.: I distinctively recall that some composition sequence used by Apple did not produce desired visual display on Windows.)I can't find the bugzilla entry handy, but I now feel at least some issues I saw might be quite similar to the issue here (aside from Apple's composition sequence problem.)
The particular Apple issue was in https://bugzilla.mozilla.org/show_bug.cgi?id=1258613
Based on my finding and Jonathan Kew, I am afraid that bug has nothing to do with this issue although the final symptom of having 0xFFFD out of nowhere looks superficially the same.
Description
•