> Since you use already Unicode internally, this should be *very* easy to
> implement. Based on my experience as the person who added UTF-8 support
> to the Linux console driver two years ago, I would say adding UTF-8
> will require less than one hour of work.
>
Nothing is that easy :-)
> Feel free to use any of the UTF-8 code from linux/drivers/char/console.c
> in the Linux kernel distribution.
>
Thanks!
> From the rest of your mail I see that you have many missunderstandings
> about UTF-8. I hope I can claify a few things:
>
You have -- thanks. I'll do some reading before making any more noise in
this vein. And yet, from what you say, it sounds like there is still
evidently a gotcha, namely that one must choose in advance between two
different worlds: UTF-8 and ISO 2022 (e.g. Latin-1, etc, with C1 controls).
So if the host uses UTF-8 but I am using a VT320 (or emulator), or the host
uses ISO 2022 with C1 controls and my emulator is switched to UTF, there
will be trouble. But that's not so bad, since we must do this now anyway
prior to making connections to systems that don't use ISO 2022, or that use
PC code pages (etc) on the wire.
> See Appendix R.6 for the ISO 2022 ESC sequence for UTF-8.
>
Will do -- I didn't notice these coming in as new pages to the International
Register but maybe I missed it.
> If you have more questions about how UTF-8 is used under Unix, I'd be
> happy to assist. Plan9 and to some degree Linux are excellent test
> environments for the pure UTF-8 experience.
>
> Looking forward to UTF-8 support in Kermit ...
>
You've been very helpful, and hopefully we'll have it sooner thanks to your
pointers. Thanks again!
- Frank
This archive was generated by hypermail 2.1.2 : Tue Jul 10 2001 - 17:20:35 EDT