Re: +n- Flaw in IE


Java script Dude wrote:
> Have tried both:
>
> <META http-equiv="Content-Type" content="text/html;
> charset=western">
> <META http-equiv="Content-Type" content="text/html;
> charset=western/iso">
>
> ... without success.

Well, you may get more success by stop inventing your own encodings and
by using existing ones (I did):

Western Latin:
<meta http-equiv="Content-Type" content="text/html;
charset=iso-8859-1">

Central European:
<meta http-equiv="Content-Type" content="text/html;
charset=iso-8859-2">

UTF-8
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">

Korean for this matter:
<meta http-equiv="Content-Type" content="text/html; charset=euc-kr">

Otherwise this so-called "flaw" is just a proof that if you feed the
browser with wrong parameters (or do not feed *required* ones) then
it's rendering behavior may be randomized. This may be an interesting
game, but one can play it with any existing browser, so why to pick up
on IE exclusively? ;-)

Also kill me if I understand why this particular behavior should be a
*flaw*. The mode called *Auto-Detect*, not *Use System Default*. So
instead of simply using system default or iso-8859-1 like wannabes do,
IE indeed tries to *auto* *detect* the encoding of the crap you fed
into it. If not a single hint provided from server or http-equiv (or
http-equiv provides a non-existing encoding) then IE studies the body
text for hints.
+n- is a valid UTF-7 character so what is your claim? Should IE connect
to ICANN to check if this domain appertains to an Asia domain? Or
submit the text to an online translator to see if UTF-7 variant can be
translated into any existing language (if not then use what?)

Namely, what is your proposed algorithm for such case? "No matter what
it is not UTF-7"? And why not?

One should never depend on server headers and have used encoding
indicated on the page itself. HTTP, XML and even sorry a** XHTML have
all means for it.

.

Relevant Pages

  • Outlook 2007 and UTF-7
    ... We are having problems sending HTML mail from Outlook 2007 with UTF-7 ... back in UTF-7 and Outlook then tries to reply with the same encoding. ... Outlook to ignore the incoming format and always send in Western European. ...
    (microsoft.public.outlook)
  • Re: File Read Spanish characters
    ... > options for reading a text file. ... Encoding seems to be the culprit. ... BOM is just a nice side effect. ... > using UTF-7 if I only care about English and Spanish? ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Cant connect to port 25 from another system
    ... I'm told UTF-7 is a better choice for getting ... Unicode through mail. ... I didn't know there was an issue with 8-bit encoding! ... There is no issue with UTF-8. ...
    (Fedora)
  • Re: QUERY: "zu" + the indexing Japanese grammar question
    ... Possibly when you reply to a iso-2022-jp post the newsreader automagically picks the same encoding as the previous post and thus your success in following up to Ben. ... Where it says "us-ascii", in order for the Japanese to be displayed ...
    (sci.lang.japan)
  • Re: Printing Filenames with non-Ascii-Characters
    ... Except for the very implicit choice of 'ascii' as an encoding when ... pretty well guarantee a generous measure of success, ...
    (comp.lang.python)
Loading