The one that does not work has following encoding in head
meta content=text/html; charset=ISO-8859-1 http-equiv=Content-Type
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:
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
robby.pelss...@nxp.com wrote:
The one that does not work has
To: users@cocoon.apache.org
Subject: RE: more encoding problems
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
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,
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
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
What does your web.xml look like?
On Thu, Sep 20, 2012 at 2:51 PM, m...@digikartta.net 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
if you are referring to this part, it's like this:
init-param
param-namecontainer-encoding/param-name
param-valueISO-8859-1/param-value
/init-param
!--
Set form encoding. This will be the character set used to decode
request
parameters. If not set the
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, m...@digikartta.net wrote:
if you are referring to this part, it's like this:
init-param
param-namecontainer-**encoding/param-name
