Re: more encoding problems

2012-09-20 Thread Jos Snellings
Just wanted to have a look. I compared to with what I had, and it is the same. No luck. On Thu, Sep 20, 2012 at 3:18 PM, wrote: > > if you are referring to this part, it's like this: > > container-**encoding > ISO-8859-1 > > > > > form-encoding > UTF-8

Re: more encoding problems

2012-09-20 Thread mika
if you are referring to this part, it's like this: container-encoding ISO-8859-1 form-encoding UTF-8 Or some else setting you are interested in? This works home and this works in another remote server. I also copied the java from working server

Re: more encoding problems

2012-09-20 Thread Jos Snellings
What does your web.xml look like? On Thu, Sep 20, 2012 at 2:51 PM, wrote: > > Also XML-element tags in xsp-files have question marks instead of scands. > I also verified that the database is delivering the right stuff. The same > database used in this (http://88.148.163.59/cocoon/** > palaute_ap

Re: more encoding problems

2012-09-20 Thread mika
Also XML-element tags in xsp-files have question marks instead of scands. I also verified that the database is delivering the right stuff. The same database used in this (http://88.148.163.59/cocoon/palaute_app/linkki/html/1059), works with local copy of cocoon. Updated data, just checked t

Re: more encoding problems

2012-09-20 Thread mika
Hi Jos, yep, that's right, the text seems not to be utf-8. Same problem occurs in another page where the text not working comes from flowscript. 1) No it's not, it's a copy. But you can verify everything is ok in http://88.148.163.59/cocoon/palaute_app/linkki/1059 (database reader). Seems to m

Re: more encoding problems

2012-09-20 Thread Jos Snellings
Hi Mika, Your page declares utf-8 as a character set, but the text you send is not in utf-8. Hence the question mark characters. Question 1: is it the same database that is accessed? (or rather, a copy) Question 2: what is the database url? Cheers, Jos On Thu, Sep 20, 2012 at 9:22 AM, wrote: >

RE: more encoding problems

2012-09-20 Thread mika
Wrong call, that ISO-8859-1 was just a test to ensure this setting would have some meaning. It has, but the scands disappear before serialization, I think. - mika - On Thu, 20 Sep 2012 10:15:16 +0200, Robby Pelssers wrote: Can you check which serializer you're using and did you explicitly

RE: more encoding problems

2012-09-20 Thread Robby Pelssers
Can you check which serializer you're using and did you explicitly set the encoding? http://cocoon.apache.org/2.1/userdocs/default/html-serializer.html http://cocoon.apache.org/2.1/userdocs/xhtml-serializer.html -Original Message- From: m...@digikartta.net [mailto:m...@digikartta.net

RE: more encoding problems

2012-09-20 Thread mika
Yep, I noticed that too. But where it is coming from? Remember, the whole cocoon directory is a copy from old to new. I also copied e.g. Tomcat server.xml same way. - mika - On Thu, 20 Sep 2012 10:03:46 +0200, Robby Pelssers wrote: The one that does not work has following encoding in http

RE: more encoding problems

2012-09-20 Thread Robby Pelssers
The one that does not work has following encoding in Robby -Original Message- From: m...@digikartta.net [mailto:m...@digikartta.net] Sent: Thursday, September 20, 2012 9:23 AM To: users@cocoon.apache.org Subject: more encoding problems Hi, C2.11, I moved my app from one server to

more encoding problems

2012-09-20 Thread mika
Hi, C2.11, I moved my app from one server to another, which resulted some pages to broke that is scands won't encode properly. I have this in my sitemap: You can try this out: Old server http://77.240.23.91/cocoon/palaute_app/linkki/841 works http://77.240.23.91/cocoon/palaut