Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search for
  Advanced Search

Re: [PATCHES] Win32 & NLS


  • From: "Magnus Hagander" <mha(at)sollentuna(dot)net>
  • To: "Peter Eisentraut" <peter_e(at)gmx(dot)net>, <pgsql-hackers-win32(at)postgresql(dot)org>, "pgsql-patches" <pgsql-patches(at)postgresql(dot)org>
  • Subject: Re: [PATCHES] Win32 & NLS
  • Date: Sun, 17 Oct 2004 18:16:22 +0200
  • Message-id: <6BCB9D8A16AC4241919521715F4D8BCE456A23(at)algol(dot)sollentuna(dot)se>

>> Which appears to suggest that we should change the locale using
>> putenv() etc, and not using setlocale() at all... Because setlocale()
>> does not support LC_MESSAGES, probably.
>
>This cannot possibly work.  putenv() doesn't change any locale.  The 
>environment variables only serve as a default when you call 
>setlocale() 
>without an actual locale value.  But to enable any locale, you always 
>need to call setlocale() somehow, somewhere.

That was my first thought, too. But it *does* appear to work.

With this patch, I can change lc_messages from
environment-before-startup, from postgresql.conf or using "set
lc_messages='foo'". 
The only main thing I see as being wrong is that it cannot check if the
specified messages were incorrect. If I literally set it to "foo", I get
english without getting any error/warning.

Clearly they don't just serve as defaults on win32. That's the only
conclusion I can draw from the fact that this works, and from the
questions in the FAQ referenced.

See also for example
http://lists.gnu.org/archive/html/bug-gnu-utils/2004-02/msg00091.html


//Magnus



Home | Main Index | Thread Index

Privacy Policy | PostgreSQL Archives hosted by Command Prompt, Inc. | Designed by tinysofa
Copyright © 1996 – 2008 PostgreSQL Global Development Group