public inbox for [email protected]  

help / color / mirror / Atom feed

From: Peter Eisentraut <[email protected]>
To: Alexander Borisov <[email protected]>
To: pgsql-hackers <[email protected]>
Subject: Re: Unicode update and some tooling improvements
Date: Mon, 13 Apr 2026 11:21:23 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

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.

view thread (6+ messages)

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: Unicode update and some tooling improvements
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox