From: Simon Josefsson <jas@pdc.kth.se>
Cc: ding@gnus.org
Subject: Re: group names with non-ascii characters
Date: 09 Jun 2000 00:39:04 +0200 [thread overview]
Message-ID: <ilud7lrvlvb.fsf@badis.pdc.kth.se> (raw)
In-Reply-To: Shenghuo ZHU's message of "08 Jun 2000 15:21:09 -0400"
Shenghuo ZHU <zsh@cs.rochester.edu> writes:
> Is anyone using group names with non-ascii characters? There could be
> some bugs in handling the path names and the entries in the .active
> files. I guess nnimap supports group names with iso-8859-1
> characters. Has anyone tested to use agent or cache with those
> groups?
I've used nnimap+agent with latin-1 group names, but that was ~6
months ago or so and I didn't test specifically that latin-1
characters worked. I think it did, though. The only reference I
could find in my .gnus is
(setq gnus-startup-file-coding-system 'iso-8859-1)
(On a different topic, I think the default of that variable should be
`mule' or something that can hold all sorts of characters. Limiting
group names to 7-bit ascii by default feels wrong.)
next prev parent reply other threads:[~2000-06-08 22:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-08 19:21 Shenghuo ZHU
2000-06-08 20:20 ` François Pinard
2000-06-08 22:39 ` Simon Josefsson [this message]
2000-06-12 17:45 ` Bjørn Mork
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=ilud7lrvlvb.fsf@badis.pdc.kth.se \
--to=jas@pdc.kth.se \
--cc=ding@gnus.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).