From: Jesper Harder <harder@myrealbox.com>
Subject: Non-ASCII group names is broken (return of the \201's)
Date: Sun, 10 Aug 2003 14:47:05 +0200 [thread overview]
Message-ID: <m3he4phe7q.fsf@defun.localdomain> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=utf-8, Size: 671 bytes --]
If I create a new nnml group with a non-ASCII name:
`G m Ãblegrød RET nnml RET'
The group turns up in the Group buffer like this
ÂÆblegrÂød
The problem is of course that Gnus thinks the name is unibyte (utf-8
specifically).
We could fix it by setting `gnus-group-name-charset-group-alist' to
nil, but then names of nntp groups which really _are_ unibyte would be
wrong.
I think it's a big mess that the list of newsgroups
(`gnus-newsrc-alist', `gnus-newsrc-hashtb' etc.) can contain a mix of
unibyte and multibyte names. It also breaks `j'
(gnus-group-jump-to-group) in the Group buffer and probably more
stuff.
I don't see any easy solution, though.
next reply other threads:[~2003-08-10 12:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-10 12:47 Jesper Harder [this message]
2003-08-10 12:57 ` Simon Josefsson
2003-08-11 12:49 ` Matthias Andree
2003-08-11 14:07 ` Matthias Andree
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=m3he4phe7q.fsf@defun.localdomain \
--to=harder@myrealbox.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).