Package: lynx-cur Version: 2.8.6-17 Severity: normal There is something wrong in what lynx sends e.g., uxterm. $ lynx -dump http://seba.ulyssis.org/thesis/howto-pinyin.php is fine. Nothing to do with raw utf-8 vs. &#stuff.
My investigation concludes that lynx is sending e.g., M-G ~ P when it should be sending M-G M-^P, where M- means high bit set. Instead of setting the high bit of ^P and sending that, it sends two characters, ~ and P. Looking at their bits, ^P 10 00010000 P 50 01010000 ~ 7e 01111110 M-^P 90 10010000 we see lynx is sending 11000111 01111110 010abcde instead of 11000111 100abcde where abcde varies with the particular char being sent. What a screw up?! Looks like some mis-estimate in your to-utf-8 converter for screen presentation. (pstree shows a "xterm--luit" connection.) None of character_set=UNICODE (UTF-8) character_set=Transparent character_set=Chinese helped. Display and Character Set Use locale-based character set(!): [ON_] Display character set : [UNICODE (UTF-8)________________] Assumed document character set(!): [utf-8___________] Raw 8-bit (!) : [ON_] also didn't help And why does "=" show Charset: utf-8 when "o" shows Assumed document character set(!): [iso-8859-1______] -assume_local_charset=UTF-8 no help, -assume_charset=UTF-8 same. file:///usr/share/doc/HOWTO/en-html/Unicode-HOWTO-4.html no help. w3m works fine. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
