Talk:Shift JIS
From Wikipedia, the free encyclopedia
Contents |
[edit] Typo?
developed by a Japanese company called ASCII
Sounds like a typo, but I don't know if it is. First google page doesn't seem show anything. JamesBrownJr 22:17, 4 May 2006 (UTC)
- It's not: the company is for real. Jpatokal 02:03, 5 May 2006 (UTC)
- Ken Lunde states on page 175 of his authoritative book "CJKV Information Processing", O'Reilly & Associates, 1999, ISBN 1565922247, that shift-JIS was "originally developed by Microsoft Corporation". Later on page 176 he makes a reference to the ASCII Corporation's version of Japanese TEX as one of four examples of computer platforms or environments that uses shift-jis internally.
- Lunde at least does not seem to be crediting the ASCII Corporation with having invented shift-jis. Morten Johnsen 23:51, 25 June 2006 (UTC)
[edit] Umlauts
Why has Shift-JIS no code points for umlauts assigned? --84.61.71.163 15:25, 15 May 2006 (UTC)
- Japanese typers rarely have a need to type the words "Mötley Crüe". You could use ISO-2022-JP-2, which has a mechanism to switch to ISO-8859-1 (includes umlauts), but you might as well just use UTF-8. --150.216.151.171 17:59, 9 July 2006 (UTC)
[edit] Upper and Lower ASCII
This page uses the term "upper ASCII" and "lower ASCII". I believe that the writer meant "characters > 127" and "characters <= 127" in a fixed-width 8-bit encoding. But ASCII only defines 127 characters. There is no "upper ASCII".
http://www.xslt.com/html/xsl-list/2002-02/msg00248.html
[edit] Browser interpretation of 0x5C
At least Firefox interprets 0x5C in Shift_JIS as '\' and not '¥'. I suspect this is because the '\' character is used to escape characters in Javascript, so having an encoding without a representation of that character would be a security problem. JeffreyYasskin 21:20, 19 December 2006 (UTC)
