Re: evil characters #bfef cause dump failure
От | Iain |
---|---|
Тема | Re: evil characters #bfef cause dump failure |
Дата | |
Msg-id | 000a01c4cbc6$ded1a1a0$7201a8c0@mst1x5r347kymb обсуждение исходный текст |
Ответ на | evil characters #bfef cause dump failure (Christian Fowler <spider@viovio.com>) |
Ответы |
Re: evil characters #bfef cause dump failure
|
Список | 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@gmx.net> To: "Iain" <iain@mst.co.jp> Cc: "Tom Lane" <tgl@sss.pgh.pa.us>; "pgsql-admin list" <pgsql-admin@postgresql.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@postgresql.org
В списке pgsql-admin по дате отправления: