[EMAIL PROTECTED] writes:
> maybe i have lost the context, but anyway:
> don't forget ISO-2022-JP, ISO-2022-JP-2, SJIS, and X11 ctext.
> we have real unix LC_CTYPE implementation for these
On Linux, we don't support ISO-2022-JP, ISO-2022-JP-2 and X11 ctext
locales because these encodings are stateful [which means that it's
easy to get your terminal emulator screwed up] and not filesystem safe
[which means some Japanese characters are considered to be directory
slashes by the filesystem, although they aren't].
On Linux, we also don't support SJIS locales, because EUC-JP and UTF-8
locales are sufficient and don't have the weird "Yen/backslash
problem".
Of course you are free to implement these in *BSD. Noone will hinder
you. For practical purposes, being able to view ISO-2022-JP files
through implicit conversion to EUC-JP or UTF-8 in the terminal
emulator (which is what 'luit' does for Japanese or 'yyt' for Chinese)
is probably good enough.
Bruno
-
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/linux-utf8/
