Markus Kuhn wrote: > "JOE is a fairly popular editor which comes with many Linux > distributions -- it is similar to WordStar and Borland Turbo-C IDE, > but has not been UTF-8 compliant until today's release: JOE 3.0. > > JOE will edit both UTF-8 and non-UTF-8 files on UTF-8 and non-UTF-8 > terminals (hit ^T U for translation when file doesn't match > terminal)." > > http://sourceforge.net/projects/joe-editor
I tried it, with xterm -u8 -fn '-efont-fixed-medium-r-*-*-16-*-*-*-*-*-iso10646-*' and it is very nice. The cursor does not lose its way any more. You can not only paste utf-8 into joe, but also copy from it now. One of the first files I tried it on was the utf-8 Compose file (/usr/X11R6/lib/X11/locale/en_US.UTF-8/Compose). BTW, it seems that this file has spent part of its life in UCS-2 form. Towards the end of the file some characters which should be 1D15F, 1D161, etc., are in reality D15F, D161, etc. (wich happen to be Korean characters). I was looking at the Compose file because I am trying to understand keyboard input. My keyboard is set for us_intl, with a lot of "dead keys". All of the combinations (I think) in the Compose file, including some very complicated ones, work in joe (on an xterm with Unicode font) and in Openoffice. However, in other programs (like Mozilla, bluefish, the input window of gucharmap) only a small subset of the combinations work. For instance, o with macron (AltGr-minus-o) works in all programs, while o with breve (AltGr-left parenthesis-o) works only in joe and Openoffice. In other programs you hear a beep, and no character appears. Why do the programs behave differently with respect to keyboard input? Is there a "cure"? Regards, Jan (very happy with the new joe). Trying to understand utf-8: www.jw-stumpel.nl/stestu.html -- Linux-UTF8: i18n of Linux on all levels Archive: http://mail.nl.linux.org/linux-utf8/
