| From: | Dave Page <dpage(at)postgresql(dot)org> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Locale + encoding combinations |
| Date: | 2007-10-10 11:48:15 |
| Message-ID: | 470CBBFF.5070701@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marc G. Fournier | 2007-10-10 11:49:40 | Re: [COMMITTERS] pgsql: Added the Skytools extended transaction ID module to contrib as |
| Previous Message | Dave Page | 2007-10-10 11:07:58 | Re: Locale + encoding combinations |