Hi Zakiya,

Thanks for sending in the file.  I don't know why it has this problem yet but will look at it in more detail later.  However, you can process it if you change the filetype being used before processing the file.  So make sure you are set up like this in your File -> Options -> Filetypes:

So uncheck the default and check this one.

Regards

Paul

Hi Paul, thanks for the quick reply. 

I did as you suggested but get the same error message as before.

The same file when converted into .sdlxliff by Studio 2015 works just fine when imported into Studio 2017.

Best regards

Zakiya

Hi Zakiya,

The filetype you make default here is exactly the same as the one being used by 2015.  So if this is not working for you my guess would be you are not really using this filetype.  Make sure of the following:

- change this in File -> Options and then open the file for translation

- if you created a project then make sure you change this in the project templates you are using

The way to see if you are using the right filetype is to check the File Type Identifier in the files view.  So you should see this:

The new filetype (that is causing you this problem) is called WordprocessingML v. 2 and not Word 2007 v 2.0.0.0

Regards

Paul

Hi Zakiya,

The filetype you make default here is exactly the same as the one being used by 2015.  So if this is not working for you my guess would be you are not really using this filetype.  Make sure of the following:

- change this in File -> Options and then open the file for translation

- if you created a project then make sure you change this in the project templates you are using

The way to see if you are using the right filetype is to check the File Type Identifier in the files view.  So you should see this:

The new filetype (that is causing you this problem) is called WordprocessingML v. 2 and not Word 2007 v 2.0.0.0

Regards

Paul

Right, I find that using the earlier Word 2007-2016 filetype as you suggested allows me to process this file in Studio 2017. Thank you for the workaround!

This doesn't answer the question why this particular file is giving trouble with the WordprocessingML v.2 filetype, though, when used in Studio 2017.

Please note that when I open the "bad" file with Studio 2015 using the WordprocessingML v. 2 filetype it works just fine. Also, I originally created 7 files at the same time, all using the same Word template. They all work fine with the WordprocessingML v. 2 filetype except this one particular file.

(By the way, I don't really want to revert to the earlier Word 2007-2016 filetype unless I have to, because then I can't have real-time Word previews while I'm working, which is such a great feature.)

These screenshots show the "bad" file in Studio 2015 as a Wordprocessing ML v. 2 file type and with Project Settings (and Options) checked only for Word 2007-2016 and yet it works fine.