Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’ve got TMX files that have a tuid that is used by the Zend Framework to translate my application’s texts. However, after importing the TMX files in SDL Trados Studio, and re-exporting them, the tuid is missing. Other editors, like Heartsome TMX editor, do preserve the TUID. However, my translation agency is using SDL Trados, so I would like to know if there’s a way to preserver this tuid.
Studio doesn’t need the TUIDs and therefore drops them during import. One way would be to run a script on the TMX to convert the TUIDs to custom field values, but then these are also ignored by the Studio import unless the TMX flavor is one of the known ones (SDLX, Studio, Workbench).
Unfortunately this is typical of data loss when processing third-party TMX in Studio. We only preserve all the data in the TMX if it’s one of our flavors as otherwise we don’t know how to interpret that data. It boils down to TMX’ complete lack of semantic specification.
Interesting that Heartsome preserves it though.