Closed
Bug 136221
Opened 23 years ago
Closed 4 years ago
In composer window title, url-unsafe characters(non-ASCII) are URL-escaped in the encoding of locale charset.
Categories
(Core :: Internationalization, defect, P5)
Core
Internationalization
Tracking
()
RESOLVED
INVALID
Future
People
(Reporter: kasumi, Assigned: smontagu)
Details
(Keywords: intl, regression)
tested 04-05-trunk Win XP Pro. JA, MacOS X, Linux 7.1 JA 1. Create a folder having DBCS as name 2. Create a file having DBCS as name in this folder 3. Launch Composer 4. Set Character coding to DBCS character coding such as Japanese(Shift-JIS) 4. Select File/Open or click Open icon on composition toolbar 5. Select that file created in Step 2 6. You will see the path is in escaped in window title THis problem occured regardless of OS.
Comment 1•23 years ago
|
||
A dup. of bug 107448.
107448 is mentioning about insert link properties dialog box. Maybe regarding of this but not sure.
Keywords: regression
QA Contact: kasumi → ruixu
Summary: In composer window title, DBCS characters are in escaped characters. → In composer window title, DBCS characters are in escaped characters for path,file name.
Comment 3•23 years ago
|
||
Yes, bug 107448 is when insert a link, and this one is when open a file, but the problem for both of them is displayed as escaped characters in path/file name. There are many actions can see the same problem: open file, insert link, insert image, add attachment...etc.
Comment 4•23 years ago
|
||
I just noticed there is a regression keyword, as far as I know, we never able to display DBCS properly when try to access those kind of path/name names since N6.0, they always display as escaped characters. Did it even worked some time before?
Comment 6•23 years ago
|
||
OK, I did misunderstand what the original problem :( We used only show the file title in Composer window title bar, but don't show the file path before(e.g. N6.2.2). But now we are showing both page title and file path in Composer window title bar. I guess it's related with bug 29698 (bug 105909), in another word, fix for bug 105909 should fix this problem here.
Comment 8•23 years ago
|
||
reassign to darin, related with bug 135854, regression caused by 124042.
Assignee: yokoyama → darin
Updated•23 years ago
|
Status: NEW → ASSIGNED
Priority: -- → P3
Target Milestone: --- → mozilla1.1alpha
Updated•22 years ago
|
Target Milestone: mozilla1.1alpha → ---
Reporter | ||
Comment 10•22 years ago
|
||
This is not cosmetic as #7 said. Once save it having incorrect file name/path, when create shortcut by drag and drop their icon, shortcut doesn't work displaying error message. This problem occurres for all OSs.
Priority: P3 → P1
Comment 11•22 years ago
|
||
seems important... moving back to untargeted. i probably won't have any time to investigate this one for a while though, so if anyone else can own this, please do. thx!
Target Milestone: Future → ---
Reporter | ||
Comment 12•22 years ago
|
||
I created a report bug 160236 which is splited from comment #10.
Comment 13•22 years ago
|
||
futuring... would be great if someone on the intl team could take this.
Target Milestone: --- → Future
Comment 14•21 years ago
|
||
This is not just DBCS vs SBCS. This problem is applicable to all non-ASCII filenames. Actually, any file with characters(even in ASCII range) that need to be url-escaped (like 'space' and &)has this problem. So, anyone using 'space' (let alone non-ASCII chars) in filenames are affected. I'm only talking about the cosmetic part because the symptom described in comment #10 (which is much more serious than this) was spun off as bug 160236. I'm changing the summary line accordingly.
Summary: In composer window title, DBCS characters are in escaped characters for path,file name. → In composer window title, url-unsafe characters(non-ASCII) are URL-escaped in the encoding of locale charset.
Updated•18 years ago
|
Assignee: darin → smontagu
Status: ASSIGNED → NEW
QA Contact: marina → amyy
Updated•15 years ago
|
QA Contact: amyy → i18n
Comment 15•6 years ago
|
||
Decreasing the priority as no update for the last 2 years on this bug. See https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md#how-do-you-triage about the priority meaning.
Priority: P1 → P5
Updated•4 years ago
|
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•