On Mon, 13 Feb 2012 18:22:13 +0100, Ian Hickson <[email protected]> wrote:
Hm, that's an interesting point. Can we make a list of features that rely
on the character encoding and have the spec require an encoding if any of
those are used?
If the list is long or includes anything that it's unreasonable to expect
will not be used in most Web pages, then we should remove this particular
"hole" in the conformance criteria.
The list starts with <a> and the moment you do not use UTF-8 (or UTF-16,
but you really shouldn't) you can run into problems. I wonder how
controversial it is to just require UTF-8 and not accept anything else.
--
Anne van Kesteren
http://annevankesteren.nl/
