Home
Description
Publications

Available Resources
Text Acknowledgements
Related links


Events


CLaRK System

CLaRK System Online Manual


Bulgarian dialects'
electronic archive



eXTReMe Tracker

 

 

 

 

 

 

 

Tools messages

Grammars 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

  • <copy-of> 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.

  • <for-each> 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.

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

  • <value-of> 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.