>> Well after a month you may think that you do not have done all the things VFP can do for developing multilanguage applications.

What does this mean? Can you rephrase this?

>> Well pseudo-simplified-chineese sounds good. Give me an example please.

What is pseudo-simplified chinese? I don't understand the question. Are you aware that you must be running on an oriental Version of Windows to take advantage of many of VFP's oriental capabilities? Are you also aware that there are Chinese localizations of VFP? Are you trying to make Chinese display with a western version of Windows/VFP? Are you also aware that you can do Chinese localizations without using Unicode? I don't understand your situation and what you are trying to do.

**--** Steve


>>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.
>
>Well after a month you may think that you do not have done all the things VFP can do for developing multilanguage applications.
>
>>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.
>
>Well pseudo-simplified-chineese sounds good. Give me an example please.
>I think that my handling of unicode strings and entering them in tables can do a lot of the work. I have some problems with the fonts in VFP, but in general I think that this, that you think is "not possible at all" is just "hard to see at first glance"
>
>I know that VFP does not support UNICODE directly - this is why I am working around this!
>
>Kind Regards