Backend=UNICODE,client=WIN-1250 - impossible

From: Olaf Frączyk <olaf(at)cbk(dot)poznan(dot)pl>
To: pgsql-general(at)postgresql(dot)org
Subject: Backend=UNICODE,client=WIN-1250 - impossible
Date: 2002-06-11 15:10:13
Message-ID: 1023808213.1622.8.camel@venus
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-jdbc

Hi,
In multibyte manual is a table of possible encodings used by postgresql.
But there is also a table o possible recodings, and if I have data
stored as UNICODE, there is not listed WIN-1250 as client encoding.
Is this documentation bug, or is it really impossible. If it is
impossible, when will it be supported?
Or maybe there is another way to get unicode data from postgres to
display on windows correctly?
Now I have data stored as iso-8859-2 but I want to use unicode.

Please CC me.

Regards,

Olaf Fraczyk

Responses

Browse pgsql-general by date

  From Date Subject
Next Message SERFIOTIs gewrgios 2002-06-11 15:55:24 View String or Representation
Previous Message Darren Ferguson 2002-06-11 15:03:17 Re: "ERROR:" Messages

Browse pgsql-jdbc by date

  From Date Subject
Next Message SERFIOTIs gewrgios 2002-06-11 15:55:24 View String or Representation
Previous Message Barry Lind 2002-06-11 05:39:01 Re: Getting ResultSet using JDBC when calling Stored-Procedures