Hi Birgit,

This could be happening because you are working on a version of Word that is more recent than SDL Trados Studio 2014 because you received the package from an agency who created it using Studio 2017. In this case you will not be able to save to Target because Studio 2014 does not have a .docx filetype. It is better to open the Word document before translation and save it as Word 97-2003 before you set up the translation project, or ask your client to do this.

Here is another similar case with further information on this subject:

Studio 2014

If you can open the original Word document and save it as Word 97-2003, here:

The above is based on opening the file in Office 365, it will look different on previous .docx-based versions but the principle is the same.

If you clean the failed sdlxliff to a new TM then you can use that TM to pretranslate the .doc in a new project and you will then be able to perform all the necessary tasks such as tag verification. You should then be able to save to Target.

If the client requires .docx then you can open the final .doc in Word and save it back to .doc :)

If you'd like to learn a little more about how not having the relevant filetype settings affects your work on a Word file, see here:

verification without correct filetype

I hope all of the above makes sense, I'm rushing as my dinner's ready... my husband cooked tonight!

All the best,

Alison

Hi Birgit,

This could be happening because you are working on a version of Word that is more recent than SDL Trados Studio 2014 because you received the package from an agency who created it using Studio 2017. In this case you will not be able to save to Target because Studio 2014 does not have a .docx filetype. It is better to open the Word document before translation and save it as Word 97-2003 before you set up the translation project, or ask your client to do this.

Here is another similar case with further information on this subject:

Studio 2014

If you can open the original Word document and save it as Word 97-2003, here:

The above is based on opening the file in Office 365, it will look different on previous .docx-based versions but the principle is the same.

If you clean the failed sdlxliff to a new TM then you can use that TM to pretranslate the .doc in a new project and you will then be able to perform all the necessary tasks such as tag verification. You should then be able to save to Target.

If the client requires .docx then you can open the final .doc in Word and save it back to .doc :)

If you'd like to learn a little more about how not having the relevant filetype settings affects your work on a Word file, see here:

verification without correct filetype

I hope all of the above makes sense, I'm rushing as my dinner's ready... my husband cooked tonight!

All the best,

Alison

Hi Birgit Woelke,

I'm so glad to hear that you were able to deliver on time.

Wouldn't it be nice if there were a way to create filetypes based on newer versions of Word or whatever, to add them to Studio as they come out but the only format that this is possible for in Studio 2014 is xml as far as I know. That in itself is pretty clever and can be extremely complex to get right.

Another teensy point is that if you want to upgrade 2014 Freelance to 2017 Freelance it isn't as expensive as all that at £255.00 and I notice that there's an option for the same price that includes SDL Certification.

Paul Filkin, does this mean Certification is thrown in for nothing? A v good deal if so, and useful in smoothing the transition to the new software with an opportunity to learn of the new features and get a taste of the wide range of functionality that comes with Studio and MultiTerm.

I've marked what I'm referring to here:

I still have a 2014 license because that way I can open 2014 if anyone needs help so I was surprised to see how little it costs to upgrade if you have Freelance rather than Pro.

All the best,

Ali