Would it be possible to exclude certain texts or scripts from the translation with a code? The script of the occupancy clone would translate independently (Geolocation is recognized)
I already have another case: a chalet name (headline) which should only be shown in German - now this is also translated.
Hi - I have pretty much identical need for this. Proposed usage is on a Hotel Website, the translations are by in large fine, but the actual Hotel name should not be translated.
It would be great if I could add a class e.g. ā.exclude_from_translationā then anything with this class would be excluded.
Or if in settings for this widget you could include terms that are excluded from translation e.g. āHĆ“tel du Moulin aux Drapsā
Hi @James73 
Thanks for pointing us in this direction! Weāll keep it in mind and see how others feel about this option 
A post was split to a new topic: Icobs get translated
please do this - this is so clutch. we have proper names getting translated
Yep - as it stands, without the ability to exclude terms/words/content, itās not viable.
I recommended the widget in two project proposals last week and could not be used for that reason after further testing.
Hello guys, @Matthew_Dunnerstick, @James73
Thank you so much for your feedback!
This suggestion totally makes sense and we agree that it would be an awesome enhancement.
However, the thing is that we have a set roadmap for our upcoming implementations. Integrating new ideas there can be challenging, no matter how good they are, as we have to balance their popularity with how easy they are to implement.
If more people support your idea, it might be prioritized sooner, but, unfortunately, we canāt make any promises for now.
Weāll promptly update you here in case of any changes
I actually thought this was a bug, not an enhancement 
If you add this āfeatureā, we will buy this. Without this, we canāt. So we arenāt a customer now - weād like to be a customer. But we need to use Weglot until this is added, who does have this ability and also have custom translations as well (the other popular request people are logging) Thanks!
In your check, Iād just add something like class=āelfsight-translate-noā or data-elfsight-translate=āfalseā. Just keep it simple. Since you are doing javascript for this widget, in terms of requests that are āeasy to implement,ā a simple class check on blocks of text may fall into the āinsanely quick and easyā category. Thanks again!
Thank you so much for your feedback!
Your comment does make sense and we would really love to add this feature to our app. However, itās a bit more complex than it may seem, thatās why we canāt implement right away.
As Iāve mentioned above, we have to prioritize based on the popularity of a request and the complexity involved, which means the most demanded features are considered first.
Personally, I think this is a great idea, and Iām hopeful it will catch the interest of more users.
While I canāt promise anything concrete right now, Iāll be happy to update you if there are any new developments
Itās really important to have the option to exclude proper names (like brand names, product titles, or location names) from being translated. For example, translating the name of a chalet or a brand can cause confusion and reduce the user experience. Proper names should remain consistent across all languages. It is like a bug, not an enhancement as said before.
We have good suggestions here, this would help a lot in ensuring the integrity of the content.
Hi there, @danielt
I completely get your point and agree that itās really important to have an option to exclude proper names from the translation.
Hopefully the devs will be able to consider this request in one of the future updates. Iāll make sure to inform you here if anything changes
A huge thank you for your comment and welcome to the Community!
This is crucial! Please implements a āDo not translateā or āCustom translationā list
This widget needs to be able to have a setting to determine the master language of the website.
English is not always the master language. It must be configurable for such a scenario.
Therefore it must be able to translate from any language to any language.
For example my website is Lithuanian. For this widget to be of any use to this website, it needs to skip translation when on the landing page, because its already Lithuanian. And translate from that to the user selected language, if they pick another preferred language. And if they select Lithuanian again, it must be the original Lithuanian text, not a translated version.
Thatās a very reasonable comment, thanks for sharing, @Adam_Plano!
Iāve moved your suggestion to the thread where we discussed similar ideas, and I really hope our devs will pay attention to this request 
Thank you for your help, and welcome to the community!
DO NOT BUY THIS!
YOU CANNOT EXCLUDE WORDS!
Personal names, business information, and even addresses are mistranslated!
How can you call this translation?
This is an INACCURATE translation widget!
Thank you for your comment, @Jura!
Iām truly sorry that our widget didnāt meet your expectations, but I agree that an exclude option would be very helpful. Iāve shared this thread with the team once again, and they found it worth considering.
While I donāt have any updates to share just yet, I promise to keep you posted here as soon as thereās any progress.
Thank you for helping us!