XHTML UA diagnostics kit 2/2

HTML

If the two following documents are rendered as HTML, the UA supports HTML parsing. If only the first one is rendered as HTML, the UA parses text/html as XML and ignores namespaces.

• HTML 4.01 Strict (well-formed if parsed as XML)
• HTML 4.01 Strict (ill-formed if parsed as XML)

Doctypeless text/html

If the two following documents are rendered as HTML, the UA supports HTML parsing. If only the first one is rendered as HTML, the UA parses text/html as XML and ignores namespaces.

• Doctypeless text/html (well-formed if parsed as XML)
• Doctypeless text/html (ill-formed if parsed as XML)

UTF-*

All XML processors must support the UTF-8 and UTF-16 encodings. However, the UA might not be able to display all Unicode characters. The encoding is not advertised in the HTTP Contet-Type header. The XML processor must apply the rules given in the XML specification.

• Latin-1 characters as UTF-8
• Latin-1 characters as UTF-8 (explicit encoding)
• Windows-1252 characters as UTF-8
• Windows-1252 characters as UTF-8 (explicit encoding)
• BMP characters as UTF-8
• BMP characters as UTF-8 (encoding explicit)
• BMP characters as UTF-16
• Astral character as UTF-8
• Astral character as UTF-8 (encoding explicit)
• Astral character as UTF-16

Entity reference

Non-validating XML processors do not need to process the DTD. However, UAs might implement more or less dirty hacks in order to support the XHTML character entities.

• Entity reference