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 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.......
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.
I agree this should be out of the box, both for local and server TMs. Especially when you know that a Server TM is a SQL database, there is really no reason to no be able to query it in either direction.
I also think this is an extremely important enhancement. Not being able to benefit from work in the reverse Language pair is limiting especially for corporations who are constantly translating content back and forth related to the same topic/field. In GroupShare I know you can add several Language pairs to a TM. In the case of adding, for example, English_US > Portuguese_BR and Portuguese_BR > English_US how would you use AnyTM Server based in this case? Or do they have to be two separate TMs? What is the purpose of creating a multi-lingual TM in GroupShare if reverse languages don’t work in the same TM? I think that ideally you should define the language pairs for a TM in GroupShare and then they update between the languages automatically, but I guess this isn’t possible, right? If I’m not mistaken I remember back in SDLX you could add all your Language pairs in a TM and if you chose EN_PT it would automatically reverse your TM in a PT_EN job. Was that because it was based on access databases? In SQL wouldn’t it work the same way?
Hi Stepan Konev , thank you for the clarification, it does make sense now that you have given us an example. Thank you.
Why would one need to search TM in its target section? But Trados still (finally) has this option.
Example: I have an abbreviation 'WPQT' that is not a term (not included in termbase) in my English source. From context, I suspect (I feel that it must be) a Russian equivalent [????????? ????] but I still need confirmation.
Now, without TB target search feature, I have to switch to Ru-En project and search for "????????? ????". After it finds a "????????? ???? ????????", I see the proper term in English: Welder Performance Qualification Test Record. Ok, from now I can safely use the suspected equivalent as true one.
I don't think Kilgray would ever add this option to their memoQ, if it was not obviously needed by translators. But they did it from their earliest versions several years ago without asking why we need it =)
Hi Vasiliy Golovatskiy Stepan Konev , 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?