Re: Unicode update and some tooling improvements

18.03.2026 17:20, Andres Freund wrote:
> Hi,
> 
> On 2026-02-26 21:36:08 +0100, 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.
> 
> 
>>  From ef15b16dcef7a3868fc37744d201bb233f8271bd Mon Sep 17 00:00:00 2001
>> From: Peter Eisentraut <peter@eisentraut.org>
>> Date: Thu, 26 Feb 2026 11:36:27 +0100
>> Subject: [PATCH 3/6] Implement unaccent Unicode data update in meson
>>
>> The meson/ninja update-unicode target did not cover the required
>> updates in contrib/unaccent/.  This is fixed now.
> 
> Makes sesne.

[..]

> 
> 
>>  From dd4b5ced419b319c24fa0928180e54d7317e1690 Mon Sep 17 00:00:00 2001
>> From: Peter Eisentraut <peter@eisentraut.org>
>> Date: Thu, 26 Feb 2026 11:38:51 +0100
>> Subject: [PATCH 6/6] Update Unicode data to Unicode 17.0.0
> 
> Looks like 18 is out, any reason to not go straight to that?

18 is currently in alpha, so it may be better to wait until the stable
release in September this year.

https://www.unicode.org/releases/

[..]

>> -UNICODE_VERSION = 16.0.0
>> +UNICODE_VERSION = 17.0.0
> 
> Wonder if we, in a separate change, should put UNICODE_VERSION and
> CLDR_VERSION version in dedicated files (probably just named
> UNICODE_VERSION/CLDR_VERSION) that then could be shared by meson & make.
> 
> 
> Greetings,
> 
> Andres Freund
> 
> 


--
Regards,
Alexander Borisov