Overview. VB scanner options allow the user to specify how to localize executables developed with Visual Basic.
VB Scanner is able to localize the stringtable resources of an executable developed with Visual Basic. If user wants to localize the forms, the software must be implemented in the way that form captions are read from stringtable resources for instance in LoadForm event.
The most important settings are the following:
This plug-in is available as a separate plug-in.
Output directory. Specifies the directory where the localized files will be created. This is the directory where Multilizer creates the localized output files and sub directories. You can control the name of the localized files and directories by setting Type, Coding, Locale separator and Country separator.
|Localized||Writes one executable for each target language. This option doesn't require any changes in the source code.|
|Resource DLL||Writes a resource-only DLL for each target language. If you choose this kind of output, you need to implement the logic of loading translations from desired resource DLL.|
This option is for writing multilingual executable. The resource identifiers use a specified offset to read correct language strings in the executable, so this requires redesign in software. Resource offset is specified in Advanced tab. See sample application \VB\Binary_Offset\Dcalc to see how it works.
This way of localizing VB software follows the Microsoft recommended localization architecture for Visual Basic (4-6) applications.
Type. Specifies how and where MULTILIZER creates the localized file version(s). Possible options are:
|Subdirectory||Create localized file(s) in sub directories named by language and locale.|
|Bundle name||Append the language and locale information in the output file name.|
|File extension||Replace the original file extension with language and locale information.|
Coding. Selects file name initial coding style. Possible values are:
|ISO||ISO standard coding style.|
|.NET||Microsoft .Net coding style.|
|Windows||Windows coding style.|
Native language field lets you specify what's the language of the software being localized.
Default language is a fallback language; if there's no translation in target language, the text of default language is used instead.
Native encoding allows the user to specify, what's the encoding of the native strings. This field can be left empty.
Encodings list allows the user to specify the encoding of texts for localized applications. Here you can also define the resource id offset, which is used if output is multilingual application. If the resource id for original (native) string is 101, then with the Resource Offset 2000 the resource id would be 2101.