Any potential issues I should be aware of when working with an editor who uses Studio 2015?

Dear Studio 2017 users,

I am not sure if this information has been provided somewhere in the Community (a link will be appreciated, if it already exists:), but here is what I want to know:

I would like to use Studio 2017 for a project that has several files (idml, pptx and xml files).  The client uses Studio 2011, and the editor uses 2015.  Will the editor encounter any error messages or run into any issues when opening my files for editing?  Will the client have any issues opening my return package?

Thank you so much for your advice.

 

Chunyi

Parents
  • Hi Chuny-yi,

    If you are getting the package from Studio 2011 and creating a return package then this should be fine... probably! We no longer test against 2011 as this is not even supported anymore so I can't guarantee it.

    On error messages... it's quite likely and you may see them too. 2011 will have created sdlxliff files using really old versions of the filetypes which you don't have. So you may not be able to save the target files or use quick inserts and may see an error message to that effect. But you using 2017 should not be the source of the problem as you are not creating the bilingual files.

    If I was you I'd do a quick test with your client before you start.

    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 Chuny-yi,

    If you are getting the package from Studio 2011 and creating a return package then this should be fine... probably! We no longer test against 2011 as this is not even supported anymore so I can't guarantee it.

    On error messages... it's quite likely and you may see them too. 2011 will have created sdlxliff files using really old versions of the filetypes which you don't have. So you may not be able to save the target files or use quick inserts and may see an error message to that effect. But you using 2017 should not be the source of the problem as you are not creating the bilingual files.

    If I was you I'd do a quick test with your client before you start.

    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