Hi Zlatin,

Just so there is no confusion, INTL is written in Foxpro so anything Foxpro can do, INTL can do. Thus when you say that "I belive that in your case INTL will fail", then more accurately what the perspon seeks to do is not possible at all using Visual FoxPro.

As long as the developer uses only the lower 128 characters of a code page, then they can switch to any language on the planet. I have many customers in Eastern Europe who develop for other locales. To do this is simply a matter of using only the lower 128 characters in the source "original" language.

This is actually incredibly easy to do. Many of my customers use a pseudo-developer language for the original language, and shell out to "USA English" or "British English" or even "Military English" from a root application that's also English. Still others use full-blown developer language for the original language, and the application natively displays field names instead of regular captions. In other words, instead of

Firm [ ]

The in-house developer sees

Customer.cCompany [ ]

Therefore there is a lot more than first meets the eye here...


**--** Steve



>
>>HI Denis, do I understand correctly that you want to change the language your messages are displayed in? If so,
>>
>>I would check out INTL at http://www.stevenblack.com
>>
>>Tracy
>>
>
>
>My regards to Steven Black, but his INTL framework DOES NOT handle strings correctly if you develop under different locale CP, from the target CP.
>
>If you develop using Western European CP, you will not be able to use messages in languages like Greek, Russian, Chineese etc.
>
>See the following UT threads if you do not believe me:
>Thread #456319 and Thread #613860
>They have both the same author, that have tested the INTL framework and it does not do the job for him.
>I belive that in your case INTL will fail
>
>Correct me if I am wrong.
>Kind Regards