| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | "Qingqing Zhou" <zhouqq(at)cs(dot)toronto(dot)edu>, pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: prevent encoding conversion recursive error |
| Date: | 2005-08-14 21:48:14 |
| Message-ID: | 3944.1124056094@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> Am Dienstag, 9. August 2005 04:51 schrieb Tom Lane:
>> which leads to the question "why aren't we using
>> bind_textdomain_codeset() to tell gettext what character set it should
>> produce"?
> That would probably require us to solve the question on how to translate
> PostgreSQL encoding names to OS encoding names.
Yeah, but don't we already have some code for that (or, actually, the
reverse direction) in initdb? It's probably not perfect, but it'd be
a lot better than crashing.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2005-08-14 21:55:20 | Re: prevent encoding conversion recursive error |
| Previous Message | Tom Lane | 2005-08-14 21:47:06 | Re: small proposal: pg_config record flag variables? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2005-08-14 21:55:20 | Re: prevent encoding conversion recursive error |
| Previous Message | Peter Eisentraut | 2005-08-14 21:03:56 | Re: prevent encoding conversion recursive error |