Open
Bug 176099
Opened 22 years ago
Updated 2 years ago
attached file name having DBCS from Eudora-J is garbled
Categories
(MailNews Core :: Internationalization, defect)
Tracking
(Not tracked)
NEW
People
(Reporter: kasumi, Assigned: cavin)
References
Details
Attachments
(1 file)
127.39 KB,
image/jpeg
|
Details |
tested on 2002-10-22-08-1.0 Win XP Pro. JA Eudora 5.0.2 Jr2 1. Launch Eudora 5.0.2 Jr2 2. Create an account, message having attachment having DBCS in filename 3. Send it to yourself 4. Launch Mozilla Mail&Newsgroups 5. Highlight that mail which sent in 3. You will see file name is in garbege in Attachments: list Please see attachment
qa over to Kasumi
QA Contact: marina → kasumi
Summary: attached file name having DBCS from Eudora-J is in garbege → attached file name having DBCS from Eudora-J is garbled
Comment 4•22 years ago
|
||
Let me take my last comment back. bug 95613 is about importing Eudora mails with dbcs attachment. And I guess this bug is about compatibility issue between Eudora and Mozilla Kasumi, How is this bug different from bug 176105 ? (except the difference between attached files)
Comment 6•22 years ago
|
||
The steps to reproduce are the same in these two bugs (this bug and bug 176105 ). I wonder how the actual results are different.
Updated•20 years ago
|
Product: MailNews → Core
Comment 9•20 years ago
|
||
*** Bug 176105 has been marked as a duplicate of this bug. ***
Comment 10•17 years ago
|
||
I know it has been many years since this bug was opened, but I would be interested to know if the same problem is present for you if you use the Penelope (Eudora 8.0.0b3) importer, available here: http://wiki.mozilla.org/Eudora_Releases We've made dramatic improvements to the importers.
Updated•16 years ago
|
Product: Core → MailNews Core
Updated•16 years ago
|
QA Contact: marina → i18n
Comment 11•8 years ago
|
||
Is this a bug in Thunderbird, in Eudora or in some interaction between them? Can it be reproduced without having Eudora on one of the ends?
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•