Hi Lera OHT

Lera OHT said:

The above options are solution suggestions, but if you have a better solution using SDL Trados Studio or/and SDL Multiterm to translate glossary terms using the existing TMs it would be great to share your ideas and solutions.

I think the solution you seem to have in mind is fine.  You didn't ask how to do that so this is probably why you didn't get a response.

One question I do have is related to the number of languages in your file.  If it's a multilingual spreadsheet then you would currently need to create multiple bilingual Excel projects, or use something like Excelling Studio from the appstore, or use Passolo.  But in the next release of Trados Studio we do have a multilingual Excel filetype (via the RWS AppStore) which would support creating a single project for all of your languages.  So a neat feature and huge timesaver as it also has the ability to handle embedded content properly and generate a single target file than contains all the languages so you don't have to put them together manually.

Thanks

The work is basically to create a bilingual Excel for each Language Pair - not a multilingual Excel file.

I can see that we can set the TM matches as a 30% minimum. This means that Studio will pop up TM matches with a minimum match of 30%. I assume it can't be set with a lower value.

A question: Is there a better way to translate a glossary using an existing large TM?

Lera OHT

Lera OHT said:

Is there a better way to translate a glossary using an existing large TM?

You basically have three ways to do this in a CAT tool:

1. Using your TM as you have said (existing translations, fragment matching, alignment...)
2. Using machine translation and post-editing
3. using your own head and manually translating each term

Lera OHT said:

The work is basically to create a bilingual Excel for each Language Pair - not a multilingual Excel file.

If you have more than one language pair are they same source multiple target languages or completely different pairs?  Just asking because of the way you phrased that statement.

interesting..

Can you add some more specific info how to handle this asked task with the way #2 you mentioned ? I mean MT way ?

That should be the futuristic style, I guess, and I have no idea how to achieve...

Kelly Edward

Kelly Edward said:

Can you add some more specific info how to handle this asked task with the way #2 you mentioned ? I mean MT way ?

Probably you are overthinking this.  Just add an MT engine to your project, pre-translate it, then post-edit the MT.

actually, my question is related following;

what is the "real" differencies between MT engine and TM engine for this strictly limited asked task ? ...except "futuristic" wordings.

Kelly Edward

I really have no idea what you are talking about.  You are definitely over complicating a very simple task.  The OP asked about how to translate glossaries using a TM.  I just suggested two other ways.  Use machine translation instead of a TM, or just do the translation yourself which might be more appropriate if the terms are not reliably translated because they need more of a transcreative approach.

I mentioned "existing translations, fragment matching, alignment" because these are all ways of leveraging a translation memory.

What exactly does ""futuristic" wordings" even mean?  Nobody is trying to be clever here.

Kelly Edward

I really have no idea what you are talking about.  You are definitely over complicating a very simple task.  The OP asked about how to translate glossaries using a TM.  I just suggested two other ways.  Use machine translation instead of a TM, or just do the translation yourself which might be more appropriate if the terms are not reliably translated because they need more of a transcreative approach.

I mentioned "existing translations, fragment matching, alignment" because these are all ways of leveraging a translation memory.

What exactly does ""futuristic" wordings" even mean?  Nobody is trying to be clever here.

hmm..
That's fine with me.

Thanks for the reply.