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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [COMMITTERS] pgsql: Explicitly bind gettext to the correct encoding on Windows.
Date: 2009-02-15 17:21:54
Message-ID: 22474.1234718514@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Magnus Hagander <magnus(at)hagander(dot)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

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2009-02-15 18:28:48 pgsql: Minor wordsmithing.
Previous Message Magnus Hagander 2009-02-15 14:08:51 Re: [COMMITTERS] pgsql: Explicitly bind gettext to the correct encoding on Windows.

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Smith 2009-02-15 18:16:32 Re: The science of optimization in practical terms?
Previous Message Magnus Hagander 2009-02-15 14:08:51 Re: [COMMITTERS] pgsql: Explicitly bind gettext to the correct encoding on Windows.