Re: Ada and Unicode

[Simon Wright <simon@pushface.org>]

Vadim Godunko <vgodunko@gmail.com> writes:

> On Sunday, April 3, 2022 at 10:20:21 PM UTC+3, Thomas wrote:
>> 
>> > But don't use unit names containing international characters, at
>> > any rate if you're (interested in compiling on) Windows or macOS:
>> > 
>> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81114
>> 
>> and this kind of problems would be easier to avoid if string types
>> were stronger ...
>> 
>
> Your suggestion is unable to resolve this issue on Mac OS X. Like case
> sensitivity, binary compare of two strings can't compare strings in
> different normalization forms. Right solution is to use right type to
> represent any paths, and even it doesn't resolve some issues, like
> relative paths and change of rules at mounting points.

I think that's a macOS problem that Apple aren't going to resolve* any
time soon! While banging my head against PR81114 recently, I found
(can't remember where) that (lower case a acute) and (lower case a,
combining acute) represent the same concept and it's up to
tools/operating systems etc to recognise that.

Emacs, too, has a problem: it doesn't recognise the 'combining' part of
(lower case a, combining acute), so what you see on your screen is "a'".

* I don't know how/whether clang addresses this.