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,fbb47f3d0d553681
X-Google-NewGroupId: yes
X-Google-Attributes: gida07f3367d7,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news2.google.com!news3.google.com!feeder3.cambriumusenet.nl!feed.tweaknews.nl!87.79.20.105.MISMATCH!news.netcologne.de!ramfeed1.netcologne.de!newsfeed.arcor.de!newsspool3.arcor-online.net!news.arcor.de.POSTED!not-for-mail
Date: Fri, 25 Jun 2010 09:03:56 +0200
From: Georg Bauhaus <rm-host.bauhaus@maps.futureapps.de>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US;
 rv:1.9.1.10) Gecko/20100512 Thunderbird/3.0.5
MIME-Version: 1.0
Newsgroups: comp.lang.ada
Subject: Re: [GNAT-specific] Using the Form parameter/-gnatW switch
References: 
 <15d17632-7377-4c60-9bb2-35f952300d42@w12g2000yqj.googlegroups.com>
In-Reply-To: 
 <15d17632-7377-4c60-9bb2-35f952300d42@w12g2000yqj.googlegroups.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Message-ID: <4c2454dc$0$6991$9b4e6d93@newsspool4.arcor-online.net>
Organization: Arcor
NNTP-Posting-Date: 25 Jun 2010 09:03:57 CEST
NNTP-Posting-Host: 8a5b0171.newsspool4.arcor-online.net
X-Trace: 
 DXC=EQ6UZCJ8jAFlU`@c^jLCbJ4IUK<Cl32<A4Fo<]lROoRA8kF<OcfhCOKg<UoilM3kmHPCY\c7>ejVH@C`m25PF>IO7HTVQ2nH:UF
X-Complaints-To: usenet-abuse@arcor.de
Xref: g2news2.google.com comp.lang.ada:12892
Date: 2010-06-25T09:03:57+02:00
List-Id: <comp.lang.ada>

On 6/25/10 4:08 AM, deadlyhead wrote:
> I've been messing around a bit with files of various encodings, and
> just recently I've become aware of the Form parameter to Open and
> Create and the -gnatW switch for handling character encoding.

(Sometimes I think that Ada designers should, as part of their
"engineering awareness", work in a "web shop" for a few
months.  The experience of working with real encoded data
might make them look again at character encoding, but less,
uhm, condescendingly.  Character encoding (or string
encoding) is a representation issue and should be treated at
this level.  ISO 10646 deals with UTF.  A character is
ubiquitously a fundamental piece of data.

In my dream, then, there is enough motivation to make
character encoding a solid part of the language proper
and thus have Ada be the first language that makes character
representation well defined and easy to use!)

> I'm okay with giving up on this method and using the XML/Ada Unicode
> libraries for the text translation.  It'd be nice if I didn't have to,
> though.

Does GNAT 2010 support the Ada 2012 strings encoding package?

http://www.ada-auth.org/cgi-bin/cvsweb.cgi/ai05s/ai05-0137-1.txt?rev=1.5&raw=Y

Another alternative might be EAstrings (encoding aware strings).
It has an IO child package. It's part of AdaCL at
http://adacl.sourceforge.net/