Re: Office 2013/2016 support?

Aspose.Words Product Family
1

Office 2016 was released some time ago. Is it safe to say that current Aspose.Words for .NET supports it’s docx format? I’ve seen some posts saying that some people already use it. Do you have any status site where one can view current status of Word 2016 format support?


Regards,
Piotr
2
Hi Piotr,

Thanks for your inquiry. We have already logged a feature request as WORDSNET-12458 to support Office 2016 for Aspose.Words in our issue tracking. We will keep you updated on this feature via this forum thread.

In the first phase, opening and saving of Office 2016 documents will be supported. More features will be added gradually as we receive more requests.

Please use latest version of Aspose.Words for .NET 16.1.0 and let us know if you have any more queries.
3

Thank You for a quick response.

We’ve tried to convert files saved in Word 2013 and 2016 to PDF and it seems to work fine. Do you fully support Word 2013 docx format? If not, when are you planning to?
Our client would like us to be able to mostly convert Word 2013 and 2016 docx files to PDF, so we’d like to know what are the chances that we will be able to do that with Your library.
4
Hi Piotr,

Thanks for your inquiry. Aspose.Words has not officially announced the support of MS Word 2013/2016 documents yet. However, Aspose.Words supports all major OOXML versions for example OOXML ECMA-376 and OOXML ISO/IEC DIS 29500. Aspose.Words does not support following MS Word 2013 features at the moment.

  • ISO/IEC 29500 Strict OOXML version
  • Load password protected document into Aspose.Words DOM

Regarding Office 2016, more features will be added gradually as we receive more requests. You can use latest version of Aspose.Words to convert MS Word 2013/2016 documents to Pdf. If you face any issue while document to Pdf conversion, please share your documents here for testing purposes. We will investigate the issue on our side and provide you more information.

5

The issues you have found earlier (filed as WORDSNET-8969) have been fixed in this Aspose.Words for .NET 17.3.0 update and this Aspose.Words for Java 17.3.0 update.

This message was posted using Notification2Forum from Downloads module by aspose.notifier.
(7)