| 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-09 21:38:47 |
| Message-ID: | 470BF4E7.7050107@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut wrote:
> Dave Page wrote:
>> Is there any reason not to accept other combinations that setlocale()
>> is happy with?
>
> setlocale() sets the locale. How does it "accept" a "combination"?
>
setlocale(LC_CTYPE, "English_United Kingdom.65001")
will return null (and not change anything) because it doesn't like the
combination of the locale and that encoding (UTF-8).
setlocale(LC_CTYPE, "English_United Kingdom.1252")
will return "English_United Kingdom.1252" and set the locale accordingly
because WIN1252 is a valid encoding for that locale. Similarly, LATIN1
and numerous other encodings are accepted in combination with that locale.
Should initdb allow any combination that setlocale() accepts, or should
it *only* accept the default encoding for the specified locale?
/D
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2007-10-09 21:44:22 | Re: ECPG regression tests |
| Previous Message | Pavel Stehule | 2007-10-09 21:36:28 | Re: some points for FAQ |