Change Details

Right now I got invites in the sidebar to translate an article [[ https://no.wikipedia.org/wiki/Leirskogen | 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.

Right now I got invites in the sidebar to translate an article [[ https://no.wikipedia.org/wiki/Leirskogen | 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.

Right now I got invites in the sidebar to translate an article [[ https://no.wikipedia.org/wiki/Leirskogen | 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.