Edit comment LC-1707 for Mobile Web Best Practices Working Group

Quick access to

Previous: LC-1713 Next: LC-1710

Comment LC-1707
Commenter: Henri Sivonen <hsivonen@iki.fi>

Resolution status:

> If the HTTP Content-Type header does not specify a character
> encoding:
> If there is no XML declaration, or UTF-8 character encoding is not
> specified in the XML declaration, FAIL

XML provides an unambiguous default. Is there a practical reason, due
to broken real-world UAs perhaps, not to PASS defaulted UTF-8?
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

Developed and maintained by Dominique Hazaël-Massieux (dom@w3.org).
$Id: 1707.html,v 1.1 2017/08/11 06:43:39 dom Exp $
Please send bug reports and request for enhancements to w3t-sys.org