Yes - character encodings are always a nightmare. I'd say the by far best solution (if at all possible) is to change your database configuration and use UTF-8 throughout. Latin-1 is a bad idea, even if you're only planning to support Norwegian in your application. I've lost count of the number of hours I've spent chasing down character encodings-related problems in different applications, but I've learned to always go for UTF-8 everywhere if I can.
/ Petter > -----Original Message----- > From: Bjørn T Johansen [mailto:[EMAIL PROTECTED] > Sent: Thursday, January 24, 2008 9:04 AM > To: [EMAIL PROTECTED] > Subject: Re: UTF-8? > > On Sat, 19 Jan 2008 11:20:18 +0100 > Bjørn T Johansen <[EMAIL PROTECTED]> wrote: > > > I am trying to use PostgresSQL as our database but I have a problem > with character encoding. I am using ISO-8859-1 > > as my encoding but it seems like Continuum insist on using UTF-8, how > can I switch to ISO-8859-1? > > > > > > Regards, > > > > BTJ > > > > --------------------------------------------------------------------- > -------------------------- > > Someone wrote: > > "I understand that if you play a Windows CD backwards you hear > strange Satanic messages" > > To which someone replied: > > "It's even worse than that; play it forwards and it installs Windows" > > --------------------------------------------------------------------- > -------------------------- > > No one knows how to get around this? We are running with ISO-8859-1 as > locale and creates the pgsql db with encoding=latin1... > When I use norwegian letters, it complains that continuum can't convert > my Norwegain character and throws an exception... > If I create the db as UTF-8 or use the included Derby database, I no > longer get an error but I only get question marks back from > the db for the Norwegian letters. > > Can this really be so hard?? > > > BTJ
