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=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,e136d2bb18e6fb60
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 2002-12-01 12:25:27 PST
Path: 
 archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news.tele.dk!news.tele.dk!small.news.tele.dk!uninett.no!news.net.uni-c.dk!not-for-mail
From: Jacob Sparre Andersen <sparre@nbi.dk>
Newsgroups: comp.lang.ada
Subject: Re: Character Sets (plain text police report)
Date: Sun, 01 Dec 2002 21:25:24 +0100
Organization: UNI-C
Message-ID: <3DEA7034.5060606@nbi.dk>
References: <mailman.1038602282.10532.comp.lang.ada@ada.eu.org>
 <asaj6c$ts5$1@slb9.atl.mindspring.net> <3DE9F24E.3010002@nbi.dk>
 <asd6tj$isb$1@slb2.atl.mindspring.net>
NNTP-Posting-Host: kaoslx07.nbi.dk
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Trace: news.net.uni-c.dk 1038774326 27236 130.225.212.98 (1 Dec 2002
 20:25:26 GMT)
X-Complaints-To: usenet@news.net.uni-c.dk
NNTP-Posting-Date: Sun, 1 Dec 2002 20:25:26 +0000 (UTC)
User-Agent: Any Browser, HTML 4.01, XHTML 1.0
X-Accept-Language: fo, sv, no, is, da, German [de]
Xref: archiver1.google.com comp.lang.ada:31329
Date: 2002-12-01T21:25:24+01:00
List-Id: <comp.lang.ada>

Marin David Condic wrote:
> Jacob Sparre Andersen <sparre@nbi.dk> wrote in message
> news:3DE9F24E.3010002@nbi.dk...


> My understanding was that the 16 bit characters covered most of the
> practical uses one would find in modern languages.

There is, as I understand it, some disagreement with that 
explanation, if you ask a native Korean, Chinese or Japanese.

> So possibly if there was some kind of variant of Text_IO that dealt with
> UTF-8 files, it might be useful.

Yes, but that is something I should be able to write myself.

 > You'd need special data types and
> operations, but that wouldn't be insurmountable.

Agreed.

>>But it would be nice, if one could demand that
>>compilers can handle UTF-8 or raw 32-bit ISO-10646 encoded
>>source files.
> 
> That sounds like an implementation issue.

Yes.

 > (You're talking about the Ada
> compiler eating Ada source that is in UTF-8? No reason that can't be done
> without a language revision.)

Yes and yes.

Jacob
-- 
"The point is that I am now a perfectly safe penguin!"