Recently, I have been taking a closer look at how to translate my addon FamilyTreeView (FTV, see the original announcement thread and (since it was split due to length) the current thread, as well as the Github repository). Thanks to everyone who gave me insights and pointed me to other resources on how translation of addons works!
Packaging the addon also creates a template.pot file (with about 300 entries). Currently this file is discarded. I will change the GitHub workflow to keep this file, once everything is prepared. My understanding of the subsequent process is as follows (please correct me if I’m wrong):
- Translators can then use the
template.potfile to translate the strings, e.g. with poedit (see @kmikkels post here, poedit’s GitHub repo or poedit’s website). - The resulting
XX-local.powill be merged with a pull request. - When packaging the addon,
- the subdirectories and the file
locale/XX/LC_MESSAGES/addon.moare created in the package, and - the addon is added to
addons-XX.jsonin thelistingsdirectory.
- the subdirectories and the file
- Gramps will find these files when the user’s language preference matches one of the translated languages.
While FamilyTreeView is still under development, you should not rush to translate the whole addon into as many languages as possible, because some strings might change before the first non-beta release. Currently I’m more interested in:
- Testing the workflow of translating the addon, from providing the
template.potfile all the way to a translated string/label in the UI of an end user who installed the addon using the Addon Manager. - Finding strings in FTV’s code that do not yet allow translation, e.g. I forgot to add
_(...). - Figuring out where strings need handling of singular/plural forms, masculine/feminine forms, and/or context, etc. to be translated correctly.
- Compiling a list of volunteers who would like to translate this addon in the future.
The following people have already offered to translate FTV:
French: @PLegoux (offered help here), @geoglorus (offered help here)
Danish: @kmikkels (offered help below)
If you would like to help to translate FTV into another to other language, I (and most likely others who use your language) would be delighted! Ideally, there are multiple volunteers for each language to review translations.
(I’m also interested in general feedback from people using other languages/writing systems, e.g. UI/UX, RTL scripts, name abbreviations in other cultures. Feel free to post your feedback in the current FTV thread, open an issue on Github, or contact me privately in this forum.)
Summary:
- Is the process described above (1. through 4.) correct?
- Do you want to help to make FTV (better) translatable?
- Do you want to volunteer in translating FTV?