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

Re: BUG #4186: set lc_messages does not work

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, "Thomas H(dot)" <me(at)alternize(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #4186: set lc_messages does not work
Date: 2008-12-07 03:24:09
Message-ID: 200812070324.mB73O9m02165@momjian.us (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-hackers
Tom Lane wrote:
> Magnus Hagander <magnus(at)hagander(dot)net> writes:
> > Thomas H. wrote:
> >> so at least that explains the "changed" behaviour. nevertheless, 
> >> LC_MESSAGES seems to be defunct - with the "locale" folder present,
> >> pg always picks the os' language and ignores the lc_message value.
> 
> > This looks like I can reproduce though, at least on cvs head. Did this
> > work for you in previous versions?
> 
> Maybe we were using a different build of gettext in the previous
> releases, one that didn't look at the same info as the current code?
> 
> Anyway the patch mentioned at the start of the thread
> http://archives.postgresql.org/pgsql-patches/2008-02/msg00038.php
> purports to fix this.  It doesn't seem to have gotten reviewed
> though.

Where are we on this?

-- 
  Bruce Momjian  <bruce(at)momjian(dot)us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

In response to

Responses

pgsql-hackers by date

Next:From: Bruce MomjianDate: 2008-12-07 03:26:13
Subject: Re: BUG #4186: set lc_messages does not work
Previous:From: Bruce MomjianDate: 2008-12-06 23:57:29
Subject: Re: [PATCH] allow has_table_privilege(..., 'usage') on sequences

pgsql-bugs by date

Next:From: Bruce MomjianDate: 2008-12-07 03:26:13
Subject: Re: BUG #4186: set lc_messages does not work
Previous:From: John R PierceDate: 2008-12-07 02:08:13
Subject: Re: question/suggestion Message-id: <493823B5.1030400@hogranch.com>

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group