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!aioe.org!.POSTED!not-for-mail From: "Dmitry A. Kazakov" Newsgroups: comp.lang.ada Subject: Re: UTF-8 Output and "-gnatW8" Date: Tue, 29 Mar 2016 09:44:35 +0200 Organization: Aioe.org NNTP Server Message-ID: References: <35689862-61dc-4186-87d3-37b17abed5a2@googlegroups.com> <3a65e71c-41ee-49eb-916d-c0be8be9abc6@googlegroups.com> <6406289c-06a8-46d1-a633-8a1c8a22f79b@googlegroups.com> NNTP-Posting-Host: bqgfK7NL3xTHnr0WRaLl4g.user.gioia.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 X-Notice: Filtered by postfilter v. 0.8.2 Xref: news.eternal-september.org comp.lang.ada:29918 Date: 2016-03-29T09:44:35+02:00 List-Id: On 29/03/2016 00:48, Michael Rohan wrote: > My approach is to encode myself and write the encoded Character via > Text_IO, Which is a bad idea, you know. Text_IO is not guaranteed to support UTF-8 encoding. Actually rather the opposite since Character is declared Latin-1. You should use Stream_IO instead of Text_IO. > It does, however, feel like there is something missing where it's > "difficult" to have a Wide_String literal without having to have extra > meta data for compiler (-gnatW8) or having a relatively cumbersome > concatenation of Wide_Character's based on code points. Why don't you use UTF-8 strings instead? -- Regards, Dmitry A. Kazakov http://www.dmitry-kazakov.de