From: Peter Eisentraut <peter_e@gmx.net>
To: Iain <iain@mst.co.jp>
Cc: pgsql-admin list <pgsql-admin@postgresql.org>
Subject: Re: evil characters #bfef cause dump failure
Date: Tue, 16 Nov 2004 13:08:18 +0100
Message-ID: <200411161308.18780.peter_e@gmx.net> (raw)
In-Reply-To: <000a01c4cbc6$ded1a1a0$7201a8c0@mst1x5r347kymb>
References: <Pine.LNX.4.61.0411150335350.10091@leda.steelsun.com>
<200411161043.52605.peter_e@gmx.net>
<000a01c4cbc6$ded1a1a0$7201a8c0@mst1x5r347kymb>
Am Dienstag, 16. November 2004 11:27 schrieb Iain:
> I know that the unicode standards are far from perfect, but I'm wondering
> why you consider it a failure.
If it were a success, then everyone would be using it and we wouldn't have
this discussion. Certainly, Unicode is reasonable and the best option in
many cases. But the original idea of replacing all other character sets
won't really happen anytime soon. Since you work in Japan, I would think you
know about the problems, since much of the technical opposition comes from
there.
--
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
Subject: Re: evil characters #bfef cause dump failure
In-Reply-To: <200411161308.18780.peter_e@gmx.net>
References: <Pine.LNX.4.61.0411150335350.10091@leda.steelsun.com> <200411161043.52605.peter_e@gmx.net> <000a01c4cbc6$ded1a1a0$7201a8c0@mst1x5r347kymb> <200411161308.18780.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