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.
Manage your TMs and Terms ... and boost your translation business
Are you ready for something fresh in the industry? TM-Town is a unique new site for you -- the freelance translator -- to store, manage and share translation memories (TMs) and glossaries...and potentially meet new clients on the basis of your prior work.
You’re a freelance translator? LSP.expert helps you manage your daily translation jobs. It’s easy, fast and secure.
How about you start tracking translation jobs and sending invoices in minutes? You can also manage your clients and generate reports about your business activities. So you always keep a clear view on your planning, AND you get a free 30 day trial period!