Setting up the Multilizer project
The first step to create a custom language pack is setting up the Multilizer project.
This page explains the following topics:
To set up a multilizer project
- Download the Multilizer Editor Free tool from http://www2.multilizer.com/downloads/.
Run the Multilizer Editor Free installer and accept all the default settings. This will create a Multilizer\Projects directory in Documents folder.
For example, for Windows 7, C:\Users\<user name>\Documents\Multilizer\Projects directory.Notes
- If you created a custom language pack for a previous release, the Multilizer\Projects directory will be created in a folder such as C:\Users\<user name>\Documents\Multilizer\Projects\language-pack\<locale code>.
- If the folder C:\Users\<user name>\Documents\Multilizer\Projects already exists, move all its contents into a backup directory such as C:\Users\<user name>\Documents\Multilizer\oldProjects.
- To get the LanguagePackCreationKit.zip:
- Extract the contents of the ZIP file into the Multilizer Project directory.
For example, C:\Users\<user name>\Documents\Multilizer\Projects. - Run the Multilizer Editor Free tool from the Start menu.
- Open the FootPrintsLanguagePack.m7x exchange project file in Multilizer Editor Free.
To upgrade a Custom Language Pack from a previous release
- In Multilizer Editor Free, open the LastFootPrintsLanguagePack.m7x exchange project file. Opening the compressed exchange projects in Multilizer Editor Free automatically creates uncompressed versions of these projects, which have m7p extensions that are required for the Multilizer Project Translation Updater Tool in the steps to follow.
- Close Multilizer.
- Create a new folder C:\myLastCustomLanguagePack and copy the last custom language pack that you generated, FootPrintsLanguagePack.xml, to this folder.
- To create a new language, go to the command prompt and run the Translation tool command.
Copy all the existing translations from your previous Custom Language Pack to the new Multilizer project (FootPrintsLanguagePack.m7p) by executing the MultilizerProjectTranslationUpdaterTool from the command line. Provide the following parameters:- projectlocation - The location of Multilizer project files.
lastcustomlanguagepacklocation - The location of your last Custom Language Pack.
For example,java -cp C:\MyLanguageProject\languagecreator.jarcom.numarasoftware.footprints.tool.translation.MultilizerProjectTranslationUpdaterTool -projectlocation C:\MyLanguageProject\ -lastcustomlanguagepacklocation C:\myLastCustomLanguagePack
Examples of System Responses:
Starting Multilizer Project Translation Updater... The Multilizer file contains 5,358 strings. Checking the Language Pack for existing translations. Please wait... . . . . . . . . . Copied 5,173 translations to the Multilizer project from the language pack. Backing up Multilizer project file Generating new Multilizer project file Finished Multilizer Project Translation Updater
- Close the command window.
- In Multilizer Editor Free, open the FootPrintsLanguagePack.m7p Multilizer project file.
- Go to To enter translations.
To create a Custom Language Pack for the first time
- To add a new language to the project, click Select Languages.
- To add a new language to the project, select the required language/country from the Available languages list and click to move it to the Target languages list, and click OK.
- Go to To enter translations.
To enter translations
Select the new language from the Language Selection list. This displays the language’s translation column in the Translation Grid.
- Select a Native Text string that requires translation from the translation grid.
- Enter the translation for the Native (English) string in the Translation text box.
Navigate through the strings using the arrow keys, and add translations for the remaining strings.
Note
Strings that are not translated will be displayed in English.
Save the project.
Note
Saving the project creates a Standard Multilizer project file with an m7p extension that is required for creating language packs.
- Exit Multilizer.
Comments
Log in or register to comment.