Closed
Bug 305498
Opened 20 years ago
Closed 20 years ago
UTF-8 e-mail encoding is not working
Categories
(Bugzilla :: Email Notifications, defect)
Tracking
()
RESOLVED
FIXED
Bugzilla 2.22
People
(Reporter: cedric.caron, Assigned: cedric.caron)
Details
Attachments
(1 file)
|
973 bytes,
patch
|
glob
:
review+
|
Details | Diff | Splinter Review |
When the UTF-8 option is enabled and the text of the e-mail contains 8bit
caracters the e-mail is not corectly formated and the non ascii catacters are
displayed as =XX whwre XX is an hex number.
this is a litle sample:
dans le reports "fournisseurs", coordonn=C3=A9es d=C3=A9taill=C3=A9es de l'=
agent : les
commentaires ne s'affichent pas sur le document d'impression.
| Assignee | ||
Comment 1•20 years ago
|
||
the replace function only seems to replace an existing entry.
| Assignee | ||
Updated•20 years ago
|
Attachment #193657 -
Flags: review?
Comment on attachment 193657 [details] [diff] [review]
Patch v.1
> the replace function only seems to replace an existing entry.
weird, the docs for replace say "If the tag does not appear in the header then
a new line will be appended to the header."
i'd be interested to know what version of Mail::Header you have.
assuming you've testing it, r=glob
Attachment #193657 -
Flags: review? → review+
| Assignee | ||
Comment 3•20 years ago
|
||
Mail::Header 1.67
| Assignee | ||
Comment 4•20 years ago
|
||
I tested the code but I don't know if this code will corectly replace an
existing field (the perl eeprom conected to my brain is a beta version ;-)
Updated•20 years ago
|
Flags: approval? → approval+
Updated•20 years ago
|
Target Milestone: --- → Bugzilla 2.22
Comment 5•20 years ago
|
||
(In reply to comment #4)
> I tested the code but I don't know if this code will corectly replace an
> existing field (the perl eeprom conected to my brain is a beta version ;-)
Does this mean this patch needs more testing? Or can we go with the checkin?
Status: NEW → ASSIGNED
| Assignee | ||
Comment 6•20 years ago
|
||
(In reply to comment #5)
> Does this mean this patch needs more testing? Or can we go with the checkin?
I made aditional testing. everything seems ok. the function replace any
existing field with the new one.
Comment 7•20 years ago
|
||
Checking in Bugzilla/BugMail.pm;
/cvsroot/mozilla/webtools/bugzilla/Bugzilla/BugMail.pm,v <-- BugMail.pm
new revision: 1.50; previous revision: 1.49
done
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•