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-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.31.73 with SMTP id y9mr326234pbh.0.1318887212821;
        Mon, 17 Oct 2011 14:33:32 -0700 (PDT)
MIME-Version: 1.0
Path: 
 d5ni23601pbc.0!nntp.google.com!news2.google.com!goblin2!goblin.stu.neva.ru!newsfeed.x-privat.org!news.jacob-sparre.dk!pnx.dk!jacob-sparre.dk!ada-dk.org!.POSTED!not-for-mail
From: "Randy Brukardt" <randy@rrsoftware.com>
Newsgroups: comp.lang.ada
Subject: Re: Why no Ada.Wide_Directories?
Date: Mon, 17 Oct 2011 16:33:28 -0500
Organization: Jacob Sparre Andersen Research & Innovation
Message-ID: <j7i6va$nso$1@munin.nbi.dk>
References: <9937871.172.1318575525468.JavaMail.geo-discussion-forums@prib32>
 <418b8140-fafb-442f-b91c-e22cc47f8adb@y22g2000pri.googlegroups.com>
NNTP-Posting-Host: static-69-95-181-76.mad.choiceone.net
X-Trace: munin.nbi.dk 1318887211 24472 69.95.181.76 (17 Oct 2011 21:33:31 GMT)
X-Complaints-To: news@jacob-sparre.dk
NNTP-Posting-Date: Mon, 17 Oct 2011 21:33:31 +0000 (UTC)
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5931
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-RFC2646: Format=Flowed; Original
Xref: news2.google.com comp.lang.ada:14011
Date: 2011-10-17T16:33:28-05:00
List-Id: <comp.lang.ada>

"ytomino" <aghia05@gmail.com> wrote in message 
news:418b8140-fafb-442f-b91c-e22cc47f8adb@y22g2000pri.googlegroups.com...
> 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.

Say what?

Ada.Strings.Encoding (new in Ada 2012) uses a subtype of String to store 
UTF-8 encoded strings. As such, I'd find it pretty surprising if doing so 
was "a violation of the standard".

The intent has always been that Open, Ada.Directories, etc. take UTF-8 
strings as an option. Presumably the implementation would use a Form to 
specify that the file names in UTF-8 form rather than Latin-1. (I wasn't 
able to find a reference for this in a quick search, but I know it has been 
talked about on several occasions.)

One of the primary reasons that Ada.Strings.Encoding uses a subtype of 
String rather than a separate type is so that it can be passed to Open and 
the like.

It's probably true that we should standardize on the Form needed to use 
UTF-8 strings in these contexts, or at least come up with Implementation 
Advice on that point.

                                       Randy.