Re: pgsql cannot read utf8 files moved from windows correctly!

From: "Trevor Talbot" <quension(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: pgsql cannot read utf8 files moved from windows correctly!
Date: 2007-12-23 15:39:19
Message-ID: 90bce5730712230739q1d1bf005rb5a243504de66733@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 12/20/07, Martijn van Oosterhout <kleptog(at)svana(dot)org> wrote:
> On Tue, Dec 18, 2007 at 02:53:16PM +0800, bookman bookman wrote:

> > I know that every line of utf8 files is started with "fffe" or "feff"
> > and ended with "\r\n" in windows but not in linux,so the character
> > "1" has a space before it in the error line.

> Err, no. In UTF-16 files it is common to begin the *file* with that
> character, but UTF-8 doesn't have that character anywhere, it's
> illegal. Just stripping them out should be fine.

A BOM is perfectly legal in UTF-8, and it's commonly used as a
signature to indicate the text is UTF-8 instead of another encoding.
But yes, it is at the beginning of the file only.

http://unicode.org/faq/utf_bom.html#29

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Martin Gainty 2007-12-23 16:00:52 Re: pgsql cannot read utf8 files moved from windows correctly!
Previous Message Martijn van Oosterhout 2007-12-23 10:38:21 Re: update pg question?