Re: Locale + encoding combinations - Mailing list pgsql-hackers

From Dave Page
Subject Re: Locale + encoding combinations
Date
Msg-id 470CBBFF.5070701@postgresql.org
Whole thread Raw
In response to Re: Locale + encoding combinations  (Dave Page <dpage@postgresql.org>)
Responses Re: Locale + encoding combinations
Re: Locale + encoding combinations
List pgsql-hackers
Dave Page wrote:
> Peter Eisentraut wrote:
>> Am Mittwoch, 10. Oktober 2007 schrieb Dave Page:
>>> So is it just a case of us generating a list of matches that may be
>>> Windows specific, or is there more to it than that?
>> You want to peruse src/port/chklocale.c.  There is already explicit Windows 
>> support in there, so maybe you just need to add on your particular cases.
> 
> Yup, found that - thanks. I'll look at updating that list.

OK so I added the appropriate entries (and posted the patch to
-patches), but my original question remains: why can I only select the
*default* encoding for the chosen locale, but not other ones that are
also be valid according to setlocale? Is this a bug, or is there some
technical reason?

/D


pgsql-hackers by date:

Previous
From: Dave Page
Date:
Subject: Re: Locale + encoding combinations
Next
From: "Marc G. Fournier"
Date:
Subject: Re: [COMMITTERS] pgsql: Added the Skytools extended transaction ID module to contrib as