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

VERIFIED WONTFIX

Status

MailNews Core
Internationalization
VERIFIED WONTFIX
16 years ago
10 years ago

People

(Reporter: Jeesun Cho, Assigned: nhottanscp)

Tracking

({intl})

Trunk
x86
Windows XP

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

16 years ago
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.
(Reporter)

Updated

16 years ago
Keywords: intl
(Assignee)

Comment 1

16 years ago
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
Last Resolved: 16 years ago
Resolution: --- → WONTFIX
(Reporter)

Comment 2

16 years ago
Then, why don't we get rid of this from the charset list?
(Assignee)

Comment 3

16 years ago
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.

(Reporter)

Comment 4

16 years ago
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.