>>Because vfp will not allow to select scripts in fonts, this implementation must use custom fonts and change all fonts to others?
>
>I do not understand this question. VFP certainly allows you to change fonts.

Fonts yes, but not scripts within fonts. It allows you to change scripts there where it opens regular font dialogue for editor, memo fields, browse windows and such, but in form and/or report designer it doesn't. In forms, there's no such thing as a possibility to define script used - it strictly conforms to the Windows ACP (Ansi code page). In reports, it calls the font dialogue where it lets you specify the script, but doesn't really use it or save it at all. In my case, it would be nice to have both cyrillic and latinic versions of the same report, but then I'd have to reboot with a different codepage to be able to work with the other codepage, and of course I couldn't work with the first one anymore.

M$ has solved this nice in Office 97, but then it uses Unicode anyime it likes, and VFP doesn't. Maybe we could use some API to do it?