Re: lynx-dev 0x9A bug

[T.E.Dickey]

> What OS are you using? 
>  
> Are you *sure* that it is lynx that is removing the character? 
> Just echoing the file to the screen may not be enough to check - 
> since the byte may actually act as a control character. 

that's a possibility - if he's using the win32 version I would expect
problems (since it's a "binary" character).  But otherwise, it's
being redirected to a file - where he seems to have lost it.
  
> Does this happen only with 0x9A, or also with other characters in the 
> range 0x80..0x9F? 

0x9a (on vt220) is a request from the host for identification. (and since
it's not in any of the ISO-8859-* sets - it's a control character there -
perhaps it is the win32 version).
  
> With which screen handling library was lynx compiled? (curses/ncurses/ 
> slang?)  There could be some relevant code differences. 

yes (slang ignores ctype in some instances)
  
>  
>     Klaus 


-- 
Thomas E. Dickey
address@hidden
http://www.clark.net/pub/dickey