SDL Trados Studio
SDL Trados GroupShare
SDL Trados Business Manager
SDL Trados Live
SDL MultiTerm
SDL Passolo
SDL Speech to Text
SDL Managed Translation - Enterprise
SDL MultiTrans
SDL TMS
SDL WorldServer
Translation Management Connectors
SDL LiveContent S1000D
SDL Contenta S1000D
SDL XPP
SDL Tridion Docs
SDL Tridion Sites
SDL Content Assistant
SDL Machine Translation Cloud
SDL Machine Translation Connectors
SDL Machine Translation Edge
Language Developers
Tridion Developers
Tridion Docs Developers
Xopus Developers
Community Help
SDL User Experience
Language Products - GCS Internal Community
SDL Community Internal Group
SDL Access Customer Portal
SDL Professional Services
SDL Training & Certification
Style Guides
Language Technology Partner Group
SDL Academic Partners
SDL Approved Trainers
SDL Enterprise Technology Partners
XyUser Group
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 XPP Ideas
Events & Webinars
To SDL Documentation
To SDL Support
What's New in SDL
Detecting language please wait for.......
SDL Trados 2007 used to have a feature that stamped the name of the file you were translating on the Translation Unit in your Translation Memory. This feature was not implemented in any of the Studio versions to date. So this plugin for SDL Trados Studio 2015 brings this back and adds some interesting options. You can decide whether you want to stamp your Translation Units with:
⇓
You can add any of these, or all of them, so they are automatically recording what you worked on when you translated your projects.
This gives you the ability to filter on these for translating work in the future and for carrying out batch editing tasks to remove unwanted translations from your translation memory, or export an extract to provide to a colleague or a client.
The plugin works as a Translation Memory provider, so you just choose RecordSourceTU when you add a Translation Memory to your project. You’ll be asked to select whether you want a new field created, or if you wish to append this information to an existing one, and you’re good to go.
As always it’s a good idea to back up your Translation Memories before you start so if you decide you don’t like to work this way it’s easy to go back.
If you want to learn more about working with fields in Studio then this article might be worth a read : http://multifarious.filkin.com/2013/07/12/fields_attributes/
Once installed, you can now start using Record Source TU by selecting it as a translation memory provider when you translate a new document or in the project settings.
Warning: The application will not record any information if there is no change made to an existing TU.