Message-ID: <85329793af3fd24fd331a0a3b29b0e4784e767a4.camel@j-davis.com>
Subject: Re: Pre-proposal: unicode normalized text
From: Jeff Davis <pgsql@j-davis.com>
To: Peter Eisentraut <peter@eisentraut.org>, Robert Haas
 <robertmhaas@gmail.com>
Cc: pgsql-hackers@postgresql.org
Date: Fri, 27 Oct 2023 14:15:00 -0700
In-Reply-To: <c5e9dac884332824e0797937518da0b8766c1238.camel@j-davis.com>
References: <f30b58657ceb71d5be032decf4058d454cc1df74.camel@j-davis.com>
	 <33a31c45-2e80-1270-771a-b75f3920a5ec@eisentraut.org>
	 <CA+TgmoYHEv_-rsSbpfbByUVr6_VVW-mDghfEK3oTcvvEm+0NYQ@mail.gmail.com>
	 <3941663a8e2f185d6acbbbc4f172c41dd3cfb6fe.camel@j-davis.com>
	 <CA+TgmoYzYR-yhU6k1XFCADeyj=Oyz2PkVsa3iKv+keM8wp-F_A@mail.gmail.com>
	 <96c0173c5156d365e132ec29e4873237be565743.camel@j-davis.com>
	 <fe5d9163-462b-4da3-a87e-b0247df0081b@eisentraut.org>
	 <CA+TgmoaJoECzK-rzMBmMktBfEVMAfLmtG8PdmHfq2UYRoHvsmg@mail.gmail.com>
	 <2bab90239c5264fa9a87372c16bbf8759c8f9e64.camel@j-davis.com>
	 <6c78e772-0c1b-4a8f-ab14-d673a086d35e@eisentraut.org>
	 <c5e9dac884332824e0797937518da0b8766c1238.camel@j-davis.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.44.4-0ubuntu2 
MIME-Version: 1.0
Archived-At: 
 <https://www.postgresql.org/message-id/85329793af3fd24fd331a0a3b29b0e4784e767a4.camel%40j-davis.com>
Precedence: bulk

On Mon, 2023-10-16 at 20:32 -0700, Jeff Davis wrote:
> On Wed, 2023-10-11 at 08:56 +0200, Peter Eisentraut wrote:
> > We need to be careful about precise terminology.=C2=A0 "Valid" has a
> > defined=20
> > meaning for Unicode.=C2=A0 A byte sequence can be valid or not as UTF-
> > 8.=C2=A0
> > But=20
> > a string containing unassigned code points is not not-"valid" as
> > Unicode.
>=20
> New patch attached, function name is "unicode_assigned".

I plan to commit something like v3 early next week unless someone else
has additional comments or I missed a concern.

Regards,
	Jeff Davis