26th June 2017

Error Messages Index

Публикации

 

File Error Messages

  • Open Error Messages

    No document(s) selected to be opened!
    This message occurs when the user opens a document in the system. There are no selected documents in the Document Manager. In order to open a document, the user must first select it.

    The current selection does not contain any documents.
    This message occurs when the user opens a document. The selection contains only groups. In order to open a document, user must select it first.

  • Save Error Messages

    Group not found: group name
    This message occurs when the user tries to save a document in a group that does not exist in the system. A possible reason is that the group was deleted.

    The document must be VALID according to DTD 'query DTD'!
    This message occurs when the user tries to save a document in a document group whose name starts with Root : SYSTEM :Queries. Such groups are used for queries of the system tools and only valid documents can be saved in those groups. The query DTD for the corresponding tool can be seen in Resources directory of the system.

    The document must HAVE a DTD 'query DTD'!
    This message occurs when the user tries to save a document in a document group whose name starts with Root : SYSTEM :Queries. Such groups are used for queries of the system tools and only valid documents can be saved in those groups. The query DTD for the corresponding tool can be seen in Resources directory of the system.

    Warning: document cannot be included in group: Group. The document must be VALID according to DTD 'Required DTD'! Document successfully saved!
    This message occurs when the user tries to apply a Save operation over a document. There are several system groups. Each of them can contain only valid documents. The user cannot add a document in such groups, uless it is valid according to the required DTD.

    Warning: document cannot be included in group: Group. The document must HAVE a DTD 'Required DTD'! Document successfully saved!
    This message occurs when the user tries to apply a Save operation over a document. There are several system groups. Each of them can contain only documents with a certain DTD. The user cannot add a document in such groups, uless it is valid according to the required DTD.

    You must enter a document name!
    This message occurs when the user wants to save a document in the system. The reason for this error is that the user did not supply a name for the document.

  • Document Manager Error Messages

    Group name is a reserved group name. It cannot be used here!
    This message occurs when the user wants to create a new group named SYSTEM, Root, Results or Queries in the Document Manager. These names are reserved for system groups.

    Please select a document to proceed!
    This error message occurs when the user tries to open or delete a document and there is no selection in All Documents panel of Document Manager Dialog. In order to open or delete a document the user must select it first.

    The following character: : cannot be used in a group name.
    This message occurs when the user creates a new group and there is a colon symbol in the name. The colon is used in the group path and for that reason it cannot be used in group names.

    The system was unable to remove the document:
    This message occurs when the user tries to remove a document from the Document Manager dialog. A possible reason is that the document was not found in the system database.

    This group name is already used in the current group. Please specify a different group name!
    This message occurs when the user creates a new group within a parent group and there is already a group with the same name.

  • Delete Error Messages

    No document(s) selected for deletion!
    This message occurs when the user deletes a document from File menu in the system. There are no selected documents in the Document Manager. In order to delete a document the user must first select it.

    The current selection does not contain any documents.
    This message occurs when the user deletes a document. The selection contains only groups. In order to delete a document the user must select it first.

    The group system group is required by the system and cannot be removed!
    This message occurs when the user tries to delete system groups. The system groups are Root, Root : SYSTEM, Root : SYSTEM :Queries, Root : SYSTEM :Results and their subgroups for each tool in the system. These groups are used by the system for saving queries or resulting documents. The query DTD for the corresponding tool can be seen in Resources directory of the system.

  • ReImport Error Messages

    Import document first!
    This message occurs when the user tries to apply ReImport operation, but there was no previously imported document in the system.

  • Export Options Error Messages

    Invalid number for spaces count!
    The numeric value entered in the Spaces Count per Generation field of the Documents Export Options dialog is not in a proper format. The system expects a non-negative integer in the range between 1 and 12.

  • Import RTF Error Messages

    No RTF data found in file: Absolute Path and File Name
    This error message appears when the user tries to Import RTF file in the system, which is not a valid RTF one.

    Unexpected end of file. Expected '}'.
    This message occurs when the user tries to Import RTF file in the system, which is not a valid RTF one.

  • Import From URL Error Messages

    Unable to connect: URL Error Message
    This message occurs when the user tries to import an XML document from URL address in the system. The entered URL address is not accessible.

    An error occurred during XML parsing: Parse Error Message. Do you want to save the downloaded data?
    This message occurs when the user tries to import an XML document from an URL address in the system. The file was successfully downloaded, but the document is not a well-formed XML one. There is a possibility to save this file. For details see the XPath Error Messages.

    Error saving data: Saving Error Message
    This message occurs when the system tries to save the file which is downloaded from the specified URL. A possible reason is that there is no free dick space on your computer or no write permission is declared.

    Invalid URL: URL Error Message
    This message occurs when the user tries to import an XML document from an URL address in the system. The entered URL address is not valid.

 

Edit Error Messages

  • Undo Error Messages

    No more undo available!
    This message occurs when the user tries to apply Undo operation. There is a limit over the number of the undo operations. The previous undo operation was the last one in the queue.

  • Search Error Messages

    Invalid Expression
    The XPath expression in the Search Expression: field of the Search dialog is not specified.

    There is no current document!
    This message occurs when the user tries to apply a Search operation, but there is no current document in the system. First, open a document in the system and then try again the Search operation.

  • Next Error Messages

    Make a search first!
    This message occurs when the user tries to apply a Next operation for searching, but there is no search operation performed before that. First, do search operation and then try again the Next operation.

    No previous search hits found for query: Search Query
    This message occurs when the user tries to apply a Next operation for searching, but the search results cannot be found in the document. Probably the document was edited and the searching hits were deleted from it.

    There is no current document.
    This message occurs when the user tries to apply a Next operation for searching, but there is no current document in the system. First, open a document in the system and then try again the Next operation.

  • Previous Error Messages

    Make a search first
    This message occurs when the user tries to apply a Previous operation for searching, but there is no search operation performed before that. First, do search operation and then try again the Previous operation.

    No previous search hits found for query: Search Query
    This message occurs when the user tries to apply a Previous operation for searching, but the searching results cannot be found in the document. Probably the document was edited and the searching hits were deleted from it.

    There is no current document.
    This message occurs when the user tries to apply a Previous operation for searching, but there is no current document in the system. First, open a document in the system and then try again the Previous operation.

 

DTD Error Messages

  • Compile DTD Error Messages

    Invalid tag name name! Invalid symbol at position position
    This is an error message from the DTD compiler. A definition of a DTD is using an illegal tag name.

  • Renew DTD Error Messages

    The selected DTD is currently in use by opened document(s) in the editor! This operation will cause changes in other file(s) related to this DTD!
    This error message appears when the user tries to save the currently edited DTD document and there is an opened XML document in the system with the same DTD. If you overwrite the DTD, all files connected with it will be validated again after their next opening in the system. The opened document will not be validated immediately. If you want to see the result from the new DTD on the document, you have to reload it.

  • Remove DTD Error Messages

    Cannot delete this DTD! There are internal documents referring to it! (see Details)
    This error message appears when the user tries to apply Remove DTD operation on a selected DTD. It is not possible the user to delete a DTD if there is a document connected with it. If the user wants to remove the DTD from the system he/she must change the DTD of all documents connected with it or to delete all these documents.

  • DTD Editor Error Messages - Create New DTD and Edit DTD

    An attribute with name AttrName for the element Tag already exists!
    This error message appears when the user has supplied an attribute name in the DTD Editor dialog which is already specified for another attribute name of the same element. The attribute names must be unique according to the XML specification. For details see the XML recommendation for the valid name standard.

    An element with name Tag already exists!
    This error message appears when the user has supplied an element name in the DTD Editor dialog which is already specified for another element name. The element names must be unique according to the XML specification. For details see the XML recommendation for the valid name standard.

    An entity with name EntityName already exists!
    This error message appears when the user has supplied an entity name in the DTD Editor dialog which is already specified for another entity name. The entity names must be unique according to the XML specification. For details see the XML recommendation for the valid name standard.

    Attribute name AttrName is not valid!
    The name of the attribute in the Attribute Name column of the DTD Editor dialog does not obey the standard. For details see the XML recommendation for the valid name standard.

    Element name Tag is not valid!
    The name of the element in the Element Name column of the DTD Editor dialog does not obey the standard. For details see the XML recommendation for the valid name standard.

    Element Name Tag in row N is not valid!
    The name of the element in the Element Name column of the DTD Editor dialog does not obey the standard. For details see the XML recommendation for the valid name standard.

    Empty Attribute Default Value for element Tag in row N!
    The default value of the attribute in row N in the Attribute Default Value column of the DTD Editor dialog is not specified. Its presence is required.

    Empty Attribute Name for element Tag in row N!
    The name of the attribute in row N in the Attribute Name column of the DTD Editor dialog is not specified. Its presence is required.

    Empty Attribute Type for element Tag in row N!
    The type of the attribute in row N in the Attribute Type column of the DTD Editor dialog is not specified. Its presence is required.

    Empty Element Description in row N!
    The description of the element in row N in the Element Description column of the DTD Editor dialog is not specified. Its presence is required.

    Empty Element Name in row N!
    The name of the element in row N in the Element Name column of the DTD Editor dialog is not specified. Its presence is required.

    Empty Entity Name in row N!
    The name of the entity in row N in the Entity Name column of the DTD Editor dialog is not specified. Its presence is required.

    Empty Entity Value in row N!
    The value of the entity in row N in the Entity Value column of the DTD Editor dialog is not specified. Its presence is required.

    Entity name EntityName is not valid!
    The name of the entity in the Entity Name column of the DTD Editor dialog does not obey the standard. For details see the XML recommendation for the valid name standard.

    EntityName is a reserved entity name!
    The name of the entity in the Entity Name column of the DTD Editor dialog is reserved and it cannot be redefined. The reserved entity names are: amp, apos, gt, lt and quot. The system requires a non-reserved and valid entity name.

    The selected DTD is currently in use by opened document(s) in the editor! This operation will cause changes in other file(s) related to this DTD!
    This error message appears when the user tries to save the currently edited DTD document and there is an opened XML document in the system with the same DTD. If user overwrites the DTD, all files connected with it will be validated again after their next opening in the system. The opened document will not be validated immediately. If user wants to see the result from the new DTD on the document, (s)he have to reload it.

    You must enter a DOCTYPE!
    This error message appears when the user tries to save a DTD in the system and the DOCTYPE is not specified. The system requires a DOCTYPE for each DTD.

  • Edit Text Layout Error Messages

    The new layout does not contain any data concerning the current DTD or Document! Check whether this is the correct layout document!
    This error message occurs when the user tries to import a document as a Text Layout, but it does not contain the appropriate type of data. The Text Layout document needs a certain XML structure.

    The system was unable to save this layout: Saving Document Error
    This error message occurs when the user tries to export the Text Layout data as an XML file out of the system. A possible reason is that there is no free disc space on your computer or no write permission is declared.

    There was an error while reading file 'FullPathFile': No XML data found!
    This error message appears when the user tries to import a document as a Text Layout in the system, but it does not contain the appropriate type of data. The Text Layout document needs a certain XML structure.

    There was an error while reading file 'Path and File Name': Loading Document Error
    This error message appears when the user tries to import a document as a Text Layout in the system. A possible reason is that the file was not found or it was corrupted.

    This file does not contain a valid layout document!
    This error message appears when the user tries to import a document as a Text Layout in the system, but it does not contain the appropriate type of data. The Text Layout document needs a certain XML structure.

  • Edit Tree Layout Error Messages

    Error compiling key 'Key' at row N :
    This error message appears when the user creates/modifies rules in a Tree Layout. The XPath expression of the Key for the Pattern at row N, which is entered for a rule of a tree layout, is not valid. For details see the XPath Error Messages.

    Error compiling XPath at row N :
    This error message appears when the user creates/modifies rules in a Tree Layout. The XPath expression for the Pattern at row N, which is entered for a rule of a tree layout, is not valid. For details see the XPath Error Messages.

    Expected '}' at row N.
    This error message appears when the user creates/modifies rules in a Tree Layout. The system expects the symbol } in the string value of the Pattern column at row N.

    Invalid attribute name at row N.
    This error message appears when the user creates/modifies rules in a Tree Layout. The attribute name for the Pattern at row N, which is entered for a rule of a tree layout, does not obey the standard. For details see the XML recommendation for the valid name standard.

    Key name not found at row N : 'KeyName'.
    This error message appears when the user creates/modifies rules in a Tree Layout. The Key name for the Pattern at row N, which is entered for a rule of a tree layout, does not exist in the system. For more details about the existing XPath Keys in the system click the View Macros button in the Tree Layout Editor dialog.

    No Tree Layout data found in file!
    This error message appears when the user tries to import a document as a Tree Layout in the system, which does not contain the appropriate type of data. The Text Layout document needs a certain XML structure.

    There was an error while reading file 'Absolute Path and Filename'. No XML data found!
    This error message appears when the user tries to import a document which is not a valid XML file as a Text Layout in the system.

    There was an error while reading file 'Absolute Path and Filename'
    This error message appears when the user tries to import a document as a Text Layout in the system. A possible reason is that the file was not found or it is corrupted.

  • Loading DTD Error Messages

    The system files for DTD 'result' are corrupted and the DTD cannot be loaded! Please, remove the DTD and compile it again!
    This error message occurs when the system fails to load a compiled DTD because it cannot find neither the binary file, nor the XML recovery file containing the DTD information. A possible reason is a deletion or corruption of these files out of the system.

 

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 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.

 

Tools messages

  • Grammars Error Messages

    Error during compiling:
    This message occurs when the user loads grammar(s) from a file in the system and he/she wants them to be compiled. For more information about the error see Compilation messages.

    Error in compiling value for variable 'variable name'!
    This message occurs when the user compiles a grammar. There was a problem while compiling a variable. For more information about the error see Compilation messages.

    Error in opening grammar 'grammar name'!
    This message occurs when the user tries to edit a grammar. The system file with the grammar is damaged and the grammar is lost.

    Error in opening grammar query 'query name'!
    This message occurs when the user tries to apply a grammar group from the Group Manager dialog. The query was deleted after it had been added to the group query.

    Error occurred while loading!
    This message occurs when the user loads grammar(s) from a file in the system. There is a problem in the communication with the operating system. Check read/write permissions of the directory in which the system writes its data files.

    Error on parsing key for element 'element name'
    This message occurs when the user tries to apply a query. The element value of the element is not a valid XPath.

    Expression expression not finished! Expected variable name!
    This message occurs when the user compiles a grammar. It means that there is a variable identifier (&) in the expression,but no capital Latin letter specifies the variable name.

    Grammar 'grammar name' not found!
    This message occurs when the user loads a grammar query and the grammar in that query is not found in the system database. A possible reason is that the grammar was deleted after the query had been created.

    Grammar Query 'query name' has an incorrect XPath expression for this group!
    This message occurs when the user applies a Grammar Group. All grammars from a group must have the same Apply to XPath expression.

    Grammars.dtd compilation error!
    This message occurs when the user wants to edit a grammar in the editor. There is a problem in compiling the system DTD. The system cannot find the file with the DTD or that file was corrupted.

    If value is Token Category, put '$' in front of it.
    This message occurs when the user compiles a grammar. The grammar compiler has found an atom and cannot determine its type. This error message proposes a probable solution.

    Invalid XPath expression in 'Apply to'!
    This message occurs when the user wants to apply a grammar over an XML document. The XPath expression in the Apply to text field is not valid. It specifies the nodes which the grammar will be applied to. For details see the XPath messages.

    Invalid XPath expression in 'Apply to'! Node Set result expected!
    This message occurs when the user wants to apply a grammar over an XML document. The XPath expression in the Apply to text field is expected to return a node set in the result, but it returns something else (number, string or boolean). The XPath specifies the nodes which the grammar will be applied to.

    Missing Filter!
    This message occurs when the user tries to apply a Grammar operation over a document. The filter node in the query is empty. The user must open the query in the Apply Grammar dialog and specify the Filter field.

    Missing Filter 'filter name' in the system!
    This message occurs when the user tries to apply a Grammar operation over a document. The specified filter in the query is not found in the system. The user must open the query in the Apply Grammar dialog and specify the Filter field.

    Missing Tokenizer!
    This message occurs when the user tries to apply a Grammar operation over a document. The tokenizer node in the query is empty. The user must open the query in the Apply Grammar dialog and specify the Tokenizer field.

    Missing Tokenizer 'tokenizer name' in the system!
    This message occurs when the user tries to apply a Grammar operation over a document. The specified tokenizer in the query is not found in the system. The user must open the query in the Apply Grammar dialog and specify the Tokenizer field.

    Problem with saving automaton in internal format!
    This message occurs when the system tries to save a grammar, but the grammar cannot be saved. Possible reasons are: no free disk space on the user's computer or no write permission declared.

    Select grammar(s) first.
    This message occurs when the user performs some operations like Edit grammar in editor or Save grammar to file. There are no grammars selected for saving or opening.

    The system cannot create the grammar 'grammar name'!
    This message occurs when the system tries to save a grammar in its database, but the grammar cannot be saved. Possible reasons are: no free disk space on the user's computer or no write permission declared.

    The system cannot load the grammar 'grammar name' from an internal file!
    This error occurs when there is a problem while loading a grammar from the system database. A possible reason is damage of the system files.

    The system cannot load the grammar automaton from an internal file!
    This message occurs when the user tries to apply a grammar. The internal format for saving grammars is changed in this version. The user must recompile the grammars to fix this problem.

    The system cannot load the grammar from an internal file!
    This message occurs when the user tries to edit a grammar. The system file with the grammar is damaged and the grammar is lost.

    The system cannot save the grammar in an internal file!
    This message occurs when the user tries to save a grammar in its database. There is a problem in the communication with the operating system. Check read/write permissions of the directory in which the system writes its data files.

    The system cannot save the grammar automaton in an internal file!
    This message occurs when the user tries to save a grammar in its database. There is a problem in the communication with the operating system. Check read/write permissions of the directory in which the system writes its data files.

    The system was not able to load query:
    This message occurs when the user loads a Grammar Group query. The query in the message is not found in the system. A possible reason is that the query was deleted after it had been added to the Grammar Group query.

    There was an error while saving in 'file name'
    This message occurs when the user tries to save grammar(s) from the system in a file and the grammar(s) cannot be saved. Possible reasons are: no free disk space on the user's computer or no write permission declared.

    There was an error while trying to open 'grammar name'
    This message occurs when the user loads a grammar in the system. There is a problem in the communication with the operating system. Check read/write permissions of the directory from which the system reads its data files.

    There was an error while trying to read from 'file name'
    This error occurs when the user loads a grammar from a file in the system. Possible reasons are: the document is in another encoding, it is not in the appropriate format or it is not a well-formed document.

    This in not a valid mark-up!
    This message occurs when the user has changed the return markup of a grammar from the select dialog. The mark-up cannot be used for changing the document because it is not a valid XML mark-up.

    Variable 'variable name' has value that can be empty!
    This message occurs when the user compiles a grammar. A variable matches the empty word. It cannot receive an empty value.

    Variable 'variable name' not defined
    This message occurs when the user compiles a grammar. The compiler has encountered a variable that is not defined. This can be corrected by adding the variable definition in the list with variables or by choosing another variable.

    Variable 'variable name' defined more than once!
    This message occurs when the user compiles a grammar. There are two or more definitions for one variable.

    Unable to apply. Grammar name not selected!
    This message occurs when the user wants to apply a grammar over the document. There is no grammar selected for applying.

    Unable to load grammar from system database!
    This message occurs when the user compiles a grammar. There is a problem in the communication with the operating system. Check read/write permissions of the directory in which the system writes its data files.

    XPath expression in 'Apply to' field not specified!
    This message occurs when the user wants to apply a grammar over an XML document. The XPath expression in the Apply to text field is not specified. It specifies the nodes which the grammar will be applied to.

     

  • Regular Expression Constraints messages

    Empty regular expression cannot be used here!
    This message occurs when the user creates or edits a regular expression and there is no value in the Regular Expression text field. The regular expression defines the constraint over the nodes' content. The regular expression may consist of: tags, token categories, token values and token value templates.

    Error in regular expression:
    This message occurs when the user creates or edits a regular expression and the value in the Regular Expression text field is not valid. The regular expression defines the constraint over the nodes' content. The regular expression may consist of: tags, token categories, token values and token value templates.

    Error in writing file 'filename'! Constraints NOT saved!
    This message occurs when the user tries to save a constraint in the system, but the constraint cannot be saved. Possible reasons are: no free disk space on the user's computer or no write permission declared.

    Incorrect constraint name!
    This message occurs when the user tries to save a constraint without a name. The user must specify a constraint name in order to save it. Constraints are identified by their names.

    No XPath expression entered!
    This message occurs when the user applies a Regular Expression Constraints operation. The Select Nodes text field is empty. The XPath expression defines the nodes which the constraints will be applied to.

    There are no new constraints to load. Please check if the file syntax is correct!
    This message occurs when the user tries to load constraints from a file and the selected XML document is not in the appropriate format. It must be valid according vconstraint.dtd stored in Resource directory of the system.

    There was an error while trying to load from file! No constraints loaded.
    This message occurs when the user tries to load constraints from a file and the selected file is not a well-formed XML document.

  • Value Constraint messages

    A non-empty source expression allowed!
    This message occurs when the XML/XPath text field in the Source panel of the Constraint Editor dialog is empty. It defines the values that will be inserted or validated by the constraint.

    A positive number expected in field Prompt for save on each ... times
    This message occurs when the Prompt for save on each ... checkbox from the Constraint Editor dialog is selected but the value is not a number. A positive integer value is expected. It tells that the document must be saved when the constraint is applied number times.

    Constraints Group name not specified!
    This message occurs when the user tries to save a constraint group without a name. The user must specify a constraint group name in order to save it. Constraint groups are identified by their names.

    Constraint Group not selected for application!
    This message occurs when the user tries to apply a group from the Value Constraints manager and there is no selected constraint group in the table with all groups. The user must select a constraint group in order to apply it.

    Context (XPath) expression not specified!
    This message occurs when the Context (XPath) text field of the Constraint Group Editor is empty. The context expression defines where the constraint group will be applied.

    Element Value at row M has incorrect key at row N! Missing Tokenizer!
    This message occurs when the user tries to apply a Grammar operation over a document. The tokenizer attribute for the key node of the key at row N of the element value at row M in the query is empty. The user must open the query in the Apply Grammar dialog, open the Keys table for Element Value at row M in the Element Values table and specify the Tokenizer field for the key at row N.

    Element Value at row M has incorrect key at row N! Missing Tokenizer 'tokenizer name' in the system!
    This message occurs when the user tries to apply a Grammar operation over a document. The specified tokenizer of the key at row N for the element value at row M in the query is not found in the system. The user must open the query in the Apply Grammar dialog, open the Keys table for Element Value at row M in the Element Values table and specify the Tokenizer field for the key at row N.

    Error in writing file 'filename' Constraints NOT saved!
    This message occurs when the user tries to save a constraint in the system and the constraint cannot be saved. Possible reasons are: no free disk space on the user's computer or no write permission declared.

    Error loading document: 'document name'! Proceeding to next constraint ...
    This error message occurs when the source of a constraint in the Constraint Editor dialog is from an external document and there is a problem while loading that document. A possible reason is that the document was deleted after the constraint creation.

    Expected positive number (number)!
    This message occurs when the value of the Position text field in the Constraint Editor dialog is not a positive integer value. It defines the position where the constraint value will be inserted as a child.

    Group entries not found.
    This message occurs when a constraint group is applied and one or more of the listed constraints are not found in the system database.

    Group XPath not specified! Group Name: 'group name'
    The XPath expression for the group 'group name' is not specified.

    Incorrect constraint name!
    This message occurs when the user tries to save a constraint without a name. The user must specify a constraint name in order to save it. Constraints are identified by their names.

    Incorrect number in field Prompt for save on each...
    This message occurs when the Prompt for save on each ... checkbox from the Constraint Editor dialog is selected but the value is not a number. A positive integer value is expected. It tells that the document must be saved when the constraint is applied number times.

    Incorrect template!
    This message occurs when the user creates/modifies templates in a Constraint Editor dialog. The entered template is not valid.

    Invalid insertion position:
    This message occurs when the value of the Position text field of the Constraint Editor dialog is not a positive integer value. It defines the position where the constraint value will be inserted as a child.

    Invalid target attribute name: 'attribute name'!
    This message occurs when the value entered in the Target Attribute text field of the Constraint Editor dialog is not a valid attribute name. A valid attribute name is expected. It defines attributes which the constraint will be applied to.

    Invalid target node name: 'node name'
    This message occurs when the value entered in the Target Node text field of the Constraint Editor dialog is not a valid node name. A valid node name is expected. It defines the target nodes where the constraint will be applied.

    Invalid XML markup. Expected element-rooted structure!
    This message occurs while the Parent constraints are being applied and the user wants to insert a different item from the ones defined in the constraint. This problem appears when the new item cannot be treated as an XML tag placed for a parent.

    Missing Constraint 'constraint name' in the system.
    This message occurs when a query is applied and the constraint specified in the query is not found in the system database. A possible reason is that the constraint was deleted after it had been added to the query.

    Missing Constraint group 'group name ' in the system.
    This message occurs when a query is applied and the constraint group specified in the query is not found in the system database. A possible reason is that the group was deleted after it had been added to the query.

    No input in field Prompt for save on each ...
    This message occurs when the Prompt for save on each ... checkbox from the Constraint Editor dialog is selected but no value is entered. A positive integer value is expected. It tells that the document must be saved when the constraint is applied number times.

    No constraints/groups to apply!
    This message occurs when no constraints or/and groups are added in the list of constraints in the Apply Constraints dialog and the Apply button is pressed. In order to apply a constraint the user must add it to the list.

    No target attribute defined!
    This message occurs when no value is entered in the Target Attribute text field of the Constraint Editor dialog. A valid attribute name is expected. It defines the attributes which the constraint will be applied to.

    No target node defined!
    This message occurs when no value is entered in the Target Node text field of the Constraint Editor dialog. A valid node name is expected. It defines the nodes which the constraint will be applied to.

    The current document is not presented in the document database of the CLaRK system. To save the document, use menu: File/Save!
    This message occurs when the Prompt for save on each: ... applications of constraint checkbox is selected in the constraint and the document which it is applied to is not saved in the system.

    The following invalid entries were detected: invalid constraints. They will be excluded.
    This message occurs when a constraint group is applied and one or more of the listed constraints from the group are not found in the system database.

    The selected group does not contain any valid constraints!
    This message occurs when there are no constraints in the group which the user wants to apply to the document.

    The Value Constraints can only be applied to Element nodes.
    This message occurs when the user presses Ctrl +D - the standard shortcut for applying Value Constraints over a selected node and the selection is on a text or attribute node. Value Constraints work over element nodes.

    There are no active constraints of suitable type to be applied!
    This message occurs when no constraints are activated and the user wants to apply constraints from the Value Constraints manager. In order to apply a constraint the user must make it active.

    There are no constraint types activated. Please check Options!
    This message occurs when there are no active constraint types in use. Constraints of a given type can be made active from the button Options, by selecting certain types.

    There are no constraints to be applied!
    This message occurs when there are no constraints defined in the system. In order to apply a constraint the user must first create it.

    There are no constraints of suitable type to be applied!
    This message occurs when there are only constraints of All Children type defined in the system. Constraints of this type are used automatically when the document is validated.

    There are no new constraints to load. Please check whether the file syntax is correct!
    This message occurs when the user tries to load constraints from a file and the selected XML document is not in the appropriate format. It must be valid according to the vconstraint.dtd stored in Resource directory of the system.

    There was an error while trying to load from file! No constraints loaded.
    This message occurs when the user tries to load constraints from a file and the selected file is not a well-formed XML document.

    Unable to parse source XML data!
    This message occurs when the user creates/modifies the source of a constraint in the Constraint Editor dialog, and the source is an XML mark-up. The entered expression is not a valid XML mark-up.

    Unable to parse source XPath expression!
    This message occurs when the user creates/modifies the source of a constraint in the Constraint Editor dialog and the source is an XPath expression. The entered XPath expression is not valid. For details see the XPath messages.

    Unable to parse the Target XPath expression!
    This message occurs when the user creates/modifies the content of the Target XPath field of a constraint in the Constraint Editor dialog that is an XPath expression. The XPath expression which is entered is not valid. For details see the XPath messages.

    Unable to parse XPath expression:
    This message occurs when the user creates/modifies the content of the Context field of a constraint group in the Constraints Group Editor dialog is an XPath expression. The entered XPath expression is not valid. For details see the XPath messages.

  • Number Constraints messages

    Invalid XPath expression at row row number, column column number
    This message occurs when the user creates/modifies the content of the Context or XPath field of a number constraint in the Number Constraint Manager which must be an XPath expression. The entered XPath expression is not valid. For details see the XPath messages.

    No active Number Constraints to apply!
    This message occurs when no number constraints are activated and the user wants to apply constraints from the Number Constraint Manager. In order to activate a Number Constraint the user must select the Use It? checkbox at the corresponding row.

    No valid and non-valid nodes to navigate in!
    This message occurs when number constraint was applied, the result table is empty and the user presses the Details button. There are no results, for which the details to be shown.

    Please, select a row in the table!
    This message occurs when the user presses the Details button and there is no row for which the details to be shown. The user must select a result from the table for which he/she wants to see the details.

    The system was unable to update the changes in the constraints:
    This message occurs when the user presses the OK button of the Number Constraint Manager dialog. The constraints cannot be saved in the system. Possible reasons are: no free disk space on the user's computer or no write permission declared.

    Wrong expression at row row number, column column number. The old value will be restored.
    This message occurs when the user creates/modifies the content of the Minimum Size or Maximum Size field of a number constraint in the Number Constraint Manager which must be a positive integer. The entered value is not valid.

  • XSLT messages

    without 'select' attribute!
    In order to copy data the user has to specify it. This is done by the select attribute required for that element. Its value must be an XPath expression.

    without 'select' attribute!
    In order to use this operator a node set must be selected. This is done by the select attribute required for that element. Its value must be an XPath expression.

    without 'test' attribute!
    In order to use this operator a condition must be defined. This is done by the test attribute required for that element. Its value must be a boolean expression.

    without 'select' attribute!
    In order to get a value of a data the user has to select it. This is done by the select attribute required for that element. Its value must be an XPath expression.

    A required attribute 'match' is missing!
    In order to use the template rule a node(s) must be selected. The match attribute is a pattern which identifies the source node or nodes which the rule applies to. It is required for template rules. Its value must be an XPath expression.

    Error deleting xslt 'transformation name'
    The transformation was not found in the system.

    Error during loading document 'document name'.
    The file was not found in the system. Probably it was deleted out of the system.

    Error while saving xslt
    The transformation cannot be saved in the system. Possible reasons are: no free disk space on the user's computer or no write permission declared.

    Expression not evaluated as a node-set.
    The XPath expression does not define any nodes which the local transformation to be applied to.

    Invalid tranformation document! Root must be either 'stylesheet' or 'transform'!
    The document which the user wants to add in the XSLT Manager is not a transformation. The root element of a transformation must be either xsl:stylesheet or xsl:transform element.

    Invalid value for attribute 'match'(XPath expression expected)!
    The match attribute is a pattern that identifies the source node or nodes which the rule applies to. Its value must be an XPath expression.

    Invalid value for attribute 'priority' (number expected)!
    The priority of a template rule is specified by the priority attribute of the template rule. Its value must be a real number (positive or negative).

    Invalid value for attribute 'select' (XPath expression expected)!
    xsl:sort has a select attribute whose value is an XPath expression. For each node to be processed, the expression is evaluated with that node as a context node and with the complete list of nodes being processed in unsorted order as a context node list. The resulting object is converted to a string as if by a call to the string() function in the XPath. This string is used as the sort key value for that node.

    Invalid XPath for local transformation:
    The defined XPath expression is not valid.

    No match attribute in pattern!
    The match attribute is a pattern that identifies the source node or nodes which the rule applies to. It is required for the template rules.

    No result produced!
    The transformation does not produce a result file from the source document.

    Root node selected as a context. This node cannot be used in local transformations and will be ignored.
    Local Tranformation cannot be applied on the root element, because it does not produce a document as a result, but a node set. In order to apply the transformation over the root element the user must not select the Use Local Transformation checkbox from the Apply XSLT dialog.

    Template rule without 'match' attribute!
    In order to use this operator (a) node(s) must be selected. The match attribute is a pattern that identifies the source node or nodes which the rule applies to. It is required for the template rules.

    The application of the current XSLT has performed an illegal DOM operation! Further processing will be cancelled.
    The result document that is produced by the transformation is not a well-formed XML document.

    The system was unable to load transformation 'transformation name'! Bad Transformation File
    The file was not found in the system. Probably it was deleted out of the system.

    The XPath expression: expression does not select any nodes!
    The XPath expression does not define any nodes which the local transformation to be applied to.

    There was an error while trying to load transformation 'transformation name' Further processing will terminate.
    A file with the transformation is not found in the system. Probably it was deleted out of the system.

    This name 'transformation name' is already in use. Do you want to overwrite the transformation?
    The entered transformation name is already used for another transformation.

    Value 'data type for attribute 'sort' is not supported!
    Only 'number' and 'text' values for that attribute are supported. It defines whether values will be compared as strings or as numbers.

    Value 'order value' for attribute 'order' is not allowed!
    The Order attribute specifies whether the strings should be sorted in ascending or descending order. Values that are allowed here are : ascending and descending.

    XPath expression for local transformation not specified.
    The XPath text field for a local transformation is empty.

    XSL transformation document not specified.
    No transformation is selected for applying.

    XSLT document 'transformation name' not found.
    The file was not found in the system. Probably it was deleted out of the system.

  • Concordance messages

    Context XPath not specified
    The XPath expression in the Define Context: field of the Concordance dialog is not specified.

    Element Value at row M has incorrect key at row N! Missing Tokenizer!
    This message occurs when the user tries to apply a Concordance operation over a document. The tokenizer attribute for the key node of the key at row N of the element value at row M in the query is empty. The user must open the query in the Concordance dialog, open the Keys table for Element Value at row M in the Element Values table and specify the Tokenizer field for the key at row N.

    Element Value at row M has incorrect key at row N! Missing Tokenizer 'tokenizer name' in the system!
    This message occurs when the user tries to apply a Concordance operation over a document. The specified tokenizer of the key at row N for the element value at row M in the query is not found in the system. The user must open the query in the Concordance dialog, open the Keys table for Element Value at row M in the Element Values table and specify the Tokenizer field for the key at row N.

    Invalid Context XPath expression XPath Error
    The XPath expression in the Define Context: field of the Concordance dialog is not valid. For details see the XPath messages.

    Invalid left context XPath expression XPath Parse Error
    The XPath expression in the Left Context: field of the Concordance dialog is not valid. For details see the XPath messages.

    Invalid right context XPath expression XPath Parse Error
    The XPath expression in the Right Context: field of the Concordance dialog is not valid. For details see the XPath messages.

    Invalid search XPath expression: Node Set result expected!
    This message occurs when the user tries to apply a Concordance operation over a document. The XPath expression in the Define Context:, Select Elements:, Left Context: or Left Context: text fields is expected to return a node set in the result, but it returns something else (number, string or boolean).

    Invalid search XPath expression: XPath Parse Error
    The XPath expression in the Search Elements: field of the Concordance dialog is not valid. For details see the XPath messages.

    Missing Filter!
    This message occurs when the user tries to apply a Concordance operation over a document. The filter node in the query is empty. The user must open the query in the Concordance dialog and specify the Filter: field.

    Missing Filter 'filter name' in the system!
    This message occurs when the user tries to apply a Concordance operation over a document. The specified filter in the query is not found in the system. The user must open the query in the Concordance dialog and specify the Filter: field.

    Missing Tokenizer!
    This message occurs when the user tries to apply a Concordance operation over a document. The tokenizer node in the query is empty. The user must open the query in the Concordance dialog and specify the Tokenizer: field.

    Missing Tokenizer 'tokenizer name' in the system!
    This message occurs when the user tries to apply a Concordance operation over a document. The specified tokenizer in the query is not found in the system. The user must open the query in the Concordance dialog and specify the Tokenizer: field.

    No search Grammar specified!
    The grammar in the Grammar field of the Concordance dialog for Normal Usage Mode is not specified.

    No search Query String specified!
    The regular expression in the Search Query field of the Concordance dialog for Simplified Usage Mode is not specified.

    No Search Query specified!
    The grammar query in the Search Query field of the Concordance dialog for Queries Usage Mode is not specified.

    Restriction Query 'query name' not found in the system!
    This message occurs when the user tries to apply a Concordance operation over a document. The specified Restriction Query in the concordance query is not found in the system. The user must open the query in the Concordance dialog and specify the Restriction Query field.

    Restriction Query - The selected document 'query name' is not a valid Grammar query!
    This message occurs when the user tries to apply a Concordance operation over a document. The specified Restriction Query in the concordance query is not a valid grammar query. The user must open the query in the Concordance dialog and specify the Restriction Query field.

    Search Query 'query name' not found in the system!
    This message occurs when the user tries to apply a Concordance operation over a document. The specified Search Query in the concordance query is not found in the system. The user must open the query in the Concordance dialog and specify the Search Query field.

    Search Query - The selected document 'query name' is not a valid Grammar query!
    This message occurs when the user tries to apply a Concordance operation over a document. The specified Search Query in the concordance query is not a valid grammar query. The user must open the query in the Concordance dialog and specify the Search Query field.

    Serach XPath not specified!
    The XPath expression in the Search Elements: field of the Concordance dialog is not specified.

    The search query element values and restriction query element values are not equal!
    In order to use a restriction grammar over the input of the search grammar, the user must synchronize the queries of both grammars on the following options: tokenizer, filter, normalize options and element values. This will allow a subword selected from the output by the restriction grammar to be acknowledged as a valid input for the search grammar.

    The search query filter and restriction query filter are not equal!
    In order to use a restriction grammar over the input of the search grammar, the user must synchronize the queries of both grammars on the following options: tokenizer, filter, normalize options and element values. This will allow a subword selected from the output by the restriction grammar to be acknowledged as a valid input for the search grammar.

    The search query normalize and restriction query normalize are not equal!
    In order to use a restriction grammar over the input of the search grammar, the user must synchronize the queries of both grammars on the following options: tokenizer, filter, normalize options and element values. This will allow a subword selected from the output by the restriction grammar to be acknowledged as a valid input for the search grammar.

    The search query tokenizer and restriction query tokenizer are not equal!
    In order to use a restriction grammar over the input of the search grammar, the user must synchronize the queries of both grammars on the following options: tokenizer, filter, normalize options and element values. This will allow a subword selected from the output by the restriction grammar to be acknowledged as a valid input for the search grammar.

  • Extract messages

    Invalid Searsh XPath expression: XPath Parse Error
    The XPath expression in the Search: field of the Extract dialog is not valid. For details see the XPath messages.

    Invalid Searsh XPath expression: Node set result expected!
    This error message appears when the user tries to apply a Extract operation over a document. The XPath expression in Search text field is expected to return a node set in the result, but it returns something else (number, string or boolean). The XPath expresion specifies the nodes which the extract operation will be applied to.

    Number attribute field is empty!
    The name of the attribute in the Create number attribute? field of the Extract dialog is not specified. The user must specify it or he/she must uncheck this option.

    Number attribute has invalid symbol at position N!
    The name of the attribute in the Create number attribute? field of the Extract dialog does not obey the standard. For details see the XML recommendation for the valid name standard.

    Path attribute field is empty!
    The name of the attribute in the Create path attribute? field of the Extract dialog is not specified. The user must specify it or he/she must uncheck this option.

    Path attribute has invalid symbol at position N!
    The name of the attribute in the Create path attribute? field of the Extract dialog does not obey the standard. For details see the XML recommendation for the valid name standard.

    Result element field is empty!
    The name of the attribute in the Create result tag? field of the Extract dialog is not specified. The user must specify it or he/she must uncheck this option.

    Result element has invalid symbol at position N!
    The name of the attribute in the Create result tag? field of the Extract dialog does not obey the standard. For details see the XML recommendation for the valid name standard.

    Search XPath not specified!
    The XPath expression in the Search field of the Extract dialog is not specified.

    Source attribute field is empty!
    The name of the attribute in the Create source attribute? field of the Extract dialog is not specified. The user must specify it or he/she must uncheck this option.

    Source attribute has invalid symbol at position N!
    The name of the attribute in the Create source attribute? field of the Extract dialog does not obey the standard. For details see the XML recommendation for the valid name standard.

  • Sort messages

    Invalid search XPath expression! XPath Parse Error
    The XPath expression in the Search Elements: field of the Sort nodes dialog is not valid. For details see the XPath messages.

    Invalid XPath expression! Node Set result expected!
    This message occurs when the user tries to apply a sort operation over a document. The XPath expression in the Select Elements: text field is expected to return a node set in the result, but it returns something else (number, string or boolean). The XPath specifies the nodes which the sort operation will be applied to.

    Error during compiling key number N! XPath Parse Error
    The XPath expression of the key at row N of the Sort nodes dialog is not valid. For details see the XPath messages.

    Key number at row N is not valid: Invalid XPath expression: XPath Parse Error
    The XPath expression of the key at row N of the Sort dialog is not valid. For details see the XPath messages.

    Key number at row N is not valid: Missing Tokenizer!
    This message occurs when the user tries to apply a Sort operation over a document. The tokenizer attribute for the key node of the key at row N in the query is empty. The user must open the query in the Sort dialog and specify the Tokenizer field for the key at row N.

    Key number at row N is not valid: Missing Tokenizer 'tokenizer name' in the system!
    This message occurs when the user tries to apply a Sort operation over a document. The specified tokenizer of the key at row N in the query is not found in the system. The user must open the query in the Sort dialog and specify the Tokenizer field for the key at row N.

    Key number at row N is not valid: XPath not specified!
    This message occurs when the user tries to apply a Sort operation over a document. The expr attribute for the key node of the key at row N in the query is empty. The user must open the query in the Sort dialog and specify the Expression field for the key at row N.

    Missing key Node!
    The XPath expression of the key in the Expression field of the Sort nodes dialog is not specified. The system expects at least one XPath expression key.

    Search XPath not specified!
    The XPath expression in the Search Elements: field of the Sort nodes dialog is not specified.

  • XPath Insert Attribute messages

    Attribute name not specified!
    The attribute name in the Attribute Name: field of the XPath Insert Attribute dialog is not specified.

    Attribute value not specified!
    The attribute value in the Value: field of the XPath Insert Attribute dialog is not specified.

    Expression does not return node-set.
    It is not possible to apply the operation over the result of the XPath expression.

    Invalid attribute name : 'AttrName'!
    The attribute name 'AttrName' does not obey the standard. For details see the XML recommendation for the valid name standard.

    Invalid XPath expression: XPath Parse Error
    The XPath expression in the XPath: field of the XPath Insert Attribute dialog is not valid. For details see the XPath messages.

    New attribute not specified!
    This message occurs when the user tries to apply an XPath Insert Attribute operation over a document. The attrInfo node in the query is missing. The user must open the query in the XPath Insert Attribute dialog and specify the Attribute Name: and Value text field.

    No appropriate element nodes selected for attribute insertion!
    It is not possible to apply the operation over the result of the XPath expression.

    XPath not specified!
    The XPath expression in the XPath: field of the XPath Insert Attribute dialog is not specified.

  • XPath Insert Child messages

    Expression does not return node-set.
    It is not possible to apply the operation over the result of the XPath expression.

    Invalid child type (Type)!
    This message appears when the user tries to apply XPath Insert Child operation over a document. The type attribute of the childInfo node in the query is not valid. The user must open the query in the XPath Insert Child dialog and specify the Insert field.

    Invalid insertion position!
    The numeric value in the at position: field of the XPath Insert Child dialog is not in a proper format. The system expects a non-negative integer.

    Invalid tagname ('Tag') !
    The name of the child element in the Insert element field of the XPath Insert Child dialog does not obey the standard. For details see the XML recommendation for the valid name standard.

    Invalid XPath expression: XPath Parse Error
    The XPath expression in the XPath: field of the XPath Insert Child dialog is not valid. For details see the XPath messages.

    New child not specified!
    The element name in the Insert element: field of the XPath Insert Child dialog is not specified.

    No nodes selected for processing!
    There are no appropriate nodes selected to execute the operation.

    No text data specified!
    The text in the Insert text: field of the XPath Insert Child dialog is not specified.

    XPath not specified!
    The XPath expression in the XPath: field of the XPath Insert Child dialog is not specified.

  • XPath Insert Parent messages

    Expression does not return node-set.
    It is not possible to apply the operation over the result of the XPath expression.

    Invalid new parent name : 'Tag'!
    The name of the parent element in the New Parent Name: field of the XPath Insert Parent dialog does not obey the standard. For details see the XML recommendation for the valid name standard.

    Invalid XPath expression: XPath Parse Error
    The XPath expression in the XPath: field of the XPath Insert Parent dialog is not valid. For details see the XPath messages.

    New parent name not specified!
    The name of the parent element in the New Parent Name: field of the XPath Insert Parent dialog is not specified.

    XPath not specified!
    The XPath expression in the XPath: field of the XPath Insert Parent dialog is not specified.

  • XPath Insert Sibling messages

    Expression does not return node-set.
    It is not possible to apply the operation over the result of the XPath expression.

    Invalid insertion direction!
    This message occurs when the user tries to apply an XPath Insert Sibling operation over a document. The dir attribute of the siblingInfo node in the query is not valid. The user must open the query in the XPath Insert Sibling dialog and specify the as field.

    Invalid sibling node type ('Type')!
    This error message appears when the user tries to apply an XPath Insert Sibling operation over a document. The type attribute of the siblingInfo node in the query is not valid. The user must open the query in the XPath Insert Sibling dialog and specify the insert field.

    Invalid tagname ('Tag') !
    The name of the sibling element in the New Sibling Name: field of the XPath Insert Sibling dialog does not obey the standard. For details see the XML recommendation for the valid name standard.

    Invalid XPath expression: XPath Parse Error
    The XPath expression in the XPath: field of the XPath Insert Sibling dialog is not valid. For details see the XPath messages.

    New sibling node not specified!
    The name of the sibling element in the New Sibling Name: field of the XPath Insert Sibling dialog is not specified.

    No nodes selected for processing!
    There are no appropriate nodes selected to execute the operation.

    No text data specified!
    The text in the Insert text: field of the XPath Insert Sibling dialog is not specified.

    XPath not specified!
    The XPath expression in the XPath: field of the XPath Insert Sibling dialog is not specified.

  • XPath Remove messages

    Expression does not return node-set.
    It is not possible to apply the operation over the result of the XPath expression.

    Invalid XPath expression: XPath Parse Error
    The XPath expression in the XPath: field of the XPath Remove dialog is not valid. For details see the XPath messages.

    Nothing to remove.
    There are no appropriate nodes selected to execute the operation.

    XPath not specified!
    The XPath expression in the XPath: field of the XPath Remove dialog is not specified.

  • XPath Rename messages

    Expression does not return node-set.
    It is not possible to apply the operation over the result of the XPath expression.

    Invalid new tag name : 'Tag'!
    The name of the element in the New Name: field of the XPath Rename dialog does not obey the standard. For details see the XML recommendation for the valid name standard.

    Invalid XPath expression: XPath Parse Error
    The XPath expression in the XPath: field of the XPath Rename dialog is not valid. For details see the XPath messages.

    New tag name not specified!
    The name of the element in the New Name: field of the XPath Rename dialog is not specified.

    XPath not specified!
    The XPath expression in the XPath: field of the XPath Rename dialog is not specified.

  • XPath Transformation messages

    Invalid attribute name: attribute name
    The name of the attribute in the as attribute with name field of the XPath Transformation dialog does not obey the standard. For details see the XML recommendation for the valid name standard.

    Invalid offset mode.
    This message occurs when the user tries to apply an XPath Transformation operation over a document. The node name node in the query is missig. The user must open the query in the XPath Transformation dialog and specify one of the sibling offset modes - after or before.

    Invalid position value : value. Non negative number expected!
    This message occurs when the value of the as child at position text field in the XPath Transformation dialog is not a positive integer value or zero. It defines the position where the source will be inserted as a child.

    Invalid Source XML fragment: XML Parse Errors
    The source XML fragmend in the Source XPath/XML field of the XPath Transformation dialog is not valid. For details see the XML Parse Error Messages or XML Validation Error Messages.

    Invalid Sourse XPath expression: XPath Parse Error
    The XPath expression in the Source XPath/XML field of the XPath Transformation dialog is not valid. For details see the XPath messages.

    Invalid Target XPath expression: XPath Parse Error
    The XPath expression in the Target field of the XPath Transformation dialog is not valid. For details see the XPath messages.

    Invalid target mode.
    This message occurs when the user tries to apply an XPath Transformation operation over a document. The node name node in the query is missig. The user must open the query in the XPath Transformation dialog and specify one of the insert modes - as parent, as child, as sibling or as attribute.

    Invalid XPath expression: XPath Parse Error
    The XPath expression in the XPath: field of the XPath Insert Attribute dialog is not valid. For details see the XPath messages.

    Missing mode node
    This message occurs when the user tries to apply an XPath Transformation operation over a document. The node name node in the query is missig. The user must open the query in the XPath Transformation dialog and specify one of the modes - Local Source, External Source or Distributed Source.

    Source document with number N not specified.
    The name of the source document with number Nof the XPath Transformation dialog is not specified.

    Source documents not specified.
    This message occurs when the user tries to apply an XPath Transformation operation over a document. The node name node in the query is missig. The user must open the query in the XPath Transformation dialog and add source documents.

    Source XPath - Node Set result expected
    This error message appears when the user tries to apply an XPath Transformation operation over a document. The XPath expression in Source XPath/XML text field is expected to return a node set in the result, but it returns something else (number, string or boolean). That is the reason because the operation can not be executed.

    Source XPath/XML not specified!
    The XPath expression or the XML fragment in the Source XPath/XML field of the XPath Transformation dialog is not specified.

    Target document with number N not specified.
    The name of the target document with number Nof the XPath Transformation dialog is not specified.

    Target XPath not specified!
    The XPath expression in the Target field of the XPath Transformation dialog is not specified.

    Target XPath - Node Set result expected
    This error message appears when the user tries to apply an XPath Transformation operation over a document. The XPath expression in Target text field is expected to return a node set in the result, but it returns something else (number, string or boolean). That is the reason because the operation can not be executed.

  • Statistics messages

    Invalid query, there are no key or many keys Element !
    This error message appears when the user tries to apply a Statistics operation over a document. The keys node in the query is missing. The user must open the query in the Statistics dialog and specify the Value Keys field.

    Invalid XPath expression: XPath Parse Error
    The XPath expression in the Select (XPath): field of the XPath Statistics dialog is not valid. For details see the XPath messages.

    Key number at row N is not valid: Invalid XPath expression: XPath Parse Error
    The XPath expression of the key at row N of the XPath Statistics dialog is not valid. For details see the XPath messages.

    Key number at row N is not valid: Missing Tokenizer!
    This message occurs when the user tries to apply a Statistics operation over a document. The tokenizer attribute for the key node of the key at row N in the query is empty. The user must open the query in the Statistics dialog and specify the Tokenizer field for the key at row N.

    Key number at row N is not valid: Missing Tokenizer 'tokenizer name' in the system!
    This message occurs when the user tries to apply a Statistics operation over a document. The specified tokenizer of the key at row N in the query is not found in the system. The user must open the query in the Statistics dialog and specify the Tokenizer field for the key at row N.

    Key number at row N is not valid: XPath not specified!
    This message occurs when the user tries to apply a Statistics operation over a document. The expr attribute for the key node of the key at row N in the query is empty. The user must open the query in the Statistics dialog and specify the Expression field for the key at row N.

    Missing key Node!
    This message occurs when the user tries to apply a Statistics operation over a document. The key node in the query is missing. The user must open the query in the Statistics dialog and specify the Expression text field in Value Keys field.

    Missing TokCat tokenizer category!
    This message occurs when the user tries to apply a Statistics operation over a document. The value of the tokenizer category in the query is missing for the defined tokenizer. The user must open the query in the CLaRK System dialog and specify the right value of the tokenizer category.

    Missing Tokenizer!
    This message occurs when the user tries to apply a Statistics operation over a document. The name node of the tokenizer node in the query is empty. The user must open the query in the Statistics dialog and specify the Choose Tokenizer: field.

    Missing Tokenizer 'tokenizer name' in the system!
    This message occurs when the user tries to apply a Statistics operation over a document. The specified tokenizer in the query is not found in the system. The user must open the query in the Statistics dialog and specify the Choose Tokenizer: field.

    XPath not specified!
    The XPath expression in the Select (XPath): field of the XPath Statistics dialog is not specified.

  • Nodes Info messages

    Error appeared while saving result: Saving Document Error
    This message occurs when the user tries to export the result from the Nodes Info operation as an XML file out of the system. Possible reasons are: no free disk space on the user's computer or no write permission declared.

    Error in XPath: XPath Parse Error
    The XPath expression in the Enter XPath for node: field of the Node Info dialog is not valid. For details see the XPath messages.

    You must select at least one document!
    It is not possible to proceed with this operation without (a) selected document(s).

  • Text Replace messages

    Apply to xpath expression is invalid! Node Set result expected!
    This error message appears when the user tries to apply a Text Replace operation over a document. The XPath expression in Apply to text field is expected to return a node set in the result, but it returns something else (number, string or boolean). The XPath expresion specifies the nodes which the text replace operation will be applied to.

    Apply to xpath expression is invalid! XPath Parse Error
    The XPath expression in the Apply to: field of the Text Replace dialog is not valid. For details see the XPath messages.

    Error in replacing string! message
    This message occurs when the user tries to apply a Text Replace operation over a document. The replace markup expression in the Replace with: text field is not valid.

    Error in search expression!
    This message occurs when the user tries to apply a Text Replace operation over a document. The search regular expression in the Search for: text field is not valid.

    Missing Filter!
    This message occurs when the user tries to apply a Text Replace operation over a document. The filter node in the query is empty. The user must open the query in the Text Replace dialog and specify the Filter field.

    Missing Filter 'filter name' in the system!
    This message occurs when the user tries to apply a Text Replace operation over a document. The specified filter in the query is not found in the system. The user must open the query in the Text Replace dialog and specify the Filter: field.

    Missing Tokenizer!
    This message occurs when the user tries to apply a Text Replace operation over a document. The tokenizer node in the query is empty. The user must open the query in the Text Replace dialog and specify the Tokenizer field.

    Missing Tokenizer 'tokenizer name' in the system!
    This message occurs when the user tries to apply a Text Replace operation over a document. The specified tokenizer in the query is not found in the system. The user must open the query in the Text Replace dialog and specify the Tokenizer: field.

    Search expression not specified!
    The regular expression in the Search for: field of the Text Replace dialog is not specified.

    XPath in the field 'Apply to' not specified!
    The XPath expression in the Apply to: field of the Text Replace dialog is not specified.

  • Multi Query Tool messages

    Duplicated label: label
    This message occurs when the user tries to apply a Multi Query Tool operation over a document. There are more than one labels with equal names. The label names must be unique for the correct identification of the corresponding label configurations. The user must rename one of the labels.

    Error in compiling xpath: XPath Parse Error
    The XPath expression in the XPath: field of the Control Operator dialog (MultiQuery Tool Manager dialog) is not valid. For details see the XPath messages.

    Invalid conditional XPath for Control operator! XPath Parse Error
    This message occurs when the user tries to apply a Multi Query Tool operation over a document. The xpath attribute of the control node in the query is not valid. For details see the XPath messages.

    Invalid Control type!
    This message occurs when the user tries to apply a Multi Query Tool operation over a document. The type attribute of the control node in the query is not valid.

    Invalid tool name 'Tool Name' for query: 'query name'!
    This message occurs when the user tries to apply a Multi Query Tool operation over a document. The tool attribute of the control node in the query is not valid.

    No conditional XPath defined!
    The XPath expression in the XPath: field of the Control Operator dialog (MultiQuery Tool Manager dialog) is not specified.

    No conditional XPath for Control operator!
    This message occurs when the user tries to apply a Multi Query Tool operation over a document. The xpath attribute of the control node in the query is not specified.

    No queries selected for applying!
    This message occurs when the user tries to apply a Multi Query Tool operation over a document. There are no queries in the Tool Queries field. The system requires at least one query.

    No target label for Control found!
    This message occurs when the user tries to apply a Multi Query Tool operation over a document. The target attribute of the control node in the query is not specified.

    No target label selected ! You must assign one before application.
    The target label in the Target: field of the Control Operator dialog (MultiQuery Tool Manager dialog) is not specified.

    Missing or invalid tool query name!
    This message occurs when the user tries to apply a Multi Query Tool operation over a document. The query name in the query is not specified or there is no such kind of query name in the system.

    Missing tool name for query: 'query name'!
    This message occurs when the user tries to apply a Multi Query Tool operation over a document. The tool attribute of the query node in the query is not specified.

    Query file for 'query name' not loaded! Reason: Error
    This message occurs when the system tries to load a query, which is not found in the system. Probably it was deleted out of the system.

    Recursive target-label pair: Target Label!
    This message occurs when the user tries to apply a Multi Query Tool operation over a document. The target label is used as a label and as a target in one control row in the Tool Queries table of the MultiQuery Tool Manager dialog.

    Target label 'Lab' used but not defined!
    This message occurs when the user tries to apply a Multi Query Tool operation over a document. The target label Lab is used as a target in the Info column in the Tool Queries field, but it is not defined as a label in the Label column.

    The query document 'query name' does not appear in a suitable query group for tool 'tool name'
    There are several system groups. Each of them can contain only documents with a certain DTD. Each query has a DTD and is located to a relevant group. The user cannot use documents without a required query DTD or documents from folders except for Root : SYSTEM : Queries.

    The selected documents either do not represent tool queries, or they do not appear in an appropriate group.
    There are several system groups. Each of them can contain only documents with a certain DTD. Each query has a DTD and is located to a relevant group. The user cannot use documents without a required query DTD or documents from folders except for Root : SYSTEM : Queries.

    The system was not able to load query: Error
    This message occurs when the system tries to load a query, which is not found in the system. Probably it was deleted out of the system.

  • Multiple Apply messages

    Some data of the current query may have been modified! Do you want to save it?
    This message occurs when the user tries to apply a query in the relevant tool dialog and the data from the query was modified. If the user wants to update the changes he/she has to click the Yes button, otherwise the user will loose the query changes.

    Some data may have been modified and the changes will be lost! Do you want to proceed?
    This message occurs when the user tries to load a query in the relevant tool dialog. If the user clicks the Yes button all data in the dialog will be modified by the data from the query. If the user does not want to loose the data in the dialog he/she has to click the No button, then save the current query and to load the new query.

  • Queries messages

    Enter all output file names
    This message occurs when the user tries to apply a Multiple Apply operation. There are output documents in the Internal Documents table which have to be specified. The system requires all the output documents to be specified.

    File on row N is already in the output!
    This message occurs when the user tries to apply a Multiple Apply operation. The output document on row N in the Internal Documents table is already used as an output document name. The system requires all the output document names to be different.

    Please insert output name
    The output document name in the Name: field of the Result Options dialog (Multiple Apply dialog) is not specified.

    Please insert output name extension
    The default extension of the output document names in the Default Extension: field of the Result Options dialog (Multiple Apply dialog) is not specified.

    Please select at least one document
    This message occurs when the user tries to apply a Multiple Apply operation. The input documents in the Internal Documents table are not specified. The system requires at least one input document.

 

Document Error Messages

  • Validate Error Messages

    Validation disabled! Please use menu 'Options' to enable it!
    This error message appears when the user tries to apply Validation operation over a current document in the system. If a validation of the current document is needed, then the user must uncheck the Disable Validation menu item from the Options menu.

 

Options Error Messages

  • Keyboard Error Messages

    Invalid numeric input: For input string "String"
    The numeric value entered in the Go to: field of the Keyboard Editor dialog is not in a proper format. The system expects a non-negative integer.

    Invalid numeric input: Value out of range (0..255).
    The numeric value entered in the Go to: field of the Keyboard Editor dialog does not represent a valid code page. The value must be in the range [0, 255].

    Invalid numeric input: Value out of range (0..65400).
    The numeric value entered in the Go to: field of the Keyboard Editor dialog does not represent a valid Unicode entry. The value must be in the range [0, 65400].

    This name is already in use. Please specify a new name!
    The keyboard name which the user has just entered is already used for another keyboard. The keyboard names must be unique in order the corresponding keyboard configurations to be identified correctly.

  • Visuals Error Messages

    Please specify an XPath expression!
    This message occurs when the user defines a rule in a Color Scheme and the XPath expression is not specified (which is required). The rule definition cannot be completed successfully unless a valid XPath expression is supplied.

    This name is already in use! Please, enter a new name!
    This error message appears when the user supplied a name for a Color Scheme which is already used for another scheme. The color scheme names must be unique for correct color scheme addressing.

    Unable to parse the XPath expression: XPath Parse Error
    This error message appears when the user creates/modifies rules in a Color Scheme. The XPath expression, which is entered for a rule of a color scheme, is not valid. For details see the XPath Error Messages.

 

More error messages

  • Tree Pop-up Error Messages

    Empty names not allowed!
    This message occurs when the user tries to add a user-defined attribute, child element or sibling element with no name of the element or the attribute. Empty elements and attributes are not allowed according to the XML Specification. For details see the XML recommendation for the valid name standard.

    Invalid character in attribute name attribute name at position: number, char: character!
    This message occurs when the user tries to add a user-defined attribute to an element. Attribute name is a token beginning with a letter or underscores and continuing with letters, digits, hyphens, underscores, colons, or full stops.

    Invalid character in tag name tag name at position: number, char: character!
    This message occurs when the user tries to add a user-defined parent, child element or sibling element. Tag name is a token beginning with a letter or underscores and continuing with letters, digits, hyphens, underscores, colons, or full stops.

    There are no Regular Expression Constraints defined!
    This message occurs when the user applies a Regular Expression Constraint over a selection of nodes in Tree Area. In order to apply a Regular Expression Constraint the user must first define it in the system.

    There are no XSLTransformations in the system.
    This error message appears when user tries to apply Invoke XSLT operation over a selection of nodes in the tree pane in the system, but there are no XSL transformations in the system. In order to apply the Invoke XSLT operation user must insert or create XSL Transformation in the system.

  • Compilation Error Messages

    Ambiguous Categories: cat1 and cat2
    The regular expressions of two categories recognize the same language. If this message appears simultaneously during the compilation of a grammar, then the two grammar rules can recognize the same words of the 3 regular expressions (left, body and right).

    Brackets not opened in expression expression
    An opened bracket in expression is not closed. To solve the problem, search for a non-closed bracket or an unproperly quoted bracket.

    Bracket not opened at position position in expression expression
    There is a closing bracket in the regular expression without a corresponding opening one!

    Brackets opened at position position not closed in expression expression
    A bracket opened at the specified position of the expression is not closed. Check for a place to put the closing bracket in the regular expression or for an unproperly quoted bracket.

    Brackets with empty content!
    In the regular expression there is an opening bracket immediately followed by a closing one.

    Empty atom at position position of expression expression!
    The regular expression contains an atom that is an empty string. Check the expression at the specified position for expressions like "()" or two operations like "|" and "," without an atom between them.

    Expression expression not finished! Expected character and quotation
    A quotation opened in the expression is not closed. To solve the problem search for a non-closed quotation or unproperly escaped quotation.

    Operator operator without expression!
    Unary operators require some regular expression! The user must specify a regular expression for the unary operator.

    Quotation opened at position position not closed in expression expression!
    A quotation opened at the specified position of the expression is not closed. Check for a place to put the closing quotation in the regular expression or for unproperly escaped quotation.

    Regular expression: expression cannot end in ',' or '|' symbols!
    The regular expression ends in a binary operation that has a missing argument. Usually the problem appears when the regular expression is not finished.

  • XPath Error Messages

    A closing bracket expected in: string!
    This message occurs when the number of the opening brackets is less than the number of closing ones or the brackets are nested incorrectly in the given string.

    An operand in Union Expression does not produce a node-set.
    This message occurs when after evaluation an operand is expected to return a node set in the result, but it returns something else - a number, a string or a boolean value. The | operator computes the union of its operands, which must be node-sets.

    Cannot convert expression to a number (string)!
    This error message occurs when there is an operator or function that expects a number value and the string which is its operand cannot be converted to a number. The expression is not a number or it is an infinite value.

    Document Axis does not allow any context Location Steps!
    This message occurs when in the XPath there is an axis document which is not in the beginning of the expression. That axis can only appear in the beginning of an XPath expression.

    Empty Path Expression!
    This message occurs when the system tries to process an empty XPath expression.

    Empty Relative Location Path!
    This message occurs when the system tries to process an empty XPath expression.

    Empty Union Expression!
    This message occurs when the XPath expression starts or ends with |. The | binary operator computes the union of the results of its operands, which must be node-sets.

    Error in regular expression regular expression!
    This message occurs when there is a complex text() node test - with two, three or four arguments. In this case if the last argument is in brackets it is expected to be a regular expression.

    Error in opening grammar query regular expression!
    This message occurs when there is a complex text() node test - with two arguments. When the second argument is without brackets it is treated as a grammar query name, saved in the system. If there is no such a query in the system or it is not a valid query.

    Expected ')' in string!
    This message occurs when an opening bracket is used without a closing one, or there are incorrectly nested brackets.

    Expected at least one Step!
    This message occurs when the XPath contains only the symbol /. The / selects the document root (which is always the parent of the document element). A location path consists of a sequence of one or more location steps separated by /.

    Expected node test or name specification after axis operator "operator" !
    Each location step has three parts:

    1. an axis, which specifies the tree relationship between the nodes selected by the location step and the context node (Axis :: ),
    2. a node test, which specifies the node type or the names of the nodes selected by the location step, and
    3. zero or more predicates, which use arbitrary expressions to further refine the set of nodes selected by the location step.

    Illegal expression in arguments of function 'function'.
    This message occurs when there is an argument of the function that is not in appropriate format or it is missing.

    Incompatible Context: string1 and string2
    This message occurs when there is a location step that receives as a context something that is not a node or a node-set (a number, a string or a boolean value).

    Incompatible XPath key 'string' (node-set expected as result)!
    This message occurs when there is a predicate or a location path from an XPath key that is not evaluated as a node-set in the required place.

    Incorrect Variable Binding: bindings not allowed in expression.
    This message occurs when there is a variable declaration that is not in the beginning of the XPath expression. The variable declarations are allowed only in the beginning of the XPath.

    Incorrect Variable Binding: expected '{'.
    This message occurs when there is a variable declaration and there is a curly closing bracket before a opening one.

    Incorrect Variable Binding: expected '}'.
    This message occurs when there is a variable declaration and there is a curly opening bracket without a closing one.

    Incorrect Variable Binding: expected ':=' in 'variable definition'.
    This message occurs when there is a variable declaration and there is no := operand that assigns a value to the variable.

    Incorrect Variable Binding: expected variable name in 'variable definition'.
    This message occurs when there is a variable declaration and there is no variable name but variable assignment.

    Incorrect Variable Binding: expected variable value in 'variable definition'.
    This message occurs when there is a variable declaration and there is no value assigned to the variable.

    Invalid additive expression. Missing left operand for "op"!
    The + and - are binary operators. These numeric operators convert their operands to numbers by calling the number() function. In this case there is a missing left operand.

    Invalid additive expression. Missing right operand for "op"!
    The + and - are binary operators. These numeric operators convert their operands to numbers by calling the number() function. In this case there is a missing right operand.

    Invalid AND expression. Missing left operand!
    An and is a binary operator. The and expression is evaluated by considering each operand and converting its value to a boolean value by a call to the boolean() function. In this case there is a missing left operand.

    Invalid AND expression. Missing right operand!
    An and is a binary operator. The and expression is evaluated by considering each operand and converting its value to a boolean value by a call to the boolean() function. In this case there is a missing right operand.

    Invalid atomic expression: string) !
    This message occurs when the expression is not recognized as number, text, expression in brackets, a variable reference or a function call.

    Invalid attribute name: 'string'!
    This message occurs when there is an attribute addressed in the XPath expression and the attribute name is not a proper name. The attribute name is a token beginning with a letter or underscore, and continuing with letters, digits, hyphens, underscores, colons, or full stops. For details see the XML Specifications.

    Invalid Axis Name "name" !
    This message occurs when in the XPath expression there is an Axis Specifier. Valid axis specifiers are: ancestor, ancestor-or-self, attribute, child, descendant, descendant-or-self, following, following-sibling, namespace, parent, preceding, preceding-sibling and self.

    Invalid bracketed expression detected: '()'!
    This message occurs when the expression is (). A function name or an expression in the brackets is expected

    Invalid Brackets in string!
    This message occurs when there is a closing bracket without an opening one and vice versa. Also it is possible that the brackets are incorrectly nested.

    Invalid element name: 'name'!
    This message occurs when there is an element addressed in the XPath expression and the element name is not a proper name. The element name is a token beginning with a letter or underscore, and continuing with letters, digits, hyphens, underscores, colons, or full stops. For details see the XML Specifications.

    Invalid element or attribute name: 'string'!
    This message occurs when there is an element or an attribute addressed in the XPath and the element name is not a proper name. A valid name is a token beginning with a letter or underscore, and continuing with letters, digits, hyphens, underscores, colons, or full stops. For details see the XML Specifications.

    Invalid equality expression. Missing left operand for "operator"!
    The = and != are binary relations. They expect two operands to be compared. In this case there is a missing left operand.

    Invalid equality expression. Missing right operand for "operator"!
    The = and != are binary relations. They expect two operands to be compared. In this case there is a missing right operand.

    Invalid Expression
    This message occurs when there is a unary operation '-' to an expression that is not a numeric one.

    Invalid expression: 'string'!
    This message occurs when there is a expression after a quoted expression.

    Invalid multiplicative expression. Missing left operand for "operator"!
    The *, div and mod are binary operators. They expect two operands. This operators convert their operands to numbers by calling the number() function. In this case there is a missing left operand.

    Invalid multiplicative expression. Missing right operand for "op"!
    The *, div and mod are binary operators. They expect two operands. This operators convert their operands to numbers as if by calling the number() function. In this case there is a missing right operand.

    Invalid Node Test: "string".
    Each location step has three parts:

    1. an axis, which specifies the tree relationship between the nodes selected by the location step and the context node (Axis :: ),
    2. a node test, which specifies the node type or the names of the nodes selected by the location step, and
    3. zero or more predicates, which use arbitrary expressions to further refine the set of nodes selected by the location step.

    Invalid Node Test: 'string'. Expected: 'n(doc_name)'.
    This message occurs when document axis is used. The syntax for document axis is document::n(document name), where document name is a name of a document saved in the system.

    Invalid OR expression. Missing left operand!
    An or is a binary operator. The or expression is evaluated by considering each operand and converting its value to a boolean value by a call to the boolean() function. In this case there is a missing left operand.

    Invalid OR expression. Missing right operand!
    An or is a binary operator. The or expression is evaluated by considering each operand and converting its value to a boolean value by a call to the boolean() function. In this case there is a missing right operand.

    Invalid Predicates List "string"!
    This message occurs when there is a predicate list without a closing square bracket, or the brackets are incorrectly nested.

    Invalid Relative Location Path "string"!
    This message occurs when the XPath expression ends with /. A relative location path consists of a sequence of one or more location steps separated by /.

    Invalid relational expression. Missing left operand for "operator"!
    The <, >, <= and >= are binary relations. They expect two operands to be compared. In this case there is a missing left operand.

    Invalid relational expression. Missing right operand for "operator"!
    The <, >, <= and >= are binary relations. They expect two operands to be compared. In this case there is a missing right operand.

    Invalid suffix: 'string'!
    This message occurs when there is an expression after an expression in brackets.

    Invalid Union Expression "expression"!
    This message occurs when the XPath expression starts or ends with |. The | operator computes the union of the results of its operands, which must be node-sets.

    Invalid variable name: 'variable name'.
    This message occurs when the variable name contains spaces, opening square brackets or colons.

    Invalid variable value type for 'variable name':expected node-set.
    This message occurs when the variable type is expected to be a node set, but it is something else (a number, a string or a boolean value).

    Literal not closed! Expected ' in : string!
    This message occurs when there is a citation of a text that is not closed.

    Missing XPath key 'key'!
    This message occurs when there is a key addressing % and there is no key with such name saved in the system.

    Missing XPath key name!
    This message occurs when there is a key addressing % and the name of the key that is addressed is missing.

    This XPath Expression selects 0 nodes for any context!
    This message occurs when there is a location step selecting child or descendant nodes of a node that cannot have descendants. For example, children of a text node, an attribute or a comment.

    There is Path Expression that returns other than Node Set
    This message occurs when the Path Expression is expected to return a node set in the result, but it returns something else (a number, a string or a boolean value).

    Variable 'variable name' not defined!
    There is a variable that is used in the XPath expression and is not defined. Variable definitions are in the beginning of the XPath expressions.