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-Thread: 103376,a82f86f344c98f79 X-Google-Attributes: gid103376,public X-Google-Language: ENGLISH,ASCII Path: g2news2.google.com!news4.google.com!news.glorb.com!newspeer1.se.telia.net!se.telia.net!masternews.telia.net.!newsb.telia.net.POSTED!not-for-mail From: =?ISO-8859-1?Q?Bj=F6rn_Persson?= User-Agent: Thunderbird 1.5.0.5 (X11/20060808) MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: Avatox 1.0: Trouble with encoding in Windows References: <45051d37@news.upm.es> <45053aec$0$5142$9b4e6d93@newsspool1.arcor-online.net> <5ZednRK-0M3K15rYnZ2dnUVZ_o2dnZ2d@megapath.net> <4507de42@news.upm.es> In-Reply-To: <4507de42@news.upm.es> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Message-ID: Date: Wed, 13 Sep 2006 18:28:00 GMT NNTP-Posting-Host: 83.250.106.238 X-Complaints-To: abuse@telia.com X-Trace: newsb.telia.net 1158172080 83.250.106.238 (Wed, 13 Sep 2006 20:28:00 CEST) NNTP-Posting-Date: Wed, 13 Sep 2006 20:28:00 CEST Organization: Telia Internet Xref: g2news2.google.com comp.lang.ada:6576 Date: 2006-09-13T18:28:00+00:00 List-Id: Manuel Collado wrote: > Sorry, the use of [Wide_]Wide_Strings doesn't imply anything about > encoding. ARM95 3.5.2(3) says: "The predefined type Wide_Character is a character type whose values correspond to the 65536 code positions of the ISO 10646 Basic Multilingual Plane (BMP)." This is essentially unchanged in the draft Ada 2005 standard. Paragraph 3.5.2(3/2) says: "The predefined type Wide_Character is a character type whose values correspond to the 65536 code positions of the ISO/IEC 10646:2003 Basic Multilingual Plane (BMP)." And the next paragraph, 3.1/2, adds: "The predefined type Wide_Wide_Character is a character type whose values correspond to the 2147483648 code positions of the ISO/IEC 10646:2003 character set." This means that a Wide_String is UCS-2LE on a little-endian machine and UCS-2BE on a big-endian machine, and a Wide_Wide_String is UCS-4LE or UCS-4BE. > To solve the problem a translation is required from the original source > file encoding to a specific standard encoding (Unicode?) Unicode is not a character encoding. Unicode defines several encodings. Anyway, the standard encoding you're asking for is Wide_String, according to Randy. (I won't be surprised if Gnat does the translation wrong though.) -- Bj�rn Persson PGP key A88682FD omb jor ers @sv ge. r o.b n.p son eri nu