Re: Errors in our encoding conversion tables - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Errors in our encoding conversion tables
Date
Msg-id 28825.1449076551@sss.pgh.pa.us
Whole thread Raw
In response to Re: Errors in our encoding conversion tables  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> On Fri, Nov 27, 2015 at 8:54 PM, Tatsuo Ishii <ishii@postgresql.org> wrote:
>> In short, there are number of reasons we cannot simply import the
>> consortium's mapping regarding SJIS (and EUC_JP).

> I haven't seen a response to this point, but it seems important.

I'll defer to Tatsuo-san concerning whether the Far Eastern conversions
should act the way they do.  However, I still think the Cyrillic and
Latin-2 conversions are broken.  There is no reason to question the
Unicode consortium's mappings in those cases AFAIK, and even if somebody
wants to, our current tables fail to round-trip some characters, which
is surely wrong.  (See the "inconsistent reverse conversion" complaints
in the test output in <32464.1448742262@sss.pgh.pa.us>.)

Regardless of that, it's dismaying that we have files in our tree that
claim to produce our mapping tables from authoritative sources, when in
fact those tables were not produced in that way.  This is a documentation
failure even if you consider the actual conversion behavior valid.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Making the C collation less inclined to abort abbreviation
Next
From: Robert Haas
Date:
Subject: Re: Logical replication and multimaster