Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: ding@gnus.org
Subject: Re: IMAP charset confusion
Date: Sun, 11 Sep 2011 00:28:16 +0200	[thread overview]
Message-ID: <m3litwf2wv.fsf@stories.gnus.org> (raw)
In-Reply-To: <b4mvctqs61x.fsf@jpl.org> (Katsumi Yamaoka's message of "Mon, 22 Aug 2011 08:23:06 +0900")

Katsumi Yamaoka <yamaoka@jpl.org> writes:

>> Hm...  would it make sense to have `gnus-group-name-charset' just return
>> nil for all nnimap groups?
>
> Doesn't this do the trick?
>
> (setq gnus-group-name-charset-method-alist
>       '(((nnimap "SERVER") . nil)))

Yes, but this should work by default...

I wonder whether this is the same charset confusion that bug#9351 (about
nnrss) is about.

If I understand the code correctly, the current model is that Gnus knows
what the charset the backends should use is.  So Gnus encodes strings to
that charset before giving the names over to the backend?

But in the case of nnimap, the backend charset should always be utf7.

But I'm not sure that's correct...

-- 
(domestic pets only, the antidote for overdose, milk.)
  bloggy blog http://lars.ingebrigtsen.no/



  reply	other threads:[~2011-09-10 22:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-21 21:17 Lars Magne Ingebrigtsen
2011-08-21 21:31 ` Lars Magne Ingebrigtsen
2011-08-21 21:37   ` Lars Magne Ingebrigtsen
2011-08-21 23:23 ` Katsumi Yamaoka
2011-09-10 22:28   ` Lars Magne Ingebrigtsen [this message]
2011-09-10 22:46     ` Lars Magne Ingebrigtsen
2011-09-10 22:50       ` Lars Magne Ingebrigtsen
2011-09-11  8:08         ` Andreas Schwab
2011-09-12  4:28           ` Lars Magne Ingebrigtsen

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=m3litwf2wv.fsf@stories.gnus.org \
    --to=larsi@gnus.org \
    --cc=ding@gnus.org \
    --cc=yamaoka@jpl.org \
    /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).