From: | "Iain" <iain(at)mst(dot)co(dot)jp> |
---|---|
To: | "Peter Eisentraut" <peter_e(at)gmx(dot)net> |
Cc: | "pgsql-admin list" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: evil characters #bfef cause dump failure |
Date: | 2004-11-16 10:27:22 |
Message-ID: | 000a01c4cbc6$ded1a1a0$7201a8c0@mst1x5r347kymb |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Hi Peter,
I know that the unicode standards are far from perfect, but I'm wondering
why you consider it a failure.
Is it technical, or just an acceptance thing?
From my personal perspective, I never had any interest in such things as
encodings or internationlization until I started working in Japan, then I
realized what a nightmare it is. I expect you can imagine, but most people
(like me a year ago) couldn't. If everyone was already using unicode, I
don't think we'd have anything to worry about.
regards
Iain
----- Original Message -----
From: "Peter Eisentraut" <peter_e(at)gmx(dot)net>
To: "Iain" <iain(at)mst(dot)co(dot)jp>
Cc: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>; "pgsql-admin list"
<pgsql-admin(at)postgresql(dot)org>
Sent: Tuesday, November 16, 2004 6:43 PM
Subject: Re: [ADMIN] evil characters #bfef cause dump failure
> 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/
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo(at)postgresql(dot)org
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2004-11-16 12:08:18 | Re: evil characters #bfef cause dump failure |
Previous Message | Peter Eisentraut | 2004-11-16 09:43:52 | Re: evil characters #bfef cause dump failure |