Re: Unicode update and some tooling improvements - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Unicode update and some tooling improvements
Date
Msg-id 7527cb15-911f-4f83-8583-2da11b8d85d5@eisentraut.org
Whole thread Raw
In response to Re: Unicode update and some tooling improvements  (Peter Eisentraut <peter@eisentraut.org>)
List pgsql-hackers
On 20.03.26 08:50, Peter Eisentraut wrote:
> On 18.03.26 13:47, Peter Eisentraut wrote:
>> On 13.03.26 11:11, Alexander Borisov wrote:
>>> 26.02.2026 23:36, Peter Eisentraut wrote:
>>>> This is the annual update of the Unicode data.  I also worked a bit 
>>>> on the tooling.  The update-unicode target under meson did not 
>>>> update the data in contrib/unaccent/, so I added that.  I also fixed 
>>>> a Python deprecation warning in the generation script and made some 
>>>> light changes in the surrounding documentation.
>>>
>>> Installed, tested, checked it out.
>>> I hope I'm not late.
>>>
>>> "[PATCH 3/6] Implement unaccent Unicode data update in meson"
>>>
>>> The idea of raising the minimum Meson version is good.
>>> But it seems like we can do without raising the version.
>>> As I understand it, the minimum version is being raised because of
>>> .replace(), but it can be successfully replaced here with the following
>>> construct:
>>> cldr_version_dashed = '-'.join(CLDR_VERSION.split('.'))
>>> url = cldr_baseurl.format(cldr_version_dashed, f)
>>
>> Good idea.  I committed it that way, without a meson version change 
>> for the moment.
> 
> I have committed the rest of this patch set, except the CLDR version 
> change, for which I will wait until the next release expected in April, 
> as usual.

I don't think there is a CLDR 49 release coming soon (as I'm inferring 
from the cadence of tags in their Git repository), so I have committed 
the update to 48.2.




pgsql-hackers by date:

Previous
From: Julien Rouhaud
Date:
Subject: Re: proposal - queryid can be used as filter for auto_explain
Next
From: SATYANARAYANA NARLAPURAM
Date:
Subject: Bug: COPY FORMAT JSON includes generated columns unlike text/CSV