[CCing bug-gettext] Alexander Sosedkin wrote in <https://lists.gnu.org/archive/html/bug-gnulib/2026-09/msg00113.html>:
> There's https://translationproject.org/latest/gnutls, > but no, say, https://translationproject.org/2026-09-28/gnutls, Yes. Neither the TP nor Weblate instances have the concept of branches or dates. They just store the newest translation of a POT file for a given language, and when that translation gets updated, the previous one becomes inaccessible. [1][2] This system does not explicitly provide for supporting maintenance releases with long-term-served maintenance branches, e.g. 1.7 1.7.1 1.8 1.7.2 1.8.1 1.7.3 1.7.4 1.7.5 1.9 1.7.6 1.8.2 ... > so something has to store the translation state as of the time we cut a > release. Yes, if the developers want to make such maintenance releases or if people want to reconstruct a release while throwing away the release tarball, they need a place to store the translations. > > I reverted back to storing translations in git, > > something that I did for most projects > > back when I was using CVS 20 years ago. It is understandable that developers did not want to store translations in a VCS, because GNU gettext's po/ directory did not integrate well with branches. But this has been fixed in gettext 1.0 [3]. The way for developers to get this feature is to put AM_GNU_GETTEXT_VERSION([1.0]) in their configure.ac file and follow the steps described in the GNU gettext manual [4]. > gnulib fetches them as part of bootstrap. At some point, this should be changed to invoke the 'po/fetch-po' script. The old code in gnulib's bootstrap for doing that is obsolete. But this is just a side note. Once the developers rely on git branches for storing the translations, they shouldn't fetch new PO files into a branch. > util-linux's [git-tp-sync]. This script is basically a combination of 'po-fetch' and 'git commit'. Bruno [1] https://www.gnu.org/software/gettext/manual/html_node/po_002dfetch-Invocation.html [2] https://docs.weblate.org/en/latest/api.html#translations [3] https://lists.gnu.org/archive/html/info-gnu/2026-01/msg00007.html [4] https://www.gnu.org/software/gettext/manual/html_node/Version-Control-Issues.html
