Closed
Bug 119507
Opened 23 years ago
Closed 23 years ago
[US locale] Can not attach a file under Japanese path name on mozilla bug report
Categories
(Core :: Internationalization, defect)
Tracking
()
VERIFIED
WORKSFORME
People
(Reporter: amyy, Assigned: nhottanscp)
Details
(Keywords: intl, regression)
Attachments
(1 file)
|
112.09 KB,
image/jpeg
|
Details |
Build: 01-10 trunk build on Mac OS 10.1
Steps:
1. Create a path name which contains Japanese character on local drive.
2. Open a bug report under http://bugzilla.mozilla.org
3. Click on Create a new attachment.
4. Choose a file under the path name that created on step 1.
Result:
The Japanese characters are displayed as "?" in the path name ( see a followed
screen shot), and when you click the Submit button, you will get an error
message that tells the file is not existing.
| Reporter | ||
Comment 1•23 years ago
|
||
| Reporter | ||
Updated•23 years ago
|
QA Contact: ruixu → ylong
| Reporter | ||
Comment 3•23 years ago
|
||
Oh, you are right - I always keep my machine default as Japanese. But yesterday
I changed it to US and I forgot this change when I report this bug.
However, even I set machine to US, I can see the Japanse path name of OS, also I
can open the files under Japanese path name, that's why I didn't realized I was
under the US locale.
Summary: Can not attach a file under Japanese path name on mozilla bug report → [US locale] Can not attach a file under Japanese path name on mozilla bug report
| Assignee | ||
Comment 4•23 years ago
|
||
Was the Japanese folder created under JA locale or US locale?
Status: NEW → ASSIGNED
| Reporter | ||
Comment 5•23 years ago
|
||
The folder that in my attachment was created in JA locale, but actually it's
doesn't matther with which locale that the file was created in, it depends on
the current locale that you are running.
Here are some more information about it.
[US locale]
Case one:
1. Create a Japanese folder name. - no problem in this step.
2. Can not open those files under Japanese folder that created in JA locale
through Navigator.
Both N6.2.1 and IE doesn't has this problem.
Case two:
1. Create a Japanese folder name.
2. Created a html file in Compose, and save it under a Japanese folder name, you
can see the Japanese folder name display fine in save file window.
3. Open this file through Navigator, then you will see the Japanese folder
doesn't contain the file file that you saved, and you will find another file
showing as "?????", click on that folder, then you will see the file there, and
Navigator can open that file.
N6.2.1 doesn't has this problem either, in another word, when you try to open
[JA locale]
Doesn't has problem with both case one and case two.
| Reporter | ||
Comment 6•23 years ago
|
||
Sorry, this comment above has not completed.
> N6.2.1 doesn't has this problem either, in another word, when you try to open
N6.2.1 doesn't has this problem either, in another word, when you try to open a
file under Japanese folder, you won't see a extra "????" folder show up.
And seems it's a regression.
| Assignee | ||
Updated•23 years ago
|
Keywords: regression
| Reporter | ||
Comment 7•23 years ago
|
||
-> nsbeta1
Since Mac OS X is a unicode base, the user should able to open the file by
switch beween the different locale, also IE and BBEdit doesn't has same problem.
This problem occurs with Latin-1 non-ASCII characters in the path name. Try
uploading a file whose name is é.txt. Mozilla incorrectly interprets the name as
e´.txt.
It works properly in Mozilla 0.9.8.
see also bug 119246
| Assignee | ||
Comment 10•23 years ago
|
||
I don't see the problem using 2/11 commercial trunk on MacOS X 10.1 default
locale set to English.
I tried 'à.txt' also tried a file name in Japanese Hiragana both are shown
correctly instead of '?'.
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
Comment 11•23 years ago
|
||
I still have this problem attaching a file é.txt using 2002021303 on Mac OS X
10.1.2, with a new profile.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
| Reporter | ||
Comment 12•23 years ago
|
||
I checked it on 02-13 trunk build, the original problem (can not attach a
Japanese file through bugzilla) is gone. I'm marking this one as works for me.
However, I still can not open such kind of file in browser, will file a seperate
bug for that.
james l:
If you still has the original problem which is can not attach a non-ascii file
in this bug report page, please re-open again.
Status: REOPENED → RESOLVED
Closed: 23 years ago → 23 years ago
Resolution: --- → WORKSFORME
| Reporter | ||
Comment 13•23 years ago
|
||
Bug 125614 filed for can not open the non-ascii named file.
Verified this one.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•