• State Verified Answer
  • Replies 3 replies
  • Subscribers 433 subscribers
  • Views 348 views
  • Users 0 members are here
Options
Related

How can I repair a corrupted Bilingual Review File?

Daniel Hug

Using Trados 2024 CU1 on Windows 10, I get the following error when trying to update from a Bilingual Review File: "Exception of type Exception occurred: Problem when merging content of segment 1"

Is there a way repair the file? DOCX files are ZIP files that contain XMLs. I just don't know what to look for...

Here is the stacktrace:

Fullscreen sdlerror-2024124-14h58m43s.sdlerror.xml Download 
<SDLErrorDetails time="04/12/2024 14:59:15">
  <ErrorMessage>Exception of type Exception occurred: Problem when merging content of segment 1
Stacktrace:
   at Sdl.FileTypeSupport.Utilities.SdlXliffConvertor.FileUpdater.ProcessParagraphUnit(IParagraphUnit paragraphUnit)
   at Sdl.FileTypeSupport.Framework.BilingualApi.AbstractBilingualContentProcessor.ProcessParagraphUnit(IParagraphUnit paragraphUnit)
   at Sdl.FileTypeSupport.Filters.Processors.SegmentRenumberingBilingualProcessor.ProcessParagraphUnit(IParagraphUnit paragraphUnit)
   at Sdl.FileTypeSupport.Framework.Core.Utilities.BilingualApi.BilingualContentHandlerAdapter.ProcessParagraphUnit(IParagraphUnit paragraphUnit)
   at Sdl.FileTypeSupport.Framework.Core.Utilities.BilingualApi.BilingualContentHandlerAdapter.ProcessParagraphUnit(IParagraphUnit paragraphUnit)
   at Sdl.FileTypeSupport.Framework.Integration.AbstractBilingualProcessorContainer.ProcessParagraphUnit(IParagraphUnit paragraphUnit)
   at Sdl.FileTypeSupport.Framework.BilingualApi.AbstractBilingualContentProcessor.ProcessParagraphUnit(IParagraphUnit paragraphUnit)
   at Sdl.FileTypeSupport.Framework.Integration.LocationMarkerLocator.ProcessParagraphUnit(IParagraphUnit paragraphUnit)
   at Sdl.FileTypeSupport.Framework.Integration.AbstractBilingualProcessorContainer.ProcessParagraphUnit(IParagraphUnit paragraphUnit)
   at Sdl.FileTypeSupport.Framework.Integration.FileExtractor.ProcessParagraphUnit(IParagraphUnit paragraphUnit)
   at Sdl.FileTypeSupport.Framework.Core.Utilities.BilingualApi.ParagraphUnitBuffer.ProcessParagraphUnit(IParagraphUnit pu)
   at Sdl.FileTypeSupport.Bilingual.SdlXliff.XliffFileReader.OutputParagraphUnit(IParagraphUnit pu)
   at Sdl.FileTypeSupport.Bilingual.SdlXliff.XliffFileReader.ParseLocalizableParagraphUnit(transunit transunit, LockTypeFlags lockFlags)
   at Sdl.FileTypeSupport.Bilingual.SdlXliff.XliffFileReader.ParseTransUnit(transunit transunit)
   at Sdl.FileTypeSupport.Bilingual.SdlXliff.XliffFileReader.ParseGroup(group group)
   at Sdl.FileTypeSupport.Bilingual.SdlXliff.XliffFileReader.OnGroup(XmlElement group)
   at Sdl.FileTypeSupport.Bilingual.SdlXliff.SdlXliffFeeder.&lt;ContinueScanning&gt;b__14_11(ISdlXliffStreamContentHandler handler)
   at System.Collections.Generic.List`1.ForEach(Action`1 action)
   at Sdl.FileTypeSupport.Bilingual.SdlXliff.SdlXliffFeeder.ContinueScanning()
   at Sdl.FileTypeSupport.Bilingual.SdlXliff.XliffFileReader.ContinueParsing()
   at Sdl.FileTypeSupport.Bilingual.SdlXliff.XliffFileReader.ParseNext()
   at Sdl.FileTypeSupport.Framework.Integration.FileExtractor.ParseNext()
   at Sdl.FileTypeSupport.Framework.Integration.MultiFileConverter.ParseNext()
   at Sdl.FileTypeSupport.Framework.Integration.MultiFileConverter.Parse()
   at Sdl.ProjectApi.Implementation.TaskExecution.ContentProcessingTaskImplementation.TaskFileExecuter.Parse(String targetFilePath)</ErrorMessage>
  <Exception>
    <Type>Sdl.ProjectApi.ProjectApiException, Sdl.ProjectApi, Version=18.0.0.0, Culture=neutral, PublicKeyToken=c28cdb26c445c888</Type>
    <HelpLink />
    <Source />
    <HResult>-2146233088</HResult>
    <StackTrace><![CDATA[]]></StackTrace>
    <InnerException>
      <Type>Sdl.ProjectApi.ProjectApiException, Sdl.ProjectApi, Version=18.0.0.0, Culture=neutral, PublicKeyToken=c28cdb26c445c888</Type>
      <HelpLink />
      <Source />
      <HResult>-2146233088</HResult>
      <StackTrace><![CDATA[]]></StackTrace>
    </InnerException>
  </Exception>
  <Environment>
    <ProductName>Trados Studio</ProductName>
    <ProductVersion>Studio18</ProductVersion>
    <EntryAssemblyFileVersion>18.0.1.2259</EntryAssemblyFileVersion>
    <OperatingSystem>Microsoft Windows 10 Enterprise</OperatingSystem>
    <ServicePack>NULL</ServicePack>
    <OperatingSystemLanguage>1033</OperatingSystemLanguage>
    <CodePage>1252</CodePage>
    <LoggedOnUser>ThatsMeExclam</LoggedOnUser>
    <DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>
    <ComputerName>MyMachine</ComputerName>
    <ConnectedToNetwork>True</ConnectedToNetwork>
    <PhysicalMemory>16440376 MB</PhysicalMemory>
  </Environment>
</SDLErrorDetails>
emoji
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
  • 0

    "Probability score": 0.9

    "Question improvement suggestion": Please provide any recent changes to the system or software.

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

    Hello,

    Based on the error message and stack trace you've provided, it seems like there's an issue with merging the content of a segment in your Bilingual Review File. This could be due to a variety of reasons, such as a formatting issue or a problem with the underlying XML structure of the DOCX file.

    Here are a few steps you can take to try and resolve this issue:

    Step 1: Try the workarounds you've mentioned. Export the document for external review again, copy the content from the completed review document to the newly created one, and then try to update from the bilingual review.

    Step 2: If the first workaround doesn't solve the issue, you can use the SDLXLIFF Converter for Microsoft Office. This app can be used to import from MS Word and update the SDLXLIFF file.

    Step 3: If neither of these workarounds solve the issue, you might need to manually inspect the XML files within the DOCX file. DOCX files are indeed ZIP files that contain XMLs, and the issue might be with one of these XML files. You can open the DOCX file with a ZIP program like 7-Zip, extract the contents, and then inspect the XML files for any issues.

    Please note that manually editing XML files should be done with caution, as it can potentially cause more issues if not done correctly.

    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
  • 0 in reply to RWS Community AI

    I opened the Word file with Word and noticed it was read-only because it originated from a web source. (It had been sent to me by email - maybe it was once attached to some project management app and then downloaded?) After selecting "Allow editing" Studio imported it without complaints - but did not import any changes or added comments.
    emoji
  • +1 in reply to Daniel Hug

     

    Usually I go this way:

    • Save the proofread bilingual export with a different name or in different folder than the export folder
    • Remove the previously exported bilingual review file from its destination
    • Export the sdlxliff file for bilingual review anew from TS
    • Open the newly exported file
    • Perform NO changes there
    • Switch off the track-changes feature in this file
    • Open the previously saved damaged bilingual file
    • Switch off the track-changes feature in this file too
    • Remove the first row of the table
    • Perform no more changes here
    • Select the target column as a whole; this works quite well with the mouse pointer placed above this column; the mouse pointer changes to arrow pointing down and selects the whole column with one click
    • Switch to the newly exported bilingual review file
    • Click somewhere in the most right cell of the second row; this is the first cell of the target document here
    • Paste the copied column
    • Word should completely replace the content with the content of the column from the damaged file
    • Save this file and attempt the import agai
    • My experience shows, that this works with no problem at all

    The problem with your file might indeed be the origin. Also only the slightest change in the first column destroys the file. Sometimes even rescaling the columns or changing something in the source is enough to prevent import. Also any additional paragraphs or manual line breaks damage the file. And of course changing tags or using the tag formatting for something else makes the file useless.

    In any case, you can contact me directly. The description of the process seems to be complicated, but the process itself is easy-peasy. I can show it to you via TeamViewer or Teams, works like a charm.

    _________________________________________________________

    When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.

    Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.

    emoji