Creating a new translation file
This help topic refers to a previous version of InstallMate. It has not been updated for InstallMate 9 yet.
InstallMate projects can be extensively localized. Once created, each .im9 project file contains all translations that are required for the project. However, when you create a new project, InstallMate uses a two-pronged approach:
- The project contents proper are taken from the project template that you selected in the New Project wizard page Project template. The project template files are stored in the InstallMate\Projects folder on your system and are listed on the Project template wizard page.
- The available translations for the various languages are taken from a separate set of files, stored in the InstallMate\Languages folder on your system. These files are listed on the Project languages page of the New project wizard.
If desired, you can add your own translation files to the InstallMate\Languages folder (or any other folder). The recommended procedure to do so is as follows:
- Create a new blank project that only uses English and save it under the English name of the language that you are translating into, for example Dutch.im9, Italian.im9, or Russian.im9.
- Go to the Languages project page. You will find the English (United States) language there. Right-click on this language, choose Change Language... from the popup menu, then select the language that you are translating into.
- Save the project file (Ctrl+S). While you are working on the translation, keep saving on a regular basis.
- Work through the project on a page-by-page basis, using the notes below as a guide while you are translating.
- (Optional) items are optional
- (Recommended) items are also optional, but have higher priority
- Do NOT change the following:
- Items that are marked "Do NOT translate" below.
- Items that are enclosed in <angle brackets>
- Items that are enclosed in [square brackets]
- Items that are not specifically listed for translation
- When you are done, go back to the Languages project page, select the new language, right-click and choose Export Translations... In the Select Objects for Export dialog box that appears, select all objects in the list (use Shift+Click), click Select, then select an output file name. Please observer the following:
- Do NOT overwrite any of the pre-existing language files.
- Set the Encoding field to Unicode UTF-16 (the default) or Unicode UTF-8.
Tip: You might find it useful to start a second instance of InstallMate and create a second blank project in that one. You can then switch between the two instances and compare your translation with the original English version.
Once you have exported the translations to a separate file, you can re-import them in subsequent projects. If you saved the translations file in the InstallMate\Languages folder it will automatically appear on the Project languages page of the New project wizard; if you saved it elsewhere, you can use the Import translations command on the Languages project page to import it.
Translation notes for specific pages
Use the notes below as a guideline during your translation.
|Product info||Do NOT translate anything on this page.|
|Requirements||Nothing to translate on this page.|
|Files and folders||
The translation of the folder names in the Target System tree on this page is OPTIONAL. Even if you do not translate them, the correct (localized)names will be used during installation.
Moreover, some of the folder names or folder locations in the tree vary between Windows versions. DO NOT ATTEMPT TO "CORRECT" THIS. The installer will automatically use the correct location for the Windows version on which the product is installed.
However, if you do translate the folder names, be sure to use the correct localized names.
Translate the following:
Do NOT translate these:
Translate the following variables (only their Value field):
Do NOT translate the other variables.
|Registry||Do NOT translate anything on this page.|
|INI files||Do NOT translate anything on this page.|
|Environment Variables||Do NOT translate anything on this page.|
|File types||Do NOT translate anything on this page.|
|COM classes||Do NOT translate anything on this page.|
|Services||Do NOT translate anything on this page.|
|Languages||Do NOT translate anything on this page.|
|RichTexts||(Optional) Translate the sample License1 and Readme1 texts.|
|Bitmaps||Do NOT translate anything on this page.|
|Icons||Do NOT translate anything on this page.|
|Font styles||Do NOT translate anything on this page.|
|Installer options||Nothing to translate on this page.|
|User interface||Do NOT translate anything on this page.|
Translate the following.
_EntryHandler action sequence:
DoUninstall action sequence:
MainInstall action sequence:
UIFirstInstall action sequence:
IMPORTANT NOTE: Do NOT make any text fields smaller. If you find any text fields that are too small, please let us know so we can change them.
Translate the text fields, button labels, etc., in all dialogs except as noted below.
Translate all "Localized text" fields. Please note that some fields start with a space, or contain line breaks, or end with a blank line. That should remain similar in your translation.
The %s, %d, and similar texts are placeholders for runtime data. They MUST appear in the translation.
In some cases, '&' characters indicate keyboard shortcuts. Choose similar shortcuts in your translation (usually the first letter). For some languages, for example Chinese, Japanese, and Korean, it is customary to place the (English) keyboard accelerator in parentheses after the actual label: ...label... (&E).
|Build Configurations||Do NOT translate anything on this page.|