Charset Handling - Need a charset manager service

RESOLVED FIXED in M13

Status

MailNews Core
Internationalization
P3
normal
RESOLVED FIXED
19 years ago
9 years ago

People

(Reporter: nhottanscp, Assigned: cata)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: rev'd by naoki, ready to go in)

(Reporter)

Description

19 years ago
Need a charset manager service to map charset to mail charset (e.g. Shift_JIS to
ISO-2022-JP).
In addition to the mapping, the service should provide the MIME encoding type
('B' or 'Q') for the mail charset.
They are necessary for sending Japanese mail.
(Reporter)

Updated

19 years ago
Target Milestone: M4
(Assignee)

Updated

19 years ago
Status: NEW → ASSIGNED

Updated

19 years ago
Summary: Need a charset manager service → Charset Handling- Need a charset manager service

Comment 1

19 years ago
Naoki wrote in email:
  This is needed for M4 to send mail. We need at least an interface.
  We may use some hard coded values for the implementation for now.

Updated

19 years ago
Target Milestone: M4 → M5

Comment 2

19 years ago
Hardcoded workaround for M4.  Fix this for M5.

Updated

18 years ago
Target Milestone: M5 → M6

Comment 3

18 years ago
Moved to M6 to give Cata time to assist Nisheeth on external DTD support
in the XML parser.

Comment 4

18 years ago
nhotta wrote:
  This issue is related to header sending only. Send body won't be
  affected, viewing should work for other charsets, just to clarify.
(Assignee)

Updated

18 years ago
Target Milestone: M6 → M7

Updated

18 years ago
Target Milestone: M7 → M8

Updated

18 years ago
Target Milestone: M8 → M9
(Assignee)

Updated

18 years ago
Summary: Charset Handling- Need a charset manager service → Charset Handling - Need a charset manager service
Target Milestone: M9 → M11
(Assignee)

Comment 5

18 years ago
Will implement after coming back from vacation, as an extensibility application.
(Assignee)

Updated

18 years ago
Target Milestone: M11 → M10
(Assignee)

Updated

18 years ago
Target Milestone: M10 → M11
(Assignee)

Comment 6

18 years ago
This is part of the extensibility work scheduled for M11. I don't know why this
was still marked M10...

Updated

18 years ago
Blocks: 11091

Comment 7

18 years ago
(target milestone is M11 or M12 - add to mail beta tracking bug)
(Assignee)

Updated

18 years ago
Target Milestone: M11 → M12
(Assignee)

Updated

18 years ago
Target Milestone: M12 → M13

Comment 8

18 years ago
nhotta,
cata says most of the code is already done and to add the mailcharset
mapping, he just needs to add a stringbundle.  Please work with cata
to nail down the specifics.
(Reporter)

Comment 9

18 years ago
Interfaces I need,

// return charset name
string MIMEMailCharset(in string charset);
// return MIME header encoding method (e.g. "B", "Q")
string MIMEHeaderEncodingMethod(in string charset);
(Assignee)

Updated

18 years ago
Whiteboard: rev'd by naoki, ready to go in
(Assignee)

Updated

18 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → FIXED
(Assignee)

Comment 10

18 years ago
It's done. Finally.
(Assignee)

Comment 11

18 years ago
Fixed.

Comment 12

18 years ago
Naoki. This looks like somthing you should be verifying.
Sending it your way.
QA Contact: momoi → nhotta
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.