ventech Wrote:However, with respect to addons, being in the official repo is optional and there's already lots of rules in place for this repo. Will adding a few more make any difference?
Call it package translations like ubuntu if you like: You can translate your addon all you want but it wont necessarily be a part of xbmc. Translations in the addon repo are considered part of xbmc and thus distributed separately. Sure, someone is not going to like it but the same can be said for all the other rules.
I really hope that this time, I can handle addons translations in Transifex. Under a different project, but with shared translation memeory. This can be done in Transifex. That is what I am planning. It will be a hell of a work to put it together and update, but I am willing to undertake this job.
ventech Wrote:Another thing that i don't think has been mentioned is how are you going to handle upstream changes? for instance, when a translation is updated in transifex, and the addon maintainer do changes without pulling from main repo, who wins? If you distinguish between upstream and package, the obliviously package trumps upstream.
This is exactly why we need to have an ability to update Transifex with the upstream language files as well, not only the source English file. This time the upstream change will immediately go into Transifex so translators there can see it. Obviously they will show up as new TRANSLATED strings so there will be no big trouble for the translators.