problem reading file names with non english characters

[mmoalem]

hi there all - have a little problem here...
have an XP (english with hebrew and chinese enabled). using the XP's explorer etc there is no problem seeing file names with foreign characters (be they hebrew, chinese, latin or whatever) but in windows commander v5 i only see foreign characters as question marks and if i for example try to copy or move a file with non english characters the software refuses.
i figured the languege packs are for the menus etc and also i want to be able to display all ccharacters without reverting to a different languege pack every time i copy a file with a different lanugege character (have many of them) ...
it's a bit like the IE languege encoding options but in XP it chosses it automaticly
any ideas of a solution?
cheers
michel

[Lefteous]

2mmoalem

The current version 6.01 has the following new unicode features. I suggest you to upgrade to the latest version.

- Show Unicode file names in file lists
- Copying and moving of files with Unicode names on Windows NT/2000/XP, also with subdirs!
- Rename Unicode file names in place
- Show tip windows with Unicode names
- Show warning message the first time the user enters a dir with file names from a different codepage (can be disabled)
- If the user hasn't chosen a default font, use "Microsoft Sans Serif" instead of "MS Sans Serif" on Win2k/XP, because it supports Unicode
- Support for Unicode UTF16 in "Compare by contents". If Unicode marker present, this also supports big endian format

[oblomov]

I noticed that after installing Middle Easter support in my English version of WinXP Pro, the extended characters changed (e.g. the ça sequence became another (single) glyph). I solved the problem by switching from MS San Serif to Microsoft Sans Serif (the TrueType font)

[ghisler(Author)]

Indeed if you changed the font yourself to something else and then back to MS Sans Serif, TC will not automatically change it to Microsoft Sans Serif.

[oblomov]

The problem was that by installing CTL support in Windows, the *default* font (MS Sans Serif) screwed up the display of (Europea) international characters, and there was *no* way to let it use MS Sans Serif with the correct Codepage.