On 2026-Oct-07, Nazir Bilal Yavuz wrote: > So, my solution is switching to using nls.json files instead > of nls.mk files and having a Perl script so that the autoconf system > can parse these nls.json files and read them as nls.mk files as > before. So the big picture is: > > - We will switch nls.mk files with nls.json files. > - autoconf will read these nls.json files with the help of perl script. > - meson will read nls.json files and will use a helper Python script > to generate *.pot files. > - meson will have init-po and update-po targets and also singular > targes like psql-init-po.
Hmm, so the source files would be .json and we generate .mk files as derivative artifacts? I don't know, that sounds potentially nightmarish. Isn't it more convenient to generate a JSON file from the nls.mk list instead? -- Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/ "Once again, thank you and all of the developers for your hard work on PostgreSQL. This is by far the most pleasant management experience of any database I've worked on." (Dan Harris) http://archives.postgresql.org/pgsql-performance/2006-04/msg00247.php
