139625 - The non-ascii path name specified during the last installation can not be displayed properly in installer

Status: RESOLVED WORKSFORME

(Core :: Internationalization, defect)

Description

[Yuying Long]

Build: 04-23 RC1 branch build on WinXP-JA.

Steps:
1. Before I installed the 04-23 branch build, I had a previous Netscape
installed under a Japanese named directory.
2. Run Netscape installer, and with "set up" step, the Japanese data in path
name which was previous Netscape installed was displayed as "..", e.g.
"..0420branch".

This problem also can be reproduced on 04-19 JA localized test build.

Comment 1

[Yuying Long]

Attachment: Screen shot of problem

Sometimes it display as like the screen shot, sometimes display as "..abc".

Comment 2

[Rui Xu]

The non-ascii path name is picked up correctly, but it is corrupted in display. 
It only happens on Windows platforms, no this feature on Mac and Linux.

It might be better to take out this feature because it doesn't help user a lot. 
If keeping this feature, we should consider to fix it based on code page and 
unicode conversions for both NT and non-NT based Windows.

Comment 3

[Roy Yokoyama]

Just to clarify:
This is a problem displaying Japanese directory in Japanese OS, correct?
If so, then isn't this a regression?

Comment 4

[Rui Xu]

It is also reproducible with SC folder name on SC Windows platforms. So, this is 
a general problem on the localized Windows, not only a problem with Japanese 
folder on Japanese Windows.
It is also reproducible with NS6.1, NS6.2, etc..., so it seems not a regression.

Comment 5

[Yuying Long]

Attachment: screen shot for uninstaller

This is a screen shot when I run uninstaller of 04-19 JA localized build.
The path name is not displayed properly, which is not the case on N6.2.2JA - I
remember the path name was displayed fine and I was able to uninstall before.

Somehow, I feel this related with the recently N7.0 installer problem, in
another word, it's a regression.

Rui, did you try to install a N6.2x version after a previous N6.2x with a
non-ascii name?  or install a N6.2x version after a previous N7.0 with a
non-ascii name?

Comment 6

[Rui Xu]

Yes, I have tried and seen this problem before (see the attachment in Bug 
137656), and I am thinking there might be some other messages which contains 
non-ascii characters coming from system.

I hope it can be fixed with fixing Bug 125106, 137656 and 125104, but if not, I 
suggest to take this feature out, which means don't pick up user specified 
information from system, because the code conversion for installer should be 
considered for both code page and unicode on both NT and non-NT based Windows, 
it will take some risks and costs, and so far we don't have a good solution for 
unicode support on Windows system level yet.

Comment 7

[Makoto Kato [:m_kato]]

I cannot reproduce on Firefox 4 beta 10.  Firefox installer uses NSIS of Unicode version, so I believe that this is already fixed.