Probability score: 0.6  

Question improvement suggestion: Provide specific details about the settings you adjusted in the embedded content section and any error messages received during the process.  

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

Hello Johannes,  

Thank you for reaching out regarding the issue with the PO file type definition in Trados Studio. It sounds like you've done a great job refining the settings, but I understand the frustration of having locked content missing in the target file. Here are some steps you can take to troubleshoot and potentially resolve the issue:  

**Step 1:** Verify the Embedded Content Settings  

- Double-check the settings you adjusted in the embedded content section of the PO file type definition. Ensure that the variables you want to lock are correctly defined and that there are no conflicting settings.  

**Step 2:** Test with a Simplified PO File  

- Create a simplified version of your PO file with minimal content and only a few variables. This can help determine if the issue is related to the complexity of the original file.  

**Step 3:** Check for Updates  

- Ensure that you are using the latest version of Trados Studio 2024. Sometimes, issues are resolved in newer updates, so checking for updates within the application can be beneficial.  

**Step 4:** Review the Output File  

- After saving the target file, open it in a text editor to see if the locked content is present but perhaps not displaying correctly. This can help identify if the issue is with the saving process or the display of the content.  

**Step 5:** Consider Alternative File Type Definitions  

- If the problem persists, you might want to explore using a different file type definition for PO files, such as creating a custom file type using Regular Expression Delimited Text, as suggested in the context.  

If these steps do not resolve the issue, please provide any specific error messages or additional details about the settings you adjusted, 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

Johannes Purer 

I can reproduce the problem with the app, but it works fine with the default PO filetype so you may want to use that?

If not, your best bet is to contact the developer: https://appstore.rws.com/Plugin/259?tab=support

Hi Paul,

thanks a lot for the reply. I will check with the tool developer.

We use the file type definition, because it enables us to translate a single PO language file, where the text to translate is in the target column. In the source column is the strign ID.

The regular PO file type definition does not support that.

Regards,

Johannes

Johannes Purer 

Interesting - so the screenshot you provided is something different to the way you use it in practice?  Probably I got confused or didn't understand what you are actually doing.

Hi Paul,

no, this is the screenshot from PO file type definition 3.1.

The standard PO file type definition is 1.0, but cannot be used with that structure of the file.

Version 3.1 offers the option to have the target text translated, not the source text.

This option is not available in version 1.

So we have to use version 3.1 for this kind of file (string ID in the source column and text to translate in the target column).

See example below, we want to translate the German text, as the source in only a string ID, which cannot be translated, or at least it does not make sense.

Hope this helps to understand the issue.

Thanks,

Johannes