Page MenuHomePhabricator

Invites to translate articles should not include low-quality ml-engines
Closed, DeclinedPublic

Assigned To
Authored By
Sep 24 2017, 6:42 PM
Referenced Files
"Like" token, awarded by Soulkeeper."Like" token, awarded by Danmichaelo."Like" token, awarded by jhsoby.


Right now I got invites in the sidebar to translate an article w:no:Leirskogen into "Deutsch" and "English". Such translations will not be supported by Apertium, but by Yandex. This means low quality machine translation. If I should make a translation into Norwegian with use of the Yandex engine the community would balk.

Either the invites to do translation should be for closely related languages with good translation engines, or limited to languages people at those project accept. Translation between disparate languages should still be possible from inside the tool, but not as invites in the sidebar.

See also T162524.

Event Timeline

Many languages don't have MT at all, and we don't have a proper way to grade those that we do have. I don't dismiss your opinion that it's bad for Norwegian; you are probably correct. But we don't have a way to do it for everything.

More importantly, our analysis of entry points shows that these gray links are not actually used by many people, so their impact on the number of translations, good or bad, is negligible. I find this surprising, because the interlanguage links are quite notable, at least for people who know Wikipedia well, but that's the fact. In my long-term strategic vision they should become the main entry point for translation, but the reality shows that it will need design work to become really effective.

I'll leave this open, to be discussed when we do this redesign work, but it's not something that is actionable now.

StjnVMF changed the task status from Open to Stalled.May 18 2018, 5:17 PM
JJMC89 changed the task status from Stalled to Open.May 18 2018, 5:44 PM
Pginer-WMF added a subscriber: Pginer-WMF.

As mentioned above ( T176582#3714376 ), we provide each language the best tools we can for translating their content. Our observations suggest that for languages without MT support, having a side-by-side editor is already making it easy to create an article compared to starting from scratch. In addition, the number of languages supported by MT have increased in the recent years. For all the above, I think it is more practical to expose the option to translate with the best tools we have for each language rather than hiding it from some.