Use this sheet to specify the file options such as run parameters.
If the source file is a library file such as DLL or OCX you can define a host application that is used to load the library. Enter the application name or click ... to browse the file.
Specifies the parameters that are passed to the application when it is run. This value can contain the file and language code parameters.
For example
-s -<iso> -admin
will be expanded to
-s -de -admin
when the current language is German.
Specifies a .h file that contains the symbolic names of the resource id. If you specify this Sisulizer uses these symbolic names instead of the resource ids that are integers. Let's have an example. We have two files: resources.rc that contains the resources and resources.h that contains names and ids. resources.h contains the following line:
#define IDS_ABOUTBOX 101
It give IDS_ABOUTBOX symbolic name and integer id 101. resources.rc contains the following lines:
STRINGTABLE BEGIN IDS_ABOUTBOX "&About Converter..." END
When the resource compiler compiles the above resource it gives the string id. The id is an integer number 101. This is stored to the resource data of EXE file with the actually string. When Sisulizer scans the resource data it gives the string id that is 101. Unfortunately this id does not tell much about the string and its context. If you give the resource id file Sisulizer uses the symbolic name of the id (IDS_ABOUTBOX ) as context. This gives more information to the translator than plain number of 101 would give.
If you set the resource id file name Sisulizer uses symbolic names instead of integer values on every possible id. This also makes it possible to import translations from localized .rc files.
Check this if you want to scan texts of spin controls.
Check this if you want Sisulizer to scan the Visible property of dialog elements. This makes it possible to hide some elements in the localized dialogs.
Check this if the application uses Microsoft Foundation library (MFC).
In Windows resource files strings are stored into string tables. There can be many string tables in a single EXE-file. By default a separate tree node for each string tables will be created. You can however to choose to combine every string rows into a single string node by checking Single string table
Some tools combine string into a single string table. In that case you can also choose the same option. After that importing from existing EXE-file can be properly done.