Re: Unicode update and some tooling improvements

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: Alexander Borisov <lex(dot)borisov(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Unicode update and some tooling improvements
Date: 2026-03-18 12:47:38
Message-ID: 1889d17b-e84a-434f-9fea-871ef447ff1e@eisentraut.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jacob Champion 2026-03-18 13:01:45 Re: Serverside SNI support in libpq
Previous Message Nazir Bilal Yavuz 2026-03-18 12:44:18 Re: meson vs. llvm bitcode files