| From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "Andrew Dunstan" <andrew(at)dunslane(dot)net>, "PostgreSQL-development Hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Encoding and i18n |
| Date: | 2007-10-07 00:26:04 |
| Message-ID: | 87hcl3u5wj.fsf@oxford.xeocode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"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. Except in my tests I don't get
any French dates even when the server is started in French mode. I think we
just don't have localizations for those strings yet.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-10-07 01:16:47 | Re: Encoding and i18n |
| Previous Message | Tom Lane | 2007-10-06 18:24:28 | Re: Encoding and i18n |