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=-0.3 required=5.0 tests=BAYES_00, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,782076a3676d5d3e X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-09-25 16:14:46 PST Path: archiver1.google.com!newsfeed.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!cpk-news-hub1.bbnplanet.com!cambridge1-snf1.gtei.net!news.gtei.net!bos-service1.ext.raytheon.com!dfw-service2.ext.raytheon.com.POSTED!not-for-mail Message-ID: <3BB10FE3.EC3B3F8B@raytheon.com> From: Mark Johnson Reply-To: mark_h_johnson@raytheon.com X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.4.6-3.1smp i686) X-Accept-Language: en MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: Text_IO on WinNT problem References: <3BB0AAFD.9F006F92@icn.siemens.de> <9oqfkg$a2g1@news.cis.okstate.edu> <3BB0D164.A45229AE@adaworks.com> <9oqo67$8a21@news.cis.okstate.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 25 Sep 2001 18:14:43 -0500 NNTP-Posting-Host: 192.27.48.41 X-Complaints-To: news@ext.ray.com X-Trace: dfw-service2.ext.raytheon.com 1001459685 192.27.48.41 (Tue, 25 Sep 2001 18:14:45 CDT) NNTP-Posting-Date: Tue, 25 Sep 2001 18:14:45 CDT Organization: Raytheon Company Xref: archiver1.google.com comp.lang.ada:13373 Date: 2001-09-25T18:14:43-05:00 List-Id: Larry Kilgallen wrote: > In article <9oqo67$8a21@news.cis.okstate.edu>, David Starner writes: > > > As I pointed out, GNAT can't read in UTF-16LE using Wide_Text_IO. > > Why is that ? (asked by somebody who does not know GNAT) A quick look at the GNAT reference manual describes six different encoding schemes - none of which appear to look like UTF-16LE. I don't have enough background to tell if one of the following matches UTF-16LE or not.... After reading the description that goes with each one, my guess is not. `h' Hex ESC encoding `u' Upper half encoding `s' Shift-JIS encoding `e' EUC Encoding `8' UTF-8 encoding `b' Brackets encoding I'll assume the original author may have already gone down that path. Another idea - if UTF-16LE is a series of 16 bit values, you could read the file as a series of 16 bit integers & convert it into something you can use the hard way. Another alternative is to request the enhancement (assuming ACT support). --Mark