TK> I will agree with "luit"...
It's a little premature to speak about that, isn't it? Luit isn't
finished yet, and it will need some more design work before I'm happy
with the way it treats non-ISO 2022 encodings (currently their
structure is hard-wired).
I've already said that, but I really don't understand why you insist
on discussing these issues now, rather than waiting either until I've
written a rock-solid version of luit, or else decided such a task is
beyond my abilities.
Juliusz
-
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/linux-utf8/
- Emacs and nl_langinfo(CODESET) Markus Kuhn
- Re: Emacs and nl_langinfo(CODESET) Pablo Saratxaga
- Re: Emacs and nl_langinfo(CODESET) Markus Kuhn
- Re: Emacs and nl_langinfo(CODESET) Bruno Haible
- Re: Emacs and nl_langinfo(CODESET) Tomohiro KUBOTA
- Re: Emacs and nl_langinfo(CODESET) Tomohiro KUBOTA
- Re: Emacs and nl_langinfo(CODESET) Juliusz Chroboczek
- Re: Emacs and nl_langinfo(CODESET) Tomohiro KUBOTA
- Re: Emacs and nl_langinfo(CODESET) Juliusz Chroboczek
- Re: Emacs and nl_langinfo(CODESET) Tomohiro KUBOTA
- Re: Emacs and nl_langinfo(CODESET) Markus Kuhn
- Re: Emacs and nl_langinfo(CODESET) Markus Kuhn
- Re: Emacs and nl_langinfo(CODESET) Tomohiro KUBOTA
- Re: Emacs and nl_langinfo(CODESET) Tomohiro KUBOTA
- Re: Emacs and nl_langinfo(CODESET) Tomohiro KUBOTA
- Re: Emacs and nl_langinfo(CODESET) Bruno Haible
