Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: Gnus changes in Emacs-Unicode branch
Date: Mon, 19 Aug 2002 16:34:18 +0200	[thread overview]
Message-ID: <ilusn1ark7p.fsf@latte.josefsson.org> (raw)
In-Reply-To: <rzq8z33jaiy.fsf@albion.dl.ac.uk> (Dave Love's message of "19 Aug 2002 13:30:45 +0100")

Dave Love <d.love@dl.ac.uk> writes:

> Simon Josefsson <jas@extundo.com> writes:
>
>> > I don't know what that means, but I _hope_ it has nothing to do with
>> > the Emacs internal encoding.
>> 
>> It shouldn't, but I haven't verified it.
>
> Then I don't understand the issue.  [Why is something utf-8 specific
> anyhow?  There shouldn't be anything special abut utf-8, which has
> been a problem with Gnus code before.]

USEFOR says to use UTF-8, so Gnus tries to decode group names as
UTF-8.  Configurable depending on hierarchy and method, of course.  If
the way Gnus achieves this depends on the internal Emacs encoding, I
couldn't tell.

>> > [This applies to Emacs.  As far as I can tell, XEmacs Mule lacks the
>> > necessary machinery to do things properly.]
>> 
>> It shouldn't be worse than it is today,
>
> I don't understand.  I'm talking about today (or maybe yesterday --
> Debian Woody).

Err, OK, I thought this was related to the Emacs Unicode branch only.
If the patch is against Oort and todays' (X)Emacs, and FWIW, I'd vote
for simply installing it.




  reply	other threads:[~2002-08-19 14:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-31 13:30 Kai Großjohann
2002-07-31 15:32 ` Simon Josefsson
2002-08-15 17:20   ` Dave Love
2002-08-15 22:12     ` Simon Josefsson
2002-08-19 12:30       ` Dave Love
2002-08-19 14:34         ` Simon Josefsson [this message]
2002-08-21 16:47           ` Dave Love
2002-08-15 17:07 ` Dave Love

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=ilusn1ark7p.fsf@latte.josefsson.org \
    --to=jas@extundo.com \
    --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).