3 Jan 2025 @Nick-Hall starts a gramps‐devel Mailing List thread about possibly using Weblate for addon translating.
9 Feb 2025 Call for testing volunteers of experimental Weblate for Addons component.
It might be reasonable to suggest a couple strings for everyone to translate… as a stress test. But also to have a common experience for discussing UX of Weblate
The situation so far is that I have concatenated the template.pot files for each addon and then removed strings that appear in the main gramps.pot file. This new addons.pot file contains the strings that appear for translation in the Addons component on Weblate. The addons.pot can be updated using a script when translations change.
I have also concatenated all the local po files for each language. The copyright statements have also been combined. This was a one off process so that we don’t lose any strings that have previously been updated.
When changes are made in Weblate, combined po files for each language are updated by pull requests. Translations for each addon are then extracted using a script.
The first batch of changes appears to have been merged successfully, but we need to do more testing.
Feedback from translators and addon developers would be welcomed. We need to know if any strings are missing from the addons.pot file. Usability may be another issue. I’m not sure how easy it would be for a translator to translate a single addon for example.
1 Like
Is this for a specific branch of the addons-source?
Yes. This is for the gramps60 branch only.
1 Like
Is there a standard weblate query for a string?
Maybe there could be a developer gramplet that reads a selected addon’s template.po and displays the string and the localized string with a hotlink to the weblate string in the current language?
Example links:
It’s actually quite easy. You can use “location” in the filter.
For example, you could search for “location:DenominoViso”.
1 Like
There may be a problem with weblate for addons.
First I couldn’t understand that i have so much to translate, since I have done a lot of translating for addons recently.
But I started, and noted the some entries looked mixed up.
I always view the Swedish translation, to help me, and I then saw that weblate claimed a polish(?) sentence was swedish:
according to the po file it should be:
#: SVWebConnectPack/SVWebPack.py:42
msgid “Arkiv Digital estate records for Skåne”
msgstr “Arkiv Digital bouppteckningar över Skåne”
2 Likes
The Weblate translation was added 4 days ago. It looks like it was a mistake by the user.
The local po file is named sv_SE-local.po rather than sv-local.po. I’ll fix it.
Update: File renamed and Weblate updated.
1 Like
Danish is in the top 5. There are only 5 languages with more than 50% of string translated.
| Language | Translated (%) |
|---|---|
| Dutch | 100% |
| German | 93% |
| Croatian | 59% |
| Portuguese (Portugal) | 55% |
| Danish | 53% |
| Swedish | 50% |
Let me know if you can find any strings that are unused. I have excluded strings that are already translated in the Program component.
Perhaps we should prioritise the popular addons?
1 Like