From: Peter Eisentraut <peter_e@gmx.net>
To: Iain <iain@mst.co.jp>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin list <pgsql-admin@postgresql.org>
Subject: Re: evil characters #bfef cause dump failure
Date: Tue, 16 Nov 2004 10:43:52 +0100
Message-ID: <200411161043.52605.peter_e@gmx.net> (raw)
In-Reply-To: <002b01c4cbb8$975c0df0$7201a8c0@mst1x5r347kymb>
References: <Pine.LNX.4.61.0411150335350.10091@leda.steelsun.com>
<200411160818.54201.peter_e@gmx.net>
<002b01c4cbb8$975c0df0$7201a8c0@mst1x5r347kymb>
Am Dienstag, 16. November 2004 09:45 schrieb Iain:
> That's seems pretty reasonable, though I think that standardizing on
> unicode (and I guess that means UTF-8) is really the way to go. It was
> designed as the universal standard after all.
It may have been designed that way, but it is a failure in practice.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: peter_e@gmx.net, iain@mst.co.jp, tgl@sss.pgh.pa.us
Subject: Re: evil characters #bfef cause dump failure
In-Reply-To: <200411161043.52605.peter_e@gmx.net>
References: <Pine.LNX.4.61.0411150335350.10091@leda.steelsun.com> <200411160818.54201.peter_e@gmx.net> <002b01c4cbb8$975c0df0$7201a8c0@mst1x5r347kymb> <200411161043.52605.peter_e@gmx.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox