Closed Bug 140360 Opened 23 years ago Closed 5 years ago

implement better error handling for Unicode conversion in mail/news

Categories

(MailNews Core :: Internationalization, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: nhottanscp, Unassigned)

References

Details

(Whiteboard: intl)

For mail/news, there are chances that we received messages which do not have charset information specified. As a result, we could encounter Unicode conversion errors because the charset we assumed is not correct. The current code bails out when Unicode decoder returns with error code. We want to change to skip invalid bytes and continue the conversion.
Target Milestone: --- → mozilla1.1beta
Blocks: 132613
*** Bug 139499 has been marked as a duplicate of this bug. ***
Target Milestone: mozilla1.1beta → ---
Product: MailNews → Core
Product: Core → MailNews Core
QA Contact: ji → i18n
Assignee: nhottanscp → nobody
Status: ASSIGNED → NEW
Whiteboard: intl

Can you imagine this is still valid?

Flags: needinfo?(mkmelin+mozilla)

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.

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.

Let's close this.

Status: NEW → RESOLVED
Closed: 5 years ago
Flags: needinfo?(mkmelin+mozilla)
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.