| From: | Itagaki Takahiro <itagaki(dot)takahiro(at)gmail(dot)com> |
|---|---|
| To: | Kasia Tuszynska <ktuszynska(at)esri(dot)com> |
| Cc: | Tatsuo Ishii <ishii(at)postgresql(dot)org>, "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-25 01:44:20 |
| Message-ID: | AANLkTin3ZH4=FdWC3CP=Nn8wjtJ1cw7UAKqL-k+thD_F@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Fri, Mar 25, 2011 at 03:33, Kasia Tuszynska <ktuszynska(at)esri(dot)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 official Postgres 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuo Ishii | 2011-03-25 02:24:10 | Re: ERROR: character 0xe3809c of encoding "UTF8" has no equivalent in EUC_JP |
| Previous Message | Kris Jurka | 2011-03-24 20:32:27 | Re: BUG #5943: jdbc client doesn't omit pg_toast_temp tables from schema views |