Re: encoding problem

From: jef peeraer <jef(dot)peeraer(at)telenet(dot)be>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: encoding problem
Date: 2006-10-14 09:17:14
Message-ID: 4530AB1A.1050005@telenet.be
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

jef peeraer schreef:
> i never thought i would be bblocked by an encoding problem :-(
> My database is in LATIN1 , i have entries like this in a table called
> gemeenten
> Column | Type | Modifiers
> ---------------+----------+--------------------------------------------------------
>
> id | integer | serial....
> gemeente | text | not null
> postcode | smallint | not null
> provincies_id | integer |
>
> This data is copied from a dump from that table
>
> 9780 Quévy 7040 7
> 9781 Quévy-le-Grand 7040 7
> 9782 Quévy-le-Petit 7040 7
>
> So, the accents are there. But with my web page, which is set to
> ISO-8859-1, i don't get the accents.
> The web-pages are build with XUL, where i set the charset to ISO-8859-1,
> but communication with the server is through XMLHttpRequest.
> Do I have to specify the charset as well in the communication between
> server and client ? Or where else could it go wrong.
>
> jef peeraer
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster
>

thanks for the help. The problem was lying in the fact that use
json_encode procedure from PHP. This procedure requires that the string
to be encoded be in UTF-8 format. So basically, my database stays in
LATIN1 and i set client encoding to UTF-8, as well as all web pages.

jef peeraer

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Markus Schaber 2006-10-14 09:43:44 Re: query optimization with UDFs
Previous Message Michael Fuhr 2006-10-14 09:04:15 Re: time type strange behaviour