[nvda-addons] Re: How to separate translations from code for addons?
- From: Doug Lee <dgl@xxxxxxxx>
- To: nvda-addons@xxxxxxxxxxxxx
- Date: Wed, 10 Jun 2015 19:53:14 -0400
James wrote:
perhaps you may be able to find someone to volunteer to make
releases for you when there are a significant number of translation changes.
I suppose my latest message (before this one of course) is effectively
a generic request for such a volunteer. :-) I'll let this one be
managed as the community sees fit, based on what I manage to put up on
my site.
I do understand that the nature of gettext itself is part of why
things work as they do for NVDA and addons. gettext is close to but
not quite the ideal I would like for localization management.
You also mentioned forks, support problems, and old other-language
versions. In my experience (mostly from the Skype scripts), support
naturally forks with language anyway. A French version 1.3 while
English is at 1.4 therefore actually results in less confusion because
a person looking for French support finds 1.3 users. When 1.4 is
translated into French, the French users hear about it and support
each other just as we do in English when there's an update.
Finally, I hold that the rules may be slightly different for a major
product like a full screen reader, because it is big enough that
support for it naturally becomes more centralized than for a small
addon.
On Wed, Jun 10, 2015 at 04:35:22PM -0700, James Teh wrote:
On 10/06/2015 3:40 PM, Doug Lee wrote:
My understanding is that, for NVDA and possibly for some if not all
addons, the coder ends up maintaining the translations even though
others actually do the translating.
Not really. The coder does have to make a release if they want to include all
new translations. However, assuming you're using a Git repository, you can
just merge a branch provided by the translation system. This is true for both
NVDA and add-ons.
- I let others translate and post their translated versions as they wish.
The problem with this is that it results in forks all over the place. It makes
support difficult because people using languages other than English end up
using old or modified versions. There's also no centralised place to get the
add-on for all users.
- I've had cases where translations said things I wouldn't say, but
only knew because I was told later.
That is certainly a risk that applies even to NVDA. We have to trust to some
extent, but also, we can make it clear that translations are provided by
others and simply remove the translation if anything bogus is reported.
- If I manage the text, people have to wait on me when a new language
is added. Since I rarely get to work on NVDA addons, this could mean
long delays.
You aren't managing the text, just merging the changes and making a release.
If even that is not something you will have time to do (which I can certainly
understand), perhaps you may be able to find someone to volunteer to make
releases for you when there are a significant number of translation changes.
From what I'm seeing, it looks like NVDA's approach to localization
requires that an addon include all translations within it.
Correct.
I'm hoping
there's another way to do this
There isn't.
Jamie
--
James Teh
Executive Director, NV Access Limited
Ph +61 7 3149 3306
www.nvaccess.org
Facebook:
http://www.facebook.com/NVAccess
Twitter: @NVAccess
SIP: jamie@xxxxxxxxxxxx
----------------------------------------------------------------
NVDA add-ons: A list to discuss add-on code enhancements and for reporting
bugs.
Community addons are available from:
http://addons.nvda-project.org
To send a message to the list: nvda-addons@xxxxxxxxxxxxx
To change your list settings/unsubscribe:
//www.freelists.org/list/nvda-addons
To contact list moderators: nvda-addons-moderators@xxxxxxxxxxxxx
--
Doug Lee dgl@xxxxxxxx
http://www.dlee.org
SSB BART Group doug.lee@xxxxxxxxxxxxxxxx
http://www.ssbbartgroup.com
"It's not easy to be crafty and winsome at the same time, and few accomplish
it after the age of six." --John W. Gardner and Francesca Gardner Reese
----------------------------------------------------------------
NVDA add-ons: A list to discuss add-on code enhancements and for reporting
bugs.
Community addons are available from:
http://addons.nvda-project.org
To send a message to the list: nvda-addons@xxxxxxxxxxxxx
To change your list settings/unsubscribe:
//www.freelists.org/list/nvda-addons
To contact list moderators: nvda-addons-moderators@xxxxxxxxxxxxx
Other related posts:
