Language file named with foreign characters

[uncpotato]

Does it really necessary to name the language file with the foreign language character set??
I use a Chinese verson Windows 2000, which is unicode capable. Every time when I install BSplayer, it always reports errors that it can't create a certain file. While knowing that it is only a language file that I never needed anyway, I happily click IGNOR to by pass it. There are a total of 3 of them, if I remember it right.
But is it really necessary to name those files like that?
Novice users might panic if they see such an error box pop up several times.

You don't name Japance/Chinese... files with their native characters, so it is really unnecessary to name those files that way. It leads to such a situation for some users.

[Tizio]

Originally Posted by uncpotato

Does it really necessary to name the language file with the foreign language character set??
I use a Chinese verson Windows 2000, which is unicode capable. Every time when I install BSplayer, it always reports errors that it can't create a certain file. While knowing that it is only a language file that I never needed anyway, I happily click IGNOR to by pass it. There are a total of 3 of them, if I remember it right.
But is it really necessary to name those files like that?
Novice users might panic if they see such an error box pop up several times.

You don't name Japance/Chinese... files with their native characters, so it is really unnecessary to name those files that way. It leads to such a situation for some users.

Please, can you tell us which file names give you such an error?
Thank you

[uncpotato]

I never take a note of it, as I know perfectly that I don't need those files.
And then I forget all about it, until next time when I upgrade bsplayer and then hit into the same old problem. (it is there from v1.x)

I tonight find the install file & do a re-install just to see the error message.
The first file my Win2k complains is

Error opening file for writing:

C:\prog.... \lang\Catal?lng
then (after an ignor)
C:\prog.... \lang\Valenci?lng


I guess there may be others with other version of windows.
Hope it helps.

Actually when I open the lang folder, I see some other file with names in (kind of) corrupted form or having funny characters, like Fran[xx]is.lng, Sloven[xx]na.lng, and one with [leading space]nsky.lng
Windows is able to create those but not displaying them correctly.

I guess no users are aware of the file name anyway, just rename them in pure US ASCII or goes all the way to unicode.

[J7N]

Yes, I agree with Uncpotato. There is no place for Unicode characters in filenames.

While both the OS and BSPlayer may be capable of processing Unicode text, it takes just one step in-between to lose the special characters. Lots of applications and communication protocols still use 8-bit codepages.