SDL Trados Studio
SDL Trados GroupShare
SDL Trados Business Manager
SDL Trados Live
SDL Speech to Text
SDL Managed Translation - Enterprise
Translation Management Connectors
SDL LiveContent S1000D
SDL Contenta S1000D
SDL Tridion Docs
SDL Tridion Sites
SDL Content Assistant
SDL Machine Translation Cloud
SDL Machine Translation Connectors
SDL Machine Translation Edge
Tridion Docs Developers
SDL User Experience
Language Products - GCS Internal Community
SDL Community Internal Group
SDL Access Customer Portal
SDL Professional Services
SDL Training & Certification
Language Technology Partner Group
SDL Academic Partners
SDL Approved Trainers
SDL Enterprise Technology Partners
ETUG (European Trados User Group) Public Information
Machine Translation User Group
Nordic SDL Tridion Docs User Group
SDL Tridion UK Meetup
SDL Tridion User Group New England
SDL Tridion West Coast User Group
SDL WorldServer User Group
Tridion Docs Europe & APAC User Group
Tridion User Group Benelux
Tridion User Group Ohio Valley
SDL MultiTerm Ideas
SDL Passolo Ideas
SDL Trados GroupShare Ideas
SDL Trados Studio Ideas
SDL Machine Translation Cloud Ideas
SDL Machine Translation Edge Ideas
SDL Language Cloud TMS Ideas
SDL Language Cloud Terminology Ideas
SDL Language Cloud Online Editor Ideas
SDL Managed Translation - Enterprise Ideas
SDL TMS Ideas
SDL WorldServer Ideas
SDL Tridion Docs Ideas
SDL Tridion Sites Ideas
SDL LiveContent S1000D Ideas
SDL Contenta S1000D
SDL XPP Ideas
Events & Webinars
To SDL Documentation
To SDL Support
What's New in SDL
Detecting language please wait for.......
Among other issues ( Adaptive TM not working nor Uplift), I have tried just about every setting imaginable (variants of character based or linguistic based search) and the SDL Language Cloud Termbase either returns nothing or seemingly every term in my Termbase, most of which are completely irrelevant to the source segment. I am not sure if the fact that the Portuguese language has "de" in a large majority of the terms or what...
I did rename the file in the SDL folder (.old) which did force me to login again, but the problem continues.
In addition the adaptive TM which should be using the terms in my Language cloud Termbase does not do so.
Tertiary, is the fact that I have long given up on Uplift actually working...
A wee bit frustrated....
I am using Trados 2017 all updated and I set the Language Cloud TB as the default TB, so I could as terms as I go... If that makes a diference.
Hello Jerel R. Pulicicchio (JerelR. Pulicicchio)
I think there are two separate issues herewhich are unconnected.
1) Translation memory & 2) Termbase
1) Translation Memory
This following video(s) shows how you need to set up your (Adaptive) MT engine correctly (via settings)
As I am sure you are aware, our Language Cloud based Termbase (still a beta model) is designed so that you can share your TermBase with others who of course need to be using Studio and also have a language cloud account.
The following video shows how to create the online Termbase and how you can share the TB
Are others who you are sharing your TermBase with experiencing the same problems?
If you are receiving either "nothing or everything" then maybe you could try changing the following settings-
Does this help at all?
If not- I would be more than happy to set up a remote webex with you to have a look at this.
Hello Jerel R. Pulicicchio (JerelR. Pulicicchio) ,
I think here we should discuss this in a little more detail as its still unclear of what is required.
First of all, it is not possible to force Adaptive MT to use terms from a local Termbase (online or otherwise).
Termbase is a separate to MT Adaptive which should be seen as an extension to your TM
MT Adaptive works in the background (and in the cloud) and learns from the way you translate and in particular your own style- (as explained in the first video above).
You should be able to get results from your term base by doing the following in your Project Settings-
Does this help?
Jerel R. Pulicicchio said:Ok. Can you tell me why the adaptive MT will have apparently learned a term, and then all of a sudden completely forget what it learned?
Because it is not as simple as that. The AdaptiveMT does not take into account every possible mistake, or intended change you make. If it did this the results of the MT would very quickly become very poor. There is a science behind the way it works so that it only uses something it is sure about before changing the way it provides you with a machine translated text.
Jerel R. Pulicicchio said:My issue still remains with the Language Cloud TB returning all no terms...
Can we do a Skype session and take a look at this? Drop me an email at firstname.lastname@example.org with your Skype details if this is ok.
Jerel R. Pulicicchio said:In the meantime, could you point me to where it was informed that the TB is not considered in the Adaptive MT? (despite the tool allowing you to configure it as such).
When 2017 and AdaptiveMT was released the ability to use dictionaries was removed altogether. This is in the release notes. The reason they were removed was because AdaptiveMT was not thought to need them. It became clear that with the limited language pairs available for AdaptiveMT we needed to bring this back for the normal LanguageCloud engines. So this was added back in with SR1 (I think...).
Unfortunately the UI doesn't do a good job of making clear where you can use dictionaries in the way you wish and where you can't. There is just a large splash across the top talking about AdaptiveMT and the Dictionaries and the non-Adaptive engine selections are in this same place. So anyone coming into this without the benefit of the history behind it couild easily be confused as you have been.
Jerel R. Pulicicchio said:Also, is there any high-level documentation of the Adaptive MT?
Only what you will find in the product help, and if you google it: