Re: ERROR: character 0xe3809c of encoding "UTF8" has no equivalent in EUC_JP - Mailing list pgsql-bugs

From Kasia Tuszynska
Subject Re: ERROR: character 0xe3809c of encoding "UTF8" has no equivalent in EUC_JP
Date
Msg-id 232B5217AD58584C87019E8933556D1102276886E2@redmx2.esri.com
Whole thread Raw
In response to Re: ERROR: character 0xe3809c of encoding "UTF8" has no equivalent in EUC_JP  (Tatsuo Ishii <ishii@postgresql.org>)
Responses Re: ERROR: character 0xe3809c of encoding "UTF8" has no equivalent in EUC_JP  (Itagaki Takahiro <itagaki.takahiro@gmail.com>)
Re: ERROR: character 0xe3809c of encoding "UTF8" has no equivalent in EUC_JP  (Tatsuo Ishii <ishii@postgresql.org>)
List pgsql-bugs
Hi,=20
We have a customer in Japan who would be interested in this fix, in the fut=
ure. Would you like me to enter it as an official Postgres bug?
Sincerely,
Kasia=20

-----Original Message-----
From: Tatsuo Ishii [mailto:ishii@postgresql.org]=20
Sent: Tuesday, March 22, 2011 10:17 PM
To: itagaki.takahiro@gmail.come=20
Cc: Kasia Tuszynska; pgsql-bugs@postgresql.org
Subject: Re: [BUGS] ERROR: character 0xe3809c of encoding "UTF8" has no equ=
ivalent in EUC_JP

> Agreed if the encoding is added as an user-defined encoding.
> I don't want to add built-in encodings only for Japanese language any mor=
e.

I do not agree here. Adding one more encoding/conversion is not big
deal.

Anyway these soltions would come to be real after one or two releases
at the earliest. The realistic solution available today is replacing
default conversion for EUC-JP and UTF-8.
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp

pgsql-bugs by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Service Wont Start
Next
From: Josh Berkus
Date:
Subject: Re: BUG #5944: COPY FROM doesn't work with international characters