Closed Bug 266718 Opened 20 years ago Closed 20 years ago

Cannot open different locale file on WinXP

Categories

(Core :: Internationalization, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 162361

People

(Reporter: tiancheng.hu, Assigned: smontagu)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20040913 Firefox/0.10
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20040913 Firefox/0.10

I meet with just the same problem as Bug 191170 (MacOS X) on the WinXP.

Note:
IE don't have this problem.

Reproducible: Always
Steps to Reproduce:
1. I have both Japanese and French accent named dirctory/files in my locale file
system.
2. Launch browser, File | Open File.

Actual Results:  
Japanese locale:
Can open files under Japanese directory, but failed to open files under latin-1
accent characters directory; will get a not found error message  instead.
Latin-1 locale:
Can open the files under accent characters directory, but failed to open those
files under Japaense directory.

Besides being unable to open files from the "foreign lanuage" directory,
it's also impossible to save files to such directory.
You will also fail to save "foreign lanuage" files to a normal English
named directory. There is no warning message displayed on failure.

Expected Results:  
When user installed both locale A and locale B on a same OS,
files named in both lanuages should have been able to be opened or saved 
from/to directories named in both lanuages. 

IE don't have this problem.
Similar Bug Reports:
191170  Cannot open different locale file  (the Most simiar which happened on Mac)
129736  Saving of file with a charset different from system local...
169712	Browser doesn't launch when install path contains Chinese...
200044  Double byte directory/file names are not listed in local ...

*** This bug has been marked as a duplicate of 162361 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.