From: Jon Babcock <jon@kanji.com>
Subject: Re: Mule-begot problems
Date: 06 Jan 1998 11:26:23 -0700 [thread overview]
Message-ID: <861zylqx0w.fsf@lotus.kanji.com> (raw)
In-Reply-To: Tore Olsen's message of 06 Jan 1998 14:28:21 +0100
I've taken Tore Olsen's advice and have written to Erik Naggum. Thanks.
I should have focused my question more specifically. What Mule-related
problems have Gnus developers experienced?
To read and write to mailing lists and newsgroups that use Japanese
and Chinese, I need Gnus. To write articles and monographs that
include CJK scripts, I need Emacs. If it were a question of only one
script, say Japanese, then I could run a nipponized version of Linux,
use kterm, etc. But it is precisely the ability to deal with multiple
scripts that makes the new Emacs so attractive to me, whose background
is classical Chinese and Buddhist prajnaparamita studies. I want to
see that multi-script functionality become a solid part of Emacs so
that Emacs offers the best solution in this area available anywhere.
Jon Babcock
jon@kanji.com
next prev parent reply other threads:[~1998-01-06 18:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-01-06 10:32 Jon Babcock
1998-01-06 13:28 ` Tore Olsen
1998-01-06 18:26 ` Jon Babcock [this message]
1998-01-06 20:12 Fabrice.Popineau
[not found] ` <x7d8i55pen.fsf@peorth.gweep.net>
1998-01-06 23:36 ` Jason L Tibbitts III
[not found] ` <x7d8i5tber.fsf@peorth.gweep.net>
1998-01-07 2:07 ` Russ Allbery
[not found] ` <x7zpl93paa.fsf@peorth.gweep.net>
1998-01-07 4:12 ` Russ Allbery
1998-01-07 5:14 ` Richard Coleman
1998-01-07 7:56 ` Steinar Bang
1998-01-07 11:03 ` Kai Grossjohann
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=861zylqx0w.fsf@lotus.kanji.com \
--to=jon@kanji.com \
/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).