Re: Cforms and Character Encoding

2008-01-23 Thread Peter Sparkes
Thanks Joerg, The problem turned out to be in web.xml I amended init-param param-nameform-encoding/param-name param-valueISO-8859-1/param-value /init-param To init-param param-nameform-encoding/param-name param-valueUTF-8/param-value /init-param

Re: Cforms and Character Encoding

2008-01-23 Thread Tobia Conforto
Peter Sparkes wrote: The problem turned out to be in web.xml I amended param-nameform-encoding/param-name param-valueISO-8859-1/param-value To param-nameform-encoding/param-name param-valueUTF-8/param-value and now everything is in UTF-8 and works properly

Re: Cforms and Character Encoding

2008-01-23 Thread Gabriel Gruber
Peter Sparkes wrote: The problem turned out to be in web.xml I amended param-nameform-encoding/param-name param-valueISO-8859-1/param-value To param-nameform-encoding/param-name param-valueUTF-8/param-value and now everything is in UTF-8 and

Re: Cforms and Character Encoding

2008-01-23 Thread Peter Sparkes
Thanks for the advice I have tested with various versions of IE and Firefox and all' fine Peter Peter Sparkes wrote: The problem turned out to be in web.xml I amended param-nameform-encoding/param-name param-valueISO-8859-1/param-value To

Re: Cforms and Character Encoding

2008-01-23 Thread Joerg Heinicke
On 23.01.2008 03:51, Tobia Conforto wrote: The problem turned out to be in web.xml I amended param-nameform-encoding/param-name param-valueISO-8859-1/param-value To param-nameform-encoding/param-name param-valueUTF-8/param-value and now everything is in

Re: cocoon.context.getRealPath cocoon 2.2

2008-01-23 Thread anil
Hi Carsten Reinhard - Thanks for your replies. Is there any documentation or examples available regarding using the SourceResolver, ideally within flowscript. I can't seem to find any resources on this topic. Many thanks, Anil. -- View this message in context:

outputBufferSize doesn't work on Cocoon 2.1.9?

2008-01-23 Thread Jens Reufsteck
Hi all, I need to process a large file and used a noncaching-pipeline with outputBufferSize=0 on Cocoon 2.1.7. Worked fine - apart from multithreading problems, which made me change to a newer version of Cocoon. On 2.1.9 outputBufferSize doesn't seem to have any effect. Output is always buffered