I have already discussed it by e-mail. But I open this issue here in order to have it tracked.
I think that Nao should be integrated in the NVDA community translation framework. This would help translators to do their job more easily for the following reasons:
Provides a standard way to indicate to translators when the translations need to be done.
No need to merge manually the .pot in .po
When updating the documentation, no need to remember which version of the doc was last translated and to check the diff with this version.
This 3rd point is a real benefit to have the documentation translated and up-to-date. On the contrary, in manual translation process, updating the documentation is a burdon when it becomes bigger.
The automatic system has also the following benefits for the add-on maintainner:
Be able to merge all translations in one single merge.
Notify translators of new translation content only when you want, e.g. only when a new version of the add-on is released.
Note: a pre-requisite to the inclusion in the international community translation system is to have the addd-on integrated on the international community website.
If needed, I can help for both these tasks, in English, Italian or French.
I have already discussed it by e-mail. But I open this issue here in order to have it tracked.
I think that Nao should be integrated in the NVDA community translation framework. This would help translators to do their job more easily for the following reasons:
The automatic system has also the following benefits for the add-on maintainner:
Note: a pre-requisite to the inclusion in the international community translation system is to have the addd-on integrated on the international community website. If needed, I can help for both these tasks, in English, Italian or French.