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,UTF8
Path: 
 g2news2.google.com!news2.google.com!news.germany.com!newsfeed01.sul.t-online.de!t-online.de!newsfeed.arcor.de!newsspool3.arcor-online.net!news.arcor.de.POSTED!not-for-mail
Newsgroups: comp.lang.ada
Subject: Re: Avatox 1.0: Trouble with encoding in Windows
From: Georg Bauhaus <bauhaus@futureapps.de>
In-Reply-To: <GZYNg.16394$E02.6228@newsb.telia.net>
References: <45051d37@news.upm.es>
	 <45053aec$0$5142$9b4e6d93@newsspool1.arcor-online.net>
	 <5ZednRK-0M3K15rYnZ2dnUVZ_o2dnZ2d@megapath.net>
	 <4507e49f$0$26945$9b4e6d93@newsspool4.arcor-online.net>
	 <GZYNg.16394$E02.6228@newsb.telia.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Organization: #
Message-ID: <1158215676.19219.32.camel@localhost>
Mime-Version: 1.0
X-Mailer: Evolution 2.6.1 
Date: Thu, 14 Sep 2006 08:34:36 +0200
NNTP-Posting-Date: 14 Sep 2006 08:29:26 CEST
NNTP-Posting-Host: d804d6bc.newsspool4.arcor-online.net
X-Trace: 
 DXC=K2PZj0eK:DUmG86`U=_nC_4IUK<Cl32<Q4Fo<]lROoRQFl8W>\BH3YRanU3Vbof<XYTiQOITnENoRFU`4:K;4eRW[cGl\<;0POWM6WHO;HgS1Y
X-Complaints-To: usenet-abuse@arcor.de
Xref: g2news2.google.com comp.lang.ada:6579
Date: 2006-09-14T08:29:26+02:00
List-Id: <comp.lang.ada>

On Wed, 2006-09-13 at 19:28 +0000, Bj=C3=B6rn Persson wrote:


> Theoretically it's better to store the encoding outside the file so that=20
> you can know what encoding to use *before* you start reading the file.=20
> In practice this is usually impossible. [...] Thus it's pretty much neces=
sary to=20
> specify the encoding inside each file, like XML does.

Yes, though Ada offers a standard notion for connecting a compilation
unit with pragmas. You needn't necessarily place them right next to
the source. So perhaps there is yet another option for
interchanging sources between compilers, operating environments,
etc. Somewhat like SGML, which I believe has ESIS for data interchange
(can be used with ASN.1 IIRC), we could adopt an extended
"SRC archive" format. It simply traces encodings, has some checksums,
carries PGP signatures, and so on.

Or use Strings that carry their encoding with them ;-)