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.

Thanks,

Mohamed

14 Replies Latest Replies: 1 Jan 2019 12:04 PM by Evzen Polenka < 1   2   3  >
  • In reply to Mohamed Zeid:

    Hi ,

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

    Scenario

    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.

    Notes:
    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.

  • In reply to Mohamed Zeid:

    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.
< 1   2   3  >

Related