Encoding and i18n

From: Gregory Stark <stark(at)enterprisedb(dot)com>
To: PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Encoding and i18n
Date: 2007-10-05 22:18:21
Message-ID: 87myuxnr2q.fsf@oxford.xeocode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


Reading the commit message about the TZ encoding issue I'm curious why this
isn't a more widespread problem. How does gettext now what encoding we want
messages in? How do we prevent things like to_char(now(),'month') from
producing strings in an encoding different from the database's encoding?

--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Shane Ambler 2007-10-06 00:50:00 Re: [SQL] Why does the sequence skip a number with generate_series?
Previous Message Zdenek Kotala 2007-10-05 20:10:45 Re: Enforcing database encoding and locale match