Hello,
Recently i had posted about problems with the xfree xterm:
> From: Sven Mascheck <mascheck@sun31.faw.uni-ulm.de>
> Subject: escape characters -> locale, isprint()
> Date: Thu, 17 Feb 2000 21:14:43 +0100
The problem is still present in 0.1.8:
There are websites using (unprintable) special characters (eg '0x96')
to 'feature' microsoft browsers. At least in the western configuration
(the only one i know), w3m doesn't check if characters are printable,
thus they confuse particularly the /xfree/ xterm (knowing more special
characters than other xterms). BTW, this xterm is also used on other
Unix platforms (than *BSD and Linux) as it is better than the MIT version.
Text after '0x96' looks like 'burnt in' after scrolling/refreshing.
See also a sample page to provoke the effect:
<URL:http://www.uni-ulm.de/~s_smasch/w3m/special_chars.html>
I guess it will only work with western w3m and certainly needs
using said xterm.
Something like the attached patch could prevent this
(also only affects western version).
Instead of (superfluously) using isprint() with the locale,
it now just checks the range (pointed out by Christian Weisgerber).
T.E.Dickeys xterm home:
<URL:http://www.clark.net/pub/dickey/xterm/>
The xterm control sequences:
<URL:http://www.uni-ulm.de/~s_smasch/w3m/ctlseqs.txt>
Cordially,
Sven
--
This archive was generated by hypermail 2b29 : Wed Jul 19 2000 - 10:30:43 CDT