From: gotoken@... (GOTO Kentaro) Date: 2000-01-04T06:49:53+09:00 Subject: [ruby-talk:01043] Re: Is this a bug? Hi, In message "[ruby-talk:01037] Re: Is this a bug?" on 00/01/04, Yukihiro Matsumoto writes: >Oh, and could you tell me any idea about treating iso-8859-1 >characters in single byte mode (with -Kn)? You can look all iso-8859-1 characters at http://users.hit.net/~bobbau/platforms/specialchars/ 0xc0..0xff are used as non ascii alphabet except 0xd7 (division sign) and 0xf7 (times sign). Maybe, we should consider existence of other character sets in ISO8859 family at this occasion. All of them are 1byte coding sistems and extend ascii code to the range 0x10..0xff only. Here I summarized http://www.terena.nl/projects/multiling/ml-docs/iso-8859.html ISO# ** Alias Languages 8859-1 [4/1] Latin1 Western Europe and Americas 8859-2 [4/2] Latin2 Latin-written Slavic and Central European languages 8859-3 [4/3] Latin3 Esperanto, Galician, Maltese, and Turkish 8859-4 [4/4] Latin4 Scandinavia/Baltic 8859-5 [4/12] Cyrillic 8859-6 [4/7] Arabic 8859-7 [4/6] Greek 8859-8 [4/8] Hebrew Non-accented Hebrew 8859-9 [4/13] Latin5 Same as 8859-1 except for Turkish instead of Icelandic 8859-10 [5/6] Latin6 Lappish/Nordic/Eskimo languages ** [4/1] (== [0x41]) stands for a termination character in iso-2022. All images of each extended part of them are available too: http://www.terena.nl/projects/multiling/ml-docs/iso-8859.html If you are going to support these character sets, I propose a command line option -C instead of -K, and -C8 (8 for 8bit) use to ISO 8859. -- gotoken