Closed Bug 152369 Opened 22 years ago Closed 22 years ago

can't include ISO-2022-KR as encoding char in compose window

Categories

(MailNews Core :: Internationalization, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED WONTFIX

People

(Reporter: jeesun, Assigned: nhottanscp)

Details

(Keywords: intl)

can't include ISO-2022-KR as encoding char in compose window

Steps:
1. Click on "Compose"
2. Go to View|Character coding, then select customize...
3. Select ISO-2022-KR and click on "Add", then OK out
4. Go to View|Character coding. There's no ISO-2022-KR.

Note: All other Korean encodings and other languages' encodings seem to work fine.
Keywords: intl
I am not sure the current behavior is intended or not. 
But ISO-2022-KR is an obsolete charset and should not be used to send out mails.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → WONTFIX
Then, why don't we get rid of this from the charset list?
The customize dialog is also used for other components (browser, composer, mail
view). That can be a bug. But I don't think it is worth to put effort making
mail edit customize dialog's charset list customizable independent from other
components unless we know more cases.

Marking as verified.
Status: RESOLVED → VERIFIED
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.