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=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII X-Google-Thread: 103376,1086bab45b40d4b0 X-Google-Attributes: gid103376,public Path: controlnews3.google.com!news1.google.com!news.glorb.com!news.tele.dk!news.tele.dk!small.news.tele.dk!news-stoc.telia.net!news-stoa.telia.net!telia.net!masternews.telia.net.!newsb.telia.net.POSTED!not-for-mail From: =?ISO-8859-1?Q?Bj=F6rn_Persson?= User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1) Gecko/20031114 X-Accept-Language: sv, en-us MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: UTF-8 in strings - a bug? References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Message-ID: Date: Thu, 06 May 2004 08:34:25 GMT NNTP-Posting-Host: 217.209.116.179 X-Complaints-To: abuse@telia.com X-Trace: newsb.telia.net 1083832465 217.209.116.179 (Thu, 06 May 2004 10:34:25 CEST) NNTP-Posting-Date: Thu, 06 May 2004 10:34:25 CEST Organization: Telia Internet Xref: controlnews3.google.com comp.lang.ada:303 Date: 2004-05-06T08:34:25+00:00 List-Id: Robert I. Eachus wrote: > Hmmmm... The technical answer is that GNAT is not validated on Fedora = > with UTF-8. The practical answer is that with GNAT, you should compile= =20 > using the UTF-8 non-standard mode, if you are using UTF-8. >=20 > But what if you want to validate on Fedora in UTF-8 mode? Then you wil= l=20 > have to modify the libraries to get this "right." A library bug it is then. I don't necessarily want to *validate* in=20 UTF-8 mode, but now that Mr. Krischik has been so kind to invite my=20 parameter handler to AdaCL, I want it to *work* in a multilingual world. = (It's not just Fedora of course. I expect this to happen in all modern=20 Unixoid OSes, and maybe Windows too.) Recompiling is not a workable solution. The encoding isn't known until=20 run time. Software is frequently distributed in precompiled form you=20 know, and the users may use many different encodings. It might even be=20 that different users on the same system use different encodings. So I=20 guess a transcoding library will have to be wrapped around=20 Ada.Command_Line, and probably around Ada.Command_Line.Environment and=20 the standard input, output and error files too. Or could it be possible to get a function Argument(Number : in Positive) = return Wide_Wide_String into Ada 2005? (Besides I couldn't see that "-gnatiw -gnatW8" made any difference.=20 Perhaps they're only for ACT-Gnat? But it doesn't really matter to me.) --=20 Bj=F6rn Persson jor ers @sv ge. b n_p son eri nu