Closed Bug 23623 Opened 26 years ago Closed 26 years ago

[Beta] Unable to migrate 4.x mailboxes with Japanese names

Categories

(MailNews Core :: Profile Migration, defect, P3)

Product:
MailNews Core
Component:
Profile Migration
Platform:
x86
Windows NT
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED DUPLICATE of bug 7844

People

(Reporter: momoi, Assigned: dbragg)

Details

** Observed with 1/10/00 Win32 build ** I have several mailboxes in a mail directory which I am using with Communicator 4.71. I want to migrate these 4.x mailboxes when I create/migrate a 4.x profile. But when I use "migrate this profile" function, the mailbox names in Japanese are not displayed as Japanese at all but instead some unitellgible ASCII garbage. Our investigation shows that if you have a mailbox name with Latin accented characters under US Windows, the name for such a mailbox displays OK after migration. But this is not true with JPN mailboxes residing on Japanese Windows. Since 4.x mailboxes themselves do not move but Mozilla simply find them as they are after a profile migration, it seems that we are simply not using the file-system charset (in this case, Shift_JIS) on the Japanese window and instead must be making some other assumption about the source charset for the mailbox names. We should query the OS where Mozilla is operating in and learn what the file-system charset is and then display the names taking that info into account. I18n should be able to provide info to get this done. As most non-Western Windows system users have mailbox names in their own languages and we want to display them correctly as we migrate the mailboxes from 4.x, I think this is a definite beta material.
QA Contact: gbush → momoi
Summary: Unable to migrate 4.x mailboxes with Japanese names → [Beta] Unable to migrate 4.x mailboxes with Japanese names
Assigning myself as QA contact since this is an important I18n item for Beta.
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → DUPLICATE
It turns out I myself filed a display bug for local folder names sometime ago and designated it for Beta. We call it migration int this bug, but it really is reduced to being able to display whatever pre-existing mailbox names are on your system. I think it would be best to combine these 2 bugs and deal with them in Bug 7844. Accordingly, I'm going to mark this bug as a duplicate of Bug 7844 and copy dbragg@netscape.com in that bug. Bug 7844 is currently assigned to putterman@netscape.com. *** This bug has been marked as a duplicate of 7844 ***
CC'ing putterman@netscape.com.
Status: RESOLVED → VERIFIED
Verified as a duplicate.
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.