[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Updating translations of gettext
From: |
Bruno Haible |
Subject: |
Re: Updating translations of gettext |
Date: |
Tue, 01 Oct 2024 22:00:34 +0200 |
Hello Michele,
> I noticed that the Italian .po translation files for gettext (and iconv)
> are rather outdated.
According to https://translationproject.org/domain/index.html, they are
from version 0.22, which is the current release (modulo bugfix releases
which don't change the POT file).
> How are those .pot files updated?
I do it as described in https://translationproject.org/html/maintainers.html :
"Whenever you make a new release of your package, you should announce it
to the TP coordinators at <coordinator@translationproject.org> by sending
them the URL of the release tarball -- this tarball should contain an up
to date POT file. (If your package isn't internationalized yet, then see
below.) Preferably you make a prerelease a week or so earlier and announce
this to the TP, so the translators get a chance to update their PO files
before the actual release of your package, so the release can go out
fully translated into several languages."
> Since I'd like to update them, I looked for a way to do that.
If you have time for updating the it.po file now, but probably won't
have time during the prerelease phase of gettext 0.23, and if you
are the assignee for this translation domain in your translation team,
you can — of course — build GNU gettext from the git repo, take the
generate POT file, translate that and keep it ready for use when the
gettext 0.23 prerelease is announced.
Bruno