Document Types > Document Types > Document Type Migration Issues > New XML-Parser Errors
New XML-Parser Errors
Some existing XML documents will now get parser errors although there is no change in how the document is read into memory (that is, no data is lost). The types of errors include:
Entity or character reference not terminated by “;” character, either in content or in an attribute value.
Ampersand character “&” not escaped in content or attribute value.
Less than character “<” not escaped in attribute value. (Content was checked formerly.)
Malformed character references. For example, “&#x0g;
For errors in attribute values, unescaped “&” characters which do not precede entity or character references will be replaced by "&amp;". (Epic Editor also performed this action for some cases in prior releases.) Epic Editor 5.0 and later requires a valid terminator following “&”. If the terminator is not present, the ampersand is escaped.