Probability score: 0.7  

Question improvement suggestion: Provide the exact version of Trados Studio 2024 you are using, and include any specific steps you have already taken to troubleshoot the issue.  

In the meantime, based on the information you have provided, here is a suggested answer to your question:  

Hello,  

It seems you're encountering a common issue when exporting target XML files in Trados 2024, especially after upgrading from Trados 2022. Here are some steps you can take to troubleshoot and potentially resolve the issue:  

**Step 1:** Verify the XML File Type Settings  

- Go to **File > Options > File Types > XML** and ensure that the 'Preserve whitespace' option is checked under the XML Settings. This is crucial for maintaining the structure of your XML files.  

**Step 2:** Check Project Settings  

- Ensure that the project settings are correctly configured to use the XML 2 file type, as the XML 1 filter is now obsolete. You can do this by going to **Project Settings > File Types** and confirming that the XML 2 file type is selected.  

**Step 3:** Create a New File Type  

- If the issue persists, consider creating a new file type based on XML 2 and importing the settings from your existing XML file. This can sometimes resolve compatibility issues that arise from the upgrade.  

**Step 4:** Use Workarounds  

- If you are still unable to export the target XML, you might want to try the workaround of creating the project directly in Trados Team or using Trados Studio 2022 CU5 to create the project locally.  

**Step 5:** Contact the Client  

- Since you mentioned that you are waiting for the client's latest SDLFTSettings file, it may be beneficial to follow up with them. Having the most recent settings can help ensure compatibility with the new version of Trados.  

If you continue to experience issues after trying these steps, please provide any additional details about the error message or behavior you're encountering, and I would be happy to assist further!  

I hope this answer addressed your question. If not, please reject the answer, add the question improvement suggestion information, and click the RWS Community AI checkbox on the right to try again.  

RWS Community AI

Tried Steps 1 through 3, issue still persists. Client also sent their sdlftsettings-file, tried to create a new file type with that as the base - did not work. The client also said, they still use Trados 2022, could that be why?

Current workaround: I've updated the old project's TM and added that to a new project with the source file. I can export the target file from that, however, as I noted in the original post, the parser settings now don't work properly anymore. Some text that has previously been translated and should be hidden in this project, is now shown in the editor, and some tags like line breaks are shown as plain text in their own segments instead of as proper tags or hidden.

Exporting a target file works with that workaround - whether the client can then use that file, we'll have to test. But it is definitely not the most efficient solution to this problem. BUt if it's the only solution we have right now, it will have to do until a proper fix can be found. 

Tried Steps 1 through 3, issue still persists. Client also sent their sdlftsettings-file, tried to create a new file type with that as the base - did not work. The client also said, they still use Trados 2022, could that be why?

Current workaround: I've updated the old project's TM and added that to a new project with the source file. I can export the target file from that, however, as I noted in the original post, the parser settings now don't work properly anymore. Some text that has previously been translated and should be hidden in this project, is now shown in the editor, and some tags like line breaks are shown as plain text in their own segments instead of as proper tags or hidden.

Exporting a target file works with that workaround - whether the client can then use that file, we'll have to test. But it is definitely not the most efficient solution to this problem. BUt if it's the only solution we have right now, it will have to do until a proper fix can be found.