[OGo-Users] Umlauts problem after upgrade

[Florian Reitmeir]

On Mit, 31 J=C3=A4n 2007, Andreas Gredler wrote:

> On Mon, Jan 29, 2007 at 12:18:53PM +0100, Florian Reitmeir wrote:
> > On Mon, 29 J=C3=A4n 2007, Andreas Gredler wrote:
> >=20
> > > Hi,
> > >=20
> > > I've upgraded a server with ogo from debian woody to debian sarge. Ogo
> > > was of course also upgraded. Postgresql is now 7.4.7 and Ogo is
> > > 1.1.svn1851.
> > > If I create a new task or contact umlauts are displayed correctly but
> > > all other umlauts of the previous entries are not displayed correctly.
> > > export PGCLIENTENCODING=3DLATIN1 is set in the init script.
> > > Any help greatly appreciated.
> >=20
> > dump your database
> > restore your dump
>=20
> One problem remains. When I restore the database I get a couple of these
> messages: invalid byte sequence for encoding "UNICODE".
> It seems that the database doesn't get restored correctly because of
> this error (e.g. address table is empty).
> Tried iconv but it didn't help. Did you have the same problem?

then..
edit the dump and remove the line:
CLIENT ENCODING .. on the beginning
and use a tool like "recode" to recode the dump
recode LATIN1..UTF8 <dumpfile>

this should correct the chars ..=20

--=20
Florian Reitmeir