From: Michael Welsh Duggan <md5i@cs.cmu.edu>
Subject: Re: "Coding system"? Eh?
Date: Sat, 05 Sep 1998 16:31:58 GMT [thread overview]
Message-ID: <v1tbtouwmf6.fsf@peoria.mt.cs.cmu.edu> (raw)
In-Reply-To: <m31zpqtups.fsf@sparky.gnus.org>
Lars Magne Ingebrigtsen <larsi@ifi.uio.no> writes:
> 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'?
No, not really. A character set is merely a set of characters.
latin-1, etc, are often called character sets because they use the
same number of characters as extended ASCII, etc. A coding-system is
just that: a coding-system. The characters could be encoded any which
way (including encrypted!). For example, old-jis uses escapes around
sequences of 7-bit characters. This is an encoding, which you can
display using a character set, but not a character set in and of
itself.
More information on {decode,encode}-coding-system: The way the
function is handled internally is that it deletes the region and
replaces it with the {de,en}coded text. This means markers in the
region are screwed. Regions are still buggy though; they shouldn't
work the way they do currently. I am looking into how hard it would
be to fix things such that markers at least can be preserved.
--
Michael Duggan
(md5i@cs.cmu.edu)
.
next prev parent reply other threads:[~1998-09-05 16:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-09-05 16:01 Lars Magne Ingebrigtsen
1998-09-05 16:31 ` Michael Welsh Duggan [this message]
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=v1tbtouwmf6.fsf@peoria.mt.cs.cmu.edu \
--to=md5i@cs.cmu.edu \
/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).