Category: How To…

Sisulizer hasn’t implemented feature for directly merging several projects to one project. However, you can do it with Sisulizer in really easy and flexible way:

1. First, you should add all sources to one project, which belong to second project. You can add these new source items to project via “Add source” UI items available via “Project” menu, main toolbar icon or via context menu of Project Tree.

2. If your second project contains some translation languages unavailable in your targeted project, you should add these languages to this project via “Project” menu -> “Languages” or via “Select target language” dropdown menu on main toolbar.

3. Next, you should use “File” menu -> “Import”. This UI item opens dialog of Import Wizard. In first step you can select imported languages. Of course, you can use here standard Windows keys (Ctrl and Shift) for selecting multiple languages. Clicking on “Next” button navigates you to next wizard step, that is, “Import Wizard – Options”. Here you can find all import options. Below are short descriptions of most important options.

Import method

• By value – Sisulizer compares original values in both projects during import. The item is imported to all rows where the original value equals to the original value of the import item. This setting could automatically translate not translated originals in your first project which have been translated already in second project. However, you can lose some translations from second project, if this project contains originals translated in different way.
• By context – Sisulizer compares context values in both projects during import. The item is imported to the row where the context value equals to the context value of the import item. You can use this setting, if you would like get translations exact matched with translations from second (imported) project. So this option can be useful, if you have duplicate originals which have been translated in different ways in imported project.  However, this setting doesn’t translate automatically not translated items in first project identical with items from second project.
• By context first then by value – Sisulizer tries first to import by context. If no match, then import by value. This setting combines merits of both mentioned above methods.

Import also those items where the translated value equals to the original value
Some translations should be identical with identical with originals, for example names or some common captions (e.g. “OK” buttons) in most languages. So you can check this option.

Import only if context and original value match
I recommend checking this option, if you would like get results exact matched with your second (imported) project.

Import translation status:
I recommend checking of “Yes” option, because it allows you import to first project all translation statuses from second project

Comments
If your imported project contains translation comments, you can select “Import if there is no comment at the moment” setting, because it allows you import these comments.

Misc
If your second project contains items with “Do Not Translate” status and with maximum string length setting, you should also check following options:

• Import Read Only status
• Import maximum string length value

When you are ready, simply click on “Finish” button, and that’s all.

Janusz

This issue could have different reasons, but most common reasons are:

1. You have checked “Integer” item on list of excluded data types in source properties -> “Excluded types”. You can open source properties via Project menu -> “Edit source”, or via “Properties” item in context menu of source node in project tree.
X, Y coordinates, width and height values are integer numbers, so if you want to change these values you need to enable integer numbers for localization in source properties.

2. You have checked “Project” menu -> “Options” -> “Lock all the components” option.

3. You have checked “Locked” option in “General” settings of “Visual Editor Properties”. “Visual Editor Properties” are available via “Tools” menu -> “Editors”-> “Form” item, or via context menu of Visual editor.

Janusz

Red dots in translation cells mark items with so called “Invalidated” status. Sisulizer automatically assigns this status to rows with existing translations marked with “Changed” status after scan for changes (red dot in Flags column of translation sheet). Invalidated status is cleared automatically after edit of translation for changed original. If you don’t change translation for changed original, you need manually clear this status via row context menu -> “Translation” -> “Invalidated” (Of course you can also check this item for any translation cell). If you use “Project” menu > “Clear Changed Status” all “Changed” statuses will be cleared and by accident you can overlook important changes in original strings required also changes in translations. You can’t revert “Changed” status for items in project, but “Invalidated” dots allows you still to find these potential overlooked items.

Hint

You can use special filter for filtering of invalidated items via “Sheet Filter” -> “Other” tab. It allows you to find quickly all invalidated translations in project. Additionally you can exclude/include invalidated items from/to exchange package (“Exchange Wizard – Filter” step of wizard -> “Other” tab) or export file (“Export Wizard – Options” step of wizard -> “Other” tab). Below is a screenshot with this filter for translation sheet.

Janusz

If you would like create localized versions of your sources included to project, you should use “Build” features available via “Project” menu, main toolbar icons and project Tree icon:
Below is a list of “Build” features available via “Project” menu:

• “Build in Selected Language” – this feature creates localized version of source file selected from sub menu for currently edited language
• “Build All sources in Selected Language” – this feature creates localized versions of all source files included to project for currently edited language
• “Build All sources in All Languages” – this feature creates localized versions of all source files included to project for all project’s languages
• “Build…” – it opens dialog window where you can select items (sources and languages) to batch building, e.g. Czech version of one source file, French version of second file etc.

“Build All sources in Selected Language” and “Build All sources in All Languages” items are also available via icons on standard toolbar of main Sisulizer window

…and via context menu “All” node of Project Tree.

If you right click on source node item in Project tree, you can find following “Build” items in context menu:

• “Build in Selected Language” – it creates localized version of selected source for currently edited language
• “Build All sources in All Languages”- it creates localized version of selected source for all languages.

Hints

1. Build features aren’t available in Sisulizer’s Free edition. If you need e.g. a subsidary or distributor to build the localized version he needs Sisulizer Translator edition.
2. Sisulizer can’t create localized files without access to your source files. You can set up source file paths, output file paths and names via “File” tab of your source properties. These features are described in this article on our blog.

Janusz

You can set up different output file path names for each source of your Sisulizer project. You can change output path and file name paths via “Project” menu -> “Edit source” -> select your source -> “File” tab or via right click on your source in Project tree -> select “Properties” item from context menu -> “File” tab. “File” tab is very important item of Sisulizer, because it contains:

• Source file setting with file path field, where you can select source file path. Sisulizer selects a path to source file automatically during adding source file to project, but here you can change it. Correct path to source file is necessary for scanning process and of course, to build output files (Sisulizer can’t build output files without access to source file)
• Output files settings. Sisulizer automatically selects most appropriate output parameters for your platform, but you have possibility of changing and adjusting all these output settings.

Important note: source file and output directory paths are always displayed as full paths, but Sisulizer internally use relative paths, so you can move your directory with sources, Sisulizer project and output directory to another drive or even PC.
Below you can find descriptions for all common output settings and parameters:

Output directory

This is the root directory where Sisulizer creates localized files with optional source directories structure and specified directories created by Sisulizer. By default the output directory is the same directory where the original source file is located. You can change this by pressing button (browse) on right side of combo box.

Output files

Here you can specify type of output files (check box) and their names (filename combo box). Available types of localized files depend on your source file platform. For example recommended output file type for Delphi applications is resource DLLs, while of course, you can’t use this type of output file for HTML or txt source files. Below is a short preview of output file kinds capabilities:

• VCL and Visual C++:  Localized files, Multilingual file, Resource DLLs, Embedded resource DLLs
• XML files:  Localized files, Multilingual file
• .NET binary and projects, TXT, Java, HTML, INI, Qt etc.:  Localized files

If your source file platform allows to use more than one output file kind, you should see in “Output files” section additional  checkboxes for every available kind of output files for selecting your favorite method. We recommend using only one kind of output files, but of course, you can check more than one method, or even all. For all output file kind you can also set up separated output file name parameters. It could be good solution for testing Sisulizer capabilities and, next select one, final method.
Below you can find short descriptions of all available kinds of output files:

• Localized files: Sisulizer creates a  localized files for each language in the project. For example if the original file is MySample.exe and the project contains German and Japanese, Sisulizer creates de\MySample.exe and ja\MySample.exe. These files are equal to the original file except resource data has been localized.
• Multilingual file:  Sisulizer creates one multilingual file containing all the languages of the project. For example if the original file is MySample.exe, Sisulizer creates all\MySample.exe that contains resources in each language of the project.
• Resource DLLs: Sisulizer creates localized resource DLL files. They are resource-only DLLs that contains the same resource data as the original file but the resource data has been localized to the target language. You can use it with Delphi and C++Builder (VCL) and Visual C++ (MFC) files.  For example if the original file is MySample.exe and the project contains German and Japanese, Sisulizer creates Sample.DE and Sample.JA resource DLL files.
• Embedded resource DLLs: Sisulizer creates an output files that contains all the resource DLL files embedded into the original file. Such an EXE can support several language in one file and the user can even change the language of the application on run time. The output directory for the embedded file is “emb”.

If your source file platform supports only one output file kind (localized files) you can find in “Output files” section only file name combo box (without above mentioned checkboxes), because you can’t change output file kind.

In next step you can type appropriate file name for output files.  Of course you can directly type file name, but this is very impractical solution if you would like to create output files for several targeted languages, because you can type here only one file name. So if you would like create files for 10 languages you should do it in 10 filename combo boxes!  But what happens if you add next 3 languages? Don’t worry Sisulizer has implemented “…” button by the combo box, Sisulizer open dropdown list (visible on attached screenshot) with friendly captions of all available patterns, and you need only click on desired item. Of course you can select from list more items, and Sisulizer add next pattern one by one. Of course, you can then manually adjust your pattern in combo box.

Short descriptions of all patterns

Add sub directory
Syntax: <dir>
Description: Variable is replaced with the relative directory to the source file including the last backslash. If the file locates in the same directory as the source directory this parameter is ignored.
Example: If the source file is C:\MyFiles\*.html and if the file to be processed is C:\MyFiles\SubFiles\Sample.html variable is replaced with SubFiles\

Add file name
Syntax: <file>
Description: Variable is replaced with the original file name with extension.
Example: C:\MyFiles\Sample.exe -> Sample.exe

Add file name without extension
Syntax: <body>
Description: Variable is replaced with the original file name without extension.
Example: C:\MyFiles\Sample.exe -> Sample

Add item name
Syntax: <name>
Description: Variable is replaced with the fixed name of the file or original file extension without period (if the file does not have a fixed name). Fixed name is a name determined by the original platform and it can’t be fixed (e.g. .NET specifies assembly name in the project file and that name must be used in order to enable satellite assembly file).
Example: C:\MyFiles\Sample.exe -> MyName

Add file extension
Syntax: <ext>
Description: Variable is replaced with the original file extension without period.
Example: C:\MyFiles\Sample.exe -> exe

Add Sisulizer language code
Syntax: <sl>
Description: Sisulizer’s locale code is used.
Example: “en” is for English, “en-US” is for English (United States), and “zh.tra” is for Traditional Chinese. The default Chinese script is the Simplified Chinese. This is why the language code of Traditional Chinese is “zh.tra”.

Add ISO language code
Syntax: <iso>
Description: ISO locale code is used. It is combination of language and country.
Example: “en” is for English, “en_US” is for English (United States), and “zh_TW” is for Traditional Chinese. ISO language code does not have any way to code a country neutral Traditional Chinese. That is why Chinese (Taiwan) is used.

Add .NET language code
Syntax: <net>
Description: NET culture code is used. It is combination of language and country.
Example: “en” is for English, “en-US” is for English (United States), and “zh-TW” is for Traditional Chinese. .NET language code does not have any way to code a country neutral Traditional Chinese. That is why Chinese (Taiwan) is used.

Add Windows language code
Syntax: <win>
Description: Windows locale code is used. It contains two or three upper case characters.
Example: “EN” is for English, “ENU” is for English (United Stated), and “CHT” is for Traditional Chinese.

Add MFC language code
Syntax: <mfc>
Description: MFC locale code is used. It contains three upper case characters.
Example: “ENE” is for English, “ENG” is for English (United Kingdom), and “CHT” is for Traditional Chinese.

Add decimal NLS language code
Syntax: <nls>
Description: Windows locale id is used. It is a integer number containing the primary and sub language ids.
Example: “9” is for English, “2057” is for English (United Kingdom), and “1028” is for Traditional Chinese.

Add hexadecimal NLS language code
Syntax: <hex>
Description: Windows locale id is used, but four digit hex value is used instead decimal value.
Example: “0009” is for English, “0809” is for English (United Kingdom), and “0404” is for Traditional Chinese.

Hints

1. Below combo box you can see sample path based on your output directory path and selected pattern. It allows you quickly check your output setting without building output files.
   
2. If you type backslash after pattern item, Sisulizer doesn’t apply pattern item to output file name, but creates folder with name based on pattern item. For example, for Polish version of sample.exe and pattern <body>\<body>.<mfc>, Sisulizer create \sample\sample.PLK output path.
3. Build features responsible for creation of output files are described in this article on our blog.

Janusz