Aaron,

>Have you any plans on how you will build the multi-lingual translation tables from an existing application ? Will you have a utility that scans through the source code looking for text strings which are then added to the translation tables ? If so, how deep will the scan go, i.e. will it also see message strings and tooltips in the code in addition to each control's Text property ?

Actually, the way localization works in MM .NET you don't need to add the original language text to the tables. The only text that gets added is the translated text. If text isn't translated for a particular language it shows up as the original text. As we speak we are adding translation forms to MM .NET that an end user can launch. These forms display all the original text in a form or menu and allows the end user (or developer) to translate the text. That said, when it comes to system messages (such as those displayed in a dialog) are stored by developers in the Messages table. We have a multi-lingual version of the MessageBox that reads from the Messages table to display the appropriate text for the message and the button text.

>By the way, has the documentation on your web site been updated recently ?

I'm not sure when you looked last, but it has been updated recently.

Regards,