Connector for Translation Manager using OpenAi
This connector used the
Azure.AI.OpenAilibrary so in theory we can also use the Azure OpenAi server (but at the moment we haven't wired up the endpoint code.
Sounds cool right ? well it probibly is but there are a few things to be aware of if you are going to use the OpenAi translation connector:
We have provided some 'suggested' defaults for the variables and settings that are passed over to the OpenAI Api when items are translated - but we don't know if they are ideal, or if there are better options depending on your content.
All we know is that we've build the connector in a way where you can change thses.
These costs are not ours, beyond our control etc. and you will have to have an account with OpenAi and pay the bills ect.
In testing we have seen the OpenAi translations take a lot longer then those from say Microsoft or Google Translation APIs.
There is some Thottling in the Connector so you can avoid hitting Usage limits, depending on your plan you can probibly turn this down, but it will still be slow compared to other machine translations.
Again during testing it would appear that AI based translations are much more likely to change per request when compared to other machine based translations, which are much more consistant.
Open AI translations come from the general AI model, and while this in theory 'knows it all' it is not a translation specific model. Some of the specific machine translation tools might produce better results.
But, AI Translations !