Re: Avatox 1.0: Trouble with encoding in Windows

["Björn Persson" <spam-away@nowhere.nil>]

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