Emma Goldsmith

You’re not doing anything wrong Emma. You just don’t know that the termbase you are trying to use is not the type of dictionary you can use in MT Cloud. This feature to use dictionaries requires a dictionary in your MT Cloud Account specifically, it has nothing to do with Trados Live and the Terminoloy solution in there.

To use MT Cloud dictionaries you need a paid account and not the free subscription you are using now.

I'm trying to investigate this but cannot find anywhere information as to how I sign up for a paid subscription and what such paid options there are. (The information given about the CU5 update only seems to indicate that the feature that Emma describes is included in that update, which -- I have learned both here and elsewhere -- is incorrect.)

Mats Linder

Mats Linder said:

I'm trying to investigate this but cannot find anywhere information as to how I sign up for a paid subscription and what such paid options there are.

You probably can't.  At the moment we don't sell Machine Translation in small packages so we don't have anything available for freelancers.  Most freelance translators (not freelancers who are really working as a small agency) will have sufficient MT provided for free within the 500k chars/month and this is borne out by the usage we see. We are going to address this in the near future, but for the time being if you do want to purchase a package the only way to do it is by contacting us through here:

https://www.trados.com/products/machine-translation/

Then use the contact us form at the bottom:



Also note the "clues" in the wording here - "If your organization requires a more comprehensive solution...".  The available paid solutions we offer today are aimed at an Enterprise and not a freelance translator and will be well in excess of the cost of Trados Studio.  At the moment we just don't cater for the needs of a freelancer who does more than 500k/month, or who wants to be able to use "dictionaries" to improve the relevance of the NMT they are getting.  This will change, and we are working on this and hope to have something available in smaller packages more suited to the needs of a freelance translator soon.

The problematic part in our documentation is the use of the word "dictionaries".

Mats Linder said:

The information given about the CU5 update only seems to indicate that the feature that Emma describes is included in that update, which -- I have learned both here and elsewhere -- is incorrect.

It's not incorrect because that the feature is indeed included.  It says this:

If I look in Studio since CU5 I see this:

This ability to add a "Glossaries" was not there before.  It was only possible using the MT Cloud plugin on the appstore.  Clicking on the link (where available) takes me to this:

A list of the available "glossaries" I have in my MT Cloud account.

There are two important things to note here:

1. "MT Cloud account" and NOT "Language Cloud account".
2. The use of the word "glossary" is a mistake in Studio and in the release notes.  It should be "dictionary" which is the correct name used in the "MT Cloud" account, like this:
   

I hope this clarifies things for you a little more?

Thanks for your efforts, Paul! The first part of which I had already been told / figured out. I was also directed to this web site, which I believe even better than your suggestion tells me what's what.

https://www.rws.com/translation/software/trados-studio/nmt-for-studio/

There is still the problem, however, that apart from the 500,000 character specification, there are no descriptions of which features are included in the free subscription and which require a paid one (see for example below).

But the last part is still problematic to me. In the first place (a minor matter), the CU5 information tells us that there should be an Add glossaries option at right, but in both your Studio and mine, there is only Glossaries. But when I try to do the same as what you do, the Glossaries option is dead. Does it have something to do with the fact that also the Manage AdaptiveMT Models button is inactive as well? Anyway, here is what I see (and I should add that I have created a De-Sv termbase which should be available but is not).

The fact is, I already approached Daniel about this, and he gives a different reply to yours: "my first question would be – do you have a paid MT Cloud subscription that entitles you to use glossaries?" Which I obviously don't. And this is the reason why I thought the statement in the CU5 description is incorrect or at least misleading: this feature, too, seemt to require the paid account that you describe in the first part of your reply. And Radu Boloveschi (yes, I have been busy!) seconds this: "As Daniel mentioned, you would need a paid MT Cloud subscription with the Dictionary add-on." Again, then: I miss a web page where such matters are clearly outlined.

So -- still confused...

Mats Linder

I’m wondering if you really read my reply! I don’t know how else to explain this to you:

1. Studio and the CU5 release notes are wrong. They should say “dictionary” and not “glossary”
2. You have created a LC termbase. This is not an MT dictionary and so your de-Sv termbase won’t appear here, nor should it.

Daniel, sorry Daniel, has not helped your understanding because he answered you as if your use of the term glossary was correct. It was not. You want to add a dictionary (not a glossary) but you do not have an appropriate account to do this. The machine translation provider uses dictionaries and not glossaries.

We actually don’t use glossaries anywhere in our software and I have no idea what possessed the developer to use this term, nor do I know how this mistake got so far and was used in the release notes and the product.

The free subscription is just that, 500k char per month. There is nothing else stated and nothing to add. You are only questioning this now because you know it is possible to use a dictionary but you don’t have an account that supports it. I also explained that for anything more than the 500k you need to contact us as stated in the website.

But having said all of that, yes I do agree that we should have an article that states what is possible and what type of package you need to achieve it. Once we have clearly defined what these are you will get one. Until then it’s simple.  Free subscription is 500k chars/month and for anything else you contact us.

Mats Linder

I’m wondering if you really read my reply! I don’t know how else to explain this to you:

1. Studio and the CU5 release notes are wrong. They should say “dictionary” and not “glossary”
2. You have created a LC termbase. This is not an MT dictionary and so your de-Sv termbase won’t appear here, nor should it.

Daniel, sorry Daniel, has not helped your understanding because he answered you as if your use of the term glossary was correct. It was not. You want to add a dictionary (not a glossary) but you do not have an appropriate account to do this. The machine translation provider uses dictionaries and not glossaries.

We actually don’t use glossaries anywhere in our software and I have no idea what possessed the developer to use this term, nor do I know how this mistake got so far and was used in the release notes and the product.

The free subscription is just that, 500k char per month. There is nothing else stated and nothing to add. You are only questioning this now because you know it is possible to use a dictionary but you don’t have an account that supports it. I also explained that for anything more than the 500k you need to contact us as stated in the website.

But having said all of that, yes I do agree that we should have an article that states what is possible and what type of package you need to achieve it. Once we have clearly defined what these are you will get one. Until then it’s simple.  Free subscription is 500k chars/month and for anything else you contact us.

Actually I did read your reply as carefully as I could. But I understand now that there is a difference between the concepts of "dictionary" and "termbase" (and from your replies, it seems that "glossary" is a third concept, different from the other two). I need to explore that closely and I'll try to do that without bothering you further.

I'm sorry -- I have to add one more question: How do I arrive at the page shown in your last image? This is my own SDL Machine Translation Cloud page header:

Mats Linder

Mats Linder said:

it seems that "glossary" is a third concept, different from the other two

Please note... it is not a third concept!  It's a mistake!  The glossary that was referred to should have been called a dictionary.

Mats Linder said:

I need to explore that closely and I'll try to do that without bothering you further.

No problem "bothering" me at all Mats, I'm always happy to engage.  I guess I'm annoyed that we made a mess of such a simple concept so it's confusing you, and that I am unable to explain this clearly to you.  My apologies.

Mats Linder said:

I'm sorry -- I have to add one more question: How do I arrive at the page shown in your last image? This is my own SDL Machine Translation Cloud page header:

You have arrived at it.  But because you don't have the same "paid" account that I have access to you are seeing different things.  Can I ask that we drop this question for a few weeks?  There are some plans to make something available as a paid package more in line with the requirements for a freelance translator, and once we have this in place we can have a sensible discussion about it.  Right now I believe the costs involved with the current packages, that are aimed at large Enterprises, means that the features you are trying to get to the bottom of are really out of reach for a freelance translator.  They are designed for companies doing well over the 6 million chars a year that we provide for free. As an example, the Enterprise package starts at around a billion chars a year and includes a lot more features than just dictionaries.

I'll revisit this thread when we have more details and expand upon the options.

OK; thanks for all your efforts, and the last reply makes good sense (and it would have helped if you earlier had not said "the feature is indeed included", without any qualification).