Re: Encoding problem

From: fritz-bayer(at)web(dot)de (Fritz Bayer)
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Encoding problem
Date: 2005-04-21 15:54:41
Message-ID: a9c0aa9e.0504210754.4d721499@posting.google.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

seltenreich(at)gmx(dot)de (Andreas Seltenreich) wrote in message news:<877jixorpl(dot)fsf(at)gate450(dot)dyndns(dot)org>...
> Fritz Bayer schrob:
>
> > The problem is that alls the "ü" characters get displayed as "<FC>".
> >
> > Why is that so?
>
> This could happen when your locale isn't properly set up. If, for
> example, LC_CTYPE is set to C, your pager thinks this character isn't
> printable and tries to do something smart with it. You can display the
> current setup by running "locale".
>
> Does it work when you export LC_CTYPE=de_DE before running psql?
>

I noticed that no locales have been generated and that the variable
was set to C. I created the locales for LATIN1 and ISO8859-15 and set
the variable to the value you suggested.

I tried it and now I get ü instead.

To give you more clues I checked the encoding which seems to be
UNICODE.

show client_encoding;
NOTICE: Current client encoding is 'UNICODE'
SHOW VARIABLE

So I tried to set it to LATIN1 using

\encoding latin1

But now I get

select * from user_requests;
ERROR: Could not convert UTF-8 to ISO8859-1

> regards,
> Andreas
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faq

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Scott Marlowe 2005-04-21 15:59:11 Re: CURRENT_TIMESTAMP vs actual time
Previous Message mmiranda 2005-04-21 15:51:16 Most specific match using between