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

From Itagaki Takahiro
Subject Re: ERROR: character 0xe3809c of encoding "UTF8" has no equivalent in EUC_JP
Date
Msg-id AANLkTin3ZH4=FdWC3CP=Nn8wjtJ1cw7UAKqL-k+thD_F@mail.gmail.com
Whole thread Raw
In response to Re: ERROR: character 0xe3809c of encoding "UTF8" has no equivalent in EUC_JP  (Kasia Tuszynska <ktuszynska@esri.com>)
List pgsql-bugs
On Fri, Mar 25, 2011 at 03:33, Kasia Tuszynska <ktuszynska@esri.com> wrote:
> We have a customer in Japan who would be interested in this fix, in the future. Would you like me to enter it as an
officialPostgres bug? 

Not a bug at all -- there are at least 3 versions of "EUCJP" encodings, and
postgres just supports one of them. I think it won't be changed in the near
term. So, you would need to define a CONVERSION for your purpose as of now.

However, I think we could have an extension of conversion procedure set
for Japanese confused encodings out of the core.

--
Itagaki Takahiro

pgsql-bugs by date:

Previous
From: Kris Jurka
Date:
Subject: Re: BUG #5943: jdbc client doesn't omit pg_toast_temp tables from schema views
Next
From: Tatsuo Ishii
Date:
Subject: Re: ERROR: character 0xe3809c of encoding "UTF8" has no equivalent in EUC_JP