X-Authentication-Warning: delorie.com: mail set sender to djgpp-workers-bounces using -f
From: <ams AT ludd DOT ltu DOT se>
Message-Id: <200505211222.j4LCMQKW025118@speedy.ludd.ltu.se>
Subject: Re: wchar_t implementation and multibyte encoding
In-Reply-To: <428F543B.2060801@phekda.gotadsl.co.uk> "from Richard Dawe at May
 21, 2005 04:31:07 pm"
To: djgpp-workers AT delorie DOT com
Date: Sat, 21 May 2005 14:22:26 +0200 (CEST)
X-Mailer: ELM [version 2.4ME+ PL78 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII
X-ltu-MailScanner-Information: Please contact the ISP for more information
X-ltu-MailScanner: Found to be clean
X-MailScanner-From: ams AT ludd DOT ltu DOT se
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

According to Richard Dawe:
> You're confusing the codepoint, which is the numbering of characters, 
                                               ^^^^^^^^^^^^^^^^^^^^^^^^
> symbols, etc. with how you represent them. The codepoints are abstract.
  ^^^^^^^^^^^^

> When you talk about "Unicode encoding", this is UTF-32, a mapping of 
> 0x10ffff to a 32-bit integer. That may not seem like an encoding, but it 
> is, because of endianness in the encoded data.

Ok.

1. But suppose I decide to use the inverted Unicode codepoints (IUC),
which I just invented, where 
"IUC character value" == 0x10ffff - "Unicode chararcter value".

Now I have a different set of codepoints. To me, IUC and Unicode are
two different encodings (of characters).

2. I which way _isn't_ Unicode a "numbering of characters, symbols,
etc"?


Right,

						MartinS