How to check version of Studio package (Studio 2014 vs 2015)

Hi guys,

 

Quick question: is there any chance how to check the version of a Studio package - so any information that says whether it was created in 2014 or 2015 (either any information in Studio itself or by opening the sdlproj/xliff file in a XML Editor)?

 

We often receive packages created in Studio 2015 but on our side Studio 2014 has been implemented (an upgrade is not planned for the time being); as a consequence the PM is often wondering why he/she is not able to generate target files due to missing file types.

 

If there isn't anything displayed in Studio maybe any script could read any information in the XML Content is what I thought...

 

Cheers

Karsten

Parents
  • Unknown said:
    We often receive packages created in Studio 2015 but on our side Studio 2014 has been implemented (an upgrade is not planned for the time being); as a consequence the PM is often wondering why he/she is not able to generate target files due to missing file types.

    Hi Karsten,

    Even if you know this it won't change the problem for you.  The same thing could happen with a 2014 package if a custom filetype was used, or a filetype available through the AppStore.  You can still work on the files and create a return package, but you won't be able to save target, use quick inserts created for these files, and a couple of other small things.  

    What would you do once you know you are going to see this message?

    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

  • Hello guys,

    Thanks for your reply so far.

    @Paul: it's rather an issue in terms of missing due dates of translation projects or loosing time.

    For instance, we also have a VM with a license of Studio 2015 that we use if any of these issues occur. So, my thought was if a project manager instantly knew that a project was created in Studio 2015, then he/she could act in a much quicker way.
    At the moment, most of them only notice the error message that pops up when generating a target file or opening the Studio editor and are consequently pretty unsure what to do, although the solution is that easy.

    Best
    K.
Reply
  • Hello guys,

    Thanks for your reply so far.

    @Paul: it's rather an issue in terms of missing due dates of translation projects or loosing time.

    For instance, we also have a VM with a license of Studio 2015 that we use if any of these issues occur. So, my thought was if a project manager instantly knew that a project was created in Studio 2015, then he/she could act in a much quicker way.
    At the moment, most of them only notice the error message that pops up when generating a target file or opening the Studio editor and are consequently pretty unsure what to do, although the solution is that easy.

    Best
    K.
Children
No Data