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!news4.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!newsfeed00.sul.t-online.de!t-online.de!feeder.news-service.com!zen.net.uk!dedekind.zen.co.uk!newspeer2.se.telia.net!se.telia.net!masternews.telia.net.!newsb.telia.net.POSTED!not-for-mail From: =?UTF-8?B?QmrDtnJuIFBlcnNzb24=?= User-Agent: Thunderbird 1.5.0.4 (X11/20060614) MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: Avatox 1.1: Trouble with encoding in Windows References: <45051d37@news.upm.es> <45053aec$0$5142$9b4e6d93@newsspool1.arcor-online.net> <4505696b@news.upm.es> In-Reply-To: <4505696b@news.upm.es> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Message-ID: Date: Mon, 11 Sep 2006 17:50:20 GMT NNTP-Posting-Host: 83.250.106.238 X-Complaints-To: abuse@telia.com X-Trace: newsb.telia.net 1157997020 83.250.106.238 (Mon, 11 Sep 2006 19:50:20 CEST) NNTP-Posting-Date: Mon, 11 Sep 2006 19:50:20 CEST Organization: Telia Internet Xref: g2news2.google.com comp.lang.ada:6553 Date: 2006-09-11T17:50:20+00:00 List-Id: 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: 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. -- Björn Persson PGP key A88682FD omb jor ers @sv ge. r o.b n.p son eri nu