On Mon, Jan 29, 2007 at 03:46:34PM -0500, Pierre Thibaudeau wrote: > * Windows XP does support UTF8, yet it is not possible (as far as I > know) to define one's locale to have anything to do with UTF8 > (presumably in the sense that UTF8 isn't an aspect of a specific > locale): there is no en_US.UTF8 or fr_CA.UTF8 locales, for instance. > But why should this matter? Say I am entering the data through a > piece of software that works with UTF8, via the ODBC driver. Say > again that I output the data with another software that expects UTF8, > via the JDBC driver. Why does it matter that my system should be > localized in another encoding? Because postgresql relies on OS support to do things like string comparison. Since Windows does not support UTF-8 locales, sorting there with UTF-8 is a bit of a hack, whereas many (some?) Unixes can handle it natively. At some point postgresql will know how to do string comparisons itself ad thus the problem will be solved, but it hasn't happened yet. Have a nice day, -- Martijn van Oosterhout <kleptog@xxxxxxxxx> http://svana.org/kleptog/ > From each according to his ability. To each according to his ability to litigate.
Attachment:
signature.asc
Description: Digital signature
