Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@extundo.com>
Subject: Re: Non-ASCII group names is broken (return of the \201's)
Date: Sun, 10 Aug 2003 14:57:38 +0200	[thread overview]
Message-ID: <ilun0ehbrgd.fsf@latte.josefsson.org> (raw)
In-Reply-To: <m3he4phe7q.fsf@defun.localdomain> (Jesper Harder's message of "Sun, 10 Aug 2003 14:47:05 +0200")

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=utf-8, Size: 1085 bytes --]

Jesper Harder <harder@myrealbox.com> writes:

> 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.

This is probably contentious, but when emacsen support Unicode well
enough, IMHO we should make all Gnus files be UTF-8.

Since, I believe, even emacs HEAD doesn't support Unicode well enough
(it can't transcode double-width Cyrillic to Unicode), I don't expect
this to happen very soon though.




  reply	other threads:[~2003-08-10 12:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-10 12:47 Jesper Harder
2003-08-10 12:57 ` Simon Josefsson [this message]
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=ilun0ehbrgd.fsf@latte.josefsson.org \
    --to=jas@extundo.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).