Closed
Bug 44353
Opened 24 years ago
Closed 24 years ago
Japanese directory name is not displayed correctly in Choose Profile Folder
Categories
(SeaMonkey :: Startup & Profiles, defect, P3)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: teruko, Assigned: shanjian)
Details
(Keywords: intl)
After you create Japanese directory name, the Japanese diretory name is
displayed as garbage in Choose Profile folder dialog when you create new
profile.
Steps of reproduce
1. Create Japanese directory name
2. ./netscape -ProfileManager
3. Click on Create profile button
4. Click on Next
5. Click on Choose folder
The Japanese directory name you created in step 1 is displayed as garbage.
Tested 2000-06-30-08 Linux build. I am using Redhad 6.2 Japanese.
This does not happen in MAC and Win32 build.
Reporter | ||
Comment 1•24 years ago
|
||
Changed QA contact to teruko@netscape.com and cc'd to gbush@netscape.com.
QA Contact: gbush → teruko
Reporter | ||
Comment 2•24 years ago
|
||
Save as dialog also does not display Japanese directory name.
Reporter | ||
Comment 3•24 years ago
|
||
Changed QA contact to ylong@netscape.com.
QA Contact: teruko → ylong
Comment 4•24 years ago
|
||
I think this is important, Japanese user in Japanese system likely to use their
Japanese name for profile (which is very reasonable). And we should not display
as garbage.
Comment 5•24 years ago
|
||
Reassigning to Conrad Carlen per Nav Traige team.
Please accept as nsbeta1.
Assignee: ben → ccarlen
Comment 6•24 years ago
|
||
Looking at:
http://lxr.mozilla.org/seamonkey/source/profile/resources/content/newProfile1_2.js,
it looks like unicode routines are being used to get the chosen file's path. In
other words, the profile front-end code seems right. Do we know that
nsIFile::InitWithUnicodePath() and nsIFile::GetUnicodePath() are correct on
Japanese Linux? How about nsIFilePicker?
Status: NEW → ASSIGNED
Assignee | ||
Updated•24 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Comment 8•24 years ago
|
||
This should have been fixed together with 65010. Please verify.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•