UTF-8 e-mail encoding is not working

RESOLVED FIXED in Bugzilla 2.22

Status

()

RESOLVED FIXED
13 years ago
11 years ago

People

(Reporter: cedric.caron, Assigned: cedric.caron)

Tracking

2.21
Bugzilla 2.22
Bug Flags:
approval +

Details

Attachments

(1 attachment)

(Assignee)

Description

13 years ago
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

13 years ago
Created attachment 193657 [details] [diff] [review]
Patch v.1

the replace function only seems to replace an existing entry.
(Assignee)

Updated

13 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: email-notifications → cedric.caron
Flags: approval?
(Assignee)

Comment 3

13 years ago
Mail::Header 1.67
(Assignee)

Comment 4

13 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 ;-)
Flags: approval? → approval+
Target Milestone: --- → Bugzilla 2.22

Comment 5

13 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

13 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

13 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
Last Resolved: 13 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.