From: Rudolf Polzer Date: 2003-01-29T07:23:36+09:00 Subject: Re: euc-jp coding of ruby talk web interface Scripsit ille aut illa Yohanes Santoso : > > > Since I haven't seen a web browser written in Ruby yet: why is that > > > a reason for the website to choose EUC-JP? > > BTW, ruby accepts UTF-8 strings. Which does every 8-bit clean language. > Its regex can also operate on UTF-8 > as well as it can on EUC-JP (since both are non-modal encodings). EUC-JP: I don't think it's a good idea if a hiragana "desu" matches a "nin/tou" kanji (I know, that's the most improbable example I could find... - I don't know the language, just the IME, kakasi and the EDICT). But I don't think such things are occuring often since you wouldn't use a single character in a RE match. But a Japanese might already be used to such a "weird" regex behaviour from other tools like grep, which might do the same. Or does grep handle character sets correctly and doesn't just apply regexes to byte arrays? I think the main problem with Ruby is that Kconv cannot convert between UTF-8 and the rest. -- Your password must be at least 18770 characters and cannot repeat any of your previous 30689 passwords. Please type a different password. Type a password that meets these requirements in both text boxes. [M$] (Fix: http://support.microsoft.com/support/kb/articles/q276/3/04.ASP)