Use this sheet to specify the format of the imported text file. It is very important that the format specified on this sheet matches the actual file format. Otherwise Sisulizer fails to import data correctly.
Shows the first two lines of the selected file. Click ... to show the selected file in the default viewer.
Specifies if text file contains plain text or structured data. Check Plain text file if you want to scan the file as plain text file. Check User defined text file if you want to parse text file using format definition you specify. The following parts are used to define the format.
Contains the list of global definitions. A global definition is a text definition that is shared with all projects of this Sisulizer installation. If you want to use an existing global definition selected it from the list. If you want to use a custom definition that is used only in this case select This is a custom definition that is used only in this case.
Click + to create a new global definition. Click x to remove the selected global definition. Click Notepad to rename the selected global definition. To edit an existing global definition select it and modify the rules and/or other options.
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.