Closed Bug 166818 Opened 19 years ago Closed 6 years ago

Cannot choose US-ASCII under View / Character Coding in reply or followup

Categories

(MailNews Core :: Composition, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: 3.14, Unassigned)

Details

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1b) Gecko/2002090311

When answering to an e-mail or a posting I cannot choose US-ASCII for character
coding, even though the text consited only of US-ASCII characters.

Related: Bug 53147 RFE: charset detection for replying message

pi
What do you mean by "I cannot choose US-ASCII for character
coding"? Can you explain exactly what you are doing?
Sure. When composing a reply or followup you can change the charset of the reply
(to change whatever Mozilla found by itself). I am not able to set the charset
to US-ASCII.

pi
Mozilla does the 7bit check before sending out, if the body text is ASCII only
then the message is actually sent out as US-ASCII.
You are right, I am not sure, though, if that did work correctly when I reported
the bug. Anyways, I find it pretty confusing, that I cannot "force" ASCII. Even,
if the reply is ASCII right away, view character coding does not say so.

pi
US-ASCII is a subset of ISO-8859-1. We do not include "US-ASCII" in UI (i.e.
charset menu) since it is redundant (and the user would be confused if we add
another Western charset). That is consistent in our browser also other mailer
like outlook express.
US-ASCII is a subset of most charsets (ISO-8859-*, utf-8, windows* and more).
I'd expect that the posting will use the charset which is displayed. So it is
confusing to do something else.

pi
Product: MailNews → Core
Severity: normal → enhancement
OS: Linux → All
Hardware: PC → All
Assignee: ducarroz → nobody
QA Contact: esther → composition
Product: Core → MailNews Core
You don't want to send charset=US-ASCII because some clients silently do bad things with that.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.