Page MenuHomePhabricator

View translated messages in Flow
Open, MediumPublic

Description

Especially on multi-language sites (such as Mediawiki.org), users may participate in discussions posting on different languages. When that happens, users that do not speak that language usually make use of an on-line automatic translation service to get a general idea of the given message.

An option to "view translation in X" (being X a language the user understands) would be helpful. It will save the user the steps of copying the whole message, going to an external website losing the links and format in the way).

Considering that ContentTranslation already provides an automatic translation service (based on Apertium) for some languages, providing the above capability should be possible (as long as the language of the original message can be identified).

Event Timeline

Pginer-WMF raised the priority of this task from to Needs Triage.
Pginer-WMF updated the task description. (Show Details)
Pginer-WMF added a subscriber: Pginer-WMF.
Restricted Application added a subscriber: Aklapper. · View Herald Transcript
DannyH triaged this task as Medium priority.May 12 2015, 12:21 AM
DannyH added a subscriber: DannyH.

I could see this being helpful. Do you want to make a mockup? :)

I like the idea of doing this if there is an open source implementation for the language pair.

Do you want to make a mockup?

Definitely. The key points I want to explore are:

  • How to activate the translation.
  • How to guess the language the user wants the text translated into.
  • How to allow to change to a different language without crowding the UI.
  • How to communicate clearly that the user is viewing a machine translated version, and switch back to the original.

We also need also some technical assessment from the Language team on whether a language detection feature (or reusing the one provided by the underlying MT service) is feasible.

I like the idea of doing this if there is an open source implementation for the language pair.

Content Translation already provides a service that can be used, it is already using a local instance of Apertium but it can be extended with additional services. I guess that if it were using a 3rd party service (e.g., contacting a hosted version of Apertium instead of a local one), we need to be careful with exposing this feature on private wikis since we may not want the information on those to travel to external systems.

I like the idea of doing this if there is an open source implementation for the language pair.

Content Translation already provides a service that can be used, it is already using a local instance of Apertium but it can be extended with additional services. I guess that if it were using a 3rd party service (e.g., contacting a hosted version of Apertium instead of a local one), we need to be careful with exposing this feature on private wikis since we may not want the information on those to travel to external systems.

My understanding is they've also now integrated Yandex (at least on Beta), which I believe is not open source, and are considering adding Google Translate (same).

For Flow, I only support exposing this feature for language pairs where it uses an open source implementation.

Should this be in the CX project, or was it just auto-added?

Should this be in the CX project, or was it just auto-added?

It's in the intersection between Flow and the translation services in which Content Translation is based on (which don't have a more specific project in Phabricator). I don't think it is an immediate priority for any of both projects (although it would have been very convenient here), but if this is considered at some point I'd expect some work being done in both sides.

Should this be in the CX project, or was it just auto-added?

It's in the intersection between Flow and the translation services in which Content Translation is based on (which don't have a more specific project in Phabricator).

Maybe CX-cxserver?

Maybe ContentTranslation-cxserver?

Up to you. Where it is easy to find when needed. Feel free to change the projects.