Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: NLS vs error processing, again
- From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
- To: Peter Eisentraut <peter_e(at)gmx(dot)net>
- Cc: pgsql-bugs(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp>, jw(dot)pgsql(at)sduept(dot)com
- Subject: Re: NLS vs error processing, again
- Date: Thu, 20 Apr 2006 06:55:48 -0400 (EDT)
Peter Eisentraut wrote: > Tom Lane wrote: > > I'm far from an expert on this, but the gettext documentation > > indicates that it tries to translate the .po file contents into > > whatever encoding is implied by LC_CTYPE. > > Correct. That is just one more reason to have server encoding, > LC_COLLATE, and LC_CTYPE matching. In practice, there is hardly a > reason to have LC_COLLATE and LC_CTYPE be different, so the problem > should not be that big. Is there any TODO here? -- Bruce Momjian http://candle.pha.pa.us EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. +
- References:
- Re: NLS vs error processing, again
- From: Peter Eisentraut
- Re: NLS vs error processing, again
- Prev by Date: Re: PGSTAT: bind(2): Can't assign requested address
- Next by Date: Re: BUG #2400: 'Ã' considered invalid UTF-8 character
- Previous by thread: Re: NLS vs error processing, again
- Next by thread: BUG #2375: ALTER COLUMN TYPE on composite types
- Indexes: