Re: BUG #1315: unconvertible BIG5 character 0xf9d8

From: Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>
To: cnliou9(at)fastmail(dot)fm, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #1315: unconvertible BIG5 character 0xf9d8
Date: 2004-11-12 01:16:36
Message-ID: 20041112.101636.74754148.t-ishii@sra.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> The following bug has been logged online:
>
> Bug reference: 1315
> Logged by: CN
>
> Email address: cnliou9(at)fastmail(dot)fm
>
> PostgreSQL version: 8.0 Beta
>
> Operating system: Linux
>
> Description: unconvertible BIG5 character 0xf9d8
>
> Details:
>
> Sorry for cross posting here after 2 days' silence regarding this issue in
> general list!
>
> My 8.0beta2 database was initialized with option "-E UNICODE". Psql sets
> client encoding to Big5:
>
> database1=# \encoding big5
>
> I get this error when inserting Big5 character 0xf9d8:
>
> WARNING: ignoring unconvertible BIG5 character 0xf9d8

The error message says all. The BIG5 char 0xf9d8 is not considered
legal by PostgreSQL. More techinicaly, the UNICODE --> BIG5 conversion
map (src/backend/utils/mb/Unicode/big5_to_utf8.map) does not have an
entry for 0xf9d8. There are two possible solutions:

1) If there is any "standard confirmance" map including an entry for
0xf9d8, we are happy to replace it with the one we have.

2) you could create your own conversin map including 0xf9d8 using
CREATE CONVERSION command. See docs for more details.
--
Tatsuo Ishii

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Fabien COELHO 2004-11-12 07:30:34 Re: "strange" rule behavior with nextval on new.* fields
Previous Message PostgreSQL Bugs List 2004-11-12 00:55:05 BUG #1315: unconvertible BIG5 character 0xf9d8