Gnus development mailing list
 help / color / mirror / Atom feed
From: Danny Siu <dsiu@adobe.com>
Subject: Re: =?iso-* in from header, again?
Date: Wed, 02 Jun 2004 18:47:48 -0700	[thread overview]
Message-ID: <u1xkxxvi3.fsf@adobe.com> (raw)
In-Reply-To: <b9ybrk1whnf.fsf@jpl.org>

Katsumi Yamaoka writes:

  >>>>>> In <un03lpihn.fsf@adobe.com>
  >>>>>> Danny Siu <dsiu@adobe.com> wrote:

  >> I am seeing raw rfc 2047 string in from headers, which I have not seen
  >> for a long time, in recent cvs gnus:

  >> =?iso-8859-1?q?J=F8rn_Helge_B=2E_Dahl?= <foo@users.sourceforge.net>
  >> bojohan+news@dd.chalmers.se (=?iso-8859-1?q?Johan_Bockg=E5rd?=)
  >> =?big5?q?Grace=20Au?= <barbarbar@yahoo.com>

  >> Can anyone remind me which varible to set so that they can be decoded
  >> automatically in summary buffer?

  >> Thanks,

  Katsumi> How are they in the " *Original Article*" buffer?  If those
  Katsumi> senders use the latest Gnus and put pre-encoded words into the
  Katsumi> message buffer, it is likely to happen.  See the following
  Katsumi> thread:

From: sigurd@12move.de (Karl =?iso-8859-1?q?Pfl=E4sterer?=)
From: =?big5?q?Grace=20Au?= <tulipwing@yahoo.com>

The first sender is using Gnus while the second is using yahoo web mail.

  Katsumi> 
  Katsumi> http://news.gmane.org/group/gmane.emacs.gnus.general/thread=57540

  Katsumi> Setting the rfc2047-encode-encoded-words as nil may help them.

Hmm.  It doesn't help.  Still seeing =?iso stuff in Summary and Article
buffers.

  Katsumi> --
  Katsumi> Katsumi Yamaoka <yamaoka@jpl.org>

-- 
Danny Dick-Fung Siu              mailto:dsiu@adobe.com
Advanced Technology Group @ Adobe Systems Incorporated





      reply	other threads:[~2004-06-03  1:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-03  0:56 Danny Siu
2004-06-03  1:32 ` Katsumi Yamaoka
2004-06-03  1:47   ` Danny Siu [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=u1xkxxvi3.fsf@adobe.com \
    --to=dsiu@adobe.com \
    /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).