From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: "Coding system"? Eh?
Date: Sun, 20 Oct 2002 23:13:16 +0000 (UTC) [thread overview]
Message-ID: <m3zpcbttym.fsf@sparky.gnus.org> (raw)
In-Reply-To: davidk@lysator.liu.se's message of "07 Sep 1998 17:12:40 +0200"
davidk@lysator.liu.se (David Kågedal) writes:
> ISO 8859-1 is both a character set, and an encoding (one-to-one from
> charater to byte), I believe. But I'm not sure how it is defined.
A character set is an encoding in normal usage. Quoth RFC2045:
2.2. Character Set
The term "character set" is used in MIME to refer to a method of
converting a sequence of octets into a sequence of characters. Note
that unconditional and unambiguous conversion in the other direction
is not required, in that not all characters may be representable by a
given character set and a character set may provide more than one
sequence of octets to represent a particular sequence of characters.
This definition is intended to allow various kinds of character
encodings, from simple single-table mappings such as US-ASCII to
complex table switching methods such as those that use ISO 2022's
techniques, to be used as character sets. However, the definition
associated with a MIME character set name must fully specify the
mapping to be performed. In particular, use of external profiling
information to determine the exact mapping is not permitted.
NOTE: The term "character set" was originally to describe such
straightforward schemes as US-ASCII and ISO-8859-1 which have a
simple one-to-one mapping from single octets to single characters.
Multi-octet coded character sets and switching techniques make the
situation more complex. For example, some communities use the term
"character encoding" for what MIME calls a "character set", while
using the phrase "coded character set" to denote an abstract mapping
from integers (not octets) to characters.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2002-10-20 23:13 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
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 [this message]
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=m3zpcbttym.fsf@sparky.gnus.org \
--to=larsi@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).