Translation engines were enabled.
There is a lot of documentation translation work being done in mediawiki.org. Unless I am missing something, all of it is being done manually.
The Translate extension allows the integration of automatic translation engines. This would save a lot of work to translators, who currently are either typing manually or are copying & pasting from external translator engines.
automatic translation engines have such a bad quality, the browser is much better in doing such things. translation support would be very much appreciated, but the current technology is unfortunately not usable and producing sub-standard mess. see https://meta.wikimedia.org/wiki/Grants:IdeaLab/de (idealab, german). click e.g. on "share ideas" - you are ending up on the english page. the page is marked 100% complete despite.
I'm using the Translate extension with automatic translation support in translatewiki.net and it is useful. Anyway, this is a flexible feature. If someone doesn't want to use the suggested translations, they don't have to use them. But I see no reason to avoid that translators willing to give them a try have the chance to do it. All the technologies involved are open source, so more usage means more potential for improvement.
I suggest to add an option for manual translation and bot translation, identify it with something "es" for translations by humans and "es (bot)", for translations by computers.
The Translate extension simply offers the automatic translation in a side box. If the translator wants to use that translation, then they have to click it, and that text moves to the main textarea. There, the translator can polish the translation.
If the translator doesn't want that offered automatic translator, then they can type the translated message in the main textarea from scratch.
Usually the workflow is:
Starting from an automatic text usually saves work. If in your specific text or language pair you see that this is not the case, you can just ignore it.
