[i18n] Xalan replaces encoded characters with entities

Hello, [I tried to Google, but could not find any references to the above; accept my apologies if this has been discussed before, and send me a pointer to that discussion] I have the opposite problem of what Upayavira described a few days ago: all my XML documents are completely in UTF-8, but

Re: Cocoon and Internationalization

På 11. mai. 2004 kl. 02.07 skrev Joerg Heinicke: On 10.05.2004 21:55, Dean West wrote: I have been tasked with internationalization for the company I work for, and since we already use Cocoon in our current appliction - I am thinking that the "I18n Transformer" should do the job? I like the c

Re: [i18n] Xalan replaces encoded characters with entities

På 28. apr. 2004 kl. 00.58 skrev Joerg Heinicke: On 20.04.2004 11:02, Sjur Nørstebø Moshagen wrote: all my XML documents are completely in UTF-8, but Cocoon outputs entities for many non-ascii characters. Although this does not create any badly formatted pages, it does increase the size of the

CForms, XUpdate and xmldb

Hello all, I'm trying to figure out the best way to edit XML document fragments stored in an xml db (eXist). I have been reading through all relevant mails I could find both on this list and on the eXist-open list, but I am still confused. Here are the usecases: Simple case: - an editor should

[CForms]: JXPath not able to add element?

Hello, I was playing around with the XML binding sample (form2xml.flow), when I got the following error: "resource://org/apache/cocoon/forms/flow/javascript/Form.js", line 171: uncaught JavaScript exception: at form2xml (file:/Volumes/Data/Users/sjur/redtest/flow/binding_example.js, Line 39) at