On Thu, Dec 07, 2006 at 12:01:58PM -0500, Ambrose Li wrote: > When the same message is piped to w3m with an argument explicitly > telling it that the input is GB2312 (as incorrectly tagged), it > correctly renders it as: > > 聽講貴處逢週二有乒乓毬活動，但網頁上??唔到
Correction: w3m -I gb2312 renders it as [C2][A0][D6]v[D9]F[CC][8E]逢[DF]L二有乒乓[9A]??[EE][84]??????W[ED][93]上[93]h唔到 (i.e., 0000000 5b 43 32 5d 5b 41 30 5d 5b 44 36 5d 76 5b 44 39 0000020 5d 46 5b 43 43 5d 5b 38 45 5d b3 7b 5b 44 46 5d 0000040 4c a4 47 a6 b3 a5 e2 a5 e3 5b 39 41 5d 3f 3f 5b 0000060 45 45 5d 5b 38 34 5d 3f 3f 3f 3f 3f 3f 57 5b 45 0000100 44 5d 5b 39 33 5d a4 57 5b 39 33 5d 68 ad f8 a8 0000120 ec in Big5, with meaningless [xx] codes, but apparently not as confused by the invalid GB2312 as mutt is.) The quoted string in the original report is the output from w3m without any arguments, where w3m correctly detected GB18030. Sorry for any confusion.
