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-7-bit
Path: 
 g2news2.google.com!news4.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!local02.nntp.dca.giganews.com!nntp.megapath.net!news.megapath.net.POSTED!not-for-mail
NNTP-Posting-Date: Tue, 12 Sep 2006 19:01:27 -0500
From: "Randy Brukardt" <randy@rrsoftware.com>
Newsgroups: comp.lang.ada
References: <45051d37@news.upm.es>
 <45053aec$0$5142$9b4e6d93@newsspool1.arcor-online.net>
Subject: Re: Avatox 1.0: Trouble with encoding in Windows
Date: Tue, 12 Sep 2006 19:01:46 -0500
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1807
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1807
Message-ID: <5ZednRK-0M3K15rYnZ2dnUVZ_o2dnZ2d@megapath.net>
NNTP-Posting-Host: 64.32.209.38
X-Trace: 
 sv3-IQrH6XKS1OlJrQXrOLJunD6+j1J/blnmSfDBzKoueRZldooCRUmH0FKRE8P9Kz62NPIPzxFIUqw9hPC!0u39xnLxnfcfyh7EVF5aqXTPX+GY0ZLce7U6GbuklMF8HCwvRaM70Oh5iT/Vi3un/x9ZBmOgF7Kb!CyvQs27bYZdlAQ==
X-Complaints-To: abuse@megapath.net
X-DMCA-Complaints-To: abuse@megapath.net
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint
 properly
X-Postfilter: 1.3.32
Xref: g2news2.google.com comp.lang.ada:6569
Date: 2006-09-12T19:01:46-05:00
List-Id: <comp.lang.ada>

"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.

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.

                           Randy.