I just wanted to get back to you to let you know that our team enabled that but they are still working on some issues they experience with it so I recommend that you wait until I get back to you with new updates.
Is there a way that we can enable DeepL for Korean?
We already had DeepL enabled for "Which translation engines do you want to use?" but this applies to all languages on our site, not just Korean.
A Korean colleague noted that the Korean translations seemed to be using a non-DeepL translation engine, whether Microsoft's or Google's translation services, so is there a way to explicitly set Korean automatic translations to use DeepL as well now?
Thank you, Mihai. Within the language mappings, I see that DeepL is one of the services that are enabled for Korean, and we have DeepL already set as our first choice of translation engine when it's available.
It helps to know that we can check the engine in use if we use the ATE and then create the automatic translations from there, rather than trying to send jobs directly our for automatic translation without the ATE.
(Although I wish that there was some sort of confirmation of which engine is being used when we send translation jobs for automatic translation without using the ATE interface.)
