Re: GNAT vs UTF-8 source file names

["Randy Brukardt" <randy@rrsoftware.com>]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1503 bytes --]

"J-P. Rosen" <rosen@adalog.fr> wrote in message 
news:ojihrl$qu2$1@dont-email.me...
> Le 05/07/2017 à 11:47, Simon Wright a écrit :
>> That reference specifies NFKC which I suppose is near!
> Not that near when it comes to ligatures and other crazy characters...
> But you are right, it's NFKC.

Actually, you were right the first time, but it doesn't show up in the Ada 
2012 as this is a recent correction (recall AI12-0004-1? It was just 
approved by WG 9 at the June meeting). NFKC is *definitely* the wrong rule.

Note that we chose NFC in part because WC3 recommends that all Internet 
content be in NFC, and because it is the more compact representation. I'm 
surprised that anyone would use NFD (since it can be three times larger than 
NFC), but I suppose I shouldn't ever be surprised by the choices of others. 
;-)

As always, you can see the *current* state of Ada by using the working draft 
RM (see http://www.ada-auth.org/standards/ada2x.html). For this rule, that 
is 2.1(4.1/5).

I suppose the working draft is a bit confusing for this use (that is, 
Ada-Comment) as corrections (like this) take effect immediately upon WG 9 
approval while amendments don't take effect until the next Standard update. 
You can tell them apart by looking at the bottom of each subclause at the 
"<something> from Ada 2012" (for instance, "Wording Changes from Ada 
2012") -- "corrections" are identified that way, while amendments are not 
identified specially.

                               Randy.