From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: Mule-UCS, Gnus, and Emacs 21
Date: Mon, 22 Oct 2001 10:11:14 +0200 [thread overview]
Message-ID: <vaf6698857h.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <878ze4g9xb.fsf@bang.priv.no> (Steinar Bang's message of "Sun, 21 Oct 2001 19:49:52 +0200")
Steinar Bang <sb@dod.no> writes:
>>>>>> Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann):
>
>> From time to time, I try Mule-UCS (0.84 currently) with Emacs 21 and
>> Gnus, but it produces b0rked UTF-8 encoding.
>
> Er... _should_ you use Mule-UCS with Emacs 21? Won't it conflict with
> Emacs 21's own Unicode support?
It seems that in fact there is some conflict. But I've heard things
which lead me to the conclusion that Mule-UCS is _supposed_ to work
with Emacs 21.
Hm.
kai
--
Lisp is kinda like tpircstsoP
next prev parent reply other threads:[~2001-10-22 8:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-21 14:23 Kai Großjohann
2001-10-21 14:38 ` Simon Josefsson
2001-10-21 16:50 ` Kai Großjohann
2001-10-21 17:11 ` Henrik Enberg
2001-10-21 17:29 ` Kai Großjohann
2001-10-21 17:49 ` Steinar Bang
2001-10-22 8:11 ` Kai Großjohann [this message]
2001-10-22 9:47 ` Simon Josefsson
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=vaf6698857h.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--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).