From: "François Pinard" <pinard@iro.umontreal.ca>
Cc: <handa@etl.go.jp>
Subject: Re: More charset things
Date: 07 Feb 1999 14:35:24 -0500 [thread overview]
Message-ID: <oqemo2ypkz.fsf@titan.progiciels-bpi.ca> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "04 Feb 1999 18:08:57 +0100"
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> (By the way -- is it "MULE" or "Mule? I'm waffling all over the place
> when I write that word. Perhaps I should start writing it "mUlE"?)
I documented this somewhere. Let me see... OK:
The spelling @code{Mule} originally stands for @cite{@emph{mul}tilingual
@emph{e}nhancement to GNU Emacs}, it is the result of a collective
effort orchestrated by Handa Ken'ishi since 1993. When @code{Mule} got
rewritten in the main development stream of GNU Emacs 20, the FSF renamed
it @code{MULE}, meaning @cite{@emph{mul}tilingual @emph{e}nvironment
in GNU Emacs}.
I guess that the FSF wanted to more clearly establish who is the boss, by
renaming the thing and changing the capitalization. By reaction, maybe,
I try to consistently write "Mule", as a tribute to the original effort.
--
François Pinard mailto:pinard@iro.umontreal.ca
Join the free Translation Project! http://www.iro.umontreal.ca/~pinard
next prev parent reply other threads:[~1999-02-07 19:35 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-03 18:09 Lars Magne Ingebrigtsen
1999-02-04 14:56 ` Hrvoje Niksic
1999-02-04 17:08 ` Lars Magne Ingebrigtsen
1999-02-04 17:21 ` Hrvoje Niksic
1999-02-04 17:49 ` Lars Magne Ingebrigtsen
1999-02-05 0:47 ` Stephen J. Turnbull
1999-02-05 2:43 ` Hrvoje Niksic
[not found] ` <m3hft163aa.fsf@peorth.gweep.net>
1999-02-05 19:06 ` Vladimir Volovich
[not found] ` <m3sockqqjx.fsf@peorth.gweep.net>
1999-02-06 15:55 ` Lars Magne Ingebrigtsen
[not found] ` <m3lnia5922.fsf@peorth.gweep.net>
1999-02-07 21:02 ` Hrvoje Niksic
1999-02-09 15:56 ` Lars Magne Ingebrigtsen
1999-02-09 17:21 ` Hrvoje Niksic
1999-02-09 17:31 ` Alan Shutko
1999-02-09 17:37 ` Lars Magne Ingebrigtsen
1999-02-09 18:06 ` Hrvoje Niksic
1999-02-08 16:04 ` Bill White
1999-02-09 16:04 ` Lars Magne Ingebrigtsen
1999-02-06 8:17 ` Lars Magne Ingebrigtsen
1999-02-09 10:27 ` Displayed [ 0: Stephen J. Turnbull ] but it had lots of lines Alf-Ivar Holm
1999-02-09 16:14 ` Lars Magne Ingebrigtsen
1999-02-09 22:07 ` More charset things Jan Vroonhof
[not found] ` <m3hft163aa.fsf@p <byu2wv6xkb.fsf@bolzano.math.ethz.ch>
1999-02-09 22:13 ` Hrvoje Niksic
1999-02-07 20:43 ` François Pinard
1999-02-08 2:09 ` Martin Buchholz
1999-02-22 15:52 ` François Pinard
1999-02-08 14:49 ` Robert Bihlmeyer
[not found] ` <m37lttydo2.fsf@peorth.gweep.net>
1999-02-08 9:55 ` Kai.Grossjohann
1999-02-08 15:52 ` François Pinard
[not found] ` <m3n22ou09w.fsf@peorth.gweep.net>
1999-02-08 23:19 ` François Pinard
1999-02-09 8:05 ` Steinar Bang
1999-02-14 18:10 ` UTF-8 (Was: More charset things) Steinar Bang
1999-02-09 16:03 ` More charset things Lars Magne Ingebrigtsen
1999-02-08 17:29 ` Karl Eichwalder
1999-02-08 22:03 ` James H. Cloos Jr.
1999-02-09 5:29 ` Russ Allbery
1999-02-09 7:33 ` James H. Cloos Jr.
1999-02-10 2:13 ` Stephen Zander
1999-02-11 10:09 ` Jan Vroonhof
1999-02-07 19:37 ` François Pinard
1999-02-08 0:06 ` Kenichi Handa
1999-02-07 19:35 ` François Pinard [this message]
1999-02-08 13:37 ` Simon Josefsson
1999-02-08 23:43 ` Kenichi Handa
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=oqemo2ypkz.fsf@titan.progiciels-bpi.ca \
--to=pinard@iro.umontreal.ca \
--cc=handa@etl.go.jp \
/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).