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=unavailable autolearn_force=no version=3.4.4
Path: 
 eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!news.eternal-september.org!feeder.eternal-september.org!nntp-feed.chiark.greenend.org.uk!ewrotcd!newsfeed.xs3.de!io.xs3.de!news.jacob-sparre.dk!franka.jacob-sparre.dk!pnx.dk!.POSTED.rrsoftware.com!not-for-mail
From: "Randy Brukardt" <randy@rrsoftware.com>
Newsgroups: comp.lang.ada
Subject: Re: GNAT vs UTF-8 source file names
Date: Fri, 7 Jul 2017 14:44:17 -0500
Organization: JSA Research & Innovation
Message-ID: <ojooah$585$1@franka.jacob-sparre.dk>
References: <lytw55kei5.fsf@pushface.org>
 <lyefuia5ur.fsf@pushface.org><lyeftw2tlc.fsf@pushface.org>
 <ojhspu$sb2$1@dont-email.me><ly60f72p1g.fsf@pushface.org>
 <ojihrl$qu2$1@dont-email.me><lyfue91k4a.fsf@pushface.org>
 <ojngbr$rcp$1@dont-email.me><lybmow1pfk.fsf@pushface.org>
 <87inj4xy8q.fsf@jacob-sparre.dk>
Injection-Date: Fri, 7 Jul 2017 19:44:18 -0000 (UTC)
Injection-Info: franka.jacob-sparre.dk;
 posting-host="rrsoftware.com:24.196.82.226";
	logging-data="5381"; mail-complaints-to="news@jacob-sparre.dk"
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5931
X-RFC2646: Format=Flowed; Original
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157
Xref: news.eternal-september.org comp.lang.ada:47321
Date: 2017-07-07T14:44:17-05:00
List-Id: <comp.lang.ada>

"Jacob Sparre Andersen" <jacob@jacob-sparre.dk> wrote in message 
news:87inj4xy8q.fsf@jacob-sparre.dk...
...
>> On the other hand, ARM 2.1(4/3) says "The coded representation for
>> characters is implementation defined", which seems to conflict with
>> (16) - but then, the AARM ramification (4.b/2) notes that the rule
>> doesn't have much force!
>
> That sounds like the classical wording.
>
> I suppose that the intent is that UTF-8 encoded ISO-10646 (in the right
> normalization form) _has_ to be supported, but that any other encoding
> is allowed in addition to that.

Precisely.

> It would of course be nice if that was also what the ARM actually said.

Mostly we're not changing text that doesn't have to be changed. In some 
cases, it would make more sense if it was changed, but since every change 
has a potential for errors and unintended consequences, its often best to 
leave stuff alone. (There are many cases where a "simple" change broke 
something else, leading to repeated fixes.)

                     Randy.