Re: Encoding and i18n

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: pgsql-hackers(at)postgresql(dot)org
Cc: Gregory Stark <stark(at)enterprisedb(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "Andrew Dunstan" <andrew(at)dunslane(dot)net>
Subject: Re: Encoding and i18n
Date: 2007-10-08 10:40:14
Message-ID: 200710081240.14867.peter_e@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Am Sonntag, 7. Oktober 2007 schrieb Gregory Stark:
> "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> > Since nl_langinfo(CODESET) is supposedly determined only by LC_CTYPE, you
> > could argue that strftime's results should be in that encoding
> > regardless,
>
> It seems to me we aren't actually using strftime any more in any case. We
> seem to be using things like _("Monday") instead.

I seem to recall that we don't use strftime *yet*, exactly because of this
sort of issue. This was discussed before the 8.2 release.

--
Peter Eisentraut
http://developer.postgresql.org/~petere/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2007-10-08 10:41:07 Re: Including Snapshot Info with Indexes
Previous Message Gokulakannan Somasundaram 2007-10-08 10:06:48 Re: Including Snapshot Info with Indexes