Re: Should the UTF-8 BOM trump overriding via HTTP or by users?

* Leif Halvard Silli wrote:
>Subject: Should the UTF-8 BOM trump overriding via HTTP or by users?

Higher-level information overrides lower-level information, explicit
information overrides fallbacks, and user agents should do what their
users want them to do. So, HTTP-level Content-Type overrides document-
internal information, a BOM overrides user-chosen fallbacks, and user-
chosen overrides trump anything else.

If you want X and your "agent" does Y against your wishes, then it's
not really an agent acting on your behalf, I don't think that point
merits any discussion at all. Similarily, for fallbacks, there is no
other way this could work due to the semantics of "fallback".

That leaves the BOM versus Content-Type. If you let the BOM override
the Content-Type header, it would be impossible to send content that
starts with something that looks like a BOM but really isn't over the
protocol. "Content-Type overrides BOM" is a "If X then Y" situation.

The other way around you get "If X then Y except when also A, then B,
ohh, and not X but Z then C, and..." as you've made the process de-
pendant on the internet media type.

Anyone who wants the BOM to take precedence over the HTTP Content-Type
header, or the charset parameter within it, is welcome to make an I-D
to that effect that updates RFC 2616 and RFC 4288 and possibly others.
Trying to sneak in such changes through backdoors is unacceptable. So,
if "HTML5" has rules as you suggest, that is most likely an error.
Björn Höhrmann · ·
Am Badedeich 7 · Telefon: +49(0)160/4415681 ·
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · 

Received on Tuesday, 7 June 2011 04:40:01 UTC