Gnus development mailing list
 help / color / mirror / Atom feed
From: Steven Woody <steven@steven4u.net>
Subject: Re: [Bug?] Content-Transfer-Encoding with mutibyte language mail message
Date: Mon, 10 Mar 2003 23:41:00 +0800	[thread overview]
Message-ID: <84y93n5iwj.fsf@zsw.com> (raw)
In-Reply-To: <848yvnjoc5.fsf@lucy.is.informatik.uni-duisburg.de>

kai.grossjohann@uni-duisburg.de (Kai Großjohann) writes:

> Simon Josefsson <jas@extundo.com> writes:
>
>> Can you forward the entire message (preferably as a gzip'ed single
>> message file to avoid triggering encoding bugs again)?  It seems weird
>> that it works better if Gnus is instructed to base64 decode non-base64
>> encoded data.
>
> I think when Steven said "if the CTE is set to base64" he meant that
> the message is also encoded in base64.  I think he wanted to say that
> Gnus groks base64-encoded messages, but not qp-encoded messages.
>

Yes, that's exactly what mean yesterday. But, today ... I found even
base64-encoded html msg dont get a correct display :(  I'v uninstall
and reinstall all of those relative packages, and cant return back to the time
when I thought base64-encoded msg was okay!

I'v already posted a message on the group to describe my the current
problem in more detail. Please check that, thank you!


-- 
Acid -- better living through chemistry.



      reply	other threads:[~2003-03-10 15:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-09 18:33 Steven Woody
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 [this message]

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