The Isotammi addons have proven to be an important resource. However, their translations are limited to just a few languages. Our whole community is not being fully served.
Can we somehow support their effort with an Isotammi component for Weblate? So there is some cross-pollination of glossaries and translators won’t have to do duplicate work for standard Gramps terminology?
Maybe mirror their repository in Gramps-project and have a Weblate component? So that we can push translation PO files periodically?
@kku and @jpek-m ; what is your opinion?
A couple of options as you mentioned:
- mirror the addons but don’t list or build it, this might allow the translations , so long as the make.py script collects the translation file still?
- Just have a blank folder with the addons name only containg the template.pot file(s) to be translated?
A extra bit of work on the side Gramps addon manager and of the external addon makers to gain translations from weblate?
Not sure if either would work and someone more familiar with addon creation and weblate will need to way-in?
Yes it is no need to misrepresent as remember they have chosen to manage the addons separately and could setup weblate themselves; or merge them into the Gramps addons repository to take advantage of the benefits (like translations handled on weblate), also I’m sure that having another person helping manage the addon builds would help everyone, as while in theory having external projects is great for development, so far in practice I’m seeing a number of addons in limbo ( Cardview / FamilyTreeView / “(MyHeritage Family Tree Builder)FTB to Gramps data transfer” to list some) that would be great if rolled into the main addon repository even in the current state they are !
2 Likes