On Wednesday 24 March 2004 14:15, Tatsuo Ishii wrote:
> > I received a unicode CSV file from someone (the file was created on a
> > windows system) and I'm trying to import it into postgresql. When it gets
> > to a line that isn't ascii it prints the following error and aborts:
> > "ERROR: copy: line 33, Invalid UNICODE character sequence found
> > (0xd956)". When I
>
> The error messages all. 0xd956 cannot be proper UNICODE (actually
> UTF-8 in case of PostgreSQL) character at all.
I _think_ I've seen something very similar though, with one of the WIN9999
charsets. Can't remember for sure, but it's probably worth checking.
--
Richard Huxton
Archonet Ltd
