Pre-sale questions

Ask us any question about Linguise service and get an instant reply!

Notifications
Clear all

Which NMT do you use

4 Posts
2 Users
0 Reactions
6,699 Views
(@Aart Jan)
Posts: 1
Topic starter
 
[#323]

Hi Linguise,

I am orienting towards your software to make our woocommerce shop multi-language. A few pre-sale questions:

What exact NMT do you use from Google. And is their a lot of improvement in this, as we see all the AI developments on the moment going on. In another way: is the translation today a lot better then a year ago?

Is it possible to use different domains for different countries from 1 woo installation? like shop.fr, shop.nl etc? or wil it work like shop.nl/fr shop.nl/uk etc. Or both?

Thanks!


 
Posted : 13/12/2024 7:29 am
(@tristan)
Posts: 105
Admin
 

Hi,

Thanks for your message.

Linguise utilizes Google's Cloud AI models to provide high-quality translations. This technology has seen significant improvements over time, consistently improving, there are no new version implementation needed, we always use the latest one. 

Currently, with the WordPress/WooCommerce plugin we support only subdirectories for languages (/nl, /fr...) and for the cloud CMS subdomains like nl.domain.com

If you need further assistance or have more questions, feel free to reach out to our technical team through our contact form, and someone will handle your query privately.

Cheers,


 
Posted : 13/12/2024 7:42 am
(@Thomas K.)
Posts: 1
 

@tristan Hi. I noticed that the Google based translation has still some problems with proper names and technical terms. I am looking for a solution that is based on DeepL or ChatGPT that takes context more into account. Can you make me an offer for further individual development with an API connection to DeepL? There probably is some budget for it available.


 
Posted : 12/02/2025 5:00 pm
(@tristan)
Posts: 105
Admin
 

Hi,

I'm sorry we don't provide custom integration with other translation platforms. As you can understand, it's a lot of work to be done 🙂

Based on our benchmarks, DeepL has not a real advantage when using the API, in terms of quality, price and languages available. As per the AI tools, for now (it changes quickly) the translation process is still very slow and doesn't fit requirements such as instant translation of a website that contains 100K pages, for example.

The translation quality issue you're facing on specific terms, I think it's related to content context, and that's one of the main reasons that makes AI translation slow. That's why we've implemented translation advanced rules.

Hope you understand.

Cheers,

 


 
Posted : 13/02/2025 6:43 am

Leave a reply

Author Name

Author Email

Title *

Preview 0 Revisions Saved