Multibyte locale vs. terminal 8bit mode / was: Re: [ksh93-integration-discuss] Small question about enabling the"multiline" mode...

[Roland Mainz]

"I. Szczesniak" wrote:
> On 8/30/06, James Carlson <james.d.carlson at sun.com> wrote:
> > Roland Mainz writes:
> > > > The multiline option only works for terminals for which \E[A causes
> > > > the cursor to move up one line.  I suspect that this is not the case
> > > > for the terminal in your example.
> > >
> > > AFAIK all the terminal emulators shipped with Solaris (e.g. "dtterm",
> > > "xterm", "gnome-terminal" and "konsole"), the native Solaris console on
> > > SPARC and the Solaris/x86 console support that sequence (AFAIK it is
> >
> > Not if you switch to Tek mode.  ;-}
> >
> > > from vt100 or earlier (vt52 ?!)).
> >
> > No, not VT52.  That was pre-ANSI and used "ESC A" for the cursor-up
> > command.  The VT100 and up used ANSI sequences, which include "CSI A"
> > for cursor-up.  CSI can be rendered in 8-bit mode as hex 9B, or as
> > "ESC [" in 7-bit mode.
> 
> I assume ksh93 could only use the 7-bit mode - the 8-bit mode would be
> incompatible with multibyte output.

AFAIK there is at least one decade between the release of vt100 and the
first appearance of any multibyte locale (Ienup may correct me). AFAIK
all of the multibyte locales (or most of them) use ASCII as basis,
making them more or less backwards-compatible to ASCII-capable
terminals, but the 8bit terminal modes are AFAIK not compatible with the
multibyte locales which use the upper bit in bytes for special
purposes... (again Ienup may be able to explain that better than I can
do... and maybe he can explain for what the "stty defeucw" stuff is used
for, too).

----

Bye,
Roland

-- 
  __ .  . __
 (o.\ \/ /.o) roland.mainz at nrubsig.org
  \__\/\/__/  MPEG specialist, C&&JAVA&&Sun&&Unix programmer
  /O /==\ O\  TEL +49 641 7950090
 (;O/ \/ \O;)