| From: | Oswaldo Hernández <listas(at)soft-com(dot)es> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: UTF8 server-side on Win32? |
| Date: | 2006-06-26 14:48:50 |
| Message-ID: | 449FF3D2.3090303@soft-com.es |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>> > The installer for 8.1 will let you pick UNICODE encoding
>> during setup.
>>
>> What if he uses initdb directly?
>
>Then it should be a simple "-E UNICODE", just as on unix.
>
>//Magnus
Hello, I'm the guy that post this question on psql-es-ayuda.
Thanks to Alvaro for forward here.
I would like explain the question:
I can do initdb with '-E UTF8' or '-E UNICODE' on windows without problem.
But the --locale switch do not permit set to 'Spanish_Spain.UNICODE', 'Spanish_Spain.UTF8' or
'Spanish_Spain.65001'.
I put the locale to Spanish_Spain.1252 (Ansi encoding) and seem to work well with database encoding
UTF8.
I'm not an encoding expert but i think that the database encoding and the right side of locale
specification may be the same for a correct work.
Am i wrong, and -E UTF8 may cohabitate with locale windows ansi 1252 without problems?
Thanks
--
*****************************************
Oswaldo Hernández
oswaldo(at)soft-com(dot)es
*****************************************
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martijn van Oosterhout | 2006-06-26 14:48:57 | Re: "Truncated" tuples for tuple hash tables |
| Previous Message | Hannu Krosing | 2006-06-26 14:47:53 | Re: vacuum, performance, and MVCC |