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.......
I have a situation here that is puzzling me.
My company has a process where we have to translate a particular form using pink text for our translation and green text for anything we want to query or comment on to the next person along the chain, while the original German is preserved in black for reference purposes. This is formatting that obviously was not present in the source file.
In order to achieve this, we are adding a color tags cell in Excel, before import, that says pink green, so that we have access to these color tags and can duplicate them through the document during translation as needed (with the "highlight target words, CTRL+Left Mouse on tag in source" process).
The problem comes in that when Studio encounters an identical segment to one that was already translated and confirmed into the TM, the match that comes up is 99% without any of the new target-only tags (those that were not present in the source).
Does anyone know what might be happening here? Is there a setting somewhere I have to enable or is this just architecturally how Studio works (tags not in the source are ignored)?
Grateful for any help you can offer!
Test file.xlsx This is a sample file I created to test it.
Project 1.zip This is a project containing that file and a blank TM based off the project settings I am using for everything, with an edited segment that is ready to confirm. When I press CTRL+ENTER then the segment is duplicated but the pink color tags disappear in the duplicates.
Hi Mark Smith
Thanks for the files. I don't get 99% matches, rather 100%, but the tags are indeed missing. I believe this is because you are duplicating the unique tag IDs by taking across the #3 tags in the next segment. If you use quick inserts for example then the tags are carried over through the TM:
I don't think it's possible to create a quick insert for the colours unfortunately so this isn't going to work. It could be done with a custom plugin I think.