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