Gnus development mailing list
 help / color / mirror / Atom feed
From: Gisle Aas <aas@sn.no>
Cc: ding@gnus.org
Subject: Re: "Coding system"?  Eh?
Date: 10 Sep 1998 22:21:22 +0200	[thread overview]
Message-ID: <m34sufbtx9.fsf@furu.g.aas.no> (raw)
In-Reply-To: davidk@lysator.liu.se's message of "10 Sep 1998 14:45:06 +0200"

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 566 bytes --]

davidk@lysator.liu.se (David Kågedal) writes:

> > You mean, all Unicode characters.  ISO 10646 might need more then three,
> > as UTF-8 is also available for ISO 10646.
> 
> True.  I was talking about Unicode.

Unicode is in sync with ISO 10646.  Also Unicode allocates characters
above U+FFFF.  http://www.unicode.org/unicode/alloc/Pipeline.html.

> The difference between UTF-16 and UCS-2 is that it can encode some of
> the charaters outside the Unicode range (BMP).  So I guess Unicode has
> no need for UTF-16.

Unicode 2.x is in a way UTF-16.

-- 
Gisle Aas


  reply	other threads:[~1998-09-10 20:21 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 [this message]
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=m34sufbtx9.fsf@furu.g.aas.no \
    --to=aas@sn.no \
    --cc=ding@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).