Re: pgsql cannot read utf8 files moved from windows correctly! - Mailing list pgsql-general

From Trevor Talbot
Subject Re: pgsql cannot read utf8 files moved from windows correctly!
Date
Msg-id 90bce5730712230739q1d1bf005rb5a243504de66733@mail.gmail.com
Whole thread Raw
In response to Re: pgsql cannot read utf8 files moved from windows correctly!  (Martijn van Oosterhout <kleptog@svana.org>)
List pgsql-general
On 12/20/07, Martijn van Oosterhout <kleptog@svana.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

pgsql-general by date:

Previous
From: Martijn van Oosterhout
Date:
Subject: Re: update pg question?
Next
From: "Martin Gainty"
Date:
Subject: Re: pgsql cannot read utf8 files moved from windows correctly!