From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Mule-UCS, Gnus, and Emacs 21
Date: Sun, 21 Oct 2001 16:23:52 +0200 [thread overview]
Message-ID: <vafn12lt6kn.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (raw)
>From time to time, I try Mule-UCS (0.84 currently) with Emacs 21 and
Gnus, but it produces b0rked UTF-8 encoding. Normally, UTF-8 encoding
is produced when I respond to an iso-8859-15 posting with iso-8859-1
characters. This causes Gnus to select UTF-8 as the encoding for the
outgoing message, but the result looks as if it UTF-8 encoded twice
(or so people tell me).
Has anybody here got any experience with that? What to do? Is it a
general problem with Mule-UCS, or with Gnus, or in the interaction of
the packages?
kai
--
Lisp is kinda like tpircstsoP
next reply other threads:[~2001-10-21 14:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-21 14:23 Kai Großjohann [this message]
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
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=vafn12lt6kn.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
/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).