Gnus development mailing list
 help / color / mirror / Atom feed
From: Steven Woody <steven@steven4u.net>
Subject: [Bug?] Content-Transfer-Encoding with mutibyte language mail message
Date: Mon, 10 Mar 2003 02:33:17 +0800	[thread overview]
Message-ID: <84bs0kxudu.fsf@zsw.com> (raw)


Some mail messages can not recognized by Emacs with following
attributes combined:

    Content-Type: text/html
    Content-Transfer-Encoding: quoted-printable
    Charset: gb2312

Chinese charactars in this kinda message dont display properly. If the
"Content-Transfer-Encoding" set to Base64, the problem dispeared.

Is there any workaround here?

-- 
I've found my niche.  If you're wondering why I'm not there, there was
this little hole in the bottom ...
		-- John Croll



             reply	other threads:[~2003-03-09 18:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-09 18:33 Steven Woody [this message]
2003-03-09 18:51 ` Simon Josefsson
2003-03-10  3:19   ` Steven Woody
2003-03-10 12:58     ` Simon Josefsson
2003-03-10 14:19       ` Kai Großjohann
2003-03-10 15:41         ` Steven Woody

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=84bs0kxudu.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).