Resolving Unconverted Entity Values in InDesign IDML Files Using SDL Trados Studio

When processing an InDesign IDML file in SDL Trados Studio, how can I configure the InDesign filetype settings or apply a workaround to handle unconverted entity values (e.g., &, <, >, or  ) that appear as plain text in the Editor instead of being converted to their corresponding characters or tags? Specifically, what adjustments can be made in the File Type settings under Adobe InDesign CS4-CC IDML or Embedded Content Processors to ensure these entities are properly interpreted, and how can I avoid syntax issues when exporting the translated IDML file back to InDesign? Please provide detailed steps or settings to address this issue.

emoji

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

  • "Probability score": 0.9

    "Question improvement suggestion": Please provide the version of Trados Studio you are using and any error messages you might be encountering.

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

    Hello,

    To resolve unconverted entity values in InDesign IDML files using Trados Studio, you can adjust the File Type settings and the Embedded Content Processors. Here are the steps:

    Step 1: Open Trados Studio and navigate to "File" > "Options" > "File Types".

    Step 2: Scroll down and select "Adobe InDesign CS4-CC IDML".

    Step 3: In the settings for this file type, navigate to "Embedded Content Processors".

    Step 4: Make sure your Embedded Content is processed by a processor, such as "Html Embedded Content 5 2.0.0.0".

    Step 5: Close the file type configuration, click on the "Embedded Content Processors" tab and click on "HTML 5".

    Step 6: Expand the "Entity settings" section and disable the "Enable entity conversion" option.

    Step 7: Create a new project to make sure the target file generated is now showing the correct symbols.

    Please note that these steps are based on the assumption that you are using a recent version of Trados Studio. If you are using an older version, the steps may vary slightly.

    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

    emoji
  •  

    Do I understand correctly that this is what you are trying to work with:

    Text box with a question about XML reserved characters and HTML entities, showing examples like ampersand amp; and ampersand lt;.

    You want the translator to see the entities and reserved characters resolved like this:

    Dark-themed text editor displaying a question about XML reserved characters and HTML entities with examples.

    The problem I see is that the IDML file type does not offer any entity conversion, neither legacy nor embedded content processors. And IDML files are too complex to handle with the generic XML file type.

    What you can do is to export your INDD stories (the text frames) to ICML and handle the ICML(s) with the generic XML file type. I have been doing that for some specific use cases for years.

    Daniel

    emoji


    Generated Image Alt-Text
    [edited by: RWS Community AI at 12:53 PM (GMT 1) on 25 Apr 2025]
  •   

    Sorry about that... I meant to remove that post.  It was actually a made up question as part of a recording for Elevate next month!

    Now that you've kindly answered it I'll leave it there!!

    Thank you.

    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

    emoji