Page MenuHomePhabricator

Enable translation engines in mediawiki.org
Closed, ResolvedPublic

Description

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.

Discussion: https://www.mediawiki.org/wiki/Topic:T2dltafe580r97ns

Details

Related Gerrit Patches:
operations/mediawiki-config : masterTranslate: Use Apertium via cxserver

Event Timeline

QuimGil created this task.Apr 19 2016, 5:56 AM
Restricted Application added subscribers: JEumerus, Matanya, Aklapper. · View Herald TranscriptApr 19 2016, 5:56 AM
QuimGil updated the task description. (Show Details)Apr 19 2016, 6:00 AM

See T111534 for "blockers". Translatewiki.net is already using Apertium hosted by cxserver.

Elitre added a subscriber: Elitre.Apr 19 2016, 4:28 PM
Restricted Application added a subscriber: TerraCodes. · View Herald TranscriptApr 19 2016, 4:28 PM

Translatewiki.net is already using Apertium hosted by cxserver.

(Though it seems broken. https://translatewiki.net/wiki/Thread:Support/WMF_Apertium_is_not_working_for_Asturian )

QuimGil added a comment.EditedApr 20 2016, 5:27 AM

Currently in the English -> Catalan pair, I get two options: Yandex (which works) and Apertium-WMF (which doesn't provide any recommendation).

To be clear, I am not claiming that using these engines is guarantee of good quality translations just by clicking one button. Compare to a white textarea, they are better motivators to start translating, and they save a percentage of the work.

Yandex requires (extremely wide, local and global) community consensus, which you would need to provide per the standard of configuration change requests or new features.

Apertium is ok, we just need to check that the configuration actually works.

We can start with Apertium, indeed. Let's not mix the Yandex discussion with the introduction of this feature.

Nikerabbit triaged this task as Normal priority.

I have a patch in review that fixes cxserver support. Apertium can be enabled in early May with a configuration change, for all WMF Translate wikis I suppose.

Nikerabbit changed the task status from Open to Stalled.Apr 20 2016, 1:27 PM
ThurnerRupert added a subscriber: ThurnerRupert.EditedApr 20 2016, 4:12 PM

if this then makes the same mess as it is done on meta for e.g. idealab - than please do not enable the extension. i would have nothing against a translation support, properly supporting to put pages including transcluded contents side by side.

see the german idealab translation as frightening example:
https://meta.wikimedia.org/wiki/Grants:IdeaLab/de, half translated, some in english, some other strange language, mostly outdated and anyway marked 100% complete. links going to english content instead of german. no support to add the "de" to links which is basically the most important interlinking feature.

@ThurnerRupert that has nothing to do with this task. We can discuss those issues one by one somewhere else, please.

Nikerabbit changed the task status from Stalled to Open.May 3 2016, 11:25 AM

Change 286632 had a related patch set uploaded (by Nikerabbit):
Translate: Use Apertium via cxserver

https://gerrit.wikimedia.org/r/286632

Change 286632 merged by jenkins-bot:
Translate: Use Apertium via cxserver

https://gerrit.wikimedia.org/r/286632

This comment was removed by Trizek-WMF.