Use this dialog to configure text settings. Text settings are used with text file localization.
Use this sheet to configure text format rules. Sisulizer can localize and import data from various text based files. In order to properly scan the text file you need to specify the format. It is done by defining text rules. It is possible to specify the rules case by case but if you need to constantly work with certain file type you can define the set of rules and give it a name. Finally you can attach the rules to a file extension.
The combo box on the upper side of the dialog contains the configured rules. Select the rule definition you want to edit. Click + button to add a new. Click - to remove the selected one. Click notepad image to rename the selected definition.
Specifies when the selected rule definition is used. Possible values are:
|Localizing files||Definition is used when localizing files. In this case the definition must contain a context item and text items do not contain language attributes.|
|Importing files||Definition is used when importing files. In this case the definition can contain a context item but it is not required. Each text item must contain language attribute.|
Specifies the character format of the file. Possible values are:
|Detect encoding each time||Sisulizer detects the format of the file. If it can not be detected the file is read as a Windows code page encoded file.|
|ANSI||File contains code page encoded data. The actual code page is specified in the Encoding property if the rule. If no encoding is given the default Windows code page of the language of the rule or file is used.|
|UTF-8||File contains UTF-8 data.|
|UTF-16, little endian||File contains little endian UTF-16 data.|
|UTF-16, big endian||File contains big endian UTF-16 data.|
Ignored lines in the begining of file specifies how many lines in the beginning of the file are ignored.
Line specifies if file uses single line comments. If a line comment string is given all chracters after comment to (and including) the line end are skipped. Also all white spaces before comment string on the same line are skipped. For example:
// This is a comment key=This is a value
In above " // This is a comment" + line end are skipped when scanning.
Start and End specify if the file uses block comments. If both start and end comment strings are given all chracters between these strings (and including) are skipped. For example:
/* First line Second line */ key=This is a value
In above " /* First line Second line */ is skipped when scanning.
Contains a list of rules that specify the format of the file. Click + to add a new rule. Click x to remove the selected rule. Click Notepad to edit the selected rule. Click Up arrow to move selected rule one step up. Click Down arrow to move selected rule one step down. Click Import to read rule definition from a file. Click Export to write rule definition to a file.