Thank you for all your efforts so far, Krinkle. I hope that the toolserver tool developers will use this system profusely.
Siebrand Mazeland M: +31 6 50 69 1239 Skype: siebrand Op 29 mrt. 2011 om 02:46 heeft Krinkle <[email protected]> het volgende geschreven: > So, as announced in the previous mailing (Agreed, I should've sent > this one first...). > Regarding the technical implementation. > > First a few points that you are likely aware of, that have stopped, > disabled or scared off doing this untill now. ie. creating a dedicated > solution that can scale for more than just 1 tool or group of tools – > And is easy to use for translators as well for developers. > > -- Past issues / obstacles > > * Separated Toolserver SVN repositories > ** For MediaWiki extensions, TranslateWiki can easily translate things > and can sync in a single commit because it has a partial check out of > a single SVN repository. Having to add all ts-account repos to TW's > configuration is way too much work and pretty much not-done. Not to > mention the fact that most tools are either not in SVN at all, or are > maintained outside SVN and pushed towards SVN for public source > viewing every once in a while. > > * Language of choice > ** Users want to set their choice once and not have to search re-do it > for all tools independently and have to find the right place to 'do > it' on everybody's tool. Nor do we want to click the same link again > every visit. And developers prefer not to have userlang-parameters > dangling in the url and have to make sure it's preserved throughout > the app with every link. > This can (and sometimes is) solved by using cookies (one example is > Luxo's contributions tool that sets a cookie) > > * Prevent vandalism but also slow-down and other down sides of a > regular MediaWiki page. > ** When translated on one wiki-page (ie. at Meta-Wiki such as Magnus' > implementation, which I think is the best implementation so far) there > isn't a good translation-oriented workflow for translators or > developers. Of course pages could be protected by sysops - and then > have to be updated from another page on request. And then there is > FlaggedRevs. But neither are not optimized towards translators (ie. > there's no way to FUZZY a message, or see translation suggestions from > services like Google Translate, or a description of the message while _______________________________________________ Toolserver-l mailing list ([email protected]) https://lists.wikimedia.org/mailman/listinfo/toolserver-l Posting guidelines for this list: https://wiki.toolserver.org/view/Mailing_list_etiquette
