Return-Path: Delivered-To: apmail-xml-cocoon-users-archive@xml.apache.org Received: (qmail 88992 invoked by uid 500); 12 Jul 2002 15:22:22 -0000 Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-users@xml.apache.org Delivered-To: mailing list cocoon-users@xml.apache.org Received: (qmail 88910 invoked from network); 12 Jul 2002 15:22:21 -0000 Message-ID: <3D2EF462.7090703@gmx.de> Date: Fri, 12 Jul 2002 17:23:14 +0200 From: Joerg Heinicke User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020529 X-Accept-Language: de-de, de, en, en-us MIME-Version: 1.0 To: cocoon-users@xml.apache.org Subject: Re: encoding problem with xslt References: <200207121417.16592.tschmid@novocron.de> <076001c229ad$3a538bb0$5e3965c1@ifb.interfacebusiness.de> <3D2EEB9C.8060500@gmx.de> <07f201c229b5$68394bc0$5e3965c1@ifb.interfacebusiness.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hmm, I didn't test it a long time and didn't find a correlating bug by a short view on Xalan bug list. It was a bug in our application that "m�" was "transformed" to "mü". (For people with different encoding: u umlaut ==> A+~ and 1/4.) I had in mind (and written in our bugzilla) that it was a Xalan bug, maybe that's wrong. It sounds a bit like the description of the original post on this thread. At least we solved it with POST form. Joerg Jens Lorenz wrote: > ----- Original Message ----- > From: "Joerg Heinicke" > To: > Sent: Friday, July 12, 2002 4:45 PM > Subject: Re: encoding problem with xslt > > > >>>If anyone has some more ideas on this topic (non-ISO-8859-1 characters >>>within URIs), I would greatly appreciate some more input. >>>Conclusion for me is to avoid such characters in URIs. But this does >>>not get easily into the heads of our customers and users. (e.g. file >>>names) >> >>According to the old Xalan bug, we used forms with javascript. But this >>doesn't solve the problem generally, only our special use case. >> >>Joerg > > Joerg, > > > which Xalan bug are you referring to ? I browsed the list of open bugs, > but only found related bugs. > IMHO this is not a bug, but a lack of specification. W3C has a draft > about an IRI (internationalized URI), but until this gets adopted > and implemented we'll have to deal with the mess. > > > > Jens -- System Development VIRBUS AG Fon +49(0)341-979-7419 Fax +49(0)341-979-7409 joerg.heinicke@virbus.de www.virbus.de --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. To unsubscribe, e-mail: For additional commands, e-mail: