Hi Julia,

Re-saving the word files as doc. was simply a workaround and not meant as a long time solution.
SDL resolved this compatibility issue with the release of Studio 2015 (which you have already seen in various other posts I believe).
Therefore the only way to use fully use Office 2016 would be to upgrade to Studio 2017 (if you do not have 2015 in your account).
SDL will not be releasing an Office 2016/Studio 2014 compatibility update as far as i'm aware, as official support for Studio 2014 will be retired at the end of June this year.

Kr

Steve

Unknown said:

P.S. With all due respect, Paul I'm a bit frustrated with the tone of your message to a paying client of your employer.

Many apologies then Artem Sedov  I don't really know what part of my tone was offensive, and I certainly didn't mean anything more than to suggest some solutions.  I guess things don't always come across well in written form.

Here is the stack trace for the error

<SDLErrorDetails time="05.09.2017 9:37:41">
  <ErrorMessage>Object reference not set to an instance of an object.</ErrorMessage>
  <Exception>
    <Type>System.NullReferenceException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</Type>
    <HelpLink />
    <Source>Sdl.FileTypeSupport.Filters.Excel</Source>
    <HResult>-2147467261</HResult>
    <StackTrace><![CDATA[   at Sdl.FileTypeSupport.Filters.Excel.FilterControllerFramework.OfficeController.UpdateDocumentFile(XsltArgumentList argsList, XslCompiledTransform xslTransform, XPathNavigator child)
   at Sdl.FileTypeSupport.Filters.Excel.FilterControllerFramework.OfficeController.IterateXsltFiles(XsltArgumentList argsList, FileMap rule, XPathNodeIterator iter, Boolean isUpdate, String targetFilePath)
   at Sdl.FileTypeSupport.Filters.Excel.FilterControllerFramework.OfficeController.IterateContentType(String xslFileNamesPath, Boolean isUpdate, String filePath, String filterStr, String targetFilePath, Boolean isCalledByRelsTableIteration)
   at Sdl.FileTypeSupport.Filters.Excel.FilterControllerFramework.OfficeController.serviceBackward()
   at Sdl.FileTypeSupport.Filters.Excel.PlugInFilter.FileParser.DocumentParser.Update()
   at Sdl.FileTypeSupport.Filters.Excel.PlugInFilter.FileParser.DocumentExtractImpl.Update(DocumentCollection srcCollection, String filename, String tgtFilePath)
   at Sdl.FileTypeSupport.Filters.Excel.PlugInFilter.FileWriterAndPreviewFileWriter.WriterImpl.EndOfInput()
   at Sdl.FileTypeSupport.Filters.Excel.PlugInFilter.FileWriterAndPreviewFileWriter.ExcelWriter.EndOfInput()
   at Sdl.FileTypeSupport.Framework.Integration.NativeWriterMessagesProxy.EndOfInput()
   at Sdl.FileTypeSupport.Framework.Integration.FileGenerator.CallEndOfInput()
   at Sdl.FileTypeSupport.Framework.Integration.FileGenerator.FileComplete()
   at Sdl.FileTypeSupport.Framework.BilingualApi.AbstractBilingualContentProcessor.FileComplete()
   at Sdl.FileTypeSupport.Framework.Integration.AbstractBilingualProcessorContainer.FileComplete()
   at Sdl.FileTypeSupport.Framework.Integration.MultiFileConverter.FileComplete()
   at Sdl.FileTypeSupport.Framework.BilingualApi.AbstractBilingualContentProcessor.FileComplete()
   at Sdl.FileTypeSupport.Framework.Integration.AbstractBilingualProcessorContainer.FileComplete()
   at Sdl.FileTypeSupport.Bilingual.SdlXliff.XliffFileReader.OnEndFile()
   at Sdl.FileTypeSupport.Bilingual.SdlXliff.SdlXliffFeeder.<ContinueScanning>b__2(ISdlXliffStreamContentHandler handler)
   at System.Collections.Generic.List`1.ForEach(Action`1 action)
   at Sdl.FileTypeSupport.Bilingual.SdlXliff.SdlXliffFeeder.ContinueScanning()
   at Sdl.FileTypeSupport.Bilingual.SdlXliff.XliffFileReader.ContinueParsing()
   at Sdl.FileTypeSupport.Bilingual.SdlXliff.XliffFileReader.ParseNext()
   at Sdl.FileTypeSupport.Framework.Integration.FileExtractor.ParseNext()
   at Sdl.FileTypeSupport.Framework.Integration.MultiFileConverter.ParseNext()
   at Sdl.FileTypeSupport.Framework.Integration.MultiFileConverter.Parse()
   at Sdl.ProjectApi.AutomaticTasks.NativeFileGenerator.GenerateFiles(ContentRestriction restriction, Boolean preview, Int32 filePercentBase, Int32 filePercentFactor)
   at Sdl.ProjectApi.AutomaticTasks.GenerateTargetTranslation.GenerateTargetTranslationTask.ProcessFile(IExecutingTaskFile executingTaskFile)
   at Sdl.ProjectApi.AutomaticTasks.AbstractFileLevelAutomaticTaskImplementation.Execute()]]></StackTrace>
  </Exception>
  <Environment>
    <ProductName>SDL Trados Studio</ProductName>
    <ProductVersion>14.0.0.0</ProductVersion>
    <EntryAssemblyFileVersion>14.1.6284.6</EntryAssemblyFileVersion>
    <OperatingSystem>Майкрософт Windows 10 Домашняя для одного языка</OperatingSystem>
    <ServicePack>NULL</ServicePack>
    <OperatingSystemLanguage>1049</OperatingSystemLanguage>
    <CodePage>1251</CodePage>
    <LoggedOnUser>DUO11\info_000</LoggedOnUser>
    <DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>
    <ComputerName>DUO11</ComputerName>
    <ConnectedToNetwork>True</ConnectedToNetwork>
    <PhysicalMemory>4070680 MB</PhysicalMemory>
  </Environment>
</SDLErrorDetails>

Solution found. I have changed priorities of the parsers and moved the "SpreadsheetML v. 1" filter up in the "File types" list. Now it takes priority over the legacy filter and Studio handles XLSX files again.

Question 1: Can I disable Excel 2007 v 2.0.0.0 filter altogether?
Question 2: How does SpreadsheetML v. 1 filter handle rows and columns order? In the legacy filter there is a setting to choose translation order, but not in the SpreadsheetML v. 1...

Thank you

Unknown said:

Question 1: Can I disable Excel 2007 v 2.0.0.0 filter altogether?

This can only be achieved in your project templates.  Also make sure you do this in your Global Settings (File -> Options as opposed to Project Settings) so that new project templates you create based on new projects you have created are using your preferred setting by default.

Unknown said:

Question 2: How does SpreadsheetML v. 1 filter handle rows and columns order? In the legacy filter there is a setting to choose translation order, but not in the SpreadsheetML v. 1...

Top left to bottom right, unless it's a Bi-Di language in which case it's top right to bottom left.

Eventually it will supersede the old one, but until we are 100% confident we are not missing anything important we have left it there. You have already identified one possible advantage in being able to configure the parsing options... maybe there are others. We're hoping for feedback from our customers in the community and this may help shape the options for the new one and also determine when we decide to remove the old one altogether.

Is it safe? It can't hurt and you won't break anything. But there is always the possibility you'll find an excel file that won't process in the new one but will in the old. We'll obviously fix the new one when we learn of these things... but good to have the backup of the older more seasoned version.

Does that answer your question?

Regards

Unknown said:

So does new parser handle translation by row or by column?

Top left to bottom right... so by row.

Unknown said:

Legacy configuration options allow to choose translation by column or by row. This is a huge difference and Excel files can have different structure, not necessarily two column Source-Target. So the configuration options to choose translation order appropriate for the content of the file.

As I asked before, can you provide some examples of when it would be more appropriate to handle this another way?  I'm sure there are some or you would not have asked, but as there are currently no plans to do this it will only happen if we have good reason to ask for the feature to be included in the new filetype too.

Thanks