| From: | Dave Page <dpage(at)postgresql(dot)org> |
|---|---|
| To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Locale + encoding combinations |
| Date: | 2007-10-09 20:32:42 |
| Message-ID: | 470BE56A.2030509@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I'm working on some code for pgInstaller that will check the locale and
encoding selected by the user are a valid combination.
The changes recently added to initdb (which highlighted the UTF-8 issue
on Windows that Tom posted about) appear to only allow the default
encoding for the locale to be selected. For example, for me that would be:
"English_United Kingdom.1252"
However, setlocale() will also accept other valid combinations on
Windows, which initdb will not, for example:
"English_United Kingdom.28591" (Latin1)
Is there any reason not to accept other combinations that setlocale() is
happy with?
Regards, Dave
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2007-10-09 20:35:03 | Re: Skytools committed without hackers discussion/review |
| Previous Message | Bruce Momjian | 2007-10-09 20:22:26 | Re: Skytools committed without hackers discussion/review |