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.......
A translation project is created with the following project description: please adhere to length restrictions and do not translate term XYZ.
When the project is sent to the translators, they get a notification with this description and they can also see it online, so they know what to do.
However client reviewers do not get the same information when they get the notification to review a translation, which in turn leads to unnecessary comments.
For example when a term left untranslated by the translator as per the project description, but the client reviewer leaves a comment "please translate". Not only does it create unnecessary work, the client reviewer might perceive the translation to be of low(er) quality.
but how do you enter this as an instruction? this is only available in the review format
I guess this would be the current solution. But unfortunately from my experience this is not how Client Reviewers work. They're often people who have other work, their primary job, and review translations…
Perhaps using Task Comment could resolve the issue? It's a global comment for a file and it is visible from Mantra.
I do not really agree. You would then need to do that for every target language (and probably multiple tasks, since you cannot be 100% sure what task the reviewer opens first) whereas the instruction is already available in the job description. I would assume that reviewers can download reference material during their review? If yes, we could add a short instruction as reference material. If not, I feel making reference material available for reviewers is something that needs to be supported in a future update.
Reference files are already available to users via the Client Review interface, so I would agree with Bernd's suggestion on how to approach this.
I guess this would be the current solution. But unfortunately from my experience this is not how Client Reviewers work. They're often people who have other work, their primary job, and review translations on the side. I see that they do not familiarize themselves sufficiently and do not download reference files. Or they only use Mantra so little that they forget functionality. So instead they log in and go right into the review interface and want to get the job done. I believe it would be a much better UX if instructions and background information could be communicated with client reviewers there, right at the top.