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,FREEMAIL_FROM autolearn=unavailable autolearn_force=no version=3.4.4 X-Received: by 10.66.118.37 with SMTP id kj5mr3394842pab.17.1385089345199; Thu, 21 Nov 2013 19:02:25 -0800 (PST) X-Received: by 10.49.24.175 with SMTP id v15mr307240qef.16.1385089345131; Thu, 21 Nov 2013 19:02:25 -0800 (PST) Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!news.eternal-september.org!news.eternal-september.org!feeder.eternal-september.org!news.glorb.com!y3no11078672pbx.0!news-out.google.com!z9ni97qaj.0!nntp.google.com!i2no1308921qav.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Thu, 21 Nov 2013 19:02:24 -0800 (PST) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=97.123.206.209; posting-account=lJ3JNwoAAAAQfH3VV9vttJLkThaxtTfC NNTP-Posting-Host: 97.123.206.209 References: <73e0853b-454a-467f-9dc7-84ca5b9c29b2@googlegroups.com> <1ghx537y5gbfq.17oazom68d4n6.dlg@40tude.net> <5bf1b290-70bc-4240-b27c-120ce6b0b840@googlegroups.com> <7464679c-6b98-4e23-a337-83b671473553@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <672ce4f6-8c65-43b5-b04b-a7b858205af8@googlegroups.com> Subject: Re: strange behaviour of utf-8 files From: Shark8 Injection-Date: Fri, 22 Nov 2013 03:02:25 +0000 Content-Type: text/plain; charset=ISO-8859-1 Xref: news.eternal-september.org comp.lang.ada:17762 Date: 2013-11-21T19:02:24-08:00 List-Id: On Thursday, November 21, 2013 6:03:29 PM UTC-7, Randy Brukardt wrote: > > P.S. Truth-in-advertising: Janus/Ada *only* takes Latin-1 input; it has no > support for any other encoding (of course it supports Wide_String at > runtime). That will have to change as we migrate to Ada 2012, but it > probably will be a while before that happens (not a lot of demand). Not a lot of demand for UTF-8, or not a lot of demand for Ada-2012 [from the customers]? (Also, would having a package aspect declaring that the /contents/ are to be read as UTF-8 [or any recognized encoding] be a possible workable solution to this problem? -- then you could have a package of String-constants of the proper encoding.)