Invalid document displays at plain text view or at normal view

[achu]

Some of invalid documents are able to display at normal view; while some of them display at plain text view.

What rules determine the view type for those invalid documents?

XMetal version: 4.6.

[Derek Read]

When attempting to display a document in TagsOn or Normal view XMetaL Author must be able to render the document.

Invalid documents can be rendered, provided XMetaL is able to guess (and insert) missing closing elements.

The product does not attempt to correct element or attribute name misspellings however. Such elements are treated the same as if they are not declared in the DTD or Schema at all. It does not attempt to move elements that are located in the wrong position either. I believe these are the situations where rendering in TagsOn and Normal views will fail and you must fix these issues in PlainText view.

If a required element or attribute is missing XMetaL Author should be able to render the document in TagsOn or Normal view. If text is located in a position it is not allowed (generally outside an element declared to contain PCDATA) that is generally OK as well and you will be able to get to TagsOn or Normal view. The same is true for invalid attribute values. However, it is possible for an attribute value to not be considered closed and this can get you stuck in PlainText views.

Keep in mind that it is virtually impossible to get stuck in PlainText view if you always work in TagsOn or Normal view and no other software touches your files. Most cases where you might get stuck fixing your XML in PlainText view are caused by editing using 3rd party software.