Closed
Bug 43689
Opened 24 years ago
Closed 23 years ago
Attachment filename in Ja is displayed as raw utf-8 string on Open/Save attachment dialog window
Categories
(MailNews Core :: Internationalization, defect, P3)
MailNews Core
Internationalization
Tracking
(Not tracked)
VERIFIED
FIXED
mozilla0.9.9
People
(Reporter: ji, Assigned: mscott)
References
Details
(Keywords: intl)
Attachments
(5 files, 1 obsolete file)
28 bytes,
text/plain
|
Details | |
16.48 KB,
image/jpeg
|
Details | |
7.72 KB,
image/gif
|
Details | |
24.82 KB,
image/jpeg
|
Details | |
3.22 KB,
patch
|
law
:
review+
sspitzer
:
superreview+
|
Details | Diff | Splinter Review |
Build: 2000062309 comm build. On the Open/Save attachment dialog window, the attachment filename in Japanese is displayed as a raw UTF-8 string. Steps of reproduce: 1. Launch Mail. 2. Compose a mail, attach a file with the filename in Japanese, sent the mail to the testing account itself after selecting View | Character Coding | Japanese (ISO-2022-JP) 3. After receiving the mail, click on the attachment icon and select the attachment file. The Open/Save Attachment dialog window comes up. On that window the attachment file has its Ja filename displayed as a raw utf-8 string.
Comment 3•24 years ago
|
||
Reassign to mscott.
Assignee: nhotta → mscott
Summary: Attachment filename in Ja is displayed as raw utf-8 string on Open/Save attachment dialog window. → Attachment filename in Ja is displayed as raw utf-8 string on Open/Save attachment dialog window.
Assignee | ||
Comment 5•24 years ago
|
||
jefft was the actual author of this dialog. Over to Jeff.
Comment 6•24 years ago
|
||
Per i18n/mail triage meeting, this bug is classified as [nsbeta3-]. There seems to be little usability impact from this bug. In future, we might simply not show the file name in this dialog window. Qa contact to ji.
QA Contact: momoi → ji
Whiteboard: [nsbeta3-]
Comment 7•24 years ago
|
||
I'm pretty sure this is fixed... Please check!
Yes, it's working now. Thanks.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
Comment 11•24 years ago
|
||
Comment 12•24 years ago
|
||
Repros on 02-15-06 + Win98-JA Click attachment for message, select Save to Disk. New attachment: Screen shot of raw utf-8 string in Save as dialog Please change Status to REOPENED to reactivate this report. (**Who do I need to see to obtain privileges so I can make this kind of administrative change myself in the future?**)
Reporter | ||
Comment 13•24 years ago
|
||
Reproducible on linux 02/14 mtrunk build as well. Reopened the bug and changed QA contact to Wesley.
Updated•24 years ago
|
Target Milestone: M18 → ---
Comment 16•23 years ago
|
||
This looks cosmetic to me, but I guess the real question si, would we accept this for the US product? Maybe for beta, but not for final. Adding nsbeta1 keyword.
Comment 18•23 years ago
|
||
moving to 0.9.2 and reassigning to varada.
Assignee: putterman → varada
Whiteboard: [nsbeta3-] → [nsbeta1+]
Target Milestone: --- → mozilla0.9.2
Comment 19•23 years ago
|
||
oops, misread the bug and thought it was an attachment in the compose window. Reassigning to mscott.
Assignee: varada → mscott
Updated•23 years ago
|
OS: Windows NT → All
Comment 20•23 years ago
|
||
Marking as nsCatFood and RTM. IMHO the user should now what they are saving in confirmation dialogue (e.g. Saftey).
Assignee | ||
Comment 22•23 years ago
|
||
I'm curious. when the helper app dialog comes up with the Open/Save options we show the name of the attachment in the windows titlebar at the top of the dialog. does the file name render correctly there too? Or is it showing the raw UTF-8? As far as the file name in the save to disk dialog if you select "save to disk" from the helper app dialog, looks like the problem is here: nsXPIDLCString leafName; url->GetFileName(getter_Copies(leafName)); if (leafName) mSuggestedFileName.AssignWithConversion(leafName); we get the file name from the url which must be UTF-8 I'm guessing. Then we put it in a unicode string. Looks like AssignWithConversion is the wrong thing to use here. Maybe a NS_ConvertUTF8toUCSII would do the trick instead?
Reporter | ||
Comment 23•23 years ago
|
||
Checked this with 07/17 win32, linux and mac branch build. The problem doesn't exist anymore. Is there any fix checked in for this? I'll mark this as wfm for now. I'll reopen if I see this again.
Status: NEW → RESOLVED
Closed: 24 years ago → 23 years ago
Resolution: --- → WORKSFORME
Reporter | ||
Comment 24•23 years ago
|
||
If the attachment file doesn't have extension and filename contains space, '[' or ']', or filename is in Japanese, the filename is shown as a UTF8 url string after received. Please see bug 91359.
Assignee | ||
Comment 25•23 years ago
|
||
ji are you sure this works if you FIRST see the helper app dialog and then click save to disk? If you are saving the attachment directly from the mail window, w/o seeing the helper app dialog first, then we have special code in mailnews to convert the attachment name to unicode to make sure it shows up correctly. I'm not sure why this would suddenly be fixed through the save to disk dialog from the helper app code because I haven't changed it in so long. Although I won't complain if you say it's fixed =).
Reporter | ||
Comment 26•23 years ago
|
||
Yes, you are right. When I try to save an attachment file, like .vcf file from helper dailog, the ja filename is shown as raw utf8 string. No problem when I save from mail window. Thanks, and reopening..
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Assignee | ||
Comment 27•23 years ago
|
||
Assignee | ||
Comment 28•23 years ago
|
||
Unfortunately on my windows machine, when I bring up a file picker with a pre filled in file name which contains japanese characters, my OS leaves the file picker empty. No file name is prefilled. So I can't verify that this patch fixes the problem but I think it will. The file name (which is an escaped UTF-8 string) was not being unescaped before I was converting it to unicode. Many thanks to Shirley for helping me get my OS showing japanese characters. This patch is also going to fix 71735 so I'm going to check it in under that bug and we can see if it fixes this bug too on proper japanese machines.
Assignee | ||
Comment 29•23 years ago
|
||
Ok, I've gone ahead and checked my patch in. shirley, can you give this a whirl in Monday's release builds to see if really fixes things for you? Thanks!
Status: REOPENED → RESOLVED
Closed: 23 years ago → 23 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 30•23 years ago
|
||
Verified with 08/10 trunk build. It's fixed.
Status: RESOLVED → VERIFIED
Reporter | ||
Comment 31•23 years ago
|
||
It's broken on 10/12 0.9.4 build.
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
Reporter | ||
Comment 32•23 years ago
|
||
Assignee | ||
Comment 34•23 years ago
|
||
i wonder why this broke again....
Target Milestone: mozilla0.9.3 → mozilla0.9.6
Comment 35•23 years ago
|
||
moving to 0.9.9
Whiteboard: [nsbeta1+]
Target Milestone: mozilla0.9.6 → mozilla0.9.9
Updated•23 years ago
|
Assignee | ||
Comment 36•23 years ago
|
||
Shirley, does this regression happen for both local and imap mail messages? I'm wondering if the problem is just with one mail protocol or both of them. Thanks!
Reporter | ||
Comment 37•23 years ago
|
||
Rechecked with 01/24 build, it happpens for both local and imap messages.
Assignee | ||
Comment 38•23 years ago
|
||
The patch for this bug exposes the unescaped suggested file name string the exthandler is already keeping track of to the helper app dialog. When the dialog goes to fill in the Title string it will now use the suggested file name if that name is present. If it isn't, it falls back to trying to extract the filename out of the url we are running. In addition to fixing this bug for mail, this has the added benefit for the browser of showing the file name retrieved from the content dispostion header as the filename we put in the window title for the helper app dialog.
Attachment #42898 -
Attachment is obsolete: true
Comment 39•23 years ago
|
||
Comment on attachment 66393 [details] [diff] [review] the fix r=law
Attachment #66393 -
Flags: review+
Comment 40•23 years ago
|
||
Comment on attachment 66393 [details] [diff] [review] the fix sr=sspitzer
Attachment #66393 -
Flags: superreview+
Assignee | ||
Comment 41•23 years ago
|
||
fix checked in.
Status: REOPENED → RESOLVED
Closed: 23 years ago → 23 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 42•22 years ago
|
||
Verified as fixed with the latest trunk build.
Status: RESOLVED → VERIFIED
Updated•20 years ago
|
Product: MailNews → Core
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•