Yep! The value element may contain UTF-8, with chinese characters or other non ISO-8859 encoding characters. While testing, the
this.startSerializedXMLRecording(XMLUtils.defaultSerializeToXMLFormat(true)); will use ISO-8859 encoding (see the properties given back from XMLUtils). However we should use a property set with the encoding from the document we are transforming. Otherwise this causes UTFDataFormatException for chinese UTF-8 for example. To use xml recording for a cinclude value element did not make sense to me anyways, so I choose to use text recording instead to prevent the problem. Thanks, Marco On Tue, 2004-03-02 at 10:51, Carsten Ziegeler wrote: > Hi Marco, > > I applied the first part (SourceUtil) of your patch. I'm not > sure about the other part (for the CIncludeTransformer). > Can you explain a little bit, why/when this might be necessary? > > Thanks > Carsten > > > -----Original Message----- > > From: Marco Dubbeld [mailto:[EMAIL PROTECTED] > > Sent: Monday, March 01, 2004 12:08 PM > > To: [EMAIL PROTECTED] > > Subject: patch to Enhance CIncludeTrasnformer to handle > > encoding ofparameters > > > > Hi cocoon developers, > > > > 1st - Thank you for making cocoon. Cocoon is good stuff, but > > I guess you know that already. ;) 2nd - I've been using > > cocoon in a little project for a search page (returns > > multilingual results), however found some limitation while > > using the CInclude transformer. I've posted a patch for it under > > > > http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26924 > > > > on 2004-02-13. It had to do with encoding of request > > parameters. The related patch to excalibur sourceresolver has > > already been applied. > > > > Without becoming pushy, just wanted to know if this can be > > applied...... > > > > Thanks, > > Marco > > > >
