Re the translations. Are there any parts of the guide that remain unchanged and could have their translations, say in a zip download somewhere should any prospective translators come along later.
toggle quoted messageShow quoted text
Having said all that, it is going to be a very difficult task to keep such a document up to date even in one language, let lone several.
This is a not just a problem on nvda but on many projects where users can add to the functionality etc.
I directly am not going to use it, but if I do meet anyone who is pretty good at programming just having one place for resources generally will be easier to pass on to them I feel.
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users
----- Original Message -----
From: "Joseph Lee" <@joslee
Sent: Monday, May 13, 2019 11:55 PM
Subject: [nvda-devel] Add-on development guide: let us remove the one found on add-ons community website in favor of GitHub version
Some of you may see this message up to three times - that's the beauty and a
curse of blind carbon copies.
There was a question raised on the add-ons list regarding where to find the
add-on development guide. At the moment the one that appears from Google
However, the most up-to-date version can be found here:
I propose that we start referring to the second link. Although the first one
has been translated into several languages, it is very out of date, as the
last revision was in 2016 and hasn't been updated ever since and won't be
updated at all. Although the second one is very up to date, it hasn't been
translated yet (personally I prefer to keep the guide in English, but I'm
open to other possibilities). The biggest advantage of the second one is
support for tables, and the fact that this is a wiki document that is also
ready for revisions through Git make it a more attractive option.
Note that even though I am the author of the add-on development guide, it is
still subject to community-based revisions. Also, Project Threshold is
slowly being planned, which will make the first link obsolete. Therefore,
you are more than welcome to provide feedback as to what to do until a few
days after Threshold is launched, at which point backwards incompatible
changes from my side (in this case, the link for the add-on development
guide) will be locked.