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

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

From: Tatsuo Ishii <ishii(at)postgresql(dot)org>
To: itagaki(dot)takahiro(at)gmail(dot)com
Cc: ktuszynska(at)esri(dot)com, pgsql-bugs(at)postgresql(dot)org
Subject: Re: ERROR: character 0xe3809c of encoding "UTF8" has no equivalent in EUC_JP
Date: 2011-03-23 04:02:55
Message-ID: 20110323.130255.390000473982295752.t-ishii@sraoss.co.jp (view raw or flat)
Thread:
Lists: pgsql-bugs
>> So if we want to do a round trip conversion between
>> EUC-JP and UTF-8, we have to choose either U+FF5E OR U+301C. We have
>> chosen U+FF5E. If we change the mapping, many existing applications
>> would break.
> 
> I heard a request a few times for an additional one-directional conversion
> from U+301C to EUC-JP (0xa1c1). It should not break existing applications.
> We already have non-round trip conversions for IBM and NEC extended
> characters in SJIS. The policy seems not so strict for me.

Doesn't breaking round-trip conversion between EUC-JP and UTF-8 itself
break backward compatibility?

I think what we can do best here is, adding new encoding and default
conversion.
--
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: Itagaki TakahiroDate: 2011-03-23 04:16:11
Subject: Re: ERROR: character 0xe3809c of encoding "UTF8" has no equivalent in EUC_JP
Previous:From: Itagaki TakahiroDate: 2011-03-23 03:38:26
Subject: Re: ERROR: character 0xe3809c of encoding "UTF8" has no equivalent in EUC_JP

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