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?) cont

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' - http://www.fileformat.info/info/unicode/c

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: . There is stated that apparently (and counter-intuitively, IMO), 'request parameters are always decoded using ISO-8859-1 ', and that

form encoding issues

Yet, entering a string with accented characters, like e.g. 'très 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 corr

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 --

Re: upgrading cocoon-2.1 to FOP-1.0

work 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

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 erro

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 t

upgrading cocoon-2.1 to FOP-1.0

omeone out 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 Aca

Re: aggregating duplicate parameters at sitemap level

note: I always discourage use-request-parameters, since it can give you problems when using caching pipelines. What alternative do you suggest? Thank you very much, Ron Van den Branden - To unsubscribe, e-mail: [EMAIL PROTECTED]

aggregating duplicate parameters at sitemap level

y a Cocoon problem (and apologize for off-topicality), but hope there may be a Cocoon solution? Thanks for any reaction! Ron Van den Branden - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]