From: Rudolf Polzer Date: 2003-01-29T00:01:19+09:00 Subject: Re: euc-jp coding of ruby talk web interface Scripsit ille aut illa Yohanes Santoso : > Rudolf Polzer writes: > > Is UTF-8 a superset of EUC-JP, > > UTF-8 is an encoding for the Unicode character set. EUC-JP is an > encoding for at least 4 character sets, "at least"... > of which all are subsets of > the Unicode character set. So, the character set representable by > UTF-8 is a superset of the character sets representable by EUC-JP. So why choose EUC-JP over UTF-8 then? > Conversion between a EUC-JP string to an equivalent UTF-8 string is a > beast as one has to use a conversion table. Is it different with EUC-JP vs. iso-2022-jp? Well, parsing escape sequences might be evil, too, but since there are only two of them... I imagine what the effect of a closed transmission while in Multi-byte mode is... Or are these just different encodings for the same character set and only the numbers are encoded differently? > The good thing is, I think > I've seen at least one ruby module that does such conversion, iconv, > which interfaces with the iconv*() functions found in modern unix. The > downside is, iconv may be a unix-only thingie. Since I haven't seen a web browser written in Ruby yet: why is that a reason for the website to choose EUC-JP? -- Nochn Hinweis: Ein Fragezeichen pro Satz reicht, mehr wirkt leicht albern. Und davor bitte kein Leerzeichen machen. Hab ich "Warum" geh�rt ? Hier hast du die Antwort. [Volker Gringmuth in de.newusers.questions]