• State Suggested Answer
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 435 subscribers
  • Views 863 views
  • Users 0 members are here
Options

Paths to SDLXLIFFs not updated when switching between two identical copies of a project

Luciano

Let us say, I hava a Studio project at location A. Project Managers use this project to create and import packages with translators. PMs report an error somewhere in the project and in order to dig into it I create a copy of this project at location B. So location A and location B have two completely different paths.

Now, if I opened the project at location A, after having a look removed it from Studio, then opened the copy of the project at location B and switched to the files view, the paths to the SDLXLIFFs are still those from the project at location A. If I, for example, switch to the source language files and back to the target language files again, now the paths are updated to those of location B.

This can lead to thinking you are working savely on a copy of a project when instead you are tampering with the SDLXLIFFs of the original project. Studio should load the files from the project you have opened, regardless of it having the same name as the one you previously opened. Maybe this is worth looking into for a future update or release. Thank you.
emoji
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
  • 0

    Yes, I have seen this happening and reported it to SDL Support. They could reproduce it and a defect was raised (CRQ-26813) so that they can ffix it in the future.

    And you are right, it can be quite dangerous because you might change the files you did not want to change! Disappointed

    There are several workarounds that I am aware of:

    - Sign in to Language Cloud. For whatever reason, this does not happen if you are signed in to Language Cloud. Unfortuntatly this is not an option for us.

    - After removing Project from location A, close Studio. When you open Studio again and open tthe project from Location B, you should be good.

    - Remove project from Location A, open project from Location B. When you go into the file list, you will see that that paths point to Location A. At this point press F5 (or in the view tab, click Refresh View). The paths will be referesh and now point to Location B.

    The problem is that, when you make a copy of the project, both projects have the same ID and Studio does not refresh some of the project information automatically when closing the project from Location A and opening the project from Location B..

    Another alternative would be revert to a previous version of Studio. We have seen this issue with Studio 2021 SRT CU8. It id not happen in Studio 2019.

    Another workaround: after making the copies of the project,, open one of the SDLPRJ files and change manually its unique project ID. This would prevent this issue from happening because each project would be considered a different one by Studio.

    Possibly, somebody could create a plugin for Studio 2021 called "Make a coipy of this project". You could right click a project from Studio and then make a copy of it and change the unique project ID. This would be really practical but I am not sure if changing the project's unique ID could have consequences further down the line.

    Hopefully this bug will be fixed soon! In some scenarios it is a simple and efficient way of splitting work across different translators working in the same office.

    Daniel

    PS. In your situation (opening projects for troubleshooting), it might be better to always make a copy of the project before doing anything else.
    emoji
  • 0 in reply to Daniel García Magariños

    Thank you, , for sharing your experiences.

    As an LSP, signing in to Language Cloud is not an option for us either. We'll have to go with refreshing the View. First step, however, is to gain awareness of the existence of this problem. Do you know if there is a database with all these reported bugs (CRQ and others)?
    emoji