I recommend making a main INTL object named _SCREEN.oINTL. It's possible to have several separate INTL objects co-exist together. Each INTL object is itself an amalgam of other INTL objects called hooks or strategies. Your main INTL object is the master INTL object in your environment, and whichever it happens to be, I assume here that it's called _SCREEN.oINTL .

Use the SetConfig( n) method to configure your main INTL object. You configure INTL with a _SCREEN.oINTL.SetConfig( n) method, where n is a bitwise integer value with the following interpretation:

Configuration integers for the ::SetConfig() method for the various INTL classes.

Example: create an INTL object that localizes strings and fonts

The operative language and locale of the main INTL object are configured with the SetLanguage() and SetLocale() methods.

How to Configure Strategies

Strategies are bitwise configured. Configuring individual strategies is easy. Simply get a reference to the strategy, then configure it. Here are the configuration meanings for each configurable strategy.

Configuration integers for the ::SetConfig() method for the various INTL classes.

To get a handle on a loaded strategy, use the ::GetStrategy() method. Thereafter, use the handle's SetConfig() method to configure the strategy.

Example: create an INTL object that localizes strings but not Tooltips. Use the oINTL.GetStrategy() method to get an object reference, then use its SetConfig() method to configure it.

Example: create an INTL object that localizes only strings and InputMasks.