Your message dated Thu, 02 Mar 2006 08:06:17 +0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#354284: lynx vs. uxterm
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
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.
--- End Message ---
--- Begin Message ---
OK, took the modem download plunge, and with lynx-cur_2.8.6-20 I can
indeed see Chinese characters -- so oops, wasted everybody's time ... closing.
However, paging down runs into something that sends rxvt-unicode-ml 7.5-1
(urxvt) into an infinite loop, just like urxterm. top(1) says it's urxvt.
Therefore I will make a fresh non-lynx bug when I find out about that.
--- End Message ---