Three simple steps to localize
The German and French Online-Help pages have been created with the help of machine translation. In doubt please read the English original.
Use this sheet to specify the Visual Basic localization options.
Context method specifies how context value of formed. Possible values are:
|Item index||Item index is the string context. Each item (code or string) has an index value that is a counting integer values starting from 0.
Compared to String value method this method creates own row for each instance of the same string letting you to translate them in a different way.
This is the default value.
|String value||String value is the string context.
If the source code contains same string twice of more then all instances share the single row and they all are translated in the same way.
Both methods can be used with any file. The difference is how duplicates strings are handled. Item index creates as many rows as there are duplicate strings. String value method always only one row for each string.
Specifies if visual source code editor is displayed or not. Uncheck this is you do not want the translator see your source code.
Note! Unchecking this does not completely remove the source code data from the project file. Even if you uncheck this source code can be extracted from the project file even it is not trivial. If you want to be 100% sure that your source code does not leak do not send Sisulizer project files (.slp) to translators but use TMX or Excel as exchange format.
If checked Sisulizer does not locale strings that is in most cases not supposed to be localized. The actual strings depend on the source code type but for example strings in the include file and pragma lines are excluded.
If checked Sisulizer compiler the localized project to an EXE file.