Information for Downloaders:Innoview
|
Dictionary Components: Dictionary components contain the information of translation, language and locale tables. In addition they define the current language and locale settings. |
|
TIvServerDictionary | This component is used for getting access to a dictionary on a server running Multilanguage Dictionary Server. |
TIvFileDictionary | Dictionary that uses external dictionary files. |
TIvEmbeddedDictionary | Dictionary that embedds the dictionary files into the exe-file Using this it is possible to build up a single file multilingual application. |
TIvDBDictionary | Dictionary that uses database tables. |
Translator Components Translator components do the actual translation. They need a dictionary component to function. Translators define, e.g., the target components to be translated. |
|
TIvTranslator | Standard translator for translating single properties, e.g., caption, text. |
TIvExtendedTranslator | Translator if the application uses TTreeView, TListView or TOutline components. |
Common Dialog Components Innoview Multilanguage Common Dialog components include one extra property Dictionary, which connects the component to the application's dictionary. |
|
TIvOpenDialog | Multilingual version of TOpenDialog. |
TIvSaveDialog | Multilingual version of TSaveDialog. |
TIvColorDialog | Multilingual version of TColorDialog. |
TIvFontDialog | Multilingual version of TFontDialog. |
TIvPrinterSetupDialog | Multilingual version of TPrinterSetupDialog. |
TIvPrintDialog | Multilingual version of TPrintDialog. |
TIvFindDialog | Multilingual version of TFindDialog. |
TIvReplaceDialog | Multilingual version of TReplaceDialog. |
Multilanguage Standard Components Innoview Multilanguage standard components include one extra property Bidirectional, which enables/disables bi-directional writing (Middle East character sets only). |
|
TIvLabel | Multilingual version of TLabel. |
TIvGroupBox | Multilingual version of TGroupBox. |
TIvRadioGroup | Multilingual version of TRadioGroup. |
TIvListBox | Multilingual version of TListBox. |
TIvComboBox | Multilingual version of TComboBox. |
TIvStringGrid | Multilingual version of TStringGrid. |
TIvDrawGrid | Multilingual version of TDrawGrid. |
Multilanguage Data aware Components Innoview Multilanguage data aware components include one extra property Bidirectional, which enables/disables bi-directional writing (Middle East character sets only). |
|
TIvDBText | Multilingual version of TDBText. |
TIvDBRadioGroup | Multilingual version of TDBRadioGroup. |
TIvDBListBox | Multilingual version of TDBListBox. |
TIvDBComboBox | Multilingual version of TDBComboBox. |
TIvDBLookupListBox | Multilingual version of TDBLookupListBox. |
TIvDBLookupComboBox | Multilingual version of TDBLookupComboBox. |
TIvDBGrid | Multilingual version of TDBGrid. |
To set up Innoview Multilanguage component:
To add Multilanguage help to Delphi's help system:
To add the Multilanguage components to the component library:
To add Multilanguage help to Delphi's help system:
To add Multilanguage components to the component library:
To add Multilanguage help to C++Builders help system:
The following steps will explain you a typical way to use Innoview Multilanguage. It is not the only way to use the product but its a good place to start. In time you will modify the procedure to meet your requirements.
The use is straightforward in standard cases:
1. Let Dictionary Editor's Wizard create a dictionary.
2. Add the Multilanguage components
3. Write the application
4. Let Dictionary Editor scan the application source file(s)
5. Translate the dictionary.
(6. Run your multilingual program!)
STEP 1: CREATE A DICTIONARY
The main idea of a multilanguage component is to iterate each child component of the form or the component and translate their Labels, Hints, Text... to another language. The translation is made by finding the corresponding string and replacing the old one with the new one. For that, Multilanguage needs a lookup table - the translation table. It contains all the strings the application uses in each language. In addition to the translation table, Multilanguage (and Windows) needs to know, which is the current language. To provide this information each dictionary contains another table called the language table. It contains information about the languages that the translation table contains.
Switching between languages is not good enough in an advanced multilingual program. The program also have to adapt itself to some local customs and standards such as date and time formats, currency and measurement system. To provide this Multilanguage uses locale data, provided in a third table called the locale table.
Note: All the tables described are created easily by Dictionary Editor's Project Wizard.
STEP 2: ADD MULTILANGUAGE COMPONENTS
Generally you have to create one dictionary for the application and one translator component for each form you have. You can visually insert a dictionary component and translator component to each form, set the properties and finally open the component in the constructor of the form. This might, however, be quite laborious in the case of several forms. In such case it is usually a good idea to derive your own form from the TForm and include TIvTranslator component to the derived form. Doing this you dont have to manually include TivMultilanguage component to every form. (See online help to get more information.)
STEP 3: WRITE THE APPLICATION
Each dictionary must contain the translation table, language table and the locales table.
If you use TIvFileDictionary or TivEmbeddedDictionary component, set the FileName, LanguageFileName and the LocaleFileName properties. If you use TIvDBDictionary, set the DatabaseName, TableName, LanguageTableName and LocaleTableName properties.
You must also specify the language using the PrimaryLanguage and the SubLanguage properties. Set the Targets and Dictionary properties of the TIvMultilanguage component.
You must open the TIvTranslator component in the constructor of the form by calling the Open method, which opens the dictionary (if not already open), iterates each component in the form and translates their texts. If you later want to change the language, just set the new value to the Locale or the Language property.
The Translate method of the TIvDictionary component can be used to translate other text (e.g. the system messages) from the native language to the current language. Use the multilingual routines to format measure quantities, format messages, show message or query boxes.
STEP 4: SCAN THE APPLICATION
Every now and then it is a good place to scan the application with the Dictionary Editor. It informs you, if it found any new strings to translate.
STEP 5: TRANSLATE THE DICTIONARY
Up till now you have programmed the application, created the dictionary and scanned the program files to update the dictionary. Your multilingual program is almost ready. The last task to accomplish is to translate the dictionary. It can be easiest with the Dictionary Editor.
If you use a file dictionary or an embedded dictionary, you can edit the dictionary file with any Windows based text editor (e.g. Notepad), too. If you use a database dictionary, you can edit the dictionary file using the Database Desktop application. Of course, Dictionary Editor can be used for editing of all kind of dictionaries.
If you have downloaded the demo version of MULTILANGUAGE Professional Edition for Delphi and C++Builder, you may wish to obtain the official version of the product or order additional copies for other developers. The commercial version of Innoview Multilanguage is available by direct purchase from all Innoview's authorized resellers.
Suggested retail pricing for Multilanguage products is as follows:
# MULTILANGUAGE, Professional Edition 2.0 - $ 990 (USD)
# MULTILANGUAGE, Professional Edition 2.0 (With Source code) - $ 1.990 (USD)
We also offer volume discounts for purchase of 5 or more licenses (Ask more: Contact Info).
After you have purchased the offical Multilanguage license, you can make the online registration at Innoview's web site or fill up the registration card and mail it to us. This will enable your personal account in at Innoview's Internet server (http://www.innoview-data.com).
Using the account you can download updates and product (build) updates. You can also join to mailing list that keeps you updated about Multilanguage Globalization Suite and multilingual programming technology.
Note: The registration card comes only with commercial product purchased from authorized Innoview reseller.
For complete instructions on using the Multilanguage Globalization Suite, see Multilanguage Online Help. You can also get more information and tips from Innoview's Internet site.
If you have a question about Innoview Multilanguage component,
* | Email: | [email protected] |
* | Internet: | http://www.innoview-data.com/support/ |
* | TEL: | +358-9-4762 0551 (time zone: +02:00 GMT) |
* | FAX | +358-9-4762 0555 |
There are two other separate products completing the Innoview MULTILANGUAGETM Globalization Suite:
MULTILANGUAGETM for Java completes the Innoview Globalization Suite´s client site tools. It continues the family of easy-to-use components and tools for software internationalization. It enables the creation of multilingual and platform independent software. Follow the News and Press Releases section at Innoview's Internet site for news on this product.
MULTILANGUAGETM Dictionary Server (MDS) makes possible the world wide distribution of Multilanguage dictionaries. Using MDS, the dictionary is located on a server. Using a TIvServerDictionary component on your form instead of other dictionary, your program is able to use remote dictionaries. Then all your programs using Multilanguage components can use this remote dictionary. This enables centralized and cost-effective managing of your multilingual applications. You can obtain an evaluation version of MDS from Innoview's Internet site.
Postal Address: |
Etelaranta 14 A 6 FIN-00130 Helsinki Finland |
Email: | [email protected] |
Internet: | http://www.innoview-data.com |
Phone: | +358-9-4762 0550 |
Fax: | +358-9-4762 0555 |