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!mx02.eternal-september.org!feeder.eternal-september.org!news.szaf.org!news.enyo.de!.POSTED!not-for-mail From: Florian Weimer Newsgroups: comp.lang.ada Subject: Re: Exclusive file access Date: Sun, 30 Aug 2015 13:35:16 +0200 Message-ID: <87oahpovpn.fsf@mid.deneb.enyo.de> References: <75714e3f-c047-413d-9aa5-3ff423167863@googlegroups.com> <1440837116.20971.33.camel@obry.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: news.enyo.de 1440934516 17573 192.168.18.20 (30 Aug 2015 11:35:16 GMT) X-Complaints-To: news@enyo.de Cancel-Lock: sha1:bwpeJAz0XRB1t3G7Cd+dXw1zh70= Xref: news.eternal-september.org comp.lang.ada:27640 Date: 2015-08-30T13:35:16+02:00 List-Id: * Dmitry A. Kazakov: > No, I meant Wide_Wide_String. > > Ada's Wide_String is legally UCS-2. Windows is UTF-16. The only full > Unicode string type is Wide_Wide_String. For an Indo-European language > there is no difference, of course. GNAT's Wide_String should be compatible with UTF-16. Wide_Wide_String definitely is not. > Under Linux most applications simply ignore Ada standard and use String > encoded in UTF-8. I suppose that under Linux GNAT calmly passes String file > names as-is, i.e. as UTF-8 [*]. I think GNAT just passes around bytes, it does not care if it's UTF-8 or a legacy encoding. As long as you don't use Wide_String—if you do use that, things get rather messy.