----- "Peter Headland" <pheadland@actuate.com> wrote:
> > The COPY command reference page saith
> >
> > Input data is interpreted according to the current client
> encoding,
> > and output data is encoded in the the current client encoding,
> even
> > if the data does not pass through the client but is read from or
> > written to a file.
>
> Rats - I read the manual page twice and that didn't register on my
> feeble consciousness. I suspect that I didn't look beyond the word
> "client", since I knew I wasn't interested in client behavior and I
> was
> speed-reading. On the assumption that I am not uniquely stupid, maybe
> we
> could re-phrase this slightly, with a "for example", and add a
> heading
> "Localization"?
>
> As a general comment, I18N/L10N is a hairy enough topic that it
> merits
> its own heading in any commands where it is an issue.
>
> How about my suggestion to add a means (extend COPY syntax) to
> specify
> encoding explicitly and handle UTF lead bytes - would that be of
> interest?
>
> --
> Peter Headland
> Architect
> Actuate Corporation
>
>
> The COPY command reference page saith
>
> Input data is interpreted according to the current client
> encoding,
> and output data is encoded in the the current client encoding,
> even
> if the data does not pass through the client but is read from or
> written to a file.
>
> Seems clear enough to me.
>
> regards, tom lane
Maybe the link might help?
http://www.postgresql.org/docs/8.4/interactive/multibyte.html
Adrian Klaver
aklaver@comcast.net