INTL is a good framework that give you the ability to easily translate strings into whatever language you want. Just note that YOU have to populate the tables with the translations.

What INTL will NOT do for you is rearrange the object on forms to compensate for the different lengths of label captions when you have objects like textboxes next to them [horizontally].

What I had to do was develop a builder that I could call while running the form so the label captions would get translated. Then with this builder I could right click in a textbox, combo or whatever to bring up the builder so I could set properties like top, left, etc., for that particular language. I stored this information in a memo field in a "formobjects" table. I have fields like formname, parent and objectname. So at runtime, in my form base class INIT, I just scan the records for that formname and position the controls for that particular language. In the formobjs table, I have a memo field for each language I need that contains these positions. I got the idea from how VFP stores these properties in the memo field of the SCX.

>Hi.
>
>We are writing a rather large application in Visual Foxpro 9 beta (the app will not be finished before the full version is released). Recently, a demand for multiple languages in the UI has surfaced. I have been looking at Steven Blacks web site for the INTL toolkit, but would really like to hear som actual opinions and experiences with this toolkit from you guys.
>
>Some questions:
> - How much code change is needed?
> - Does the toolkit handle (or mark) things like Messagebox("Some error occured")?
> - What about strings that are not supposed to be translated, like quoted select statements etc?
>
>Thanks,
>
>Eyvind.