![]() |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() |
|
![]() |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() |
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Users of the free xplorer² lite in far eastern and other countries with complex language locales (e.g. Arabic, Hebrew, Greek, Bulgarian etc) sometimes complain that some filenames won't show up properly but display full of question marks. For instance ÅËËÇÍÉÊÁ.TXT will show as ????????.TXT. Characters in the local language are replaced with ? and you can't read the filename. Users with the professional version on the other hand see the filenames properly. This is not some plot to increase the sales of the professional version <g>. The cause of this problem is that xplorer² lite is plain text (ANSI) application whereas the professional version is UNICODE. If you refer to an older article you will see that the UNICODE standard allows for much more characters than plain ANSI (65536 vs just 256!). Interpreting numbers to language characters is much more straightforward under UNICODE. This simple trick will solve most of your language-specific problems. If you manage files with names in many languages, e.g. both chinese and japanese, then some question marks will remain. In such complex scenarios only the professional xplorer² will cope.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
© 2002—2010 Nikos Bozinis, all rights reserved |