W3C

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

Quick access to

Previous: LC-1464 Next: LC-1465

Comment LC-1466
:
Commenter: Dan Connolly <connolly@w3.org>

or
Resolution status:

I see:

"If the request response does specify a character encoding but it is not
"UTF-8", FAIL"
-- http://www.w3.org/TR/mobileOK/#id4485785

How about US-ASCII? especially since you can treat US-ASCII
as UTF-8 and preserve the meaning of the bytes.

It's perhaps not worthwhile to complicate things, if very
few documents are labelled US-ASCII.

p.s. I wonder if it's acceptable to limit encodings to UTF-8
and exclude UTF-16; it wasn't when XML was ratified.
But I'll leave it to those who have 1st-hand experience
with the need for UTF-16 to comment on that.

p.p.s. The fragid #id4485785 seems fragile. If you're
going to break it, break it only once, for the next draft.
At that point, change it to something like #char-encoding-support
and keep it that way for future revisions.
(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: 1466.html,v 1.1 2017/08/11 06:44:05 dom Exp $
Please send bug reports and request for enhancements to w3t-sys.org