From: Dave Love <d.love@dl.ac.uk>
Subject: Re: Gnus changes in Emacs-Unicode branch
Date: 15 Aug 2002 18:20:27 +0100 [thread overview]
Message-ID: <rzqk7msnin8.fsf@albion.dl.ac.uk> (raw)
In-Reply-To: <iluznw7lxp0.fsf@latte.josefsson.org>
Simon Josefsson <jas@extundo.com> writes:
> I can think of at least one unicode related feature present
> in Oort not present in 5.9.0; support for the new usefor UTF-8
> headers.
I don't know what that means, but I _hope_ it has nothing to do with
the Emacs internal encoding.
> If this path is chosen, it would mean that your code cannot
> simply assume it is running in a unicode emacs,
I have tried to _eliminate_ assumptions in the MIME code about what
it's running in. There's little reason for the code to care about the
internal encoding, despite how it was written.
[This applies to Emacs. As far as I can tell, XEmacs Mule lacks the
necessary machinery to do things properly.]
next prev parent reply other threads:[~2002-08-15 17:20 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 [this message]
2002-08-15 22:12 ` Simon Josefsson
2002-08-19 12:30 ` Dave Love
2002-08-19 14:34 ` Simon Josefsson
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=rzqk7msnin8.fsf@albion.dl.ac.uk \
--to=d.love@dl.ac.uk \
/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).