Jo Bourne wrote: > Hi, > > We are trying to migrate to cocoon2 from 1.8x. Our app receives xml > content which is MacRoman encoded and cocoon 1.8 has been conveniently > converting this to utf8 on the way out. Cocoon 2 spits the dummy. I can > see plenty of posts on specifying your output encoding in the sitemap, but > how do we specify the input encoding in order for it to be converted as it > is in c1.8? > > and yes we do know it would be best if our content wasn't macroman > encoded, but fixing that isn't a choice. > > thanks in advance > Jo
Hello Jo, you say that your files are working with Cocoon 1.8x and MacRoman, i.e. you had a parser in Cocoon 1.8x which understands MacRoman encoding. If the parser of the Cocoon 2 (normally Xerces 2.0.x) does not understand this encoding (anymore??), you have to search for another one. The parser is the important, not the possible output transformation to utf-8. You can specify the output encoding in the sitemap, but the input encoding is specified in the XML and read by the parser (by default it's utf-8). If the old parser really reads MacRoman and the new one does not, you maybe should use the old one. THere is no other possibility I think. Regards, Joerg -- System Development VIRBUS AG Fon +49(0)341-979-7419 Fax +49(0)341-979-7409 [EMAIL PROTECTED] www.virbus.de --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
