>Take a look at article#346 'How to ease the multilingual input for your users'
>
>>I posted something similar a L O N G time ago...
>>
>>I'm in charge of an application that's currently deployed in about 18 central european countries. One of them (Slovenia) wishes to use their own language. I've got the Slovenian keyboard installed, and in other Windows apps, can type in their language by toggling it on. However, I cannot type in their language in my app. We had the same problem with cyrillic a while back.
>>
>>The response I got then was FoxPro did not know how to handle unicode fonts and that I would be better off simply installing the Central European version of Windows. Unfortunately, cash IS an obstacle in many of these places, so we would prefer finding an alternate solution.
>>
>>We do use Stephen Black's international toolkit, but it has not been able to address this problem, that is, being able to access the central european language script as part of the textbox properties.

Vladimir's class is a keyboard layout switcher, but it doesn't do much for the fonts displayed.
From my experience, displaying stuff in other character sets involves couple of steps:
- installing support for that codepage in Windows (meaning fonts and keyboard layouts)
- making sure that appropriate .nls files are present in the system directory
- in some W9x systems, it also takes making sure the .fon files used for the screen support the new codepage
- editing the ANSI key in registry from 1252 (Western) to 1250 (Central European) or 1251 (Cyrillic). Don't know where this key exactly is now in W2K, and I've searched my disk looking for the backups of .reg files I used to put into my startup directory while I had a W9x, to no avail. Usually it takes searching for the OEMCP value, which is under the same key.
- setting codepage=auto (or the specific codepage) in config.fpw
- reboot & hope for the best.

Some files which are parts of the project (i.e. those with .dbf structure, like classes, forms, menus, reports) may need to undergo a treatment with cpzero.prg (available in home()+'tools\cpzero' directory).

Fox is not Unicode aware, so it can display only one codepage (namely the system codepage, that's why it takes editing the registry) at a time, at least in forms, menus and reports. The editing windows, however (method code, browse windows, code, memo windows), which keep their font settings in foxuser.dbf, are codepage aware, and the script combo in font settings does work there.