*Brief Introduction*
There was an extensive discussion about (form) encoding problems using
Cocoon/Jetty/mysql or PostgreSQL, particularly under OS X, obviously
mainly Yves Vindevogel and myself had these problems.
My application is and was running perfectly on Linux with the same
I have no idea ... ;-)
Basically, my problem was solved with a workaround, as described.
I created my database (again) with the latin1 encoding.
When I ask my data with dburl ...?charSet=UTF8, I now get the correct stuff back
I only got this to work with the jdbc2 driver from 7.2 (postgresql)
BTW: when I use ?charSet=latin1 (or iso-8859-1 or macRoman), which is the database encryption, is does NOT work.
On 08 Apr 2004, at 00:43, Yves Vindevogel wrote:
I have no idea ... ;-)
Basically, my problem was solved with a workaround, as described.
I created my database (again) with the
IMHO, yes tested with two platforms as server (OSX and Slackware 9) and 3 client platforms (OSX, Linux and the thing from Redmond)
Even stranger: connecting to the same database gave different results depending on the platform Cocoon was running on.
On 08 Apr 2004, at 00:55, Joerg
Joerg Heinicke wrote:
On 08.04.2004 00:33, Alexander Schatten wrote:
My application is and was running perfectly on Linux with the same
configuration, but destroyed all Umlauts after form send on OS X.
Just curious: This is only dependent on the system where the server is
running? And is
