Closed
Bug 334280
Opened 18 years ago
Closed 17 years ago
can attach but cannot send a file with a name outside the default codepage (Japanese named file on French Windows)
Categories
(MailNews Core :: Attachments, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 332110
People
(Reporter: jshin1987, Assigned: jshin1987)
References
(Depends on 1 open bug)
Details
a spin-off of bug 332108 which is about a non-ASCII-named file within the file system codepage. This bug deals with a file whose name contains characters not covered by the default system codepage (for 'A' APIs). Bug 162361 fixed nsILocalFile so that it can now deal with any filename on Windows 2k or later, but mailnews attachment still uses nsFileSpec so that filenames always need to be covered by the file system codepage. By switching to nsIFile, we can solve the problem. Taken from bug 332108 comment #4 > perhaps a long term solution would be to replace |nsFileSpec* > mFileSpec| in nsMsgAttachmentHandler with |nsCOMPtr<nsILocalFile> mLocalFile|.
Comment 1•17 years ago
|
||
The bug still occurs in TB 2.0 Italian, on Win XP PRO Italian, attaching a file with Jap character in file name (and in folder who contain it).
Comment 2•17 years ago
|
||
Jshin, DUP of Bug 332110?
Comment 3•17 years ago
|
||
This is a dupe of the 2nd symptom of 332110. Note that this problem still exists even with the patches for bug 33451.
Updated•17 years ago
|
QA Contact: attachments
I read the above comments. So what is the fix? By the way, I am running with 2.0.0.9. I already changed the settings for "mail.strictly_mime.parm_folding" from 3 to 0. Should I change it back?
Updated•17 years ago
|
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
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
•