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

Parents
  •  

    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]
Reply
  •  

    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]
Children