Skip site navigation (1) Skip section navigation (2)

Re: ERROR: character 0xe3809c of encoding "UTF8" has no equivalent in EUC_JP

From: Kasia Tuszynska <ktuszynska(at)esri(dot)com>
To: Tatsuo Ishii <ishii(at)postgresql(dot)org>, "itagaki(dot)takahiro(at)gmail(dot)com"<itagaki(dot)takahiro(at)gmail(dot)com>
Cc: "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: ERROR: character 0xe3809c of encoding "UTF8" has no equivalent in EUC_JP
Date: 2011-03-24 18:33:39
Message-ID: 232B5217AD58584C87019E8933556D1102276886E2@redmx2.esri.com (view raw or flat)
Thread:
Lists: pgsql-bugs
Hi, 
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 official Postgres bug?
Sincerely,
Kasia 

-----Original Message-----
From: Tatsuo Ishii [mailto:ishii(at)postgresql(dot)org] 
Sent: Tuesday, March 22, 2011 10:17 PM
To: itagaki(dot)takahiro(at)gmail(dot)come 
Cc: Kasia Tuszynska; pgsql-bugs(at)postgresql(dot)org
Subject: Re: [BUGS] ERROR: character 0xe3809c of encoding "UTF8" has no equivalent 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 more.

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


In response to

Responses

pgsql-bugs by date

Next:From: Josh BerkusDate: 2011-03-24 18:53:38
Subject: Re: BUG #5944: COPY FROM doesn't work with international characters
Previous:From: Heikki LinnakangasDate: 2011-03-24 18:08:28
Subject: Re: Service Wont Start

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group