Hello,
Available, as usual, in the directory
ftp://ftp.dcs.ed.ac.uk/pub/jec/programs/
For now, the filename is luit-0.5.tar.gz, but don't count on it
staying this way.
I've made terminal input go through the ISO 2022 state. It is not
clear that this is the right thing: a real VT100 appears to take all
terminal input through G0. Should terminal input go through (G0,G2)
instead of (GL, GR)? In addition, is terminal input allowed to
generate single shifts, as I currently do?
I've also implemented 128-byte charsets, for KOI8-R. When selected in
GL, these behave like 96-byte charsets. When in GR, or selected by
single-shifts, they cover the contingent control range. With this
design, C0 is always at the right spot, except possibly immediately
after a single shift.
I would be very grateful if people could try compiling it on their
system, and telling me why it breaks. In particular, I do not have
access to old BSD systems, old SV (pre-R4), or to the Hurd.
Main news:
- Multibyte encodings now really, really work;
- terminal input now really, really works;
- support for 128 byte encodings (such as KOI8-R or CP-1252) and
128x128 encodings;
- major code cleanup;
- portable across Linux, BSD and SVR4 (tested on Linux, FreeBSD,
OpenBSD and Solaris 2.5).
To do:
- Support for Big5, UTF-8 and The New GBK On The Block;
- user-customisation of encodings;
- locale sensitivity;
- more portability.
Juliusz
-
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/linux-utf8/
