Each file rule can have different options applied, which effect how Perceptive Enterprise Search - Local Administration Console will read the text of each document. Options include:
Selecting this option from the drop-down list will use the default document options for the indexing rule.
If you use the Ventura Publisher desktop publishing package and the documents covered by this rule may contain Ventura paste-up markers, select this option from the drop-down list. Perceptive Enterprise Search - Local Administration Console will then correctly interpret the special markers that Ventura inserts into documents, wherever they may occur
Use this option if your documents are in a word-processor format in which every line ends with a hard return and every paragraph ends with two consecutive hard returns.
Use this option if your documents are in a word-processor format, are completely double-spaced and every paragraph ends with three consecutive hard returns.
The preceding two options only apply to documents in a word processor format where there is a concept of a hard-return. ASCII, by comparison, does not have the concept of paragraphs, and so it is normal for every line to end with a hard return.
By default, the Perceptive Enterprise Search - Local Administration Console browser automatically wraps wide documents to a right margin of 76 characters for maximum browsing performance. Select this option if you need to browse highly formatted, wide ASCII material, such as 132-column mainframe report files. You can also compensate for wide documents by using the Quality presentation option, or by amending the ISYS.CFG file.
In most situations with English-style languages, there is no real difference between ASCII files (as usually generated by DOS programs), and ANSI files (as usually generated by Windows programs). By default, Perceptive Enterprise Search - Local Administration Console assumes ASCII files have been created using the ASCII character set. If you have ASCII files that are actually coded in ANSI, and if this distinction matters in your language, use the "ANSI" option when creating your indexing rules.