Invites to translate articles should not include low-quality ml-engines
Open, Needs TriagePublic

Description

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.

jeblad created this task.Sep 24 2017, 6:42 PM
Restricted Application added subscribers: jhsoby, Aklapper. · View Herald TranscriptSep 24 2017, 6:42 PM
jeblad updated the task description. (Show Details)Sep 24 2017, 6:55 PM
Restricted Application added a subscriber: Danmichaelo. · View Herald TranscriptSep 24 2017, 6:55 PM
jeblad updated the task description. (Show Details)Sep 29 2017, 12:34 PM
Arrbee moved this task from Backlog to Long term on the ContentTranslation board.Oct 27 2017, 5:30 AM

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.