[OGo-Users] Umlauts problem after upgrade

[Andreas Gredler]

On Mon, Jan 29, 2007 at 12:18:53PM +0100, Florian Reitmeir wrote:
> On Mon, 29 Jän 2007, Andreas Gredler wrote:
> 
> > Hi,
> > 
> > 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=LATIN1 is set in the init script.
> > Any help greatly appreciated.
> 
> dump your database
> restore your dump

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?

greets Jimmy

-- 
                 Andreas "Jimmy" Gredler 
   ,'"`.         http://www.jimmy.co.at/ | jimmy@g-tec.co.at
  (  grml.org -» Linux Live-CD for texttool-users and sysadmins
   `._,          http://www.grml.org/    | jimmy@grml.org