Working with both 2014 and 2017 versions of SDL Trados Studio Freelance mismatches my job!

Hello, I have just upgraded my SDL Trados Studio Freelance 2014 to 2017. Now, working within 2017, all my files are saved in my SDL 2014 folder. How to correct it?

Parents
  • Hi Thierry,

    Files are saved wherever you choose to save them. If you use the defaults then they will be saved in different locations. But why is this a problem for you?

    Regards

    Paul

    Paul Filkin | RWS Group

    ________________________
    Design your own training!

    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

  • Hi Paul,

    I thought that when upgrading to 2017, all my files and folders from SDL Trados 2014 would be converted/incorporated into my new version 2017. But it's a bit astonishing that when creating a new project in 2017 version, I have to search for all my files in 2014 version although I have no trail of a project created in 2014 SDL Trados. Why is this choice not automatic: a project created in 2017 version gives all its files created under the 2017 version?

    Maybe I've found the reason why: the .sdlxliff file I received to work on was created in the 2014 version. Is this the cause?

    Regards,

    Thierry
  • Hi Thierry,

    As I said, the choice of where to put your files is yours entirely. If you choose the use the defaults then this is where they will be placed and they will be in different locations for 2014 compared to 2017. This is just the way it works. If you organise your folders so you save your projects into a location of your own choosing, or if you migrate your projects when you upgrade then you won't have this discrepancy.  Maybe this article will be useful for you:

    multifarious.filkin.com/.../

    I'd like to see a migration option built into the tool, but there isn't one. So you have to make the conscious decision to do it yourself.

    The version of sdlxliff has nothing to do with this. You may well find you can't save target from a project created in 2014 when using 2017, and vice versa. But this is something else and nothing to do with locations of projects.

    As a general rule though I would not share projects between two different versions of Studio if I owned them both. Make a decision and choose one as the master (2017 makes sense) and then just share the sdlxliff files for editing if you really want to.

    Regards

    Paul

    Paul Filkin | RWS Group

    ________________________
    Design your own training!

    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

Reply
  • Hi Thierry,

    As I said, the choice of where to put your files is yours entirely. If you choose the use the defaults then this is where they will be placed and they will be in different locations for 2014 compared to 2017. This is just the way it works. If you organise your folders so you save your projects into a location of your own choosing, or if you migrate your projects when you upgrade then you won't have this discrepancy.  Maybe this article will be useful for you:

    multifarious.filkin.com/.../

    I'd like to see a migration option built into the tool, but there isn't one. So you have to make the conscious decision to do it yourself.

    The version of sdlxliff has nothing to do with this. You may well find you can't save target from a project created in 2014 when using 2017, and vice versa. But this is something else and nothing to do with locations of projects.

    As a general rule though I would not share projects between two different versions of Studio if I owned them both. Make a decision and choose one as the master (2017 makes sense) and then just share the sdlxliff files for editing if you really want to.

    Regards

    Paul

    Paul Filkin | RWS Group

    ________________________
    Design your own training!

    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

Children
No Data