You get the error Unmatched tag pair/revisioned or locked content calls detected! when trying to open an IDML file in Trados Studio 2015/2017/2019/2021, TMS, or WorldServer (until version 11.7.3).



Unmatched tag pair/revisioned or locked content calls detected!

No longer reproducible in Trados Studio 2022 and WorldServer 11.8.1. Upgrade to these versions to solve the issue.

In affected versions, apply the solutions below.

Solution 1:

 Remove the corrupt Table of Contents (TOC) and recreate it

1. Open the document in Adobe InDesign
2. Select the TOC and delete it with [Del]
3. Now either save and translate the document as is, and readd the TOC afterwards, or continue with step 4
4. Recreate the TOC via
   Layout > Table of Contents...
5. Once the TOC is recreated, save your changes and use this document for translation

Solution 2:

Remove and re-add all pages

1. Open the IDML in InDesign and delete all the pages
2. Restore the pages using [CTRL]+[Z]
3. This should fix the issue with the file 
4. Unzip the IDML files using WinZip or other tools and extract the XML file from the folder Stories
5. Compare the original version internal XML file with the resaved one (which works fine)
6. Some files will be changed and will contain the affected ParagraphStyleRange or CharacterStyleRange

In some cases, the issue cannot be isolated in the way described above and the reduction method has to be used - cut the IDML file in halves over and over until you manage to single out the part in the file which causes the error. Then open the XML file to determine where the broken tag pair is located.

Solution 3:

  Isolate and remove the faulty content:

1. Delete pages from the IDML, saving the file each time to see on what page the error comes from. Divide and conquer approach
2. Once you found the page, identify the problem, for instance, a specific hyperlink, remove it in a copy of the original file
3. Save your changes and use this file for translation

Paragraph and Character Styles from the IDML are nested in the file. Or, on other occasions, the CharacterStyleRange tag pair is not assigned to any text and Studio/WorldServer cannot read it correctly. Or the table of contents (TOC) is corrupted.

More details in case for isolating the issue for Solution 2:

 Remove and readd all pages

1. Open the IDML in InDesign and delete all the pages
2. Restore the pages using [CTRL]+[Z]
3. This should fix the issue with the file 
4. Unzip the IDML files using WinZip or other tools and extract the XML file from the folder Stories
5. Compare the original version internal XML file with the resaved one (which works fine)
6. Some files will be changed and will contain the affected ParagraphStyleRange or CharacterStyleRange

In some cases the issue cannot be isolated in the way described above and the reduction method has to be used - cut the IDML file in halves over and over until you manage to single out the part in the file which causes the error. Then open the XML file to determine where the broken tag pair is located.

Solution:

 To isolate the issue:

1. Delete pages from the IDML, saving the file each time to see on what page the error comes from. Divide and conquer approach
2. Once you found the page, identify the problem. In my case, it was a text that had a hyperlink to it. Once I deleted that, the problem went away.
3. To better understand what is the cause, I extracted the content of the IDML then went into the Stories folder, looked up the text of the hyperlink that was the cause, and observed the structure.

The problem came from the fact that there was a ParagraphStyleRange tag inside the HyperlinkTextSource tag which was inside another ParagraphStyleRange. I think the problem is that you can not have a ParagraphStyleRange inside of another. It does not really make sense. So I removed the ParagraphStyleRange that was inside the HyperlinkTextSource then re-zipped the file, renamed it to IDML and the problem was fixed.

So from this section:

            <HyperlinkTextSource Self="u95d2" Name="Cisco Safety and Security Information 226" Hidden="false" AppliedCharacterStyle="n">
                <CharacterStyleRange AppliedCharacterStyle="CharacterStyle/blue-links" RubyFontSize="-0.8026992662941584" KentenFontSize="-0.8026992662941584">
                    <Content>Cisco Safety and Security Information</Content>
                </CharacterStyleRange>
                <CharacterStyleRange AppliedCharacterStyle="CharacterStyle/$ID/[No character style]" FillColor="Color/R=14 G=177 B=83" FontStyle="ExtraLight" PointSize="10" StrokeWeight="0.8026992662941584" Underline="true" UnderlineOffset="2" UnderlineWeight="1" MiterLimit="3.2107970651766338" RubyFontSize="-0.8026992662941584" KentenFontSize="-0.8026992662941584">
                    <Properties>
                        <Leading type="unit">14</Leading>
                        <AppliedFont type="string">CiscoSans</AppliedFont>
                    </Properties>
                    <Br />
                </CharacterStyleRange>
                <ParagraphStyleRange AppliedParagraphStyle="ParagraphStyle/bullets">
                    <CharacterStyleRange AppliedCharacterStyle="CharacterStyle/blue-links" />
                </ParagraphStyleRange>
            </HyperlinkTextSource>

I removed this part:
                <ParagraphStyleRange AppliedParagraphStyle="ParagraphStyle/bullets">
                    <CharacterStyleRange AppliedCharacterStyle="CharacterStyle/blue-links" />
                </ParagraphStyleRange>


Solution 2: Example 2
Fixed issue by removing the extra hard return, which deleted the extra unassigned CharacterStyleRange. See section in Yellow removed from right screenshot.