Hi, I think it could be easier to reviewers if your add-on is available
in a repo of the NVDA add-on team Bitbucket site. If you want, see the
NVDA add-ons processes about revision. There it's explained that
translations can be merged to stable branch from the add-ons translation
system.
Of course, you can choose to manage this outside or in other way. If you
are interested, you can request an invitation to join the NVDA add-on
team, or one of the members can create repos for your add-ons and send
you an invitation so you can write to these repos.
Thanks.
El 11/06/2015 a las 4:06, Doug Lee escribió:
I just posted versions of my TeamTalk and Virtual Audio Cable addons----------------------------------------------------------------
for review by those interested in localization. These have not yet
replaced the versions I posted publicly for download. For anyone
interested, here are the URLs for the localizable versions:
TeamTalk: http://www.dlee.org/test/TeamTalk%20Classic.nvda-addon
Virtual Audio Cable: http://www.dlee.org/test/vac.nvda-addon
I want to make sure I did this right and that there's nothing else I
need to do to render these addons localizable. In particular I am
assuming I don't need to make a gettext file for the English
translation since that's the native language of the addon. Feedback
welcome, and apologies for the fact that I'm extremely new to this
branch of NVDA development. According to my tests, both addons run in
English as expected; but I won't be surprised if I missed or
misunderstood a rule somewhere...
