From: Pierpaolo BERNARDI <bernardp@cli.di.unipi.it>
To: John Max Skaller <skaller@ozemail.com.au>
Cc: OCAML <caml-list@inria.fr>
Subject: Re: Unicode (was RE: JIT-compilation for OCaml?)
Date: Thu, 18 Jan 2001 18:49:04 +0100 (MET) [thread overview]
Message-ID: <Pine.GSO.4.00.10101181843090.1886-100000@carlotta.cli.di.unipi.it> (raw)
In-Reply-To: <3A65F487.3F91E502@ozemail.com.au>
On Thu, 18 Jan 2001, John Max Skaller wrote:
> Pierpaolo BERNARDI wrote:
> >
> > On Thu, 11 Jan 2001, Dave Berry wrote:
> >
> > > I thought Unicode was a recognised subset of ISO-10646, corresponding to the
> > > range 0-2^16.
> >
> > No. ISO-10646 and Unicode contains exactly the same code points.
> > Unicode has room for about 2^20 code points. The ISO committee has
> > agreed to limit ISO-10646 to the same range.
>
> Unless it has changed recently, the first 64K code points of ISO-10646
> are known as the Basic Multilingual Plane (BMP), which corresponds
> to ISO-10646. The other 'planes' are not currently used AFAIK,
> but they exist.
Let me repeat: ISO has formally agreed to not use code points outside of
the Unicode possibility. This leaves room for about 2^20 characters.
Today has been published a draft of Unicode 3.1 (the definitive version
is due out in a couple of months, which already uses code points outside
of the BMP. See the Unicode FAQs at www.unicode.org for more
informations.
> Indeed, some code points from the BMP are reserved
> so Unicode can use multi-word encodings of the lower 4 planes.
Unicode can be encoded in several ways, for example, UTF-8, UTF-16,
UTF-32, UCS2, etc.. This has nothing to do with the number of characters
that can be encoded.
Cheers,
Pierpaolo
next prev parent reply other threads:[~2001-01-20 15:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-11 12:58 Dave Berry
2001-01-11 18:49 ` Xavier Leroy
2001-01-12 9:24 ` John Max Skaller
2001-01-12 12:05 ` Pierpaolo BERNARDI
[not found] ` <3A5F7685.FF2593BB@snob.spb.ru>
2001-01-12 21:33 ` Nickolay Semyonov
2001-01-17 19:47 ` John Max Skaller
2001-01-12 0:19 ` Pierpaolo BERNARDI
2001-01-17 19:37 ` John Max Skaller
2001-01-18 17:49 ` Pierpaolo BERNARDI [this message]
2001-01-22 20:27 ` John Max Skaller
2001-01-22 21:44 ` Pierpaolo BERNARDI
2001-01-24 13:41 ` John Max Skaller
2001-01-12 8:33 ` John Max Skaller
[not found] ` <3A5F77B7.52D8F933@snob.spb.ru>
2001-01-12 21:33 ` Nickolay Semyonov
2001-01-12 21:25 ` Nickolay Semyonov
[not found] <Pine.GSO.4.00.10101222155260.697-100000@carlotta.cli.di.unipi .it>
2001-01-22 21:57 ` Pierpaolo BERNARDI
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=Pine.GSO.4.00.10101181843090.1886-100000@carlotta.cli.di.unipi.it \
--to=bernardp@cli.di.unipi.it \
--cc=caml-list@inria.fr \
--cc=skaller@ozemail.com.au \
/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