some users have reported problems with ksh93 vs UTF-8 locales
in particular garbage characters being emitted in ksh vi or emacs edit mode
to date the reports have been anecdotal
my (and dgk's) efforts to reproduce the problems have failed
possibly due to improper xterm/os/env setup on my part
I'd like to either capture ksh in the act or debunk the anecdotes
so that the integration sources can be finalized for this round
if anyone has seen this behavior with LC_ALL=en_US.UTF-8 and
a true UTF-8 terminal could you please trace/strace/truss
ksh reading the utf-8 chars in and then printing them out
e.g., capture the ksh93 process read/write syscalls (with
expanded buffer/size data) for a command like
echo ascii<utf-8-char-sequence>ascii
my guess is that the reported bad behavior is caused by invalid
UTF-8 character input (garbage in) and not a bug with ksh' multibyte
char processing -- provide a trace to prove me wrong
thanks
-- Glenn Fowler -- AT&T Research, Florham Park NJ --
