Re: Avatox 1.0: Trouble with encoding in Windows

[Manuel Collado <m.collado@lml.ls.fi.upm.es>]

Randy Brukardt escribi�:
> "Georg Bauhaus" <bauhaus@futureapps.de> wrote in message
> news:45053aec$0$5142$9b4e6d93@newsspool1.arcor-online.net...
> 
>>Manuel Collado wrote:
>>
>>>1. The ASIS API should provide a way to know the character encoding of
>>>the source file (I think it doesn't).
>>
>>Yes! This will help a lot in avoiding character set issues.
>>And it might help prevent dodgy arguments like the ones presented
>>by implementers against the clever requirement to write the
>>identifier ? in the Ada 2005 library. :-)
> 
> ASIS 99 currently returns identifiers in Wide_Strings. That is enough to
> handle all possible Ada 95 programs. I suspect that the problem is in the
> XML conversion tool not handling Wide_Characters properly and not with ASIS.
> (Or just as likely, the XML processing tools not handling UTF-8 properly.)
> 
> I suspect that the new version of ASIS will provide an option to get
> identifiers in Wide_Wide_Strings.

Sorry, the use of [Wide_]Wide_Strings doesn't imply anything about 
encoding. The Avatox problem appears just with characters with 
codepoints < 256. Example: the character with codepoint 0xC1 is

    0xC1	0x00C1	#	LATIN CAPITAL LETTER A WITH ACUTE

if encoded as ISO-8859-1 (western countries), but it its

    0xC1	0x0391	#	GREEK CAPITAL LETTER ALPHA

if encoded as ISO-8859-7 (Greece). The use of wide_chars just extends 
the codepoint range.

To solve the problem a translation is required from the original source 
file encoding to a specific standard encoding (Unicode?) for strings 
reported via the ASIS API. Or else, don't make a translation, and report 
also the original source code encoding. This way the ASIS application 
can interpret (or simply report) strings in a meaningful way.

> 
> In any case, one of the big advantages of using ASIS over writing your own
> parser is that the resulting program is independent of the character set
> used. So it works with anything supported by your compiler vendor (and still
> does if you change vendors). ASIS code that depends on the input source
> representation (which is not defined by Ada anyway) is probably broken. And
> there is no chance of any sort of agreement on source representations for
> ASIS (or even the naming of them) if there isn't be any for Ada.

I'm not sure to understand you. Some style checks depend on source code 
representation. Like non-uniform casing for identifiers (mixing alpha 
and Alpha in the same source).

Am I missing anything?

> 
>                            Randy.

Regards.
-- 
To reply by e-mail, please remove the extra dot
in the given address:  m.collado -> mcollado