@fastfinge To localise the settings panel: import addonHandler, call addonHandler.initTranslation(), and then wrap all user-facing labels (e.g. text of checkboxes) in a call to the magic underscore (_) function.
E.g. _('&Maximum number of history entries (requires NVDA restart to take effect)')
@jscholes We are not using scons. We are not using the NVDA addon template. We are not using anything even vaguely resembling a sane build system. See build.cmd and build.py and cry. In other words, if it needs to happen, I need to do it myself.
@fastfinge No, but I did forget one thing: you should put a # Translators: ... comment on the line above where some user-facing text is used for the first time, explaining what that text is for. E.g.:
# Translators: the label for the button to update community dictionaries from GitHub
@fastfinge Ah... well: there is a translation workflow which will pull the translatable strings out of your add-on, put them somewhere for translators to translate, and then push the locale files back into your add-on. What I'm unsure about is whether they'd accept Eloquence as an add-on in that system.
@jscholes We also aren't technically supposed to host the eloquence dll files on github. That's why the build process is...the way it is. So that when the repo that contains them gets pulled down, we can get them elsewhere with a quick change.
