Closed
Bug 23111
Opened 25 years ago
Closed 25 years ago
Filename gets lost when sending mail with attachment with int. chars in the filename
Categories
(MailNews Core :: Internationalization, defect, P3)
Tracking
(Not tracked)
VERIFIED
FIXED
M13
People
(Reporter: bugzilla, Assigned: nhottanscp)
Details
Attachments
(2 files)
(deleted),
image/gif
|
Details | |
(deleted),
patch
|
Details | Diff | Splinter Review |
I attach a file called "זרו.jpg" with Mozilla and sends it. The Mime part is
now:
Content-Type: image/jpeg;
name="=?ISO-8859-1?Q?jpg?="
Content-Transfer-Encoding: base64
Content-Disposition: inline;
filename="=?ISO-8859-1?Q?jpg?=
The filename got lost....
Using build 2000010416
Assignee | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Comment 1•25 years ago
|
||
Adding rhp to cc.
Assignee | ||
Comment 2•25 years ago
|
||
When we apply MIME encode to the file name, we get URI escaped string and
unescape it. But it also needs charset conversion from platform file system to
UTF-8. MIME encoder requires an input string in UTF-8. We have the data loss
because the encoder expecting UTF-8 while the input string is some other
charsets.
So we need to get the platform charset and convert the string to UTF-8.
Assignee | ||
Comment 3•25 years ago
|
||
Assignee | ||
Comment 4•25 years ago
|
||
All I need was the file name "nscpnáo.gif", didn't have to attach the image...
Comment 5•25 years ago
|
||
Oe more thing to keep in mind.
Assignee | ||
Updated•25 years ago
|
Summary: Filename gets lots when sending mail with attachment with int. chars in the filename → Filename gets lost when sending mail with attachment with int. chars in the filename
Assignee | ||
Comment 6•25 years ago
|
||
Adding mscott to cc as this may be related to 23109.
Assignee | ||
Updated•25 years ago
|
Target Milestone: M13
Assignee | ||
Comment 7•25 years ago
|
||
Assignee | ||
Updated•25 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 8•25 years ago
|
||
checked in, I tested latin1 and japanese file names.
Comment 9•25 years ago
|
||
marina, could you check this for Latin 1 names? I'll check for JPN names.
Comment 10•25 years ago
|
||
** Checked with 1/24/00 Win32 build **
On Japanese Windows, I can see file names in Japanese and
save them also through a save as dialog.
On US Windows-NT, I was also able to see the file name in
Latin 1 accented characters but as I went to save this file
the characters for the Save as dialog's suggested name were
incorrect. We are probably not sending the data in system charset.
Should we file a separate bug for this?
Comment 11•25 years ago
|
||
I guess this bug is only about whether or not the filename
gets deleted in the Content headers. That is no longer the case.
I'll mark this fix verified and deal with the data charset
problem under US Windows in another bug.
Status: RESOLVED → VERIFIED
Assignee | ||
Comment 12•25 years ago
|
||
The dialog problem has been filed separately as 24864.
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
•