Cannot export target file from Excel

Not sure why this is happening in the first place. It seems somehow SDL Trados Studio remembers the original path of the file at the translator's end. I got a translated SDLXLIFF file from a translator. I made some changes to translation. Now, I am trying to save the file, but I initially got this message:


"file xxx doesn't exist" and it gives me the path from translator's machine which is "C:\ZZ\WORK\Work from home\2018\December\30-12".

So, I tried to go along with Trados and I created the same exact path on my machine. Now, when I try to export target or save it as target, I get this error message:


"Failed to save target content: The paragraph unit supplied should always have Contexts properties defined!"

Not sure what does this mean? Any idea? 

How I can resolve this issue? Also, is there any logical explanation of such issue in the first place?

I am using SDL Trados Studio 2019 by the way.



  • Hi ,

    I have run some tests in trying to reproduce the issue that you have mentioned here.  To avoid any misinterpretation, can you please confirm the steps that I have mentioned underneath.

    1. Create a new project in 2019 SR1
    2. Add a single xlsx file.
    Q 1: Is the *.xlsx file embedded in the SDLXLIFF file?
    3. Complete the project creation.
    4. Created a Studio Package and provided it to the linguist.
    Q 2: Did you provide the linguist with SDL Studio Package, target SDLXLIFF file and or the original source file (*.xlsx), or simply the entire project?
    5. Your understanding is that the Translator opened the studio package, translated the file and provided you with the translated file.
    Q 3: Is there a reason why the linguist did not provide a return package?
    Q 4: Any additional pre-processing done by the linguist?

    Tip: you can configure whether the native file is embedded in the SDLXLIFF file by updating the setting mentioned here

    Given the information you provided, I have deducted that your case is best aligned with the following scenario; if different, please advise.


    •    Created a project in Studio 2019 SR1 with a single *.xlsx file
    •    *.xlsx embedded in the SDLXLIFF file
    •    Created a SDL Studio Package
    •    Opened the package and translated the file
    •    The linguist did not create a return package; instead sent the translated SDLXLIFF file
    •    Copied the translated SDLXLIFF file back into target folder of your project, overwriting the existing file.

    In this scenario, the only case where I can see it being reproducible is when the translated SDLXLIFF file that you receive from the translator is recreated from the native file.  The original path of the reference file is defined when the file is created and relevant when not working with an embedded native file. 

    From the tests that I carried out, the original path was not updated when simply providing translations in the SDLXLIFF file. However, I was successful in updating this original path information, when creating a new project from the native file, as follows:
    •    Open the studio package
    •    Open the file in the editor and select the option File>Save Target As
    •    Create a new project from the native file.

    Note: In this user-case, it can also be seen that additional complications may occur; including variant segmentation & whether or not the native file is embedded with the creation of the new project, which might lend itself to the issues noted by .

    Tip: You can verify if the base64 encoded string of the embedded file is validate from here: Simply create a separate file with only the base64 encoded string and upload it, under the section: ‘Decode file from Base64 format’.

  • Hi ,

    I checked with the translator. She simply opened the XLSX file in Trados Studio and she didn't create a project for it. I didn't create a project at my end as well because it was a small file.

    I hope this helps answer some of your questions.

  • Hi ,

    Thank you for following up with this. I understand, so the steps to reproduce would better resemble the following:


    1. Project Manager:
      • Provide Translator with the source file (*.xlsx)
    2. Translator:
      • Create new project with the *.xlsx source file
      • Provide translations and return translated SDLXLIFF file to PM
    3. Project Manager
      • Open the SDLXLIFF file by creating a new project (or single document project)
      • Create translated native file -> Save Target As


    Original file (Embedded/Not Embedded)

    • Not Embedded: Studio will prompt the user with a message box asking them to locate the original file.  This is because the path  referencing the location of the native file is located on the translators computer (because the SDLXLIFF file/project was created on that computer).
    • Embedded: Studio will not prompt the user for the original file because it can recreate the original file from the base64 encoded string of the embedded file.

    In this scenario, you might still encounter problems in cases where the file type information used on the translators computer is different to what is present on the PM's computer. To avoid any unforseen issues as such, try to adopt the more regulated procedure of providing a Studio Package and then importing the Return Package.

Reply Children
  • Hi ,


    Can you please explain more on how 'embedded vs. not embedded' may play a role in this problem?

    • You can configure whether the native file is embedded in the SDLXLIFF file by updating the setting mentioned here, from the studio options. 
    • In your case, the translator created the SDLXLIFF from the native file that you provided them.  So, the path to xlsx file saved in the SDLXLIFF is referencing a physcial path on their computer.  If the xslx file is not embedded with the SDLXLIFF (given the option here), then Studio will prompt you to locate that file when you attempt to load the translated SDLXLIFF on your computer.  To resolve, simply provide the correct path of where you have that same file (that you provided to the translator), located on your computer.
    • However, there are some gotcha's, especially if the file type or configuration used on the translators computer is different to what you have on your environment that influences structure or segmentation, which can result in Studio not being able to regenerate the target file.


    and how to avoid this in the future?

    • try to adopt the more regulated procedure of providing a Studio Package and then importing the Return Package.
    • If that is not possible, then mabye provide the prepared SDLXLIFF file to the translator, so that you are not at the mercy of how the SDLXLIFF file is prepared from their environment.
  • Thanks for taking the time to explain and thanks for your support. I appreciate it.