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.9 required=5.0 tests=BAYES_00,FORGED_GMAIL_RCVD,
	FREEMAIL_FROM autolearn=no autolearn_force=no version=3.4.4
X-Google-Thread: 103376,5bcc293dc5642650
X-Google-NewGroupId: yes
X-Google-Attributes: gida07f3367d7,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Received: by 10.68.8.229 with SMTP id u5mr15899672pba.0.1318640870000;
        Fri, 14 Oct 2011 18:07:50 -0700 (PDT)
Path: 
 d5ni8367pbc.0!nntp.google.com!news2.google.com!postnews.google.com!y22g2000pri.googlegroups.com!not-for-mail
From: ytomino <aghia05@gmail.com>
Newsgroups: comp.lang.ada
Subject: Re: Why no Ada.Wide_Directories?
Date: Fri, 14 Oct 2011 18:06:05 -0700 (PDT)
Organization: http://groups.google.com
Message-ID: 
 <418b8140-fafb-442f-b91c-e22cc47f8adb@y22g2000pri.googlegroups.com>
References: <9937871.172.1318575525468.JavaMail.geo-discussion-forums@prib32>
NNTP-Posting-Host: 122.17.53.140
Mime-Version: 1.0
X-Trace: posting.google.com 1318640869 23593 127.0.0.1 (15 Oct 2011 01:07:49
 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Sat, 15 Oct 2011 01:07:49 +0000 (UTC)
Complaints-To: groups-abuse@google.com
Injection-Info: y22g2000pri.googlegroups.com; posting-host=122.17.53.140;
 posting-account=Mi71UQoAAACnFhXo1NVxPlurinchtkIj
User-Agent: G2/1.0
X-Google-Web-Client: true
X-Google-Header-Order: HNKUARELSC
X-HTTP-UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_5_8)
 AppleWebKit/535.1 (KHTML,
 like Gecko) Chrome/14.0.835.202 Safari/535.1,gzip(gfe)
Xref: news2.google.com comp.lang.ada:13955
Content-Type: text/plain; charset=ISO-8859-1
Date: 2011-10-14T18:06:05-07:00
List-Id: <comp.lang.ada>

Hello.
In RM 3.5.2, Ada's Character/String types are not UTF-8 but Latin-1
(except Ada.Strings.UTF_Encoding).
I'm afraid that is violation of the standard even if the
implementation accepts UTF-8.

Of course, I think that the standard is impractical, too.
If we must keep the standard, there is no way to access a file (and
other environment features) named with non-ASCII, at all.
I'm unlikely to bear... But that's another problem.

I do not know why the standard does not have Wide_Directories and
Text_IO.Wide_Open and Wide_Command_Line and Wide_Environment_Variables
and...,
Still, too, I hope these (or the standard allows that Character/String
represent UTF-8).