Under Community Review

Reversing language directions for server TMs

Users quite often work with AnyTM for file based resources but when they migrate to GroupShare the feature is unsupported as result the functionality of the translation system is decreased from translator's point of view.

Yuriy Belik
Parents

  • Hi   , thank you for your contribution.  This is very good, it helps us understand better the customer perspective. This idea is for sure a good one (I voted for it! :)). I think that for file-based TMs right Studio needs to create a reverse TM in the background due to the technology used for the TM. I don't think it is even technically possible to directly look up languages in the reverse order, so this may require a bigger change, but it is indeed a good suggestion. As for termbases, you currently can assign any project language to any termbase language and term recognition/term search will work.  For more serious term management, you can use MultiTerm Desktop which will allow the search to be performed for any of the languages. Why would you need to search in the target language though in the Studio Editor? I am not a translator myself, so maybe I am missing something, but right now, if you click inside a target segment, Studio will automatically recognize all terms. Then you have AutoSuggest who will present to you the target translation of the term, so it is very easy to insert it. I am not sure when and why would one need to search in the target language?

Comment

  • Hi   , thank you for your contribution.  This is very good, it helps us understand better the customer perspective. This idea is for sure a good one (I voted for it! :)). I think that for file-based TMs right Studio needs to create a reverse TM in the background due to the technology used for the TM. I don't think it is even technically possible to directly look up languages in the reverse order, so this may require a bigger change, but it is indeed a good suggestion. As for termbases, you currently can assign any project language to any termbase language and term recognition/term search will work.  For more serious term management, you can use MultiTerm Desktop which will allow the search to be performed for any of the languages. Why would you need to search in the target language though in the Studio Editor? I am not a translator myself, so maybe I am missing something, but right now, if you click inside a target segment, Studio will automatically recognize all terms. Then you have AutoSuggest who will present to you the target translation of the term, so it is very easy to insert it. I am not sure when and why would one need to search in the target language?

Children
No Data