Source Code Scanner plug-in enables Multilizer to localize source code files.
There is out-of-the-box localization support for the following source code formats:
Other formats are supported by simply specifying rules for how to identify texts and comments.
This scanner plug-in is made as simple as possible. For more comprehensive configuration options and regular expressions support, see Custom Text Scanner.
Source file. Specify the file to localize. Use wildcards to specify multiple files. The scanner tells how many files meet the wildcard criteria.
Process subfolders. Check this option, if the scanner should scan also all subfolders recursively.
Output directory. Specifies the directory where the localized files will be created. This is the directory where Multilizer creates the localized output files and subdirectories. You can specify the name of the localized files and directories by setting Type and Language code.
Note! Both Source file and Output directory can be specified either with relative path or with absolute path. Relative path is related to Multilizer project location.
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.|
Source Type. Specify the format (the programming language) of the text file to parse.
Either use the pre-defined source type or specify the options manually by selecting Custom as source type.
Settings for Custom source type:
Character that specifies begin/end of a string . This is called string delimiter.
Source scanner requires that the delimiter is the same for the beginning and the end of the string.
Some source code formats, such as PHP, support multiple delimiters. If you need support for this contact us.
|Escape||This denotes how a string delimiter inside the text is escaped.|
|Comment||Line||Begin character/string of a single-row comment. End-of-line is assumed as the end of a single-row comment.|
|Block start||Begin character/string of a block comment. A block comment can span over multiple rows. Block end character is used to mark end of a block comment.|
|Block end||End character/string of a block comment|
Native (source) language. Specifies the native language that is used in the target . Set this to match the language in the original user interface. If the original user interface contains two or more languages mixed, set the language to most widely used.
Native (source) encoding. Specifies the native encoding that is used in the target with each character set.
Encoding list. Contains the encodings to be used in the localized files. To change the value right click the line and select a new value.
Write byteorder mark (BOM). This option applies when writing out Unicode encoded files.
On this tab the user can specify additional directives for scanning source code.
Scan directives. Specify scan directives, if you have tagged the source code to specify how Multilizer should work.
By default the scanner scans all strings. It is set in Exclusive scan mode: it scans all strings except those that are specifically marked for no scanning. Strings are marked in source code by specifying an end-of-the-row comment for the source line.
If there user specifies nomlz in scan directives and the Pascal code looks like this...
str2:='2nd string'; // This is a comment
str3:='3rd string'; // nomlz
... the scanner will scan strings '1st string' and '2nd' string only.
Context format. Choose whether the context looks like the text having been scanned or as hash. Hash is the preferred way.
Context prefix. This option gives an additional part to the context for identifying the string. Setting context prefix to File name makes it easier to find the strings of a specific file in Multilizer project.
Note! Modifying the contexts requires a scan after the change. This can cause loss of translations. Therefore context settings should be set properly before starting translation.