On Sun, 19 Apr 2020, Sven Schreiber wrote:
Am 19.04.2020 um 17:57 schrieb Allin Cottrell:
> On Sun, 19 Apr 2020, Sven Schreiber wrote:
>> Am 19.04.2020 um 16:42 schrieb Allin Cottrell:
>>>
>>> No, that's wherever you're running configure and make.
>>>
>> Right - so that means while translators work with the po files in git,
>> and the underlying C source changes are also done in git, in between
>> there's a necessary step that leaves the realm of the git tree?
>
> If you're building outside of the source tree (which is generally
> recommended), yes. The .po files are kind of a special case, generated
> from the C sources (and so requiring a "make") but edited by the
> translators thereafter.
>
So what's the preferred workflow for marking another string for
translation? I'd say the first-step change in the C source would be
enough, because eventually you (or somebody else) are going to run the
po-update step when a bunch of new translation gaps have accumulated. No
need to do it every time. Right?
Right, unless you really want a newly translated string to show up
right away in snapshots.
I've perhaps been a bit slow to run po-update of late, but it
doesn't have to done on every relevant change in the C sources.
Allin