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.
Summary: Need a charset manager service → Charset Handling- Need a charset manager service
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.
Hardcoded workaround for M4. Fix this for M5.
Moved to M6 to give Cata time to assist Nisheeth on external DTD support in the XML parser.
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.
Summary: Charset Handling- Need a charset manager service → Charset Handling - Need a charset manager service
Target Milestone: M9 → M11
Will implement after coming back from vacation, as an extensibility application.
This is part of the extensibility work scheduled for M11. I don't know why this was still marked M10...
(target milestone is M11 or M12 - add to mail beta tracking bug)
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.
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);
Status: ASSIGNED → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → FIXED
It's done. Finally.
Naoki. This looks like somthing you should be verifying. Sending it your way.
QA Contact: momoi → nhotta
You need to log in before you can comment on or make changes to this bug.