WARNING: This server is unstable and will be retired in the next days.
If you want to keep this forum available, please request immediately a migration
on the Nabble Support forum.
Forums that don't receive any migration request will be deleted forever.
>> 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.
Exactly. Which is why I don't think this would be a common case for
Russian or Thai users (although my assumptions are based on Russian
particularly). Regardless of the OS locale, I believe those users are
very likely to have the correct 8-bit codepage chosen, because otherwise
not just VLC's installer wouldn't work, but pretty much any localized
non-unicode application would break too.
> 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!
You are right. But I assume that that does not stop them from choosing a
good non-unicode codepage in the system preferences. Unless of course
Firefox is one of just few applications localized into their language,
and all of the localized apps they use are unicode-aware.
> 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.
I agree. I just don't think this problem is that severe, and assuming it
hadn't been discovered and escalated before, I would be right. ;)
That doesn't stop us from having an L10n note above that string or
something similar. Or trying to come up with even better measures (e.g.
the warning dialog I suggested earlier).