Feature: Machine translation

[kyubisation]

Support machine translation in the translation server (and consume it in the app).

API:
/api/targets/:language/units/:id/machine-translation
Response:

interface MachineTranslationResponse {
  provider: string;
  translation?: string;
  error?: string; // 
}

Possible Providers:

• Google
• DeepL
• Others?

Open Questions:

• Is this a reasonable requirement or would a mass-machine-translation via schematics be preferable?
• Should a custom provider implementation be possible for business internal translation APIs?

Important Notice:
I currently have no need for this feature. Unless this changes or a consumer voices a strong requirement, this will not be implemented. If you want to contribute this feature, describe your use-case in this issue before you start.

[aledavidgueva]

Hi! I think that your tool is amazing. I don't think that is neccesary a massive translation via schematics, but is desereable inside the translation dashboard with some available options according to target languages. For example, massive translation only with de untranslated words or selecting not final or not reviewed translations. I would consider include the source language and context in the request to translation machine, and translation status in the response.

In my opinnion, the most important option is the internal translation server. The endpoint can be prepared for supply of multiple translation sources with a really simple backend.

Thank you for considering it.