• State Suggested Answer
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 433 subscribers
  • Views 400 views
  • Users 0 members are here
Options
Related

Different source, same target translation

Zora Schneider

Hi everyone

I saw that a similar question was asked 4 years ago, but there was no solution provided for the problem.

We are regularly translating specific terminology consisting of one or two words. Let's say we want to translate "fishing rod" into German. The equivalent would be "Angel".

Now a week later we need to translate "door hinge", which would also be "Angel" in German (if kept short). The problem is the client can only input translations/expressions which have not been used yet. This means because "Angel" has already been used before, it cannot be used again as a translation for this new term "door hinge". Of course, the translator could look up their translation in concordance search to make sure this translation is not in the translation memory. But doing this for every single word when we roughly translate 1.000 words per week (into 8 languages) is too time-consuming.

We also considered implementing all the translated content as "forbidden terms" into the termbase, but this would also be extremely time-consuming.

So I was wondering if anyone knows of a workaround or function which could offer the solution to this issue.

Thanks a lot in advance!
emoji
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0

    Hello, Zora!

    Using a synonym can always help... Türangel, z.B. Türscharnier...

    Anyway, concordance search in a TM is not so time-consuming...

    By "implementing all the translated content as forbidden", you mean all the terms in all languages in your TDB? What about the terms with approved translation? I mean, what will be shown in the Multiterm window if all the terms in the database are forbidden?

    From my point of view, if you actively use the TDB, you have to work on that. On a daily basis.

    Repeated terms can be easily avoided at the moment a new term is added to the termbase: the program will always ask you if you want to merge the terms and this is the red red light saying: this term is already being used for another concept.

    This will work when adding terms from the Editor window or when you create new items directly in the Multiterm app.

    True that having several terminology databases (per project) is convenient, because sometimes you just cannot avoid using the same term....however, if applied to unrelated fields, and different projects, this could do perfectly.

    Best regards!
    emoji
Reply
  • 0

    Hello, Zora!

    Using a synonym can always help... Türangel, z.B. Türscharnier...

    Anyway, concordance search in a TM is not so time-consuming...

    By "implementing all the translated content as forbidden", you mean all the terms in all languages in your TDB? What about the terms with approved translation? I mean, what will be shown in the Multiterm window if all the terms in the database are forbidden?

    From my point of view, if you actively use the TDB, you have to work on that. On a daily basis.

    Repeated terms can be easily avoided at the moment a new term is added to the termbase: the program will always ask you if you want to merge the terms and this is the red red light saying: this term is already being used for another concept.

    This will work when adding terms from the Editor window or when you create new items directly in the Multiterm app.

    True that having several terminology databases (per project) is convenient, because sometimes you just cannot avoid using the same term....however, if applied to unrelated fields, and different projects, this could do perfectly.

    Best regards!
    emoji
Children
No Data