> | I am surprised by the "must only be used". It seems I am not > | conforming by including a meta statement in the utf-16 HTML page. I > | should either remove the statement or encode the HTML up to and > | including that statement as ascii. I'll check on this. > > It doesn't make much sense to have the meta statement there, as I > would expect most browser to assume ASCII compatibility, but I agree > that "must only be used" sounds too harsh. > > [...] > > it struck us: "if we can see that the page claims to be UTF-16, it > can't be, because our meta declaration scanning assumes ASCII > compatibility".
I think you just answered why the spec says "must only be used" :) it is so that the parsing of the meta tag can happen with predictability. YA
