Re: +n- Flaw in IE

Java script Dude wrote:
> I would propose that IE read the http-equiv meta tag in the body before
> trying to figure out by itself what the encoding is by parsing the page
> contents.

So it does! But if http-equiv Content-Type points to a non-existing
encoding like "Western" instead of the proper "iso-8859-1" then it's
still left alone with the crap to analize at the best of its
capabilities. And no one (AFAIK) claimed yet IE as a text recognizion
software.

> As I mentioned before, there are cases where there will be no
> http-header such as when the file is served up from the local file
> system. In these cases, there is the just the file header so the only
> way to avoid this flaw in IE in these cases is to ensure that the files
> are hard encoded in an encoding other that ASCII.

Do not mix a God's gift with an omlet as my father used to say :-)
It is not your preoccupation where your HTML/XHTML/XML file may appear
(it may appear in N places). But it is *your* preoccupation to make
sure that any place interested in your file's Content-Type could get a
clear and prompt answer from within the file. Content-Type and XML
equivalent give you such mechanics so please use it.

> BTW - I have tried <meta http-equiv="Content-Type" content="text/html;
> charset=iso-8859-1"> as well and on an ASCII file, IE still tries to
> auto-detect utf-7.

Re-install your IE.
Received on Tue Jan 17 17:14:16 2006