On Fri, Dec 4, 2009 at 3:52 PM, Christian Boos <[email protected]> wrote: > > I was told that there were some concerns about this, and questions about > the implications this will have for our translation process. So let's > discuss this openly here. The statistics themselves are a non-issue, as > this is merely informative and should have no consequences, other than > perhaps motivating the translators to update their translations, of > course ;-)
I hardly imagine what transifex is. Seems it support some translation statistics. Good, but can you tell a bit more - what is the source data by which statistics is built? What's wrong with translation process now? And What are alternatives? > The real question is if it would be a good idea to allow submissions > from Transifex, what would be the pros and cons. Do you mean write access to SVN or some licensing issues? If former then that options do you have - limit SVN access only to translation directory or to all repo? Will commits be done automatically meaning some kind of bot imports them from outside? What is the risk of getting some "bad language" as a consequence? Do they have "translate" -> "reverse translate" -> "compare" process? > Most large projects are delegating direct write permissions in the > repository to their translators; so far, no one has requested this for > Trac, but I can see how this could be a good idea, as this would > streamline the contribution process, and let translator have direct > control over the translations they contribute. This doesn't mean that > there couldn't be someone who takes care of the technical quality of the > contributions, checks that the correct tools are used, etc. In that > respect, Transifex used as a middle man would alleviate all the > administrative burden, as only one account would have to be created. The > technical details, whether we should get those contributions by e-mail > or use an intermediate dvcs repository are also open. Anyway, having an > official Trac mirror somewhere (be it a git or mercurial one, or both), > would be a nice thing in any case. Hosting our own mirror would also be > option, I imagine. http://mercurial.selenic.com/wiki/DeveloperRepos - very nice approach to i18n and not only. > Transifex also has "Collections" of related projects (currently Django, > GNOME and LXDE). I can imagine a "Trac" collection in this picture, as a > way to collect all the translation projects for all the plugins, once > people realize they can already translate their plugins ;-) What is this? Some kind of shared translation memory or just a bunch of files in one named place? > Editing translations directly on Transifex's site is probably not an > option as of yet, due to the limitations of Lotte regarding the size of > the catalogs, but as I understand it, this is going to change. The best thing I've seen for editing translations is http://translate.google.com/toolkit/ > While the ideal for getting high quality translations remain in my > opinion having people actually running Trac and testing their > translations to see how well they work "in context", having the > possibilities to get translations directly from a web interface doesn't > sound bad either. I am not sure what does "get from we interface" mean. As for usability and convenience to make a change - Trac installation can have link to "report a better translation" or "suggest doc fix" with redirect to Transifex, Google Translate or whatever. -- anatoly t. -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en.
