On Thu, Sep 8, 2022 at 12:39 PM John Naylor
wrote:
>
> On Fri, Sep 2, 2022 at 3:19 PM Kyotaro Horiguchi
> wrote:
> >
> > At Fri, 2 Sep 2022 13:43:50 +0700, John Naylor
> > wrote in
> > > If there is any doubt about including all of Cf, we could also just
> > > add a branch in wchar.c to
po 12. 9. 2022 v 10:29 odesílatel John Naylor
napsal:
> On Mon, Sep 12, 2022 at 12:44 PM Pavel Stehule
> wrote:
> > This is not a critical issue, really. On second thought, I don't see
> the point in releasing fresh Postgres with this bug, where there is know
> bugfix - and this bugfix should
On Mon, Sep 12, 2022 at 12:44 PM Pavel Stehule wrote:
> This is not a critical issue, really. On second thought, I don't see the
> point in releasing fresh Postgres with this bug, where there is know bugfix -
> and this bugfix should be compatible (at this moment) with 16.
I agree the actual
po 12. 9. 2022 v 7:37 odesílatel John Naylor
napsal:
> On Thu, Sep 8, 2022 at 12:51 PM Pavel Stehule
> wrote:
> >
> >
> >> Does anyone want to advocate for backpatching these missing ranges to
> >> v12 and up? v12 still has a table in-line so trivial to remedy, but
> >> v13 and up use a script,
On Thu, Sep 8, 2022 at 12:51 PM Pavel Stehule wrote:
>
>
>> Does anyone want to advocate for backpatching these missing ranges to
>> v12 and up? v12 still has a table in-line so trivial to remedy, but
>> v13 and up use a script, so these exceptions would likely have to use
>> hard-coded branches
čt 8. 9. 2022 v 7:39 odesílatel John Naylor
napsal:
> On Fri, Sep 2, 2022 at 3:19 PM Kyotaro Horiguchi
> wrote:
> >
> > At Fri, 2 Sep 2022 13:43:50 +0700, John Naylor <
> john.nay...@enterprisedb.com> wrote in
> > > If there is any doubt about including all of Cf, we could also just
> > > add a
On Fri, Sep 2, 2022 at 3:19 PM Kyotaro Horiguchi
wrote:
>
> At Fri, 2 Sep 2022 13:43:50 +0700, John Naylor
> wrote in
> > If there is any doubt about including all of Cf, we could also just
> > add a branch in wchar.c to hard-code the 200B-200F range.
>
> If every way has defect to the similar
On 2022-Sep-02, Kyotaro Horiguchi wrote:
> UnicodeData.txt
> 174:00AD;SOFT HYPHEN;Cf;0;BN;N;
>
> Soft-hyphen seems like not zero-width.. usually...
Soft-hyphen *is* zero width. It should not be displayed. It's just a
marker so that typesetting software knows where to add real
At Fri, 2 Sep 2022 13:43:50 +0700, John Naylor
wrote in
> On Fri, Sep 2, 2022 at 12:17 PM Kyotaro Horiguchi
> wrote:
> > > Including them into unicode_combining_table.h actually worked, but I'm
> > > not sure it is valid to include Cf's among Mn/Me's..
>
> Looking at the definition, Cf means
On Fri, Sep 2, 2022 at 12:17 PM Kyotaro Horiguchi
wrote:
>
> At Thu, 01 Sep 2022 18:22:06 +0900 (JST), Kyotaro Horiguchi
> wrote in
> > At Thu, 1 Sep 2022 15:00:38 +0700, John Naylor
> > wrote in
> > > UnicodeData.txt has this:
> > >
> > > 200B;ZERO WIDTH SPACE;Cf;0;BN;N;
> > >
At Thu, 01 Sep 2022 18:22:06 +0900 (JST), Kyotaro Horiguchi
wrote in
> At Thu, 1 Sep 2022 15:00:38 +0700, John Naylor
> wrote in
> > UnicodeData.txt has this:
> >
> > 200B;ZERO WIDTH SPACE;Cf;0;BN;N;
> > 200C;ZERO WIDTH NON-JOINER;Cf;0;BN;N;
> > 200D;ZERO WIDTH
At Thu, 1 Sep 2022 15:00:38 +0700, John Naylor
wrote in
> On Thu, Sep 1, 2022 at 2:13 PM Pavel Stehule wrote:
> > problem is in bad width of invisible char 200E
>
> I removed this comment in bab982161e since it didn't match the code.
> I'd be interested to see what happened after v12.
>
> -
On Thu, Sep 1, 2022 at 2:13 PM Pavel Stehule wrote:
> problem is in bad width of invisible char 200E
I removed this comment in bab982161e since it didn't match the code.
I'd be interested to see what happened after v12.
- * - Other format characters (general category code Cf in the
Hi
I found some data that are badly formatted in psql
create table foo(a varchar);
insert into foo values('Dětská šperkovnice Goki 15545');
insert into foo values('Tlakoměr Omron Evolv s Bluetooth připojením');
insert into foo values('Řetěz KMC BE08SEP22 stříbrný');
psql older than 12 shows
14 matches
Mail list logo
