> My conclusion is that this problem is much more likely to occur when the
> name of your download folder contains symbols outside of the system's
> non-unicode codepage, which shouldn't often be the case. So it's not
> that bad, after all.
What "is not that bad, after all" failing every now and then with not
clear indication of what happened? Going through the install process
without being able to detect the problem? Forcing users to use the same
language for the operating system and the browser?
> I think that whether ot not this should affect localization, depends on
> how likely the users of that locale are to use an incompatible 8-bit
> codepage. Maybe the situation is rather specific to Esperanto?
In case you missed it, I already stated in the bug that the same happens
to Russian and Thai, it is not specific to one single localization
(actually I knew somebody would say just that so I took the time to test
other localizations). It is rather a mismatch between the Windows XP
locale and that of Firefox. And as we get more people involved that is
going to happen more often. Some people might be willing to use a
localized version of Firefox, but that does not mean they want (or even
can) have Windows XP in the same language!
My point is, Firefox is great, because I can use it in the language I
want, even if the operating system does not support it. We all expect
it to work. If that is not the case, users and localization teams
should be warned or a solution be found. At least that's what I think.