Re: ERROR: character 0xe3809c of encoding "UTF8" has no equivalent in EUC_JP
От | Tatsuo Ishii |
---|---|
Тема | Re: ERROR: character 0xe3809c of encoding "UTF8" has no equivalent in EUC_JP |
Дата | |
Msg-id | 20110323.105832.497527362714561205.t-ishii@sraoss.co.jp обсуждение исходный текст |
Ответ на | ERROR: character 0xe3809c of encoding "UTF8" has no equivalent in EUC_JP (Kasia Tuszynska <ktuszynska@esri.com>) |
Ответы |
Re: ERROR: character 0xe3809c of encoding "UTF8" has no
equivalent in EUC_JP
|
Список | pgsql-bugs |
> Hi, > I was wondering if this was considered a bug, and if so what were the plans to fix it: http://archives.postgresql.org/pgsql-bugs/2005-08/msg00211.php > > I searched the: pgsql-bug archive and found nothing > I also searched the wiki to do list and found nothing > But I could have missed it. I don't consider it's a bug. We maps "WAVE DASH" of EUC-JP (0xa1c1) to U+FF5E, not U+301C. U+FF5E and U+301C look same, but there are different code point by some reason I don't know. On the other hand EUC-JP has only one code point for WAVE DASH. 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. Same thing can be said to MINUS sign. -- Tatsuo Ishii SRA OSS, Inc. Japan English: http://www.sraoss.co.jp/index_en.php Japanese: http://www.sraoss.co.jp
В списке pgsql-bugs по дате отправления: