Weblate and Python project: New strings commited in weblate repo but ignored in translation interface

[buhtz]

This is partly an X-Post from here: https://codeberg.org/Codeberg/Community/issues/965

As you can see in this screenshot I was able to keep my upstream repo and the weblate's internal repo synced. They are on the same state/commit.

There are two strings new strings in that repo that are not translated yet. But this strings do not appear in the translation interface here:

You see 5 strings. But there should be 7 with 2 untranslated.
How can this be when there are definitely (?) 7 translatable strings in weblates internal repo?

[nijel]

For some reason, Weblate didn't process the update. I can think of two reasons:

1. The process crashed, either due to a bug or being killed by OOM. This should be visible from the server logs. Having the logs showing the issue might be useful to diagnose.
2. The update of files was missed for some reason, but tracked as parsed by Weblate.

To recover, you will need console access to the Weblate server:

1. Try weblate loadpo --foreground bitdemo/bit_demo. If this does the update, the first issue happened. (In future, you will be able to do this from Weblate as well, I've just implemented UI for this in 804f9f9).
2. Try weblate loadpo --force --foreground bitdemo/bit_demo. This would indicate the second issue.

[nijel]

Okay, if they do not exist in the PO files, we have FAQ covering this: https://docs.weblate.org/en/latest/faq.html#why-does-weblate-still-show-old-translation-strings-when-i-ve-updated-the-template

[buhtz]

That is what I meant. The toolchain of "pygettext3" and "msgmerge". Weblate should do this by itself because it has the whole repo cloned.

[nijel]

You can configure Weblate to do it.

[buhtz]

Nice to know. How can I configure it?

[pietervdvn]

I had a similar problem with XXX strings are not being translated here (or XXX strings are not translated here) under a little ghost icon + a new language not being translateable. The loadpo --foreground <component> worked for me.

(I'm adding the error message here so that this conversation can be discovered more easily)

[nijel]

As this has been recently commented on anyway, let's update the discussion:

• Update POT file (xgettext) add-on can be used to update POT files based on the source changes
• Update PO files to match POT (msgmerge) can be used to update PO files based on POT

[buhtz]

Ui, that is an old thread. And it is out-dated.

I never used the mentioned add-ons, but found my own semi-automatic solution. After I understand that the Weblate instance does manage its on git repo of my upstream repo and I can access it with git commands, the solution was obvious.

The result is this script that manage to synchronize the upstream repo with the Weblate instance. Additionally it does a lot more syntax checking and other stuff related to my specific project.