From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-0.3 required=5.0 tests=BAYES_00,
	REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4
X-Google-Thread: 103376,421baaa91aa096a7
X-Google-Attributes: gid103376,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news1.google.com!news4.google.com!feeder1-2.proxad.net!proxad.net!feeder2-2.proxad.net!newsfeed.arcor.de!newsspool3.arcor-online.net!news.arcor.de.POSTED!not-for-mail
From: "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>
Subject: Re: Wide_[Wide_]Character
Newsgroups: comp.lang.ada
User-Agent: 40tude_Dialog/2.0.15.1
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Reply-To: mailbox@dmitry-kazakov.de
Organization: cbb software GmbH
References: <MrNoSpam-A54511.17443812072008@news-server.bigpond.net.au>
 <lv8778vm2w8k$.1n437e635ut8v$.dlg@40tude.net>
 <MrNoSpam-90C89A.21000512072008@news-server.bigpond.net.au>
Date: Sat, 12 Jul 2008 22:56:44 +0200
Message-ID: <9mxr6xum3cb$.kbtv0ggru4ls$.dlg@40tude.net>
NNTP-Posting-Date: 12 Jul 2008 22:56:47 CEST
NNTP-Posting-Host: f533f7d1.newsspool2.arcor-online.net
X-Trace: 
 DXC=Vm;7KUCQBHi]l@YUW5NBknA9EHlD;3Ycb4Fo<]lROoRa8kF<OcfhCOkdSh9VMa?D0h[6LHn;2LCVn[<mhadbfdUkDQ6i`_A`L_a<2WgJZAecih
X-Complaints-To: usenet-abuse@arcor.de
Xref: g2news1.google.com comp.lang.ada:1130
Date: 2008-07-12T22:56:47+02:00
List-Id: <comp.lang.ada>

On Sat, 12 Jul 2008 11:00:05 GMT, Dale Stanbrough wrote:

> Dmitry A. Kazakov wrote:
> 
>> RM 3.5.2 talks about "code positions" (=code points, I guess), represented
>> by Wide_Wide_Character. From this I conclude that it shall be UCS-4 with
>> some implementation-defined endianness.
> 
> Code points can be represented by any set of encodings. Wide_Character 
> seems to deliberately confine itself to the BMP, so UCS-2 would suffice 
> (and seems implied).
> 
> I can't see any implication that would cause me to think 
> Wide_Wide_Character is definitely UCS-4 (and not UTF-16).

How about this: Wide_Wide_Character may obviously use only the encodings
which would make  any Wide_Wide_String composed out of Wide_Wide_Characters
a properly encoded string in the same encoding. This automatically excludes
UTF-8 and UTF-16.

BTW, why do you care? (:-)) I wonder if there is any use of
Wide_[Wide_]Strings. IMO, anything one could wish from Unicode is provided
by UTF-8 and plain Strings...

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de