43915 - A check mark for the current message charset is not displayed

Status: VERIFIED DUPLICATE of bug 28869

(MailNews Core :: Internationalization, defect, P3)

Description

[Katsuhiko Momoi]

** Observed with 6/26/2000 Win32 build **

Now that the charset override is working, we want to test this 
feature fully. If a message is showing incorrectly or as garbage
characters, the user should have a chance to override the MIME
charset information contained in the message headers with the
one he/she chooses.

For the override feature to work properly, I need to see the
correct current charset info with a checkmark next to it when I
open the View | Character Coding menu. I can see the chechmark
correctly when I use the Browser window, but on the Messenger 
window, all I see is one menu item at the bottom, Western 
(ISO-8859-1) no matter what language message I am displaying. 
There is no checkmark next to the Western item, either.

The correct feedback on the current charset is an essential 
part of the charset override feature which has been already 
implemented. Not having this makes the charset override feature
very confusing to the user. 

The correct charset feedback is also an essential part of the 
general charset menu UE spec as described in the following
document written last year and accepted by all concerned. The user
is now used to this behavior/feedback in the Browser. 
It is also part of international PR2 requirements.

http://www.mozilla.org/projects/intl/uidocs/browsercharmenu.html

Not having the same UI/UE for Mail is very confusing, unworkable,
and unaaceptable for PR2. We have had this requirement for a
long time. We should now fix this bug.

Comment 1

[Katsuhiko Momoi]

Nominating for nsbeta2.
This also nearly blocks proper testing of charset
override feature. 

Comment 2

[bobj]

This is the user manifestation of bug 28869.
I maded it dependent upon bug 28869.  Should we mark it dup?

Comment 3

[Scott MacGregor]

I still don't understand why this isn't a dup of 28869. Sounds like you are
asking for the same thing? 

Comment 4

[bobj]

mscott,

See my previous comment.  I agree that the fix fro bug 28869 is the same and
this could be marked a dup.  The only difference is this summary describes
the user level manifestation (which is what we need to work) whereas the
summary of 28869 describes the underlying specific implementation.

I renominated 28869 with more justification and reassigned it to nhotta
assuming he can fix it after talking to you.

momoi and nhotta, I'll make this a dup.  If you disagree, change it back
and explain why.

*** This bug has been marked as a duplicate of 28869 ***

Comment 5

[Katsuhiko Momoi]

Bob, if we can work with Bug 28869 to correct the
problems described in this report, that is fine with me. 
The sticking point was that the other bug was marked as 
[Feature]. The perspective of this bug is that it is a bug,
not a feature. 

Comment 6

[Katsuhiko Momoi]

The other bug is now nsbeta2+ and it makes me feel good that the
concerns expressed here will be addressed there. 
Marking it verified as a duplicate.