Thread:Support/is this possible/reply

I think we should respect, cherish and nurish the different communities; you can't do everything in one wiki. IMO that is confusing.

What we can do is try and get the processes that support translation lined up. We - developers of the Translate extension - think that page translation in wikis that have a lot of static documentation can benifit hugely from the structured process that the Page Translation feature offers. Within Wikimedia I indeed see use cases in, and. However, there are two main issues preventing implementation of the Translate extension within Wikimedia: our code has not been audited by a senior MediaWiki developer on the Wikimedia pay-roll, which is a requirement for implementation, and the process leaders for translation within the aforementioned Wikimedia communities are either not aware of the functionality that Translate has to offer, or they think they can do without.

The first issue - code audit - is something that's on the roadmap. Ariel Glenn allegedly has planned to do some auditing, although I doubt his hopefully positive verdict will suffice; he may not be senior enough. The second is something you, as a community member of both translatewiki.net and possibly various Wikimedia projects can do something about: advocate the use of the feature, find a relevant group of users supporting use on the Page Translation feature in another wiki, have a poll, create a request for installation and ask as many users as possbile to vote for this issue. Do realise this is no guarantee for success, but every little bit may help...

As for supporting FireFox extensions: that may be possible, although I have no idea of the file format for localisation of Firefox extensions. We have a special page with the requirements for adding new projects to translatewiki.net: New project. Please give it a read, get a developer of the product involved and maybe we can make it happen.