Where I can set up output file names and paths?
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
- 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.
- 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.
- Build features responsible for creation of output files are described in this article on our blog.
Janusz
Did you enjoy this post? Why not leave a comment below and continue the conversation, or subscribe to my feed and get articles like this delivered automatically to your feed reader.
This is the first article in a row of HowTo-Articles related to Sisulizer directly. They are written by the Sisulizer support team in the hope that all users of Sisulizer can make use of it.
Markus