Re: Release Notes - Info request on correct way to update .po for a language
Beatrice Torracca <beatricet@libero.it> writes:
> Hi Holger, and everyone,
>
> On 09/08/25 15:19, Holger Wansing wrote:
>> The ideal workflow would be, to call 'make update-po' for all
>> languages (and also commit the pot files in that step as well), when
>> English has changed (or once a day at least, or similar), and I did
>> that in the past indeed several times.
>
> I will do that from now on then, if I update Italian. I just didn't
> want to get into other people's workflows.
>
>> PS: I'm a quite unhappy with the 'make update-po' functionality in
>> Sphinx/reST. Comparing that with the old docbook-based variant it is
>> lacking an important feature for translators: it does not add the
>> old English text to the po files as comment (this is what
>> docbook/po4a does via the '--previous' commandline option).
>> That feature allows translators easily to see what has changed in
>> the English original text in their po editor (I use lokalize for
>> that, for example).
>> I opened an issue against sphinx on github to ask for such feature,
>> but the upsteam authors seem to think different about this:
>> <https://github.com/sphinx-doc/sphinx-intl/issues/121>
>
> Yes, that is a pity. It seems to me that upstream thought that the
> shifts to Weblate/Transifex and other similar tools, makes a workflow
> like ours obsolete. I don't agree but I see the merits of those
> tools. They seem to not rule out the implementation of this feature if
> someone provides it... maybe we can hope.
I think there is some misinterpreting of upstream's reply in this
thread. They did say that most poeple will use a tool that already
provides this feature, but i would read their reply as "patches welcome"
and rather than "we can hope", "we can help" would be the better attitude!
Reply to: