Re: BUG #1315: unconvertible BIG5 character 0xf9d8 - Mailing list pgsql-bugs

From Tatsuo Ishii
Subject Re: BUG #1315: unconvertible BIG5 character 0xf9d8
Date
Msg-id 20041112.101636.74754148.t-ishii@sra.co.jp
Whole thread Raw
In response to BUG #1315: unconvertible BIG5 character 0xf9d8  ("PostgreSQL Bugs List" <pgsql-bugs@postgresql.org>)
List pgsql-bugs
> The following bug has been logged online:
>
> Bug reference:      1315
> Logged by:          CN
>
> Email address:      cnliou9@fastmail.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

pgsql-bugs by date:

Previous
From: "PostgreSQL Bugs List"
Date:
Subject: BUG #1315: unconvertible BIG5 character 0xf9d8
Next
From: Fabien COELHO
Date:
Subject: Re: "strange" rule behavior with nextval on new.* fields