Re: LYNX-DEV minor display problem (?character 0xA2?)

[T.E.Dickey]

> 
> 
> Klaus Weide wrote:
> 
> > > not occur when using "wy60".  Lynx set up for IBM PC character set, raw
> >                                                 ^^^^^^^^^^^^^^^^^^^^
> > > translated to 0x9b on output.  The SCO ANSI console takes 0x9b as CSI,
> >                                      ^^^^^^^^^^^^^^^^
> > > Control Sequence Initiator, same as ESC [.  This is pretty standard
> > > behavior for ANSI terminals of various sorts.  
if it's ANSI, half of the characters in the range 0x80 to 0x9f are
reserved for control purposes, and will not print.  I just counted 16
non-printing codes.

> Yet other reports indicate that the Linux console behaves similarly; a
> significant part of Lynx's audience is affected by this problem.
depends on the code set that is loaded (and the version of the kernel ;-).

> I think all other chars in the 0x80..0x9f range can be displayed
> directly.  Also, IBM PC chars in the range 0x01..0x1f can be displayed
> with the "ESC [ = <decimal> g" sequence.  This might be useful...
> 
> >Bela<
> ;
> ; To UNSUBSCRIBE:  Send a mail message to address@hidden
> ;                  with "unsubscribe lynx-dev" (without the
> ;                  quotation marks) on a line by itself.
> ;
> 


-- 
Thomas E. Dickey
address@hidden
http://www.clark.net/pub/dickey
;
; To UNSUBSCRIBE:  Send a mail message to address@hidden
;                  with "unsubscribe lynx-dev" (without the
;                  quotation marks) on a line by itself.
;