This screenshot was taken after I imported 2 sdlxliff files into an empty TM. How should this be interpreted? Why is the number of TUs imported not the same as the number of TUs read? If none are invalid, what happened to those that were read but not imported? How do I make all of the TUs go into the TM?
Many thanks in advance,
Charlotte
Did the AI answer your question? It's set as the verified answer so just checking.
It did mention this:
When you import SDLXLIFF files into a TM, the number of Translation Units (TUs) read may differ from the number of TUs imported due to several factors, such as confirmation levels, invalid TUs, or existing TUs in the TM.
A more likely reason would be things like duplicate translation units, number only segments, segments that are the same apart from a variable that is in your settings etc. An SDLTM doesn't retain every single TU that is imported unless they really are unique based on the way Trados works. It shouldn't change the effectiveness as you'll still get everything translated.
The downside of this approach is when you share a TMX based on a project with users working in other CAT tools that might need to have every TU. They don't necessarily have the efficiency Trados Studio strives for built into their own tools so you might not get everything translated in their tools from the same TM.
Paul Filkin | RWS Group
________________________
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
Did the AI answer your question? It's set as the verified answer so just checking.
It did mention this:
When you import SDLXLIFF files into a TM, the number of Translation Units (TUs) read may differ from the number of TUs imported due to several factors, such as confirmation levels, invalid TUs, or existing TUs in the TM.
A more likely reason would be things like duplicate translation units, number only segments, segments that are the same apart from a variable that is in your settings etc. An SDLTM doesn't retain every single TU that is imported unless they really are unique based on the way Trados works. It shouldn't change the effectiveness as you'll still get everything translated.
The downside of this approach is when you share a TMX based on a project with users working in other CAT tools that might need to have every TU. They don't necessarily have the efficiency Trados Studio strives for built into their own tools so you might not get everything translated in their tools from the same TM.
Paul Filkin | RWS Group
________________________
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
Hi Paul,
I didn't verify the AI answer so it must have done so itself:-) Sharing an xml with a colleague who's using a different tool was exactly what I was doing, and it seems he did not get my full translation from the import-export-import process. But as I understand your answer, this is simply a downside of using different tools, and there's no way around it?
Kind regards,
Charlotte
You could convert your sdlxliff files with this tool: https://appstore.rws.com/Plugin/113
That doesn't use the APIs so you'll probably get a 1:2:1 conversion suitable for use in another tool. Worth a try anyway. I know 2024 isn't listed (Oana Nagy) but I doubt it makes any difference at all. So download and install from the appstore as opposed to within the integrated appstore in Trados Studio (where you probably won't see it) and just give it a go.
Paul Filkin | RWS Group
________________________
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
Translate
