When you create Japanese Profile name in Communicator 4.x (I used 4.72), the Japanese Profile name is displayed as garbage in Netscape6's Profile Manager. Steps of reproduce 1. Use Communicator 4.x to create Japanese Profile name 2. Start Netscape6's Profile Manager Actual result Japanese Profile name is displayed as garbage in the Profile Manager Expected result Japanese Profile name is diaplayed correctly in Japanese Windows. Tested 2000042709 Win32 build.

Changed QA Contact to teruko@netscape.com

Could this be a migration issue because 4.x uses native encoding (e.g., SJIS for Japanese profile names on Windows) and 6.0 uses UTF-8?

This realy should be nsbeta2 since when profile names are in Japanese as described above, migration will not proceed and simply quit when you give a go-ahead to the prompt to migrate the 4.x profile. Thus if you have an older profile named in Japanese, no migration is possible for that profile. Nominating for nsbeta2.

Putting on [nsbeta2+] radar for beta2 fix.

dbragg is out on sabbatical till 6/6, so this won't make into next tuesday m16

Actually this is a Profile Manager issue, not a Profile Migration issue. (At least not yet :-) Reassigning to Bhuvan.

I tested this in 2000-06-27-08 Win32 build. After I created the Japanese profile and I tried to run the profile in Netscape6, message in the console, "Inside Migrate Profile routine. JavaScript error: line 0: uncaught exception: [Exception... "Component returned failure code: 0x8 0004005 (NS_ERROR_FAILURE) [nsIProfile.migrateProfile]" nsresult: "0x80004005 ( NS_ERROR_FAILURE)" location: "JS frame :: chrome://communicator/content/profile /profileSelection.js :: onStart :: line 160" data: no]" then, the Japanese profile did not run in Netscape6.

Fixed. So, the next level changes are in profile migration's code. Don Bragg owns a bug (44764) to address that problem. All macintosh issues should be addressed in the bug 45183.

I verified this in 2000-07-12-09 Win32 build.