Re: UTF16 surrogate pairs in UTF8 encoding

On 9/7/10, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> On sön, 2010-08-22 at 15:15 -0400, Tom Lane wrote:
> > > We combine the surrogate pair components to a single code point and
> > > encode that in UTF-8. We don't encode the components separately;
> > that
> > > would be wrong.
> >
> > Oh, OK. Should the docs make that a bit clearer?
>
>
> Done.

This is confusing:

(When surrogate
pairs are used when the server encoding is <literal>UTF8</>, they
are first combined into a single code point that is then encoded
in UTF-8.)

So something else happens if encoding is not UTF8?

I think this part can be simply removed, it does not add anything.

Or say that surrogate pairs are only allowed in UTF8 encoding.
Reason is that you cannot encode 0..7F codepoints with them,
and only those are allowed to be given numerically. But this is
already mentioned before.

--
marko