Salesforce

Trados Studio 2024 - after opening a WSXZ package, when trying to save as target, I receive the error "Failed to save target content: Cannot find file type definition with id Custom XML v 1.3.0.0"

« Go Back

Information

 
TitleTrados Studio 2024 - after opening a WSXZ package, when trying to save as target, I receive the error "Failed to save target content: Cannot find file type definition with id Custom XML v 1.3.0.0"
URL Name000022435
SummaryThis is a side effect of the complete removal of XML 1.2.0.0 and XML 1.3.0.0 File Types in Trados Studio 2024. While these File Types have been removed from the native Trados Studio program for a long time, in Trados Studio 2022 it is still possible to import XML 1.x File Type configurations exported from WorldServer. This feature has been completely removed from Trados Studio 2024.

So while you will still be able to open the WSXZ package exported from WorldServer projects segmented using these Custom XML (deprecated) file types, saving as target will not work because it requires the native File Type to be recognizable. This is no longer possible in Trados Studio 2024.

Solution: as a WorldServer administrator, consider migrating all your File Types to Custom XML 2, which is fully supported in Trados Studio 2024.
Workaround: As a Trados Studio user handling these packages, work in Trados Studio 2022 only.
Scope/EnvironmentTrados Studio 2024
WorldServer
Question
After opening a WSXZ package exported from a WorldServer project with XML source files segmented with a Custom XML (Legacy Embedded Content) - corresponding to XML 1.2.0.0 - or a Custom XML (Embedded Content Processor) File Type configuration, I receive the error

Failed to save target content: Cannot find file type definition with id Custom XML v 1.3.0.0....

Important: the same issue can happen with TMS, GroupShare or Studio packages using XML 1.x File Type

User-added image

or

Failed to save target content: Cannot find file type definition with id Custom XML v 1.2.0.0

User-added image
Answer
This is a side effect of the complete removal of XML 1.2.0.0 and XML 1.3.0.0 File Types in Trados Studio 2024. While these File Types have been removed from the native Trados Studio program for a long time, in Trados Studio 2022 it is still possible to import XML 1.x File Type configurations exported from WorldServer. This feature has been completely removed from Trados Studio 2024. Please read this article for more details:

Trados Studio 2024 - error when importing XML 1.2.0.0 and XML 1.3.0.0 File Type configurations exported from WorldServer

So while you will still be able to open the WSXZ package exported from WorldServer projects segmented using these Custom XML (deprecated) file types (or packages exported from TMS, GroupShare or earlier Trados Studio versions), saving as target will not work because it requires the native File Type to be recognizable. This is no longer possible in Trados Studio 2024.

Solution: as a WorldServer, TMS or GroupShare administrator, consider migrating all your File Types to Custom XML 2, which is fully supported in Trados Studio 2024. Please refer to this article for instructions: 

Migrating XML 1 file type settings to XML 2 in Trados Studio

Workaround: As a Trados Studio user handling these packages, work in Trados Studio 2022 only.
Reference
Attachment 1 
Attachment 2 
Attachment 3 
Attachment 4 
Attachment 5 

Powered by