From: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
---|---|
To: | mss(at)transas(dot)com |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Character encodings... |
Date: | 2000-04-16 04:01:20 |
Message-ID: | 20000416130120U.t-ishii@sra.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> On Fri, Apr 14, 2000 at 03:44:09PM +0900, Tatsuo Ishii wrote:
> > Oh, he is using the multibyte support and expects an automatic code
> > conversion between KOI8-R and UNICODE that is not supported yet.
> Not exactly. If you had a look on my first message, you would see that the
> problem I see that the behaviour is not consistent. Some time this data gets
> through, and sometimes it does not. I'd say that an arbitrary text in KOI8-R
> can hardly be something reasonable in UTF-8, so I'd see that all (yes, ALL) my
> requests would fail (and preferably with correct diagnostics).
Sorry. I don't understand your point. What I wanted to say was KOI8-R
and UTF-8 are totally different encodings (except ASCII part).
> > # make a KOI8-R database
> > $ createdb -E KOI8
> Thanks. I was looking for something like this in man page, but unfortunately
> it does not have this information.
Please look at doc/README.mb.
> > In the next case, he might want to set PGCLIENTENCODING environment
> > variable so that a conversion between KOI8-R and ISO-8859-5
> > automatically performed.
> What are the requirements for this to work?
Please explain your backgrounds. If you need KOI8-R only, you could
forget about ISO-8859-5.
--
Tatsuo Ishii
From | Date | Subject | |
---|---|---|---|
Next Message | Frank Joerdens | 2000-04-16 11:52:48 | To BLOB Or Not To BLOB |
Previous Message | Joseph | 2000-04-16 01:55:20 | Win32 Install |