Closed
Bug 243558
Opened 21 years ago
Closed 21 years ago
Bad support of directories written in East-Asian languages
Categories
(SeaMonkey :: Download & File Handling, defect)
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 162361
People
(Reporter: eghost, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a) Gecko/20040513
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a) Gecko/20040513
It seems that the Download Manager (DM) internally changes East-Asian Characters
(in my case Japanese kana) in a pathname to any location into "_" (underline
symbols).
I have Windows XP with East-Asian Support installed. Programs like MSIE handle
normally those characters in pathnames.
Reproducible: Always
Steps to Reproduce:
So, if you want to save a file in any location, where the path contains those
symbols, the symbols are transormed into "_". For example:
"e:\[4symbolsOfJapKanaHere]\Projects" is changed into "e:\____\Projects".
If such directory already exists, the DM saves the file into that directory
(with underline symbols). If not, a message is shown: " could not be saved
because unknown error occured. Try saving in another location".
Actual Results:
Either error occurs or saving in another location.
Expected Results:
Saving using right pathname (with Japanese kana).
Comment 1•21 years ago
|
||
> It seems that the Download Manager (DM) internally changes East-Asian Characters
no, this is done by xpcom, at the border to nspr.
of course that doesn't make a difference for you :)
*** This bug has been marked as a duplicate of 162361 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Comment 2•21 years ago
|
||
(judging from your mail address, I assume you are using a russian windows
version. saving to directories with russian names should work fine.
also, if you were using a japanese system, saving to a japanese-named directory
should work fine.
it's just saving to directories with names outside the system charset that's
broken.)
No, I don't use Russian Windows.
Cyrrilic support is solved very simply --
Control Panel|Regional Settings|Advanced|Language for non-Unicode Programs
But, of course in this way you can only set one language at a time.
(And AFAIR it requires restarting the Windows to change this setting).
That is quite a problem also -- though I'm a Russian, I live in Lithuania
and study Jap. Although non-Unicode programs work fine with Russian filenames,
lithuanian in this case might be a problem (of course the biggest trouble is
with non-Unicode volumes like FAT).
Just FYI. ;)
Comment 4•21 years ago
|
||
That's exactly what cbie meant. On Win2k/XP, regardless of the language version
of the OS (whether it's French, German, Korean, Japanese, Hebrew, Arabic,
English or whatever), you can control what 'ANSI' code page(legacy code page) to
use for non-Unicode applications as you described. Bug 162361 is about making
Mozilla take the full advantage of Unicode-capability of Win 2k/XP while still
making it work on Win 9x/ME (which is not Unicode-capable or have a limited
Unicode support).
Updated•21 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•