form encoding issues

annoying', this comes out as: 'très annoying'... On the other hand, when entering the according URL (http://localhost:/test?input=tr%C3%A8s+annoying) directly, the characters are passed on correctly. Does anyone know how this can be fixed? Any hints much appreciated! Ron Van den Branden

Re: form encoding issues

Hi again, Thank you very much for the quick help; meanwhile I think I found an answer in a post on cocoon-dev: http://markmail.org/message/nm6bnvqztbee4s5o. There is stated that apparently (and counter-intuitively, IMO), 'request parameters are always decoded using ISO-8859-1 ', and that

Re: form encoding issues

Hi Thomas, I'm not much of an expert in encoding matters, and could indeed be happy with ISO-8859-1 instead of UTF-8. However, testing with ISO-8859-1 set as container-encoding, even Arabic input is passed through correctly: ص (Arabic letter 'sad' -

Re: form encoding issues

Hi Andre, On 29/09/2010 12:01, Andre Juffer wrote: Actually, Tomcat does, but Jetty does not (by default, UTF8). According to specification, servlet engine are suppose to decode using ISO-8859-1 by default. I don't see any difference between both. And lo: changing the (over-eager?)

upgrading cocoon-2.1 to FOP-1.0

there who has managed to figure out the necessary steps, and would like to provide step-by-step instructions for upgrading FOP in Cocoon-2.1? Any help much appreciated, Ron -- Ron Van den Branden Wetenschappelijk Attaché Centrum voor Teksteditie en Bronnenstudie (CTB) Koninklijke Academie voor

Re: upgrading cocoon-2.1 to FOP-1.0

Hi Jasha, Ah, that's even more than I asked for ;-). Apologies, for one reason or another I missed the connection with Cocoon-2.1.12-dev. I remember having tried to build it some time ago, but it failed. Op 26/07/2010 13:12, Jasha Joachimsthal schreef: a few weeks ago, I have upgraded FOP

Re: upgrading cocoon-2.1 to FOP-1.0

Ok, Op 26/07/2010 14:19, Jasha Joachimsthal schreef: I have grabbed a fresh checkout, and it works perfectly with FOP-0.95. I have tried to replace the FOP-related jars in %COCOON_HOME%\build\webapp\WEB-INF\lib with those in the most recent FOP distribution, but then I'm hitting following

Re: upgrading cocoon-2.1 to FOP-1.0

for integrating FOP-1.0 in Cocoon-2.1.12-dev source code: Op 26/07/2010 14:56, Ron Van den Branden schreef: Thanks, but no success here... This is what I did: -replace fop-related jars in %COCOON_HOME%\lib\* with updated versions from FOP-1.0 + added missing ones -updated %COCOON_HOME%\lib

Re: upgrading cocoon-2.1 to FOP-1.0

Hi Jasha, Op 26/07/2010 15:47, Jasha Joachimsthal schreef: Cool! Can you create an issue for this describing which dependencies you updated? I'll pick it up then. Done: https://issues.apache.org/jira/browse/COCOON-2295. I hope this is all you need. Kind regards, Ron

aggregating duplicate parameters at sitemap level

with my current cocoon knowledge (not much beyond simple pipeline concepts, ie. no flowscript, actions, XSP...). I recognize this is not strictly a Cocoon problem (and apologize for off-topicality), but hope there may be a Cocoon solution? Thanks for any reaction! Ron Van den Branden