Updating .pot files

Updating .pot files

[Stephen Casner]

What's the procedure for updating .pot files?  Is there any
expectation that .pot files should be updated as source files are
changed, or only as releases are set?

For example with the gas.pot file, I see Nick's commit 1b1bb2c67bb on
Jan 18 2020 for "Update version to 2.34.50.  Regenerate configure and
.pot files."  But git annotate shows the file was subsequently updated
by commit 8f595e9b4fd on May 20 2020 even though that file is not
shown in the git diff for that commit.  There must be some magic there
somewhere.

I was in charge of gettext-based i18n for a project in a previous
life, but that was a while ago and I recall the process being mostly
manual.

                                                        -- Steve

Re: Updating .pot files

[Nick Clifton]

Hi Stephen,

> What's the procedure for updating .pot files?

Ad hoc. :-)  Ideally they should be regenerated any time a translatable
string is changed or added.  But in practice this rarely happens.  The
most common time is when a release branch is created, and the regeneration
is one of the steps in this process.


> For example with the gas.pot file, I see Nick's commit 1b1bb2c67bb on
> Jan 18 2020 for "Update version to 2.34.50.  Regenerate configure and
> .pot files."  But git annotate shows the file was subsequently updated
> by commit 8f595e9b4fd on May 20 2020 even though that file is not
> shown in the git diff for that commit.  There must be some magic there
> somewhere.

Nope - just a snafu - the update should have been mentioned in the commit.

Cheers
  Nick