RE: shift_jis / windows-31J

[Shawn Steele <Shawn.Steele@microsoft.com>]

Well, that saves me looking at the MLang source :).  But whichever name you used to get the encoding/code page, we'd still call 932 "shift_jis" when you asked for the web name, so your asp.net server would say a page was shift_jis.  W3C is getting around that with the variations for HTML5, but that doesn't help other applications, MIME, random documents, etc. :(

-Shawn

-----Original Message-----
From: Bjoern Hoehrmann [mailto:derhoermi@gmx.net] 
Sent: Thursday, November 11, 2010 11:14 AM
To: Shawn Steele
Cc: ietf-charsets@iana.org
Subject: Re: shift_jis / windows-31J

* Shawn Steele wrote:
>Then I'll get "shift_jis" as the encoding name.  (WebName's effectively 
>as close as .Net gets to the IANA charset names.)  That cannot change 
>without breaking tons of stuff.  C# does happen to recognize 
>csWindows-31J, but the next line will throw an exception.  I'd have to 
>dig more to see if MLang recognized the csWindows-31J, but that 
>wouldn't really solve the problem.

http://lists.w3.org/Archives/Public/www-archive/2008Jun/0155.html

  ...
  | 932      | csShiftJIS                                    |
  | 932      | csWindows31J                                  |
  | 932      | ms_Kanji                                      |
  | 932      | shift-jis                                     |
  | 932      | shift_jis                                     |
  | 932      | sjis                                          |
  | 932      | x-ms-cp932                                    |
  | 932      | x-sjis                                        |
  ...
--
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/