[Michael Schroeder (Re: Backspace problem in Xterm/rxvt) writes:]
>> On Mon, Aug 06, 2001 at 09:46:48PM +1000, Jim Breen wrote:
>> > [Markus Kuhn (Re: Backspace problem in Xterm/rxvt) writes:]
>> > [snip]
>> > >> Various Japanese users told us however that they strongly prefer that
>> > >> Backspace moves always one character cell, not one character. The rational
>> > >> given was only that this is how existing EUC terminal emulators such as
>> > >> kterm have worked for years and that they got used to that. I'm not
>> > >> entirely convinced yet, but didn't make a big fuzz about it so far,
>> > >> because we need more some stability, otherwise the developers of proper
>> > >> editors will become annoyed.
>> >
>> > I find that amazing. I have used kterm for about 10 years with editors
>> > like jvim and jstevie, not to mention non-Unix editors like Word, etc.
>> > with Japanese. In all cases backspace erases the *whole* character; not
>> > just half it.
>>
>> Backspace doesn't delete characters in kterm, it just moves the
>> cursor one position to the left. Delete (i.e. 0177) is just ignored.
>>
>> It's the job of the terminal driver (or the application, if "raw"
>> mode is used) to erase characters if the user presses the backspace
>> key. This is normally done by sending <BACKSPACE><SPACE><BACKSPACE>.
A bit of testing demonstrated that Michael's description is correct.
What I have been observing was being carried out at the application
level, and not within kterm.
kterm's long-term practice notwithstanding, a BS should backspace over a
whole character, and not fragment of one.
Jim
--
Jim Breen [[EMAIL PROTECTED] http://www.csse.monash.edu.au/~jwb/]
Computer Science & Software Engineering, Tel: +61 3 9905 3298
P.O Box 26, Monash University, Fax: +61 3 9905 5146
Clayton VIC 3800, Australia $B%8%`!&%V%j!<%s(B@$B%b%J%7%eBg3X(B
-
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/linux-utf8/
