Resolving ambiguity in translations by using mulgtiple source texts #28
Description
Using automatic translation for our web app (with Google Translate) we have found, that individual translations (where often only a single word (eg field name) is translated) tends to be ambiguos (and a longer context is not seen).
So we came up with the idea of translating from multiple source languages into a target language. In development we use English as the main language and do (as Germans) a manual German translation (to see if we have marked all translatable text correctly). Sometimes we also have a native translations for another language. So we have at least 2 source texts for automatic translation. We currently do this with a custom prompt via Gemini or ChatGPT.
["We have help panels for a web app in Markdown. The English version is: \n\n", en, "\n\nThe German version is: \n\n", de, f"\n\nWhat is the {targetLanguage} translation in Markdown?"]
Maybe you could extend you API to cover that use case.