Hi Mohamed Zeid,
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 Evzen Polenka.
Tip: You can verify if the base64 encoded string of the embedded file is validate from here: https://www.base64decode.org/. Simply create a separate file with only the base64 encoded string and upload it, under the section: ‘Decode file from Base64 format’.