[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Encoding Standard (mostly complete)

To: Shawn Steele <Shawn.Steele@microsoft.com>
Subject: Re: Encoding Standard (mostly complete)
From: Masatoshi Kimura <VYV03354@nifty.ne.jp>
Date: Sun, 22 Apr 2012 00:22:08 +0900
Authentication-results: mauve.mrochek.com; dkim=pass (1024-bit key)header.i=@nifty.ne.jp; x-dkim-adsp=none
Cc: Anne van Kesteren <annevk@opera.com>,ietf-charsets <ietf-charsets@iana.org>, Doug Ewell <doug@ewellic.org>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nifty.ne.jp;s=mar2011msa; t=1335021733; bh=woc4/CxLPxfpF9SZe7SzteSdcSLyd3JPrEJJxxbWPj4=;h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding;b=ie2YqvAoueD8i8CfcASOW2TW/4hOgEftxCijFAN8S0c3qWJAcEIzJ17Q1K3g351J7vC52dyHf79qJ6kW7+VNtyGJt3gLulr0heGwEFtMaU+1yTdKrrsoCRVv6b4U1CSZPv15a9bKYXFlNvZliISLNRhon1jHMpcUr4YdZOE1XTs=
In-reply-to: <E14011F8737B524BB564B05FF748464A618A25F1@TK5EX14MBXC139.redmond.corp.microsoft.com>
List-Id: <ietf-charsets.mail.apps.ietf.org>
List-Owner: <mailto:ietf-charsets-owner@mail.apps.ietf.org>
List-Subscribe: <mailto:mailserv@mail.apps.ietf.org?subject=subscribe%20ietf-charsets>
List-Unsubscribe: <mailto:mailserv@mail.apps.ietf.org?subject=unsubscribe%20ietf-charsets>
Original-recipient: rfc822;ned+ietf-charsets@mrochek.com
References: <20120417112034.665a7a7059d7ee80bb4d670165c8327d.c18ae3d34d.wbe@email03.secureserver.net><op.wcx7ipih64w2qv@annevk-macbookpro.local><E14011F8737B524BB564B05FF748464A6189E908@TK5EX14MBXC139.redmond.corp.microsoft.com><op.wcz5wpsh64w2qv@annevk-macbookpro.local><E14011F8737B524BB564B05FF748464A618A25F1@TK5EX14MBXC139.redmond.corp.microsoft.com>
Spam-test: False ; 1.0 / 4.5 ; SPF_SOFTFAIL
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; ja; rv:1.8.0.8)Gecko/20061025 Thunderbird/1.5.0.8 Mnenhy/0.7.4.0

> Our implementation of encodings WILL NOT change.  Ever.
Actually MS11-057 changed the IE decoder [1].

> However, there are millions of our customers that depend on our
> current behavior.  If that behavior changes even slightly, then
> that will "corrupt" their data.
Indeed, MS10-090 broke some ISO-2022-JP encoded Web pages [2]. Please
make your action consitent with your words.

> Use Unicode.
Even if we ignored non-Unicode encodings, we will need a documentation
about UTF-16 anyway due to IE quirks (BOM overrides everything, default
endian is little-endian contrary to the Unicode Standard, etc).
Otherwise other browser implementors will have to (and did)
reverse-engineer to develop a competing browser. Obviously TUS is
useless about IE quirks.

[1] https://bugzilla.mozilla.org/show_bug.cgi?id=690225#c14
[2] http://support.microsoft.com/?kbid=2467659

Follow-Ups:
- Re: Encoding Standard (mostly complete)
  - From: Doug Ewell <doug@ewellic.org>

References:
- RE: Encoding Standard (mostly complete)
  - From: Doug Ewell <doug@ewellic.org>
- Re: Encoding Standard (mostly complete)
  - From: Anne van Kesteren <annevk@opera.com>
- RE: Encoding Standard (mostly complete)
  - From: Shawn Steele <Shawn.Steele@microsoft.com>
- Re: Encoding Standard (mostly complete)
  - From: Anne van Kesteren <annevk@opera.com>
- RE: Encoding Standard (mostly complete)
  - From: Shawn Steele <Shawn.Steele@microsoft.com>

Prev by Date: RE: Encoding Standard (mostly complete)
Next by Date: Re: Encoding Standard (mostly complete)
Prev by thread: RE: Encoding Standard (mostly complete)
Next by thread: Re: Encoding Standard (mostly complete)
Index(es):
- Date
- Thread