This is the
talk page for discussing improvements to the
Shift JIS article. This is not a forum for general discussion of the article's subject. |
Article policies
|
Find sources: Google ( books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL |
![]() | This article is rated C-class on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
can someone put this in english for the common man? —Preceding unsigned comment added by 75.108.224.182 ( talk) 05:22, 25 February 2008 (UTC)
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)
The article has an underscore in the title which appears nowhere else in the article. Is this correct or a typo? If it's correct, it should be used throughout. User:Fredhoysted 14:57 (UTC)
Why has Shift-JIS no code points for umlauts assigned? -- 84.61.71.163 15:25, 15 May 2006 (UTC)
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
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)
Hi, I wrote a large portion of this article (before I had a sign-in) and that is what I meant when I wrote it. Sadly I could not remember where I read it, but I've done some googling so I'll add a link that backs up what I said. —The preceding unsigned comment was added by Tim Band ( talk • contribs) 15:38, 7 May 2007 (UTC).
JIS X 0201:1997 (for the single-byte characters) and JIS X 0208:1997 (for the double byte characters)
What does :1997 mean? The linked articles don't yield a clue, and both state that the standards were set in 1969 and 1990(?). Were they revised in 1997? If so, why didn't they simply get a new four-digit number? Shinobu 16:16, 31 August 2007 (UTC)
So the ":1997"'s in the article are wrong and should go, right? Shinobu 05:32, 4 November 2007 (UTC)
The article says "the competing 8-bit format EUC-JP, which does not support halfwidth katakana" - but EUC does indeed have the halfwidth katakana (upper half of JIS-X-0201:1976) in G2 (i.e., as two-byte sequences 0x8E 0xA1 .. 0x8E 0xDF) Tacitus Prime 11:22, 11 September 2007 (UTC)
"it is recommended that Unicode be used instead" recommended by unicode.org, isn't it? Should be added then! —Preceding unsigned comment added by 84.56.91.141 ( talk) 01:06, 4 June 2009 (UTC)
The artice states some malfunctioning transformation formulas:
If you apply these formulars to some randome examples you will get e.g.:
It appears to be that you have to increase both, j1 and j2 by 32 (0x20) before doing this kind of calculation, witch will correct the first two example and the 1. Byte of the last one but will get E) instead of BE for the second byte of 鯣. Do you have an idea how to fix also this one? -- Sannaj ( talk) 14:55, 11 November 2012 (UTC)
I've looked at this for a while now, and I'm pretty sure that the formula for in the odd should have rather than . Isn't the purpose of that skip to avoid the non-printing DELETE character (code 127) in the second byte? As it stands it skips code 126 instead, which doesn't make sense. Uranographer ( talk) 19:33, 1 February 2013 (UTC)
On October 30 2011 user BIL added: https://en.wikipedia.org/?title=Shift_JIS&diff=458095114&oldid=455096120 "The same thing is valid for UTF-8 which is a world standard, better supported by software, and is predicted to fully replace Shift-JIS and EUC-JP." On December 8 2010 user 131.107.0.81 added: http://en.wikipedia.org/?title=Shift_JIS&diff=401316723&oldid=396679673 "... , conflicting with some code points. This is one reason why applications are recommended to use Unicode such as UTF-8 or UTF-16 instead." There was no explanation or citation. I added "By whom?" markers in May 2013. I'll be happy if someone cites some respected authority. Until then, these UTF-8 endorsements don't belong. I removed them. Peter Gulutzan ( talk) 02:09, 21 October 2013 (UTC)
The JIS X 0213 article links to Shift JIS-2004 but Shift JIS-2004 redirects here. It is *not* the same encoding and no information about Shift JIS-2004 is present on this page. 58.173.133.147 ( talk) 10:56, 20 May 2014 (UTC)
The lead bytes for the double byte characters are "shifted" around the 64 halfwidth katakana characters in the single-byte range 0xA1 to 0xDF.
Wut? Can someone explain this without the jargon? Maury Markowitz ( talk) 16:09, 23 September 2015 (UTC)
http://www.dozine.co.jp/duke/ displays this:
http://blasterhead.product.co.jp/ displays this:
What problem with JIS could cause that? Ranze ( talk) 07:58, 15 August 2016 (UTC)
I think there should be some sort of clarification that the ASCII company is unrelated to the ASCII character encoding scheme within the article. Possibly something like ASCII, unrelated to the encoding scheme, and then continue on with the article after the comma. 207.131.207.202 ( talk) 18:17, 26 June 2023 (UTC)
This is the
talk page for discussing improvements to the
Shift JIS article. This is not a forum for general discussion of the article's subject. |
Article policies
|
Find sources: Google ( books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL |
![]() | This article is rated C-class on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
can someone put this in english for the common man? —Preceding unsigned comment added by 75.108.224.182 ( talk) 05:22, 25 February 2008 (UTC)
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)
The article has an underscore in the title which appears nowhere else in the article. Is this correct or a typo? If it's correct, it should be used throughout. User:Fredhoysted 14:57 (UTC)
Why has Shift-JIS no code points for umlauts assigned? -- 84.61.71.163 15:25, 15 May 2006 (UTC)
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
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)
Hi, I wrote a large portion of this article (before I had a sign-in) and that is what I meant when I wrote it. Sadly I could not remember where I read it, but I've done some googling so I'll add a link that backs up what I said. —The preceding unsigned comment was added by Tim Band ( talk • contribs) 15:38, 7 May 2007 (UTC).
JIS X 0201:1997 (for the single-byte characters) and JIS X 0208:1997 (for the double byte characters)
What does :1997 mean? The linked articles don't yield a clue, and both state that the standards were set in 1969 and 1990(?). Were they revised in 1997? If so, why didn't they simply get a new four-digit number? Shinobu 16:16, 31 August 2007 (UTC)
So the ":1997"'s in the article are wrong and should go, right? Shinobu 05:32, 4 November 2007 (UTC)
The article says "the competing 8-bit format EUC-JP, which does not support halfwidth katakana" - but EUC does indeed have the halfwidth katakana (upper half of JIS-X-0201:1976) in G2 (i.e., as two-byte sequences 0x8E 0xA1 .. 0x8E 0xDF) Tacitus Prime 11:22, 11 September 2007 (UTC)
"it is recommended that Unicode be used instead" recommended by unicode.org, isn't it? Should be added then! —Preceding unsigned comment added by 84.56.91.141 ( talk) 01:06, 4 June 2009 (UTC)
The artice states some malfunctioning transformation formulas:
If you apply these formulars to some randome examples you will get e.g.:
It appears to be that you have to increase both, j1 and j2 by 32 (0x20) before doing this kind of calculation, witch will correct the first two example and the 1. Byte of the last one but will get E) instead of BE for the second byte of 鯣. Do you have an idea how to fix also this one? -- Sannaj ( talk) 14:55, 11 November 2012 (UTC)
I've looked at this for a while now, and I'm pretty sure that the formula for in the odd should have rather than . Isn't the purpose of that skip to avoid the non-printing DELETE character (code 127) in the second byte? As it stands it skips code 126 instead, which doesn't make sense. Uranographer ( talk) 19:33, 1 February 2013 (UTC)
On October 30 2011 user BIL added: https://en.wikipedia.org/?title=Shift_JIS&diff=458095114&oldid=455096120 "The same thing is valid for UTF-8 which is a world standard, better supported by software, and is predicted to fully replace Shift-JIS and EUC-JP." On December 8 2010 user 131.107.0.81 added: http://en.wikipedia.org/?title=Shift_JIS&diff=401316723&oldid=396679673 "... , conflicting with some code points. This is one reason why applications are recommended to use Unicode such as UTF-8 or UTF-16 instead." There was no explanation or citation. I added "By whom?" markers in May 2013. I'll be happy if someone cites some respected authority. Until then, these UTF-8 endorsements don't belong. I removed them. Peter Gulutzan ( talk) 02:09, 21 October 2013 (UTC)
The JIS X 0213 article links to Shift JIS-2004 but Shift JIS-2004 redirects here. It is *not* the same encoding and no information about Shift JIS-2004 is present on this page. 58.173.133.147 ( talk) 10:56, 20 May 2014 (UTC)
The lead bytes for the double byte characters are "shifted" around the 64 halfwidth katakana characters in the single-byte range 0xA1 to 0xDF.
Wut? Can someone explain this without the jargon? Maury Markowitz ( talk) 16:09, 23 September 2015 (UTC)
http://www.dozine.co.jp/duke/ displays this:
http://blasterhead.product.co.jp/ displays this:
What problem with JIS could cause that? Ranze ( talk) 07:58, 15 August 2016 (UTC)
I think there should be some sort of clarification that the ASCII company is unrelated to the ASCII character encoding scheme within the article. Possibly something like ASCII, unrelated to the encoding scheme, and then continue on with the article after the comma. 207.131.207.202 ( talk) 18:17, 26 June 2023 (UTC)