From: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
---|---|
To: | frederic(at)juliana-multimedia(dot)com |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [GENERAL] Problem with the accents |
Date: | 2001-10-03 01:01:16 |
Message-ID: | 20011003100116I.t-ishii@sra.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
> Tatsuo Ishii wrote:
> >
> > You are definitely inputting ISO 8859-1 characters, not UTF-8. That's
> > the source of your problem.
> >
>
> Hello, In fact, we create and lodge Web sites and we use
> PostgreSQL/Apache/PHP.
>
> I parameterized the encoding in "UNICODE" thinking that it was most
> flexible.
>
> We are French, but we have also Brazilian customers.
So you need to have an Unicode database but your client apps does not
have the capability to input Unicode, right?
Then the only solution would be upgrading to 7.1 and turning on
--enable-unicode-conversion. 7.1 would do the conversion between ISO
8859 and Unicode on the server side.
> According to you, by using PostgreSQL 6.5.3 (the passage to version 7.1
> is planned for the end of the year) can encoding MULE_INTERNAL solve the
> problem ?
Yes. create a MULE_INTERNAL database and use set client_encoding to
whatever...
> Thank you.
>
> PS: Sorry for my English: -)
Me too:-)
--
Tatsuo Ishii
From | Date | Subject | |
---|---|---|---|
Next Message | Barry Lind | 2001-10-03 01:03:26 | Re: LOCK TABLE oddness in PLpgSQL function called via JDBC |
Previous Message | Dave Harkness | 2001-10-03 00:38:40 | Table locking oddness in PLpgSQL function |
From | Date | Subject | |
---|---|---|---|
Next Message | Tatsuo Ishii | 2001-10-03 01:01:22 | Re: Unicode combining characters |
Previous Message | Bruce Momjian | 2001-10-03 00:59:07 | Re: Missing inserts |