From: Steven Woody <steven@steven4u.net>
Subject: Now I'm sure it's a bug! please help me
Date: Mon, 10 Mar 2003 22:45:53 +0800 [thread overview]
Message-ID: <84llzn700u.fsf@zsw.com> (raw)
I'm currently runing Emacs 21.2.1 + Oort gnus 0.16. After some steps
of setting, now I can read/write Chinese (plain text email, news
group). However, if I received a mail message in HTML+Chinese, gnus
will not properly represent it to me.
I'v tried almost all the text-html-renderer, include w3m, w3, lynx
2.8.3 and lynx 2.8.4. Now I post the test result here, just for your
information, and most important, hope some one can help me to resolv
the problem.
This is the oringial email message (in raw data) for test:
---- cut begin ---------
...
From: a@b.c
To: a@b.c
Subject: =?gb2312?B?SFRNTCvW0M7E?=
..
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_0038_01C2E74E.8E9D6420"
...
...
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
This is a multi-part message in MIME format.
------=_NextPart_000_0038_01C2E74E.8E9D6420
Content-Type: text/plain;
charset="gb2312"
Content-Transfer-Encoding: base64
RW5nbGlzaA0K1tDOxA==
------=_NextPart_000_0038_01C2E74E.8E9D6420
Content-Type: text/html;
charset="gb2312"
Content-Transfer-Encoding: base64
PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv
L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgaHR0cC1lcXVpdj1Db250ZW50LVR5cGUgY29udGVu
dD0idGV4dC9odG1sOyBjaGFyc2V0PWdiMjMxMiI+DQo8TUVUQSBjb250ZW50PSJNU0hUTUwgNi4w
MC4yODAwLjExNDEiIG5hbWU9R0VORVJBVE9SPg0KPFNUWUxFPjwvU1RZTEU+DQo8L0hFQUQ+DQo8
Qk9EWSBiZ0NvbG9yPSNmZmZmZmY+DQo8RElWPjxGT05UIHNpemU9Mj5FbmdsaXNoPC9GT05UPjwv
RElWPg0KPERJVj48Rk9OVCBzaXplPTI+1tDOxDwvRk9OVD48L0RJVj48L0JPRFk+PC9IVE1MPg0K
------=_NextPart_000_0038_01C2E74E.8E9D6420--
---------cut end ----------------------------------------------------
Output of lynx 2.8.4 as renderer
================================
English
????
Note: lynx can display Chinese web page in the command line w/o any
problem. But when it works as a Gnus renderer, it display the two
Chinese characters as four '?'s. I dont know Lisp, but after check
the code, I found Gnus call lynx with "-stdin -dump -fource_html", I
tried this on the command line and found no problem, so I dont
understand why lynx change it's behavior in Gnus with the same call?
Consequently I think the data Gnus feed to Lynx may be a problem, but
why plain text base64 message can display properly, this seems imply
base64 decoding is not the source of the problem, right? Who come on
to answer the question?
Output of w3m as renderer
=========================
English
^[$(AVPND^[(B
Note: w3m can display Chinese web page in the command line w/o any
problem.
Output w3 as renderer
==============================================================
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=gb2312">
<META content="MSHTML 6.00.2800.1141" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT size=2>English</FONT></DIV>
<DIV><FONT size=2>中文</FONT></DIV></BODY></HTML>
Note: As many people said, w3 is very unforgivening, most of my html
mail can not be process by it, so it output a html source file. But,
there is a very strange thing that the Chinese charactars were
*correctly* displayed!
Output of Lynx 2.8.3 as renderer
=================================
...
Invalid Options '-stdin'
...
Note: this caused by that the lynx 2.8.3 dont has a '-stdin' option,
so I remove it and install the newer 2.8.4.
--
Put your Nose to the Grindstone!
-- Amalgamated Plastic Surgeons and Toolmakers, Ltd.
next reply other threads:[~2003-03-10 14:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-10 14:45 Steven Woody [this message]
2003-03-10 22:20 ` Kai Großjohann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=84llzn700u.fsf@zsw.com \
--to=steven@steven4u.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).