Some of these cookies are essential to the operation of the site,
while others help to improve your experience by providing insights into how the site is being used.
Since I bought Studio 2014, I've been using it to translate TagEditor files (.ttx) (in stead of using TagEditor itself). This *usually* goes without problems - after using 'Generate Target translations', I get a fully translated TagEditor file again. However, sometimes (not always!), the XU segments (which were converted to locked segments in Studio 2014) come out NOT locked anymore in the final target file. According to the client, this presents problems (not sure what those problems are, the tech guy speaks minimal English and the PM speaks minimal Tech). Has anyone had this problem as well? If so, how did you solve it?
The client now asks me to please go back to using TagEditor, which I really would hate to do, as I vastly prefer Studio 2014.
Thanks for any help,
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
Well, I asked the client, and he sent me some files to investigate. However, these did not present the issue (they exported XUs correctly). So I've notified the client, and have not heard from him again yet. I will keep you informed.
The leading translation software used by over 250,000 translators.
SDL Trados Studio 2019 has evolved to bring translators a brand new experience. Designed with user experience at its core, Studio 2019 transforms how new users get up and running, helps experienced users make the most of the powerful features, ensures new
Translate faster & easier, using a sophisticated CAT tool built by a translator / developer.
Accept jobs from clients who use SDL Trados, MemoQ, Wordfast & major CAT tools.
Download and start using CafeTran Espresso -- for free