Open
Bug 238016
Opened 21 years ago
Updated 2 years ago
ACE En-/Decode domainparts in email addresses for display and assembling mail headers
Categories
(MailNews Core :: Internationalization, defect)
MailNews Core
Internationalization
Tracking
(Not tracked)
NEW
People
(Reporter: ch.ey, Unassigned)
References
Details
Attachments
(1 file)
21.00 KB,
patch
|
Details | Diff | Splinter Review |
Additionally to handle UTF-8 strings for mail and hostnames in the background (bug 235312), domainparts of email addresses have to be en- and decoded when sending resp. presented to the user.
Reporter | ||
Comment 1•21 years ago
|
||
This patch uses the new function EncodeUTF8Mailaddresses(), called at one point in nsMsgComposeAndSend::SetMimeHeader() to encode From:, To: Reply-To:, Cc: and Bcc: to ACE. That what the first three files are about. All the rest is about decode ACE coded mail addresses to UTF-8 to present them to the user. The actual work is done in the new function DecodeAceMailaddresses() called in MIME_DecodeMimeHeader(). It sits there because this is a function which is called for mime-decoding of each address to be displayed. The problem is, that it is called very often and also for headers other the one we're interested in. So I had to introduce a boolean parameter decodeACE. The rest of the patch consists of modifications to callers of MIME_DecodeMimeHeader() and callers of such functions. No big thing but we've a bunch of them.
Updated•20 years ago
|
Product: MailNews → Core
Updated•17 years ago
|
QA Contact: marina → localization
Assignee | ||
Updated•16 years ago
|
Product: Core → MailNews Core
Comment 2•16 years ago
|
||
Christian, any interest in reviving this patch for TB 3.0 beta 2?
Reporter | ||
Comment 3•16 years ago
|
||
I'm not sure anymore. Have ACE coded addressed ever been allowed in mail headers? Decoding them from such incoming mails might be reasonable if there are other clients around which produce them. But I don't think it's right for TB to generate those. RFC 5335 and 5336 specify other ways to handle internationalized Email Headers. But I don't have time for that anyway, sorry.
Comment 4•16 years ago
|
||
(In reply to comment #3) > RFC 5335 and 5336 specify other ways to handle internationalized Email Headers. These are part of the eai working groups current work, most of which is in draft at the moment: http://tools.ietf.org/wg/eai/
Updated•16 years ago
|
QA Contact: localization → i18n
Comment 7•11 years ago
|
||
(In reply to :aceman from comment #5) > Is this still needed after bug 127399? Given bug 918901 (just duped to this bug), yes.
Assignee: ch.ey → nobody
Flags: needinfo?(mnyromyr)
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•