From: "François Pinard" <pinard@IRO.UMontreal.CA>
Subject: Re: More charset things
Date: 08 Feb 1999 18:19:22 -0500 [thread overview]
Message-ID: <vrhfswfpqd.fsf@raptor.IRO.UMontreal.CA> (raw)
In-Reply-To: Stainless Steel Rat's message of "08 Feb 1999 15:07:55 -0500"
Stainless Steel Rat <ratinox@peorth.gweep.net> writes:
> > UTF-8 is an encoding scheme, comparable to uuencode.
> It is? Then I'm confused... for some reason I was thinking that UTF-8
> *was* Unicode.
Nowadays, the UCS may be represented as UCS-2 or UCS-4 internally, yet
UCS-2 is often seen externally. The latest Unicode, if I understand
things correctly, highly promotes what was once called UTF-16, which is
a way of using one or two UCS-2 super-bytes for representing one million
characters. There is also UTF-8 which is popular (and nice) and UTF-7
which is getting popular (and ugly). Nicety and ugliness is well hidden
in decoders/encoders, so it does not really matter in practice. UTF-7 is a
MIME related invention, it does not come from Unicode nor ISO. There also
are other encodings, but they are obsolent enough to not be worth mentioning.
--
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-08 23:19 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 [this message]
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
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=vrhfswfpqd.fsf@raptor.IRO.UMontreal.CA \
--to=pinard@iro.umontreal.ca \
/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).