63297 - NS 4.7 profile name is displayed incorrectly

Status: VERIFIED WORKSFORME

(Core :: Internationalization, defect)

Description

[Max Sanzharov]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; m18) Gecko/20001213
BuildID:    2000121304

Profile manager incorrectly displays the Netscape 4.7x profile name with
non-ascii letters. If I try import it, Manager creates "-1" subfolder in the
Users50 folder. I created Netscape 4.7 profile with cyrillic letters in the
name, but Mozilla Profile Manager displays another characters.

Reproducible: Always
Steps to Reproduce:
1. Run Netscape 4.7 Profile Manager
2. Create new profile with non-ascii characters in the name
3. Start Communicator and Quit it
4. launch Mozilla Profile Manager

Actual Results:  Profile Manager displays NS 4.7 profile in the list, but the
profile name is incorrect

Tested on the Russian NT 4.0 SP6a

Comment 1

[nhottanscp]

Is this related to bug 59498? Is your "Users50" directory in Russian?

Comment 2

[Teruko Kobayashi]

To see the 4.7 profile name in profile manager dialog, you need to
do the following.

Steps to Reproduce:
1. Run Netscape 4.7 Profile Manager
2. Create new profile with non-ascii characters in the name
3. Start Communicator and Quit it
4. Run the dos prompt, go to the directory you installed Mozilla.exe
   For example, c:\Program files\Netscape\Netscape 6
5. Run the Profile Migration instead of Profile Manager
   Netscp6 -Installer
Then, the Profile manager dialog will show up.
At this time, if you cannot see the 4.x profile name correctly. This is the bug.

Max Sanzharov, could you try this again?

Comment 3

[Max Sanzharov]

registry.dat was not exist, and Mozilla got incorrect name from mozregistry.dat, 
created by M15 build. I launched "mozilla -installer", and now I see the old 
entry with incorrect name and new entry with with correct name. Both of them 
reference to the same Netscape 4.7 profile.

Comment 4

[Keyser Sose]

Reporter so can we mark this WORKSFORME? It seems to me that that the bug was a
result of an old Mozilla build.

Comment 5

[Max Sanzharov]

I have two conjectures about this situation:
1. Incorrect data are transferred.
2. Correct data are transferred incorrectly.
Mark this WORKSFORME, if my first conjecture is true.

Comment 6

[Keyser Sose]

Marking WORKSFORME as per comments.

Comment 7

[Teruko Kobayashi]

Verified.