On Mon, 14 May 2001, Markus Kuhn wrote:
> Bruno Haible wrote on 2001-05-14 16:52 UTC:
> > Juliusz Chroboczek writes:
> > > a filter between a tty and a pty that intercepts ISO 2022 sequences
>
> Why not use GNU screen for that purpose?
_Currently_, screen wouldn't be able to cope. I've used it to translate
the ISO646 regional codes to Latin1 before (and that worked well) but
the UTF-8 translation facilities seem to be able to cope with only
Latin1 as the eight bit set for now (it needs more translation tables).
But Michael is open to patches and the like.
However there is a serious problem:
How is screen supposed to tell the terminal what width the characters
should be. The client program _will_ be expecting wide cyrillic
when using DBCS and we currently have _no_ way of forwarding this
information to the display.
I think I'll be adding a feature to 'PuTTY's unicode support so that any
character that's followed by a U+303f will be wide even if it isn't when
you use the normal wcwidth table.
PS: Is that character a reasonable choice or should I use U+F200 ?
--
Rob. (Robert de Bath <rdebath @ poboxes.com>)
<http://www.cix.co.uk/~mayday>
-
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/lists/
