public inbox for [email protected]help / color / mirror / Atom feed
branching soon 6+ messages / 2 participants [nested] [flat]
* branching soon @ 2025-02-24 10:14 Peter Eisentraut <[email protected]> 0 siblings, 2 replies; 6+ messages in thread From: Peter Eisentraut @ 2025-02-24 10:14 UTC (permalink / raw) To: [email protected] Hopefully, we're done with releases and re-releases for now. So now I would like to do the translations branching soon. We did it around this time last year, which I think worked fine. One reason I would like to move forward with this soon is that I would like to get <https://commitfest.postgresql.org/patch/5429/; committed and run it through the whole pipeline before feature freeze. Unless there are any concerns, I will do this later this week. ^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: branching soon @ 2025-02-27 10:28 Peter Eisentraut <[email protected]> parent: Peter Eisentraut <[email protected]> 1 sibling, 2 replies; 6+ messages in thread From: Peter Eisentraut @ 2025-02-27 10:28 UTC (permalink / raw) To: [email protected] On 24.02.25 11:14, Peter Eisentraut wrote: > Hopefully, we're done with releases and re-releases for now. So now I > would like to do the translations branching soon. We did it around this > time last year, which I think worked fine. > > One reason I would like to move forward with this soon is that I would > like to get <https://commitfest.postgresql.org/patch/5429/; committed > and run it through the whole pipeline before feature freeze. > > Unless there are any concerns, I will do this later this week. This has been done. Be sure to adjust your local checkouts as appropriate. ^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: branching soon @ 2025-02-27 16:01 Guillaume Lelarge <[email protected]> parent: Peter Eisentraut <[email protected]> 1 sibling, 0 replies; 6+ messages in thread From: Guillaume Lelarge @ 2025-02-27 16:01 UTC (permalink / raw) To: [email protected] On 27/02/2025 11:28, Peter Eisentraut wrote: > On 24.02.25 11:14, Peter Eisentraut wrote: >> Hopefully, we're done with releases and re-releases for now. So now I >> would like to do the translations branching soon. We did it around >> this time last year, which I think worked fine. >> >> One reason I would like to move forward with this soon is that I would >> like to get <https://commitfest.postgresql.org/patch/5429/; committed >> and run it through the whole pipeline before feature freeze. >> >> Unless there are any concerns, I will do this later this week. > > This has been done. Be sure to adjust your local checkouts as appropriate. > Thanks. -- Guillaume Lelarge Consultant https://dalibo.com ^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: branching soon @ 2025-03-02 17:10 Peter Eisentraut <[email protected]> parent: Peter Eisentraut <[email protected]> 1 sibling, 0 replies; 6+ messages in thread From: Peter Eisentraut @ 2025-03-02 17:10 UTC (permalink / raw) To: [email protected] On 27.02.25 11:28, Peter Eisentraut wrote: > On 24.02.25 11:14, Peter Eisentraut wrote: >> Hopefully, we're done with releases and re-releases for now. So now I >> would like to do the translations branching soon. We did it around >> this time last year, which I think worked fine. >> >> One reason I would like to move forward with this soon is that I would >> like to get <https://commitfest.postgresql.org/patch/5429/; committed >> and run it through the whole pipeline before feature freeze. >> >> Unless there are any concerns, I will do this later this week. > > This has been done. Be sure to adjust your local checkouts as appropriate. It looks like I created the branch wrong (at a wrong branch point), so I had to delete it and recreate it again. So you'll probably get some kind of error if you git pull your REL_17_STABLE checkout. Sorry about that. Also, there had been a couple of commits to the (now deleted) REL_17_STABLE that synced the translations with the wrong upstream. So those are probably no longer necessary. ^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: branching soon @ 2025-03-02 17:17 Peter Eisentraut <[email protected]> parent: Peter Eisentraut <[email protected]> 1 sibling, 1 reply; 6+ messages in thread From: Peter Eisentraut @ 2025-03-02 17:17 UTC (permalink / raw) To: [email protected] On 24.02.25 11:14, Peter Eisentraut wrote: > One reason I would like to move forward with this soon is that I would > like to get <https://commitfest.postgresql.org/patch/5429/; committed > and run it through the whole pipeline before feature freeze. I have committed a subset of that patch to try it out. Specifically, I have committed the part for pg_checksums. So you can try out translating pg_checksums for PG18. The issue is the new approach for embedding int64_t format directives. See explanation here: <https://www.gnu.org/software/gettext/manual/html_node/No-string-concatenation.html#The-_003cinttypes...;. So it should like this #: pg_checksums.c:144 #, c-format msgid "%<PRId64>/%<PRId64> MB (%d%%) computed" msgstr "%<PRId64>/%<PRId64> MB (%d%%) berechnet" (I don't expect any particular problems. It's just worth trying it at small scale first.) ^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: branching soon @ 2025-03-03 16:33 Guillaume Lelarge <[email protected]> parent: Peter Eisentraut <[email protected]> 0 siblings, 0 replies; 6+ messages in thread From: Guillaume Lelarge @ 2025-03-03 16:33 UTC (permalink / raw) To: [email protected] On 02/03/2025 18:17, Peter Eisentraut wrote: > On 24.02.25 11:14, Peter Eisentraut wrote: >> One reason I would like to move forward with this soon is that I would >> like to get <https://commitfest.postgresql.org/patch/5429/; committed >> and run it through the whole pipeline before feature freeze. > > I have committed a subset of that patch to try it out. Specifically, I > have committed the part for pg_checksums. So you can try out > translating pg_checksums for PG18. > > The issue is the new approach for embedding int64_t format directives. > See explanation here: <https://www.gnu.org/software/gettext/manual/ > html_node/No-string-concatenation.html#The-_003cinttypes_002eh_003e- > macros>. So it should like this > > #: pg_checksums.c:144 > #, c-format > msgid "%<PRId64>/%<PRId64> MB (%d%%) computed" > msgstr "%<PRId64>/%<PRId64> MB (%d%%) berechnet" > > (I don't expect any particular problems. It's just worth trying it at > small scale first.) > It looks like it is working for me. -- Guillaume Lelarge Consultant https://dalibo.com ^ permalink raw reply [nested|flat] 6+ messages in thread
end of thread, other threads:[~2025-03-03 16:33 UTC | newest] Thread overview: 6+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2025-02-24 10:14 branching soon Peter Eisentraut <[email protected]> 2025-02-27 10:28 ` Peter Eisentraut <[email protected]> 2025-02-27 16:01 ` Guillaume Lelarge <[email protected]> 2025-03-02 17:10 ` Peter Eisentraut <[email protected]> 2025-03-02 17:17 ` Peter Eisentraut <[email protected]> 2025-03-03 16:33 ` Guillaume Lelarge <[email protected]>
This inbox is served by agora; see mirroring instructions for how to clone and mirror all data and code used for this inbox