Re: [COMMITTERS] pgsql: Explicitly bind gettext to the correct encoding on Windows.
| От | Magnus Hagander |
|---|---|
| Тема | Re: [COMMITTERS] pgsql: Explicitly bind gettext to the correct encoding on Windows. |
| Дата | |
| Msg-id | 499821F3.7050004@hagander.net обсуждение исходный текст |
| Ответ на | Re: [COMMITTERS] pgsql: Explicitly bind gettext to the correct encoding on Windows. (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: [COMMITTERS] pgsql: Explicitly bind gettext to the correct encoding on Windows.
|
| Список | pgsql-hackers |
Tom Lane wrote: > mha@postgresql.org (Magnus Hagander) writes: >> Explicitly bind gettext to the correct encoding on Windows. > > I have a couple of objections to this patch. First, what happens if > it fails to find a matching table entry? (The existing answer is > "nothing", but that doesn't seem right.) Second and more critical, > it adds still another data structure that has to be maintained when > the list of encodings changes, and it doesn't even live in the same > file as any existing encoding-information table. > > 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? //Magnus
В списке pgsql-hackers по дате отправления: