Re: Avatox 1.1: Trouble with encoding in Windows

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

Björn Persson wrote:
> Manuel Collado wrote:
> 
>> My suggestion is that the Avatox encoding issue can be solved by 
>> simply writing non-ASCII characters as XML character references just 
>> when the final XML output is generated.
> 
> 
> It would be much easier to just put the right encoding in the XML 
> declaration. In your case:
> <?xml version="1.0" encoding="windows-1252" ?>
> 
> Then the rest of the file could be exactly as it is now, and Avatox 
> wouldn't have to scan each and every identifier for non-ASCII characters.

Alright!  Alright!  Y'all SHAMED me into it!!    :-)   :-)  :-)

I've been putting off dealing with character encoding for as long as I 
could, but it's time I finally got into it and did things right.

Gimme a little time and I'll get an encoding-friendly version of Avatox out 
as soon as I can--day job and other responsibilities permitting.

Thanks for the beating, I will now became a better person because of it :-)

(Manuel, if you'd be so kind as to send me a standalone compilable example 
of Ada code that uses an alternate character set that I could use as an 
Avatox test case, I would be most grateful.)


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