Closed Bug 288484 Opened 20 years ago Closed 11 years ago

Character Encoding menu should have Unicode submenu (inconsistent with Firefox)

Categories

(Thunderbird :: Mail Window Front End, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: musiphil, Unassigned)

Details

Attachments

(2 files)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2
Build Identifier: Mozilla Thunderbird version 1.0.2 (20050317)

The Character Encoding menu doesn't have any Unicode encodings other than
UTF-16, and this is strange; you cannot set the character encoding to UTF-8
manually. It should include other Unicode encodings such as UTF-8, just as
Mozilla and Firefox do.

Reproducible: Always

Steps to Reproduce:
has a separate Unicode submenu
has no separate Unicode submenu
Note that you can get those other Unicode encodings into the menu by selecting:
  View | Character Encoding | Customize List...
and adding the desired encodings to the list.  (I think this requires a resart 
to actually take effect.)  They will appear in the main list, rather than in a 
submenu.

xref bug 253575.
Severity: normal → minor
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: Character Encoding menu should have other Unicode encodings such as UTF-8 → Character Encoding menu should have all Unicode encodings (inconsistent with Firefox)
Version: unspecified → Trunk
If I'm not mistaken, UTF16 can't be used in email because that would contain the 0 values in the text stream, unless those strings are encoded within Base64 MIME parts. And on the other hand, only UTF8 is recommended to encode email for international usage:
http://www.imc.org/mail-i18n.html

Personally, I've never come across emails encoded in UTF16. So this menu option is purely misleading and might even lead to error. I suggest raising this bug's severity to normal.
Severity: minor → normal
(In reply to comment #4)
> UTF16 [...] menu option is purely misleading and might even lead to error.
> I suggest raising this bug's severity to normal.

This bug is not at all about what you're describing.  In fact, it sounds like you're talking about removing something from the Compose Window encoding menu; this bug is about adding to the Message Window encoding menu.
Summary: Character Encoding menu should have all Unicode encodings (inconsistent with Firefox) → Character Encoding menu should have Unicode submenu (inconsistent with Firefox)
No, no, I was really talking about the View menu in TB main window.  The one in Compose window is put within Option menu.

Actually, the encoding specified to view the message is used as the encoding when we reply to it. The possibility of leading to an error is of course very small, but, we'd better try to avoid error in the first place, no?

OTOH, I don't think it's necessary to keep consistency with Firefox.  But as you like ...
QA Contact: front-end
Assignee: mscott → nobody
This got fixed some time ago. -> WFM
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: