I’m attaching two files. One file gets converted and the other file not. I’m using the latest version of the converter and of Studio. This has been a regular problem with this converter during all the years and all the versions that I have used it. It will convert most files, but not all files, throwing the infamous and incomprehensible error message “An item with the same key has already been added”. Help please.
You have provided two sdlxliff files that seem to be PPTX files converted to SDLXLIFF. The SDLXLIFF to Legacy Converter is not for this purpose so please explain what you are doing. If you read the help it says this:
The SDLXLIFF to Legacy Converter allows you to quickly export SDLXLIFF files to the following formats.
The application also allows you to import from-
This tool is especially useful for translators that do not use Studio, so that the translator can work in the legacy file formats.
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
Where does it say that this tool cannot convert sdlxliff files that have been created from PPTX files? I'm converting from sdlxliff to TTX. I'm not converting to PPTX. Both files have been converted from PPTX to sdlxliff by RWS. Why does it convert only some of these files?
I'm attaching another couple of sample files that I had kept from 2021 and they are displaying the same behaviour today with the latest version of everything as back in 2021.
You're right... I had my head up my a***.
I cannot offer an explanation for why this app only handles one of your files... most likely it's because we have not done any work on it for many years and the structure of the SDLXLIFF could have changed under some circumstances and prevented this from working. It may have always been a problem... who knows!
But I wonder if the tools you use to handle this as TTX would be able to handle a very basic XLIFF format? If so you could try exporting to XLIFF with the XLIFF Manager. If this works for you the workflow is also much more transparent and easier to handle. TTX is so old now I doubt we'll get around to attempting to fix this any time soon.
I have attached a conversion to the very basic and 100% vanilla XLIFF we can create using this tool so you can see if it's a workable solution for you:
This is also a very much upto date app and will be developed more in the future so a better choice than the old Legacy Converter. The XLIFF formats supported are one for Polyglot (a basic format for Google) and one we created for more general use that is properly XLIFF compliant in a sensible way. The latter is the format I used here and any sensible CAT should be able to manage this.... as long it isn't older than around 2002... although I think the first proper XLIFF was around 2008. Hopefully whoever you provide these files to isn't using anything older than that!
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
What is the purpose of converting these files? Your files in the first sample are fully translated, so what shall ttx be for?
_________________________________________________________
When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.
Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.
I’m using the legacy converter for proofing purposes. Like so: Convert from SDLXLIFF to TTX. Convert TTX to RTF (using another tool I have). (Yes, I know I can export to RTF directly with the converter, but this causes various other problems that I don’t want). Clean up RTF in Trados Workbench (yes, the old amazing tool that is still faster and, in many respects, better than any current tool) to get a target only file. Analyse all clean RTFs in an empty Workbench memory to get rid of all duplicates. Export the result to 1 RTF file. Open this file in Word and do the proofing there. Manipulate in Word as desired (alphabetically for instance). Any linguistic issues found to be fixed in Studio. Other checks (tags, termbase) also to be done in Studio. I’m using this method because I’m not aware of any facility in Studio to export the entire target text from a large, multi-file project to one file with a neat format. Also I have a macro in Word that formats any tags into just a red bracket so that I know that a tag is there, but it doesn’t interfere with my proofreading.
Thanks for the explanation. Fairly complicated, but I'm afraid "Export for bilingual review" will not fulfil your needs, as I previously hoped.
_________________________________________________________
When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.
Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.
Yes, sadly it doesn’t. Proofreading is an essential task, and there are so many things that Studio doesn’t provide for this task. Such as the lack of vertical view as the default view. Was missing for so many years and still only available as an add-in with missing features and bugs that prevent me from using it. Or not letting you know which segments have a different translation than those in your translation memory, and not highlighting these differences. And not automatically confirming those segments that have a 100% proofed target match in the translation memory.
Not strictly correct...
not letting you know which segments have a different translation than those in your translation memory
"Confirm and translate until next fuzzy match". It won't show you target segment differences but it will stop at every segment that is different to the ones in your TM.
not automatically confirming those segments that have a 100% proofed target match in the translation memory
Isn't this just a setting?
the lack of vertical view as the default view.
Still not the default, but you could save your project to the cloud and get the layout you want there. It's not the default, but once you switch it (couple of clicks) that will be the one you use.
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
If I in Review mode use “Confirm and Translate until Next Fuzzy Match” it doesn’t set the status to “Reviewed” for the concerned segments.
“Save to Cloud” is not available.
I’m not sure if anyone at RWS understands the enormous difference in quality and efficiency there is between vertical and horizontal view of source and target. 
Translate
