Feedback-ID: ie0a040ee:Fastmail
Message-ID: <7527cb15-911f-4f83-8583-2da11b8d85d5@eisentraut.org>
Date: Mon, 13 Apr 2026 11:21:23 +0200
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Unicode update and some tooling improvements
From: Peter Eisentraut <peter@eisentraut.org>
To: Alexander Borisov <lex.borisov@gmail.com>,
 pgsql-hackers <pgsql-hackers@postgresql.org>
References: <2a668979-ed92-49a3-abf9-a3ec2d460ec2@eisentraut.org>
 <d1c7e27d-54dc-4345-8301-c5f44329131e@gmail.com>
 <1889d17b-e84a-434f-9fea-871ef447ff1e@eisentraut.org>
 <78841a7c-fbab-4b31-b5e2-e40fb504528a@eisentraut.org>
Content-Language: en-US
In-Reply-To: <78841a7c-fbab-4b31-b5e2-e40fb504528a@eisentraut.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: 
 <https://www.postgresql.org/message-id/7527cb15-911f-4f83-8583-2da11b8d85d5%40eisentraut.org>
Precedence: bulk

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.