Forum Discussion
Export to XLIFF 2.0 File in Rise
Hi Thor,
thanks, I was looking for that. Unfortunately, I am not our team manager, so I would have to ask him. Unfortunalety, in a European company, which is aware of certain security risks, anything AI is not so easy and needs to be checked by IT first.
Any data being processed outside Europe for example is an issue, especially countries like Russia, China and , yes, even USA...
Hi Felix,
AI can be a frustrating word these days as anything technology related seems to be called this. From the Articulate team, they're using both DeepL and Amazon Translate (when DeepL doesn't have an equivalent language), which are both algorithm in nature rather than 'AI'.
But to answer your more pertinent question, is where the data is processed and Articulate changed that last year which should address IT's valid concerns.
This article from Articulate can help you with your conversations and also give some more insight into how they are thinking about translation:
https://access.articulate.com/support/article/Articulate-360-FAQs-Articulate-Localization#trial
Small update - DeepL is using large language models in addition to their original language models/algorithms. Some caveats though for usage - 1) The developer has to enable the option on their end, 2) Not all languages are supported with the new models.
The Articulate team would have to share if they've included this in their approach as it's not viewable in their current implementation.