| From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
|---|---|
| To: | John Naylor <john(dot)naylor(at)enterprisedb(dot)com>, Jacob Champion <pchampion(at)vmware(dot)com> |
| Cc: | "michael(at)paquier(dot)xyz" <michael(at)paquier(dot)xyz>, "pavel(dot)stehule(at)gmail(dot)com" <pavel(dot)stehule(at)gmail(dot)com>, "laurenz(dot)albe(at)cybertec(dot)at" <laurenz(dot)albe(at)cybertec(dot)at>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, "horikyota(dot)ntt(at)gmail(dot)com" <horikyota(dot)ntt(at)gmail(dot)com> |
| Subject: | Re: badly calculated width of emoji in psql |
| Date: | 2021-08-19 18:12:10 |
| Message-ID: | 49ad1fa0-174e-c901-b14c-c484b60907f1@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 16.08.21 22:06, John Naylor wrote:
> Peter, does the combining char table exclude values > 0xFFFF for size
> reasons, correctness, or some other consideration?
I don't remember a reason, other than perhaps making the generated table
match the previous manual table in scope. IIRC, the previous table was
ancient, so perhaps from the days before higher Unicode values were
universally supported in the code.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Dilger | 2021-08-19 18:19:36 | Re: reporting TID/table with corruption error |
| Previous Message | Jesper Pedersen | 2021-08-19 18:04:20 | Re: Middleware Messages for FE/BE |