Basic Reading Material and Vocabulary

[Harisenbon]

So the browser probably tried to honor the content type provided and that ended up breaking things. Perhaps we could say that if an invalid content type is given, perhaps the browser should try sniffing the content type from the page (which is in EUC-JP itself).

I believe that Firefox, IE and most other browsers do try to sniff out the content type from the byte order of the document, but in my experience EUC-JP is for some reason incredibly difficult to detect through bite-order.

Some sites I've seen (and have even made for testing) without a set content type will start rendering in one Encoding, and then switch halfway through as soon as the browser finds a byte-code that doesn't match the originally assumed encoding.

It's kind of interesting to watch a page turn from complete 文字化け to EUC-JP during load.

[phreadom]

I see that the pages were actually created with MS Word 97 and 98.

Anyway... it appears that in FireFox if I set "Auto Detect" to "Universal" the pages work fine. If I set "Auto Detect" to "Off", it goes back to being broken. So I suppose if you set it to universal auto detect maybe it works fine for such pages? Maybe it's just turned off by default? It would be interesting to know.

[Yudan Taiteki]

I basically never have a problem with Auto-Detect->Universal.

[Infidel]

Enough thread hijacking.

Your thread hijack prevention method turned into an even bigger hijack

[phreadom]

Enough thread hijacking.

Your thread hijack prevention method turned into an even bigger hijack

Well at least we learned something valuable. Turn on your Universal Auto Detect!

[furrykef]

Next we'll talk about how XHTML is evil and everybody should use HTML... or is it the other way around?