Re: [COMMITTERS] pgsql: Explicitly bind gettext to the correct encoding on Windows. - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [COMMITTERS] pgsql: Explicitly bind gettext to the correct encoding on Windows.
Date
Msg-id 22474.1234718514@sss.pgh.pa.us
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: Explicitly bind gettext to the correct encoding on Windows.  (Magnus Hagander <magnus@hagander.net>)
Responses Re: [COMMITTERS] pgsql: Explicitly bind gettext to the correct encoding on Windows.  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
Magnus Hagander <magnus@hagander.net> writes:
> Tom Lane wrote:
>> What makes more sense to me is to add a table to encnames.c that
>> provides the gettext name of every encoding that we support.

> Do you mean a separate table there, or should we add a new column to one
> of the existing tables?

Whichever seems to make more sense is fine with me.  I just don't want
add-an-encoding maintenance requirements spread across N different
source files.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: [COMMITTERS] pgsql: Explicitly bind gettext to the correct encoding on Windows.
Next
From: Greg Smith
Date:
Subject: Re: The science of optimization in practical terms?