Trados Business Manager
Speech to Text
Managed Translation - Enterprise
Translation Management Connectors
Language Weaver Connectors
Language Weaver Edge
Tridion Docs Developers
RWS User Experience
RWS Community Internal Group
RWS Access Customer Portal
RWS Professional Services
RWS Training & Certification
RWS Enterprise Technology Partners
Trados Academic Partners
Trados Approved Trainers
ETUG (European Trados User Group) Public Information
Machine Translation User Group
Nordic Tridion Docs User Group
Tridion Docs Europe & APAC User Group
Tridion UK Meetup
Tridion User Group Benelux
Tridion User Group New England
Tridion User Group Ohio Valley
Tridion West Coast User Group
WorldServer User Group
Trados GroupShare Ideas
Trados Studio Ideas
Language Weaver Ideas
Language Weaver Edge Ideas
RWS Language Cloud TMS Ideas
RWS Language Cloud Terminology Ideas
RWS Language Cloud Online Editor Ideas
Managed Translation - Enterprise Ideas
Tridion Docs Ideas
Tridion Sites Ideas
LiveContent S1000D Ideas
Events & Webinars
To RWS Documentation
To RWS Support
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.
MATE or similar broker could automatically add job description as a task comment if it's not used for other purpose, but probably that'd be an overkill if reference materials could do the trick.
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.