Re: Avatox 1.0: Trouble with encoding in Windows

["Marc A. Criley" <mcNOSPAM@mckae.com>]

Stephen Leake wrote:
> Manuel Collado <m.collado@fi.upm.es> writes:
> 
> 
>>1. The ASIS API should provide a way to know the character encoding of
>>the source file (I think it doesn't).
> 
> Please send this suggestion to the ARG, at ada-comment@ada-auth.org;
> they are currently revising the ASIS standard for Ada 2005.

Just to try to drag this thread back to its original topic...

I've found out that the ASIS-for-GNAT that accompanies GNAT GPL 2006 does 
not permit on-the-fly compilation of Ada units using a character set other 
than ASCII.  Largely because there's no way to pass the "-gnatW8" switch 
via the ASIS interface to the compiler.

ASIS can handle such character sets, it's simply that it has to interact 
with the sources via their corresponding tree, ".adt", files.  These are 
generated by specifying the -gnatc and -gnatt options to gnatmake.

For example:

$ gnatmake -c -gnatc -gnatt -gnatW8 bisiesto.adb

AdaCore has already remedied this situation in their current version of 
ASIS-for-GNAT, but which is not yet publically available.

And Avatox 1.2 will be out shortly to handle non-ASCII character sets.

-- Marc A. Criley
-- McKae Technologies
-- www.mckae.com
-- DTraq - Avatox - XIA - XML EZ Out