implement better error handling for Unicode conversion in mail/news
Categories
(MailNews Core :: Internationalization, defect)
Tracking
(Not tracked)
People
(Reporter: nhottanscp, Unassigned)
References
Details
(Whiteboard: intl)
| Reporter | ||
Comment 1•23 years ago
|
||
| Reporter | ||
Comment 2•23 years ago
|
||
| Reporter | ||
Updated•23 years ago
|
| Reporter | ||
Comment 3•23 years ago
|
||
| Reporter | ||
Updated•23 years ago
|
Updated•21 years ago
|
| Assignee | ||
Updated•17 years ago
|
Updated•16 years ago
|
Updated•12 years ago
|
Comment 5•5 years ago
|
||
I don't think this problem is serious enough today although I don't rule out occasional error conversion.
(I think more clients are quiet well behaved as far as character set usage is concerned, and I don't think
I encounter such problems often with NEW e-mails any more.
Of course, if I go back in time and look at old e-mail messages, there may be such problematic messages, but
I know they are not that many and I know they are broken and so am OK to deal with such messages with separate editor, etc. to
salvage the content.)
Just my current take on the issue.
Comment 6•5 years ago
|
||
I don't think this is still an issue because no nsMsgI18NConvertFromUnicode callers set reportUencNoMapping to true and DecodeWithoutBOMHandling will never return a failure nsresult except OOM.
Comment 7•5 years ago
|
||
Let's close this.
Description
•