Hi again Chunyi,

I've never seen that particular error message before but I never work on any translation as a 'single file'. I always work with projects because it is tidier. I always have, ever since Studio and projects began.

Actually, there is a fix for this on the Knowledgebase:

kb.sdl.com/.../

In case for some reason the link doesn't work for you, here is what it says you must do:

Follow these steps:

1. 1. Exit Studio.
   2. Go to...

...the project file (*.sdlproj)

1. 1.  of the affected project in the folder of the project or located in the same folder where the source file is located when using 

Translate Single Document

1. 1. ...or...

...when this issue occurs when editing a project template

1. 1. , go to the affected project template file with 

*.sdltpl

1. 1.  extension.

2. Open the project or template file with a text editor (for example Notepad).
3. Change all occurrences of the string MicrosoftOffice.Common to MicrosoftOffice.Core.Common within the <SettingsGroup Id="WordprocessingML v.2> element:

    

           <SettingsGroup Id="WordprocessingML v. 2">
          <Setting Id="NonTranslatableStyleMappingRules3">

            <NonTranslatableStyleMappingRule xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/Sdl.FileTypeSupport.Filters.MicrosoftOffice.Core.Common">

    

                 <StyleName>tw4winMark</StyleName>

              <TagProperty>Inline</TagProperty>

            </NonTranslatableStyleMappingRule>

          </Setting>
   
   
   Be sure to repeat this action for all occurrences of this string (by default it occurs four times).
4. Restart Studio. You should now be able to edit the project settings or template.

(Explanation:

This error occurs in the following circumstance:

• In a previous Studio 2015 release (such as Studio 2015 CU3), you accessed and confirmed the Styles settings within the Microsoft Word 2007-2016 file type settings.

In Studio 2015 SR2, the settings structure for styles has been modified. Normally, these settings are not actively written by the Microsoft Word file type, which is why this issue occurs only rarely. But if you access and change these settings or leave them unchanged, but confirm the dialog box with OK, then the settings are written to the *.sdlproj (project) or *.sdltpl (project template) file. This then causes the error in SDL Trados Studio 2015 SR2 as it no longer expects this settings structure.)

If you tried the above and this doesn't work for you...

Since before Studio, if a Word file has caused me trouble, I have always gone back to the original file in Word before taking it to the Project stage. That is where you will be able to create a file that works. This can involve various possibilities, depending on what content is causing the problem. It can be as simple as saving to a new docx file with a different filename or saving to .doc or .rtf, or as complex as eliminating macros, headers, footers, images, imported tables or other '3rd-party' content, in order to create a file that works.

Thankfully most of these problems are relatively rare now but the thing that has stayed the same is that it is a lot easier to create a file that works on saving to Target BEFORE translation than after. So whatever you try, as soon as you create your Project, save to Target to see if it works. If it doesn't try eliminating some content that could be causing the problem, from a copy of the orginal Word file, and then see if that will save to Target.

Finally, I find using a project is always the most stable way of working, whatever original format of file you are working on.

All the best,
Ali

Hi again Chunyi,

I've never seen that particular error message before but I never work on any translation as a 'single file'. I always work with projects because it is tidier. I always have, ever since Studio and projects began.

Actually, there is a fix for this on the Knowledgebase:

kb.sdl.com/.../

In case for some reason the link doesn't work for you, here is what it says you must do:

Follow these steps:

1. 1. Exit Studio.
   2. Go to...

...the project file (*.sdlproj)

1. 1.  of the affected project in the folder of the project or located in the same folder where the source file is located when using 

Translate Single Document

1. 1. ...or...

...when this issue occurs when editing a project template

1. 1. , go to the affected project template file with 

*.sdltpl

1. 1.  extension.

2. Open the project or template file with a text editor (for example Notepad).
3. Change all occurrences of the string MicrosoftOffice.Common to MicrosoftOffice.Core.Common within the <SettingsGroup Id="WordprocessingML v.2> element:

    

           <SettingsGroup Id="WordprocessingML v. 2">
          <Setting Id="NonTranslatableStyleMappingRules3">

            <NonTranslatableStyleMappingRule xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/Sdl.FileTypeSupport.Filters.MicrosoftOffice.Core.Common">

    

                 <StyleName>tw4winMark</StyleName>

              <TagProperty>Inline</TagProperty>

            </NonTranslatableStyleMappingRule>

          </Setting>
   
   
   Be sure to repeat this action for all occurrences of this string (by default it occurs four times).
4. Restart Studio. You should now be able to edit the project settings or template.

(Explanation:

This error occurs in the following circumstance:

• In a previous Studio 2015 release (such as Studio 2015 CU3), you accessed and confirmed the Styles settings within the Microsoft Word 2007-2016 file type settings.

In Studio 2015 SR2, the settings structure for styles has been modified. Normally, these settings are not actively written by the Microsoft Word file type, which is why this issue occurs only rarely. But if you access and change these settings or leave them unchanged, but confirm the dialog box with OK, then the settings are written to the *.sdlproj (project) or *.sdltpl (project template) file. This then causes the error in SDL Trados Studio 2015 SR2 as it no longer expects this settings structure.)

If you tried the above and this doesn't work for you...

Since before Studio, if a Word file has caused me trouble, I have always gone back to the original file in Word before taking it to the Project stage. That is where you will be able to create a file that works. This can involve various possibilities, depending on what content is causing the problem. It can be as simple as saving to a new docx file with a different filename or saving to .doc or .rtf, or as complex as eliminating macros, headers, footers, images, imported tables or other '3rd-party' content, in order to create a file that works.

Thankfully most of these problems are relatively rare now but the thing that has stayed the same is that it is a lot easier to create a file that works on saving to Target BEFORE translation than after. So whatever you try, as soon as you create your Project, save to Target to see if it works. If it doesn't try eliminating some content that could be causing the problem, from a copy of the orginal Word file, and then see if that will save to Target.

Finally, I find using a project is always the most stable way of working, whatever original format of file you are working on.

All the best,
Ali

Hi Chunyi, hi Jerzy,

Thank you Jerzy, I wouldn't have thought of that.

Chunyi, do you mean that you actively work to files on OneDrive, or that you download files from there when you want to work on them locally? The former would cause problems for my setup because I live in an area where the internet connection is unreliable. The latter should not cause any problem.

Anyway, I'm sure that SDL Support will help you better than I. On the other hand, I believe that Jerzy has the knowledge and ability to help you as well as anyone from SDL Support ;-)) He's one of my Heroes :))

Enjoy the rest of your Sunday,
All the best,
Ali