You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In this thread of add-on mailing list, you indicate that you do not know the current status of this add-on's translation. And that you agree, with help, to have it translated.
The process is described on the mrconfig repo page.
To have your add-on registered (paragraph "Steps for addon authors"), you just need to create a stable branch in your repo and ask the add-on's inclusion in the translation framework on the add-on mailing list; the rest will be done by @nvdaes and NVAccess.
Once it is registered, you will have to update periodically the translations (cf. paragraph "Maintaining the add-on").
I am available for it if you need assistance.
The text was updated successfully, but these errors were encountered:
I have just seen that Speech History is not based on the add-on template (probably created before that time).
I think that the following will be missing (even if not documented in the readme of mrconfig repo):
Files sconstruct and buildVars.py
Capability to run scons pot mergePot (actually allowed by these 2 files)
Would you mind upgrade your add-on to be compatible with the template? Or accept a PR for this?
Also, the translation system uses the website page as documentation in the add-on (in English and translated). Presently, the website page is not up-to-date. You may want to update it before asking the integration in the translation system; you could also update it afterwards, but it would be a pity to make translators work on something that you will change just after.
In this thread of add-on mailing list, you indicate that you do not know the current status of this add-on's translation. And that you agree, with help, to have it translated.
The process is described on the mrconfig repo page.
To have your add-on registered (paragraph "Steps for addon authors"), you just need to create a stable branch in your repo and ask the add-on's inclusion in the translation framework on the add-on mailing list; the rest will be done by @nvdaes and NVAccess.
Once it is registered, you will have to update periodically the translations (cf. paragraph "Maintaining the add-on").
I am available for it if you need assistance.
The text was updated successfully, but these errors were encountered: