Closed Bug 117956 Opened 18 years ago Closed 18 years ago
Non-latin attachment name sent from Drafts is displaying garbled
183.68 KB, image/jpeg
Changed to use a default charset for non forward case, if we cannot find a charset in the header or the override is set. Also removed unnecessary conversion to UTF-8.
2.84 KB, patch
|Details | Diff | Splinter Review|
*** observed with 2002-01-03 build *** Steps to reproduce: - have a non-latin1 message in the Drafts folder that was forwarded as an attachment( i used Central European-8859-2 and ISO-2022-jp); - select the message; - click on the "Edit" drafts button; //note that at this point the attachment name on the envelpe is quoted correctly; - send message from Drafts; - get message and note that the attachment name displays as ((( or ????
it is present in 6.2
Cc to ducarroz, is there any special handling for a file name sent by Draft folder?
Wierd, I don't have a clue about what could append!
The screen shot looks like a forward as inline. Is that really a forward as attachment?
This is a forward as attachment.
changing qa contact
QA Contact: ji → marina
This can be fixed with the patch of bug 66098 (and the depending bug) and a little change to mimedraft.cpp. Also seem to fix the edit as new bug.
Depends on: 66098
The patch also needs to take care the override case.
Comment on attachment 68606 [details] [diff] [review] Changed to use a default charset for non forward case, if we cannot find a charset in the header or the override is set. Also removed unnecessary conversion to UTF-8. Looks good. R=ducarroz
Attachment #68606 - Flags: review+
Comment on attachment 68606 [details] [diff] [review] Changed to use a default charset for non forward case, if we cannot find a charset in the header or the override is set. Also removed unnecessary conversion to UTF-8. sr=bienvenu
Attachment #68606 - Flags: superreview+
checked in the patch but need bug 110689 to get the folder charset
depends on bug 110689
Target Milestone: mozilla0.9.9 → mozilla1.0
Please try tomorrow's build. I think this is fixed by bug 66098.
Mark as fixed, please verify using the trunk.
Status: ASSIGNED → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
same problem with the 2002-04-18-03 trunk build. reopening.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
How about the branch?
the display in the branch is Ok , except i encounter bug 136938 that got fixed but is not in the build i am looking at now.
i got hit by bug 110729 ( non-ascii mail displaying garbled after viewing pdf file), so i am going back to fixed resolution.
Status: REOPENED → RESOLVED
Closed: 18 years ago → 18 years ago
Resolution: --- → FIXED
verified with 2002-04-23 build
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.