[TYPO3-core] FYI24 #14118: Exception handler does not produce valid (X)HTML

Patrick Broens patrick at netcreators.com
Thu Apr 15 13:02:59 CEST 2010


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 15-4-2010 12:40, Oliver Klee wrote:
> Hi,
> 
> Patrick Broens schrieb:
>> Yes, if we want to do it right, we need the XML prologue.
> 
> Why do we need it? Isn't it optional anymore? (I might be mistaken, so a
> current source on this would be great.)
XML prologue is required when the character encoding is other than the
default UTF-8 or UTF-16, which can be the case in the backend. However,
the exception handler only outputs UTF-8, but I'd rather stick to XML
prologue everywhere, like strongly recommended by the W3C.

W3C says about a XML 1.0 document prologue:
Definition: XML documents SHOULD begin with an XML declaration which
specifies the version of XML being used. [1]

Somehow the statement above doesn't fit the one following.

For strictly conforming documents in XHTML 1.1 W3C states:
An XML declaration like the one above is not required in all XML
documents. XHTML document authors are strongly encouraged to use XML
declarations in all their documents. Such a declaration is required when
the character encoding of the document is other than the default UTF-8
or UTF-16. [2]

Cheers

Patrick


[1] http://www.w3.org/TR/xml/#sec-prolog-dtd
[2] http://www.w3.org/TR/xhtml11/conformance.html

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkvG8mMACgkQNgvIvIQSN/wTQgCfce6VW/1lc270PyCX2VbAf2Jk
LJ4An0yEH9cGo8f51EfOg7lYjTjNpNE+
=D8Si
-----END PGP SIGNATURE-----


More information about the TYPO3-team-core mailing list