Return-Path: 
 <cocoon-dev-return-26594-apmail-xml-cocoon-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org
Received: (qmail 11368 invoked by uid 500); 7 May 2002 20:11:56 -0000
Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:cocoon-dev-help@xml.apache.org>
list-unsubscribe: <mailto:cocoon-dev-unsubscribe@xml.apache.org>
list-post: <mailto:cocoon-dev@xml.apache.org>
Reply-To: cocoon-dev@xml.apache.org
Delivered-To: mailing list cocoon-dev@xml.apache.org
Received: (qmail 11356 invoked from network); 7 May 2002 20:11:55 -0000
Message-ID: <3CD8352A.3040906@gmx.de>
Date: Tue, 07 May 2002 22:12:26 +0200
From: Gerhard Froehlich <g-froehlich@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.0rc1) Gecko/20020417
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Cocoon Developer List <cocoon-dev@xml.apache.org>
Subject: normalize encodings notations.
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

Hi,
there are some issues with Xalan and Saxon using different
encoding notations.

Tomcat3.3 + Saxon woes, when you use <encoding>iso8859-1</encoding>
instead of <encoding>ISO-8859-1</encoding>.

Is this our problem or that from the subjacent API like Xalan
or Saxon?

A solution would be a normalization of encoding notations to official
ones.

Greets
Gerhard

-- 

"God put me on this Earth to accomplish a certain number of things.
Right now, I am so far behind I shall never die."


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org