Forum: SDL Trados support
Topic: Studio 2011 SP2: Cannot create target (clean) .docx/.xlsx with localised versions of Office
Poster: Catheireann
Hi all,
Some translators are reporting problems creating clean .docx and .xlsx files in Studio 2011 SP2 using localised versions of Office.
We create packages for translation using Office in English. Translators then are able to localise and verify the content, but when they try to generate the target file, this error shows up:
"Failed to save target content. Object reference not set to an instance of an object".
This only happens when translators use our packages with a localised version of Office, e.g. in Spanish or Italian. Any other translator that uses Office in English is able to generate targets without problems.
We've found two solutions: convert the .docx and .xlsx to pre-2007 versions (.doc and .xls) or ask translators to create their own packages. In those cases the conversion error doesn't repro. However none of these workarounds are very convenient and are having an impact on schedules and resources. Upgrading to Studio 2014 or getting Office in English for all translators is out of the question for the moment.
Is this a known issue, and does anyone know a solution? Haven't been able to find any info on the SDL KB.
Thanks.
Topic: Studio 2011 SP2: Cannot create target (clean) .docx/.xlsx with localised versions of Office
Poster: Catheireann
Hi all,
Some translators are reporting problems creating clean .docx and .xlsx files in Studio 2011 SP2 using localised versions of Office.
We create packages for translation using Office in English. Translators then are able to localise and verify the content, but when they try to generate the target file, this error shows up:
"Failed to save target content. Object reference not set to an instance of an object".
This only happens when translators use our packages with a localised version of Office, e.g. in Spanish or Italian. Any other translator that uses Office in English is able to generate targets without problems.
We've found two solutions: convert the .docx and .xlsx to pre-2007 versions (.doc and .xls) or ask translators to create their own packages. In those cases the conversion error doesn't repro. However none of these workarounds are very convenient and are having an impact on schedules and resources. Upgrading to Studio 2014 or getting Office in English for all translators is out of the question for the moment.
Is this a known issue, and does anyone know a solution? Haven't been able to find any info on the SDL KB.
Thanks.