359200 - double clicking on a file with a "unicode" name fails

Status: RESOLVED WORKSFORME

(Firefox :: Shell Integration, defect)

Description

[Jungshik Shin]

Double-clicking on a file whose name includes characters outside the default system codepage (e.g. Japanese name where 1252 is the default code page)  fails. 
(bug 193358 comment #19)

Although bug 162361 was fixed, we still need to fix bug 282285 (see bug 281781) 

I compromised in the summary line and used 'unicode name' hoping that will make this bug easier to be found.

Comment 1

[石庭豐 (Seak, Teng-Fong)]

Concerning bug 282285:
I don't know much about DDE, but I remember that Word 2000 had this problem, ie double-clicking on a Unicode-named document and Word was unable to open it.

Microsoft has corrected this bug in Word XP and Word 2003.  I think Word XP was supposed to work in Win98 as well.  So maybe you could take a look at how parameters are passed in DDE so as to maintain backward compatibility.

But I think this problem comes from FF which doesn't expect to receive Unicode string.

Comment 2

[Jungshik Shin]

(In reply to comment #1)

> But I think this problem comes from FF which doesn't expect to receive Unicode
> string.

Yes, that's our bug. Did I say otherwise? 
 

Comment 4

[utf16]

This is the same bug as https://bugzilla.mozilla.org/show_bug.cgi?id=374122

Comment 5

[Robert Strong (they/them - no direct email)]

Is this still a problem now that bug 374122 is fixed?

Comment 6

[Masayuki Nakano [:masayuki] (he/him)(JST, +0900)]

In the default settings which registered by Firefox, I can open Unicode file name by double click on explorer (both when Fx isn't launched and is running). But I'm not sure about when I open it via DDE.

# Where can I change the settings for using DDE on Win7?

Comment 7

[Robert Strong (they/them - no direct email)]

We should be using DDE on Win7 unless you manually modify registry settings.

Comment 8

[石庭豐 (Seak, Teng-Fong)]

Attachment: HTML test file with "Unicode" name

I upload this test case in case there would be any regression in the future and we'd need some test case.

The name of this HTML file is
ABC_çàñ_řşŧ_άέή_ЖЙЯ_東西马_あいう_가각갂_∯∀⊈.html
which contains the following characters groups:

1. Simple ASCII
2. Extended Latin for western Europe
3. Extended Latin for eastern Europe (well, I think :p)
4. Greek (non trivial characters - because trivial ones might be included in some other charset)
5. Cyrillic
6. Chinese (including Traditional, "neutral" and Simplied Chinese characters)
7. Japanese
8. Korean
9. Mathematical symbols

The name is made up so that whatever system locale one is using, there should be some non-ANSI characters in it and as a result, if full Unicode is not supported, the HTML file can't be opened.

Comment 9

[石庭豐 (Seak, Teng-Fong)]

Using the test case I've just uploaded, I've done the double-click test with the following FF versions in XP Pro after a default installation:

2.0.0.20 ==> fail
3.0.19   ==> OK
3.6.17   ==> OK
4.0.1    ==> OK

Therefore, I also think this bug could be closed as solved.

Comment 10

[Mats Palmgren (inactive)]

Per last comment => WFM