From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: "Coding system"? Eh?
Date: 05 Sep 1998 18:01:03 +0200 [thread overview]
Message-ID: <m31zpqtups.fsf@sparky.gnus.org> (raw)
Isn't what MULE calls a "coding system" what the entire rest of the
world call a "character set"? So `decode-coding-system' should
really have been called `decode-charset'?
MULE is confusing.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@ifi.uio.no * Lars Magne Ingebrigtsen
next reply other threads:[~1998-09-05 16:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-09-05 16:01 Lars Magne Ingebrigtsen [this message]
1998-09-05 16:31 ` Michael Welsh Duggan
1998-09-05 20:07 ` Lars Magne Ingebrigtsen
1998-09-05 20:45 ` Hrvoje Niksic
1998-09-05 21:12 ` Lars Magne Ingebrigtsen
1998-09-05 21:47 ` Hrvoje Niksic
1998-09-07 15:12 ` David Kågedal
1998-09-09 18:50 ` François Pinard
1998-09-10 12:45 ` David Kågedal
1998-09-10 20:21 ` Gisle Aas
1998-09-11 6:27 ` François Pinard
1998-09-11 6:16 ` François Pinard
1998-09-11 16:14 ` Hallvard B Furuseth
2002-10-20 23:13 ` Lars Magne Ingebrigtsen
1998-09-09 18:59 ` François Pinard
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=m31zpqtups.fsf@sparky.gnus.org \
--to=larsi@ifi.uio.no \
/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).