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,1b78051e65d4576a
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 2004-02-27 05:58:31 PST
Path: 
 archiver1.google.com!news2.google.com!news.maxwell.syr.edu!newsfeed.icl.net!feed.news.tiscali.de!newsfeed.stueberl.de!news2.telebyte.nl!news.jgaa.com!news.hacking.dk!pnx.dk!munin.nbi.dk!not-for-mail
From: Jacob Sparre Andersen <sparre@nbi.dk>
Newsgroups: comp.lang.ada
Subject: Character encoding (Was: types and non-contigous ranges)
Date: 27 Feb 2004 14:58:29 +0100
Organization: Munin
Sender: sparre@sparre.crs4.it
Message-ID: <plu11c7hfe.fsf_-_@sparre.crs4.it>
References: <403e001b$0$144$edfadb0f@dread11.news.tele.dk>
 <plk72996sl.fsf@sparre.crs4.it>
 <403ef7ec$0$128$edfadb0f@dread11.news.tele.dk>
 <ply8qo7k3z.fsf@sparre.crs4.it>
 <403f4459$0$173$edfadb0f@dread11.news.tele.dk>
NNTP-Posting-Host: 80.241.165.38
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Trace: munin.grove.home 1077890310 16311 80.241.165.38 (27 Feb 2004 13:58:30
 GMT)
X-Complaints-To: sparre@munin.nbi.dk
NNTP-Posting-Date: Fri, 27 Feb 2004 13:58:30 +0000 (UTC)
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2
Xref: archiver1.google.com comp.lang.ada:5894
Date: 2004-02-27T14:58:29+01:00
List-Id: <comp.lang.ada>

Erlo Haugen skrev:
> Jacob Sparre Andersen skrev:

> > That is probably because you and your compiler aren't in complete
> > agreement about which character encoding you are using.  If the
> > compiler expects you to use ISO-8859-1 (which is very likely) and
> > you are actually using UTF-8 (which I would guess from the error
> > message), then the compiler will not read what you see as "�" as
> > "�" but as a sequence of two other characters.
>
> In the source?

Yes.

> type Valid_Characters is ('0', '1', '2', ... '9',
>                            'A', 'B', 'C', ... '�'); <<<<-----this is
> where I get the error.

Yes.

> How do I get in sync with the compilers idea of which encoding we
> use?

It depends on which compiler you use.

If you are working on a Unix system, I think the command `locale`
should reveal which character encoding your system in general uses
(for your account).

If you use GNAT as you compiler, then it as the standard expects the
code to be coded in ISO-8859-1, but there are command line argumente
for making it work with other encodings.  I think it is the "-gnati?"
flags, but I am not sure, and I can't find a copy of the GNAT manual.

Jacob
-- 
�Fuck amerikansk kulturimperialisme!� - graffiti p� N�rrebro