• Definitions Error Messages

• Tokenizers Error Messages

• Filters Error Messages

• Element Features Error Messages

• Attribute Features Error Messages

• XPath Macros Error Messages

• Keys Error Messages

• Shortcuts Error Messages

Definitions Error Messages

Tokenizers Error Messages

• Ambiguous categories!

  This message occurs when a tokenizer is being compiled. There are two categories in the tokenizer that recognize the same regular language.

• Category definition category name not found!

  This message occurs when the user compiles a tokenizer. The category in the tokenizer was not found in any of the parent tokenizers in the hierarchy.

• Category name name already used in the hierarchy!

  This message occurs when the user compiles a tokenizer and a category is already defined in one of the tokenizers that are its ancestors. It is possible that there is a cycle in the hierarchy.

• Category name is empty!

  This message occurs when the user creates or modifies a tokenizer. There is a cell in the Category column of the table that is empty.

• Code is not in category value

  This message occurs when the user chooses the normalization option of constraints for the current category. The specified symbol in the normalization table does not belong to the symbols defined by the primitive tokenizer of the Tokenizer that is normalized.

• Empty Category Declaration! Define Category Name First

  This message occurs when the user normalizes a category of a primitive tokenizer without a category name. There is a cell in the Category column of the table that is empty.

• Empty category declaration on line line number

  This message occurs during compilation when the user creates or modifies a tokenizer. There is a value in the tokenizer definition that does not have a category assigned to it.

• Empty category name on line line number

  This message occurs during compilation when the user creates or modifies a tokenizer. There is a value in the tokenizer definition that has no category assigned.

• Empty Value!

  This message occurs during compilation when the user creates or modifies a tokenizer. There is a category in the table with a corresponding empty value cell.

• Error during compilation

  This message occurs when the user loads a tokenizer in the system. There is a problem during the compilation of the tokenizer. For more information see Compilation Error Messages.

• Error during compilation of category category name

  This message occurs during compilation when the user creates or modifies a tokenizer. There is a problem during compiling one of the tokenizer categories. For more information see Compilation Error Messages.

• Error during tokenizer compilation:

  This message occurs during compilation when the user creates or modifies a tokenizer. For more information see Compilation Error Messages.

• Invalid Category name

  This message occurs during compilation when the user creates or modifies a tokenizer. There is a value in the tokenizer definition that has an invalid category name assigned to it.

• Invalid Category Value

  This message occurs during compilation when the user creates or modifies a tokenizer. There is a category in the tokenizer definition which has an invalid value assigned to it.

• Invalid normalize table

  This message occurs when the user loads a tokenizer that is normalized in the system. The number of the characters and the number of the normalized characters are not equal. For each character there must be a normalized value. It may be equal to the character itself.

• Invalid or missing tokenizer name!

  This message occurs when the user loads a tokenizer in the system. The tokenizer name that is the content of the <name> element is either not valid or does not exist.

• Invalid Value value!

  This message occurs when the user creates or edits a value of a category in a tokenizer. The value does not correspond to syntax rules.

• Invalid Value value! Number Expected

  This message occurs when the user creates or edits a value of a category in a tokenizer. The value does not correspond to syntax rules.

• No value defined for attribute 'Normalize_Category' for number normalizeUnit element!

  This message occurs when the user loads a tokenizer that is normalized in the system. The category of the normalized character is specified in Normalize_Category attribute of normalizeUnit element. But there is no value defined for it.

• No value defined for attribute 'Normalize_Value' for number normalizeUnit element!

  This message occurs when the user loads a tokenizer that is normalized in the system. The normalized character is specified in Normalize_Value attribute of normalizeUnit element. The system cannot normalize the character without that value.

• No value defined for attribute 'Value' for number normalizeUnit element!

  This message occurs when the user loads a tokenizer that is normalized in the system. The normalized character is specified in a Value attribute of normalizeUnit element. The system cannot normalize it without that value.

• Normalize char is not a char!

  This message occurs when the user normalizes a category of a primitive tokenizer. The normalize char should be only one Unicode symbol.

• Missing Category name

  This message occurs when the user loads a tokenizer in the system. There is a value in the tokenizer definition that has no category assigned to it.

• Missing Value

  This message occurs when the user loads a tokenizer in the system. There is a category in the tokenizer definition with no value assigned to it.

• Normalize code is not a number!

  This message occurs when the user normalizes a primitive tokenizer. Normalize code should be a Unicode number of a symbol.

• Parent and Child are the same!

  This message occurs when the user changes the parent tokenizer of a tokenizer. The user is trying to set the tokenizer itself as parent.

• Problem with parent tokenizers:

  This message occurs during tokenizer compilation when the user changes the parent tokenizer of a tokenizer to one that is not compiled or he/she loads a tokenizer with a parent tokenizer that does not exist in the system.

• Remove is impossible. Tokenizer(s): list of tokenizer names use tokenizer for parent!

  This message occurs when the user removes tokenizers from the system. The tokenizer cannot be removed because there is at least one tokenizer that uses it for a parent.

• Repeated value symbol at row number!

  This message occurs when the user creates or modifies a primitive tokenizer. The symbol appears more than once in the definition of the primitive tokenizer.

• Repeated Value Declaration!

  This message occurs when the user creates or modifies a primitive tokenizer. There is a symbol that appears more than once in the definition of the primitive tokenizer.

• Sort Order not found! Automatic Generation!

  This message occurs when the user loads a tokenizer in the system. The sort order of the tokenizer categories that is in so element is not found. The system is generating an order of categories based on their appearances in the definition.

• Symbol symbol not allowed in Category Declaration!

  This message occurs when the user compiles a tokenizer that was created or modified. Special symbols used by regular expressions are not allowed to appear in the categories of tokenizers.

• The following tokenizers were not compiled:

  This message occurs when the user compiles selection of tokenizers from Tokenizer Manager dialog. There is a problem with the definitions of the tokenizers in the list. For that reason they have no compiled form.

• The category specified in attribute 'Normalize_Category' for number normalizeUnit element is not defined in the tokenizer!

  This message occurs when the user loads a tokenizer that is normalized in the system. The category of the normalized character is specified in Normalize_Category attribute of normalizeUnit element. That category is not defined within the tokenizer.

• There was an error while trying to open file name

  This message occurs when the user loads a tokenizer in the system, and there is a problem in the communication with the operating system. Check read/write permissions of the directory where the system writes its data files.

• There was an error while trying to read from file name

  This error occurs when the user loads a tokenizer in the system. Possible reasons are the following: the document is in another encoding, it is not in the appropriate format or it is not a well-formed document.

• There was an error while trying to write to file name

  This error message occurs when the user tries to save a tokenizer(s) from the system to a file and the tokenizer(s) cannot be saved. A possible reason is that there is no free disk space on user's computer or no write permission is declared.

• This is not a valid tokenizer document!

  This message occurs when the document which the user is trying to load a tokenizer from is not a valid XML document or it does not match the structure of the tokenizer's DTD.

• This name is forbidden by the System

  This message occurs when the user creates a new tokenizer. The names: [DTDTokenizer] and [NoTokenizer] are reserved for system tokenizers.

• Tokenizer already exists!

  This message occurs when the user creates a new tokenizer. There is already a tokenizer with this name defined in the system.

• Tokenizer tokenizer name is not compiled!

  This message occurs when the user compiles a tokenizer and its parent tokenizer is not compiled. This terminates the compilation of the tokenizer.

• Tokenizer expected!

  This message occurs when the user loads a tokenizer in the system. The document which the user is loading the tokenizer from is not a valid XML document or it does not match the structure of the tokenizers DTD.

• Tokenizer is not compiled! Also all tokenizers in the hierarchy below it are not compiled!

  This is just a warning message. It means: due to a problem while compiling the tokenizer it has no compiled version. Note that all the tokenizers that have this tokenizer on an upper level in the hierarchy will loose their compiled state as well. Once the user corrects the error, all these tokenizers will regain their compiled state.

• Tokenizer is not correct. Cycle created!

  This message occurs when the user changes the parent of a tokenizer. The user has created a cycle in the tokenizer hierarchy.

• Tokenizer is not saved!

  This message occurs when the user tries to save a tokenizer in the system. A possible reason is that there is no free disk space on the user's computer or no write permission is declared.

• Tokenizer name must have at least 2 letters.

  This message occurs when the user creates a new tokenizer. The tokenizer name must consist of at least two symbols because of implementation issues.

• Tokenizer type is not specified correctly!

  This message occurs when the user loads a tokenizer in the system. The value of type attribute of tokenizer element that specifies whether the tokenizer is primitive or complex, is not correct. Its value must be primitive for primitive tokenizers or normal for complex ones.

• Type category name may have empty content!

  This message occurs during tokenizer compilation. There is a category in a complex tokenizer that recognizes the empty word.

• Unknown tokenizer for parent Set to default!

  This message occurs when the user loads a tokenizer in the system. The parent tokenizer specified by the tokenizer does not exist or it has not been loaded yet.

• Value symbol already used!

  This message occurs when the user creates or modifies a primitive tokenizer. The described symbol appears more than once (in more than one categories) in the definition of the primitive tokenizer.

• You must choose a tokenizer!

  This message occurs when the user wants to perform an action and no tokenizer is selected. The user must select a tokenizer from the list of possible choices.

 

Filters Error Messages

• Empty filter name.

  This error message appears when the user tries to add a new filter in the system. The name of the filter is not specified.

• Error occurred during XPath Compiling.

  This error message appears when the user tries to add a new XPath expression for a filter in the Filter dialog which is not valid. For details see the XPath Error Messages.

• This filter name is already used or forbidden.

  The user is trying to overwrite an already existing filter or to use a filter name that is used for special purposes.

• This XPath is already used for filtering.

  There is a filter that has the same filter XPath expression as this one.

 

Element Features Error Messages

• Element already inserted!

  There is a value defined for this element on another row of the element value editor table.

• Element elName is already defined!

  The user cannot define more than once a value of an element in one query.

 

Attribute Features Error Messages

• Attribute type is not Enumeration!

  This error message appears when the user tries to Sort Values in Attribute DTD Features dialog. The sort operation cannot be executed over elements with an attribute whose type is not an enumeration. The system expects the attribute type of the elements to be enumeration.

• Select row first!

  This error message appears when the user tries to Sort Values in Attribute DTD Features dialog and there are no selected rows. The system expects the user to select some rows for sorting.

 

XPath Macros Keys Error Messages

• XPath Macro name already used!

  This error message appears when the user has supplied a name for an XPath Macro which is already used for another XPath macro. The XPath macro names must be unique for correct addressing.

• XPath Macro returned error message while compiling: XPath Parse Error

  This error message appears when the user creates/modifies the XPath expression in an XPath Macro. The XPath expression which is entered for a rule of an XPath macro is not valid. For details see the XPath Error Messages.

• XPath Macro "Name" has invalid symbol 'Symbol' !

  The string value entered in the Select name for the new xpath macro: field of the Name? dialog (XPath Macros Editor dialog) is not in a proper format. The XPath macro name cannot contain the symbol Symbol.

 

Keys Error Messages

• Key name already used!

  This error message appears when the user has supplied a name for a key which is already used for another key. The key names must be unique for correct key addressing.

• Key returned error message while compiling: XPath Parse Error

  This error message appears when the user creates/modifies the XPath expression in a Key. The XPath expression which is entered for a rule of a key is not valid. For details see the XPath Error Messages.

• Key "Name" has invalid symbol 'Symbol' !

  The string value entered in the Select name for the new key: field of the Name? dialog (Key Editor dialog) is not in a proper format. The Key name cannot contain the symbol Symbol.

 

Shortcuts Error Messages

• Please, select at least one query!

  This error message appears when the user defines a rule in a shortcut and a query is not specified (which is required). The rule definition cannot be completed successfully unless a valid query is supplied.

• The selected documents do not represent tool queries or they do not appear in an appropriate group.

  There are several system groups. Each group can contain only documents with a certain DTD. Each query has a DTD and is located in the relevant group. The user cannot use documents without a required query DTD or documents from folders except for Root : SYSTEM : Queries.

• This action is also bound to a key combination: 'Key Combination' (which is not a problem). Do you want to proceed?

  There are more than one key combinations which refer to one action.

• This key combination is already defined for action : 'Command' !

  The key combination which the user has just entered is already used for another key combination. The key combination must be unique because the corresponding key combination configurations have to be identified correctly.

• Please, select a key!

  This error message appears when the user defines a rule in a Shortcut and a Key Code is not specified (which is required). The rule definition cannot be completed successfully unless a valid Key Code is supplied.

• Please, select an action!

  This error message appears when the user defines a rule in a Shortcut and an Action is not specified (which is required). The rule definition cannot be completed successfully unless a valid Action is supplied.

• Please, select at least one modifier key!

  This error message appears when the user defines a rule in a Shortcut and one of the Modifiers is not specified (which is required). The rule definition cannot be completed successfully unless a valid Modifier Key is supplied. The system expects one of the following modifiers - Shift, Ctrl, Alt or Meta.

• Unable to apply query: Error Message

  This error message appears when the system tries to load a query, which is not found in the system. Probably it was deleted or modified out of the system.

• Unable to load query 'Query Name'!

  This error message appears when the system tries to load a query, which is not found in the system. Probably it was deleted out of the system.