From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: Xemacs (Mule) and GNU Emacs, problem with drafts and encoding.
Date: Thu, 28 May 2015 10:29:07 +0900 [thread overview]
Message-ID: <b4msiah8p7g.fsf@jpl.org> (raw)
In-Reply-To: <87pp5m5glb.fsf@mat.ucm.es>
On Wed, 27 May 2015 14:51:12 +0200, Uwe Brauer wrote:
> I tried that but this coding setting but alas it does not make the
> drafts compatible.
Supposing you meant escape-quoted, it is the only real universal
coding system in XEmacs 21.5 and 21.4 (with Mule) AFAIK, but is
not available in Emacs. I think the iso-2022-7bit choice is not
so bad since the etc/HELLO file uses it in both Emacsen.
> Why does Xemacs not support the utf-8 coding for drafts, although in
> general it does support this format?
XEmacs 21.5 supports utf-8 natively but 21.4 requires the Mule-UCS
XEmacs package, that is a bit buggy, AFAIK.
next prev parent reply other threads:[~2015-05-28 1:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 12:51 Uwe Brauer
2015-05-28 1:29 ` Katsumi Yamaoka [this message]
2015-05-28 9:26 ` Uwe Brauer
2015-05-29 2:46 ` Katsumi Yamaoka
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=b4msiah8p7g.fsf@jpl.org \
--to=yamaoka@jpl.org \
--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).