>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.


INTL is an excellent product. The code changes are not that much IMO. You have to of course change your hard-coded literals to a function. So a button caption would not be "Save" but i("Save"). At instantiation time INTL would do a lookup into a translation table, that you have to populate, and return the caption in the current language. This allows you to even switch languages on the fly, which makes for a very compelling demo to a client.

There is a supplied replacement for MessageBox (MsgSvcs) which allows for translatinfg MessageBoxes and does more. The manual and examples are good and show you how to do reports, menus and form's controls. I would recommend INTL wholeheartedly.