Closed Bug 5326 Opened 25 years ago Closed 25 years ago

Message headers are not displayed for the msgs encoded in charsets for which Unicode converters don't exist yet

Categories

(MailNews Core :: Internationalization, defect, P3)

x86
Windows NT
defect

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: momoi, Assigned: nhottanscp)

Details

** Observed with 4/20/99 Win32 build **

Using Communicator 4.51 I sent several msgs in Cyrillic.
They are received by the POP account and downloaded -- they are
there in the Inbox file itself, but the thread pane does not
show that they exist. One would think that undecodable
strings should at least show in the header pane.

Perhaps the problem is caused by there being no Unicode/KOI8-R
converter in the source. This is not confirmed since I have not
looked at other mail charsets for which the converters are not yet
ready.
Status: NEW → ASSIGNED
Target Milestone: M6
Probably I should return the original string for the case.
This means not decoded MIME string will appear. Is this acceptable?
Cyrillic mail header &bod display has been working for the
past 2 days or so. I guess the converter has gotten into the
code. The one I had sent but did not show up before in my mailbox
are now there and displayed correctly.
Do we still need to fix this or not?
I tried one of the charsets not included in the current build and
which can be easily tested, i.e. UTF-7.
This message with header and body in UTF-7 actually displays in
the mailbox though the proper converters are not there.

Given this fact, I'm inclined to think that this is working now.
Let me resolve this as Worksforme unless you have an objectio to it.
I have no objection for resolving this.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
Status: RESOLVED → VERIFIED
Resolved as Worksforme and verified as such also.
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.