>Hi Dragan,
>
>So - is yours a NO answer to the question whether I can have a single VFP app truly serving for Western European languages and Greek (or Russian or Serbian) at the same time?
>Or, to correct myself rather, - an internationalized application where I'd use VFP tables for run-time translations and make a good use of Steven Black's INTL.
>
>Apparently, I cannot?
>
>I could use RTF, - many thanks to Ron Brahma for sharing the technique - but it won't not solve the menus-labels-messaging task.
>And to my knowledge, there is no Greek version of VFP ( as well as Russian?)
>
>Also, back again to my original question about a Greek only VFP app.
>Does this mean it can only possibly *practically* work with Windows set up as Greek 1253 (if I were not to only use RTF)?
>
>I also read from your discussion with Nadya Mosonovsky back in February ("Customizing my VFP environment..."), and as slow as I am in getting all these languages-codepages-fonts settings and issues, it feels as though this is the verdict...
>Am I right? Or - not quite again?

Not quite - neither of us. As Ron says, VFP can't deal with fonts with multiple codepages (or scripts, as they are called in the font selector), like the elementary Arial, Times NR and Courier that you get with each Windows, at least not by itself. It uses only one codepage out of them, and that is - the one which corresponds to the active codepage for that machine (see the registry entry I pasted above in this thread). Now since elementary English, Italian and maybe a few other languages use only the lower part of the ASCII table, most of the other languages use at least some characters from the upper part of it (the Chr(128) to chr(255), those are the 128 that Steven Black mentions). This means that, since VFP uses only the system-wide defined codepage, you can run it in Russian and English, Greek and English, Polish and English, but not all three combinations at the same time - you'd need different machines, or rebooting with a different value of ACP in the registry.

You have probably seen apps which can switch between codepages at runtime, like Word (and the rest of the Office), Web browsers (tried with both Netscape and Explorer, both show them fine), and I think Access after some version, but they either have the capability of storing their data in Unicode format (which means two bytes per character) or use HTML (or RTF) tags to denote the language of the current piece of text.

VFP has no way to do that as of v6.0 SP3, and if anyone knows of its capabilities on this matter in VFP7, that one's probably bound by the NDA and can't speak now.

So, to your original question, it will work in Greek on a machine where ACP=1253 (so the default codepage to show in fonts is the Greek codepage) and international support is installed (so we actually have the fonts and language support tables at the system level). Other than that, you may try to add codepage=1253 line into your config.fpw, and use home()+'tools\cpzero\cpzero.prg' to convert the codepage of your tables (including .scx, mnx, pjx, vcx files) to codepage 1253, but that still doesn't guarantee you'll see Greek on your forms, reports and menus.

I'm not doing any of this codepage anymore - note the flag - but I remember what a hassle it was.