On Tue, May 5, 2020 at 09:20:39PM +0800, John Naylor wrote:
> Hi Bruce, thanks for working on this again!
>
> +<para>
> +Allow UTF-8 escapes, e.g., E'\u####', in clients that don't use UTF-8
> encoding (Tom Lane)
> +</para>
>
> I believe the term we want here is "Unicode escapes". This patch is
> about the server encoding, which formerly needed to be utf-8 for
> non-ascii characters. (I think the client encoding doesn't matter as
> long as ascii bytes are represented.)
>
> +<para>
> +The UTF-8 characters must be available in the server encoding.
> +</para>
>
> Same here, s/UTF-8/Unicode/.
OK, new text is:
Allow Unicode escapes, e.g., E'\u####', in clients that don't use UTF-8
encoding (Tom Lane)
The Unicode characters must be available in the server encoding.
I kept the "UTF-8 encoding" since that is the only Unicode encoding we
support.
--
Bruce Momjian <br...@momjian.us> https://momjian.us
EnterpriseDB https://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
