Talk:Extended Unix Code

From Wikipedia, the free encyclopedia
Jump to: navigation, search
WikiProject Korea (Rated Start-class)
WikiProject icon This article is within the scope of WikiProject Korea, a collaborative effort to build and improve articles related to Korea. All interested editors are invited to join the project and contribute to the discussion.
Start-Class article Start  This article has been rated as Start-Class on the project's quality scale.
 ???  This article has not yet received a rating on the project's importance scale.

which of the codes specified in ISO-2022-JP is byteshifted in EUC-JP? Plugwash 22:11, 15 Dec 2004 (UTC)

Move to Extended Unix coding?

I disagree with the move - it appears that it is capitalised in most references. violet/riga (t) 19:31, 18 July 2005 (UTC)


Can anyone give a reference to the name "Extended Unix Coding"? I have never heard of such a name; I have only heard of EUC being referring to "Extended Unix Code".

"Extended Unix Code" is also the form used by IBM, HP, SCO, Sun, etc. (as any quick Google search can confirm)—Wing 21:58, 28 September 2005 (UTC)

Since no one has replied, I have moved the page. For reference (especially since I gave a very detailed reason that got truncated because it is too long), I am reproducing my reason for the move below:
  • As far as I know (since the early 90's), EUC does not stand for "Extended Unix Coding" but rather "Extended Unix Code". If I google "Extended Unix Coding" and remove all the results that are copies of Wikipedia, only SCO and Apple are major Unix vendors who use "Extended Unix Coding", and SCO only uses it in the context "Extended Unix Coding Supplement" [which grammatically can mean: the supplement which supports the act of using "extended unix code"] and it also uses the spelling "Extended Unix Code" in other places. Apple is a new player (despite its NeXT lineage). This is in stark contrast with vendors using the spelling "Extended Unix Code" which include IBM, Sun, even SCO (outside the "Extended Unix Coding Supplement" context) and even Microsoft.
  • Additional support for the move is that, when you google “"extended unix" euc” and restrict by "site:" to domains,,,,,, or (i.e., all government and university sites in regions actually using this encoding system), one finds overwhelming use of the use of the spelling "extended unix code".
  • I therefore firmly believe that the spelling "Extended Unix Coding", as main entry, is wrong and should be corrected.
PS:It is worth noting that ja:EUC (Wikipedians who actually use the EUC coding system) uses the spelling "Extended Unix Code" and not "Extended Unix Coding".
Wing 04:48, 6 October 2005 (UTC)

"EUC-CN is a form of GB18030" and character set vs. encoding confusion[edit]

This is stated in the EUC-CN section, which seems quite wrong, though I'd like someone to confirm this - EUC-CN is a character encoding that encodes the GB18030 character set. Unfortunately the character set link redirects to the character encoding, which may explain the confusion.

Quite a few Wikipedia pages in this area appear to be confused (and confusing), although some of the Unicode pages are better on distinction between character set, character encoding and character repertoire.

Also, why is this page using the Korean template when it's not just about Korean encodings?


I agree - GB18030 is actually a Unicode Transformation Format (UTF), i.e. a Unicode encoding, and I've never heard of anyone using EUC-CN as an encoding of GB18030. This may well happen in some cases, but it can't be correct to say this is common, so will make edit to state it is not so common.

Richard Donkin 06:33, 30 September 2006 (UTC)

the encoding[edit]

"In Japan, the encoding is heavily used by Unix or Unix-like operating systems, but seldom used elsewhere. It is consequently the least-used of the big 3 Japanese encodings, behind both ISO-2022-JP (JIS) and Shift-JIS.":

Don't say "it" and "the". Use proper nouns. My screen is too small to figure out what you are referring to.

Ambiguous description of EUC-KR[edit]

> KS X 1003 (formerly KS C 5636)/ISO 646:KR/US-ASCII.

The encoding KS X 1003 is indeed also known as ISO 646-KR, but this encoding is not US-ASCII. US-ASCII has a backslash character in it, whereas KS X 1003 has the won sign (₩) in its place.

Which encoding is it supposed to be? (talk) 12:17, 29 April 2014 (UTC)