Background of the issue:
I want to use DeepL as the default translation engine for my site hidden link. I have set it up as the default translation engine.
Symptoms:
When I translate, I always get the first backup engine instead of DeepL. If I disable all other engines in the settings and leave only DeepL, the option for automatic translation is not available.
Questions:
What can I do to repair the issue where DeepL is not being used as the default translation engine?
Why is the option for automatic translation not available when only DeepL is enabled?
Unfortunately, Croatian is not currently supported by DEEPL translation engine, you can check full list of supported language per engine, on next link: hidden link.
You can use other translation engine, or WPML will use next fallback engine in line, as it currently does for you.
Oh ok. I was under the impression that croatian is available. Too bad.
I have a "on hands" question regarding Google vs WPML AI engine.
Google translate has a bit of a bad reputation. I'm guessing the engine here is the same? Is WPML AI 2x better then Google? Most pages will be double checked but some translations might slip through though..
Should we use Google or is it much better / safer to use WPML AI?
Google engine uses similar but not the same as you use in Google translate, it also includes some other improvements from our side etc, but yes in general WPML AI seems to do a better job and we are constantly improving it.
Also if you get any bad translation you can report it back to us, and since it is our translation engine, we can further check / treat it like a bug and improve the quality of it.
I consulted with chat GPT 🙂
I think we'll use a combination of both. Google for products, WPML for marketing pages.
One wish / suggestion:
It would be nice if it were possible to select the engine in the translation editor.
BR
sure, however it works and is best for your usage case. 🙂
Thanks for suggestion, but for now we do not have plans for such change / feature in the near time, but that would be nice addition in the future and we will keep it on our mind for future improvements feature.