Le Lundi 25 Février 2002 12:33, Dave Page a écrit :
> Yes, but my point is that setting the client encoding on the server worked
> for latin, so would the same work for EUC_JP? Following other emails
> though, I assume not because the PCs are already in latin1 and that is the
> big difference?
La
> -Original Message-
> From: Jean-Michel POURE [mailto:[EMAIL PROTECTED]]
> Sent: 25 February 2002 11:25
> To: Dave Page
> Cc: [EMAIL PROTECTED]
> Subject: Re: [pgadmin-hackers] [ODBC] pgAdmin2 UTF-8 support
>
>
> Le Lundi 25 Février 2002 10:55, Dave Page a
> I tried EUC_JP, it does work.
Sorry, I meant it does NOT work.
Le Lundi 25 Février 2002 10:55, Dave Page a écrit :
> Does it matter? I thought it was the client encoding that mattered: I would
> guess that it should be set to EUC_JP.
Yes, it matters. EUC_JP is a unix encoding. It will never display under
Windows.
Jean-Michel
Hmm - interesting idea. We werent able to display or enter hebrew chars in
Pgadmin2 because apparently the VB objects it uses dont support hebrew. Let
me try and I'll get back to you real soon
danny
Le Lundi 25 Février 2002 10:55, vous avez écrit :
> Does it matter? I thought it was the client encoding that mattered: I would
> guess that it should be set to EUC_JP.
I tried EUC_JP, it does work. This is a Japanese encoding for Unixes. We need
its Windows equivalent, if exists. It could be ad
> -Original Message-
> From: Jean-Michel POURE [mailto:[EMAIL PROTECTED]]
> Sent: 25 February 2002 09:42
> To: Dave Page
> Cc: [EMAIL PROTECTED]
> Subject: Re: [pgadmin-hackers] [ODBC] pgAdmin2 UTF-8 support
>
>
> Le Lundi 25 Février 2002 10:23, Dave Pag
Dear Danny,
Could you try pgAdmin2 and enter 'SET CLIENT_ENCODING = ISO-8859-8'. Then try
to display data in pgAdmin2. Does it work?
Information can be found at
http://developer.postgresql.org/docs/postgres/multibyte.html#AEN16680
Cheers,
Jean-Michel POURE
Le Lundi 25 Février 2002 10:23, Dave Page a écrit :
> Cool. Is it possible for you to try a simple test on one of your Japanese
> databases?
I don't knwo the Windows encodings names.
Le Lundi 25 Février 2002 10:02, Dave Page a écrit :
> So, to get this straight in my non multilingual brain, if you set client
> encoding to latin1 then european charsets (i.e. latin based) work perfectly
> in pgAdmin?
Have a look at :
http://www.postgresql.org/idocs/index.php?multibyte.html#AEN
> We have a Unicode hebrew db in PG7.2. Uou dont need to write the functions
> and views in UTF-8 unless you have some
> literals inside the code. We had this issue with Hebrew; so we store all
> the literals as tokens in another table which may have some overhead but
> makes for great flexibili
> -Original Message-
> From: Jean-Michel POURE [mailto:[EMAIL PROTECTED]]
> Sent: 25 February 2002 09:15
> To: Dave Page
> Cc: [EMAIL PROTECTED]
> Subject: Re: [pgadmin-hackers] [ODBC] pgAdmin2 UTF-8 support
>
>
> Le Lundi 25 Février 2002 10:02, Dave Pa
Le Lundi 25 Février 2002 10:02, Dave Page a écrit :
> So, to get this straight in my non multilingual brain, if you set client
> encoding to latin1 then european charsets (i.e. latin based) work perfectly
> in pgAdmin?
Yes.
> So probably we need to _at least_ do something similar for Japanese/Heb
> -Original Message-
> From: Jean-Michel POURE [mailto:[EMAIL PROTECTED]]
> Sent: 25 February 2002 08:51
> To: Dave Page
> Cc: [EMAIL PROTECTED]
> Subject: Re: [pgadmin-hackers] [ODBC] pgAdmin2 UTF-8 support
>
>
> > OK, what about if you select the dat
> OK, what about if you select the data back in pgAdmin - does it then
> display it?
Sure, it does. This is a new feature of PostgreSQL 7.2.
> Also, does SET CLIENT_ENCODING SQL_ASCII; work?
No it does not. "é" is stored as 'i'.
> -Original Message-
> From: Jean-Michel POURE [mailto:[EMAIL PROTECTED]]
> Sent: 25 February 2002 08:39
> To: Dave Page
> Cc: [EMAIL PROTECTED]
> Subject: Re: [pgadmin-hackers] [ODBC] pgAdmin2 UTF-8 support
>
>
> Le Lundi 25 Février 2002 09:29,
Le Lundi 25 Février 2002 09:29, Dave Page a écrit :
> SET CLIENT_ENCODING Latin1;
> INSERT INTO table_foo (field_bar) VALUES ('é'); SELECT field_bar FROM
> table_foo WHERE field_bar='é';
In case of an UTF-8 database,
- schema queries should always be sent in Latin1.
- SQL highlightbox should allo
> -Original Message-
> From: Jean-Michel POURE [mailto:[EMAIL PROTECTED]]
> Sent: 25 February 2002 08:30
> To: Dave Page
> Cc: [EMAIL PROTECTED]
> Subject: Re: [pgadmin-hackers] [ODBC] pgAdmin2 UTF-8 support
>
>
> Le Lundi 25 Février 2002 09:29, Dave Page
Le Lundi 25 Février 2002 09:29, Dave Page a écrit :
> Presumably we should do this in SQL (I don't think you can do it in the
> ODBC connect string can you?). Have you tried in pgAdmin:
>
> SET CLIENT_ENCODING Latin1;
> INSERT INTO table_foo (field_bar) VALUES ('é'); SELECT field_bar FROM
> table_
> -Original Message-
> From: Jean-Michel POURE [mailto:[EMAIL PROTECTED]]
> Sent: 25 February 2002 08:18
> To: Dave Page
> Cc: [EMAIL PROTECTED]
> Subject: Re: [pgadmin-hackers] [ODBC] pgAdmin2 UTF-8 support
>
>
> Dear Dave,
>
> I used pgsql with Pos
: "Jean-Michel POURE" <[EMAIL PROTECTED]>
To: "Hiroshi Inoue" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Sunday, February 24, 2002 11:39 PM
Subject: [ODBC] pgAdmin2 UTF-8 support
Dear friends,
PostgreSQL 7.2 offers extensive
Dear Dave,
I used pgsql with PostgreSQL 7.2 and noticed there was an automatic
translation between UTF-8 <-> Latin characters. This is a new feature of
PostgreSQL 7.2.
So fine :
Suppose we have a Unicode database :
\Encoding Latin1 (\same with \Encoding SQL_ASCII does not work)
INSERT INTO ta
Dear friends,
PostgreSQL 7.2 offers extensive UTF-8 support. In case of an UTF-8 database,
the big news seems that we now have to write function and view definitions in
UTF-8.
The problem is that pgAdmin2, HighlightBox (the colour code editor) and the
result view do not support Unicode by now
23 matches
Mail list logo
