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

Windows Code Pages 932, 936, 949 and 950

To: ietf-charsets@iana.org
Subject: Windows Code Pages 932, 936, 949 and 950
From: Erik van der Poel <erikv@google.com>
Date: Thu, 02 Nov 2006 21:53:24 -0800
Cc: mikeksar@microsoft.com
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns;h=received:message-id:date:from:to:subject:cc:mime-version:content-type:content-transfer-encoding:content-disposition;b=S/xW1+wWeeK9faf/PBhj0/9Vqbod9KIMmYLauqJNRccag+D2tYinvxvQuja+z/JeJHvIfPL4a9KzSFHE8cynow==
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>
Message-hash: 162DDE8A28E677F43F5CE8194F9F9DCC
Original-recipient: rfc822;ned+ietf-charsets@mrochek.com
Spam-test: False ; -0.1 / 4.5 ; RCVD_IN_BSP_OTHER

It turns out that MSIE does not support the following charset names:

windows-932
windows-936
windows-949
windows-950

Of course, MSIE does support those code pages, but the most commonly
used names for those code pages in MSIE are shift_jis, gb2312, euc-kr
and big5, respectively.

If we are emphatic about cp1252 not being an alias for windows-1252
for interoperability reasons, then for the same reasons, we should not
register windows-932, windows-936, windows-949 and windows-950.

(Windows-874 is supported by MSIE, so it will probably be OK to
register this one.)

Erik

Follow-Ups:
- Re: Windows Code Pages 932, 936, 949 and 950
  - From: Erik van der Poel <erikv@google.com>

Prev by Date: RE: GSM 03.38 substitution character?
Next by Date: Re: Windows Code Pages 932, 936, 949 and 950
Prev by thread: Re: Update of windows 1252
Next by thread: Re: Windows Code Pages 932, 936, 949 and 950
Index(es):
- Date
- Thread