Open
Bug 145674
Opened 22 years ago
Updated 2 years ago
Store text attachment with character encoding option
Categories
(MailNews Core :: Internationalization, enhancement)
Tracking
(Not tracked)
NEW
People
(Reporter: masaki.katakai, Assigned: smontagu)
Details
I believe this issue had been discussed before but I'm sorry I could not find the exact bug id for this. Please close as dup if the same bug already exists. If people sends e-mail with EUC or SJIS plain text in mail attachment, and receiver tries to store the attachmen to the file, currently the file is stored as ISO-2022-JP. But usually receiver wants the file as the original character encoding. After the file is stored as ISO-2022-JP, if receiver is end user, I believe he/she can not find the way how to display japanese properly. I can not ask such enduser to use iconv. Is there any good preference to set character encoding for storing attachment? For example, ISO-2022-JP is japanese, running locale is EUC, then store the attachment is EUC. We need to have preference of character encoding like composer. But it would not be good enough. We need to provide the default value such as Japanese-EUC for suggestion.
Updated•22 years ago
|
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla1.2alpha
Updated•22 years ago
|
Target Milestone: mozilla1.2alpha → ---
Updated•20 years ago
|
Product: MailNews → Core
Updated•16 years ago
|
Product: Core → MailNews Core
Updated•16 years ago
|
Assignee: nhottanscp → smontagu
QA Contact: ji → mailnews.i18n
Summary: RFE: Store text attachment with character encoding option → Store text attachment with character encoding option
Updated•16 years ago
|
Status: ASSIGNED → NEW
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•