Free Support Forum - aspose.com

Converting to PDF adds extra text for MACROBUTTON

Hi,

We have a problem with converting a Word document having the 97-2003 format (see the attached file MACROBUTTON issue.doc) that contains a MACROBUTTON. The PDF copy (see attached file MACROBUTTON issue.pdf) contains the HTMLDirect name of the MACROBUTTON.
Is there any chance we can avoid that without changing the file?

What we use:
1. Aspose.Words .NET component version 16.2.0.0, Runtime version v4.0.30319.
2. The actual conversion code looks like this:
var doc = new Document(input);
doc.Save(output, new PdfSaveOptions { SaveFormat = WordSaveFormat.Pdf });

What we tried so far:
1. PreserveFormFields set to true in SaveOptions argument. It doesn’t help.
2. Converting the document to the DOCX format. The conversion will remove the button entirely. This is not good.
3. We successfully converted the file to PDF using Word 2016 Save As PDF functionality.

The restriction we have is that we cannot replace the file so it will extremely helpful if you can help us with an Aspose.Words version or a piece of code that we can use to make the problem go away.

Thanks!


Hi Panos,

Thanks for your inquiry. We have tested the scenario and have managed to reproduce the same issue at our side. For the sake of correction, we have logged this problem in our issue tracking system as WORDSNET-13408. You will be notified via this forum thread once this issue is resolved. We apologize for your inconvenience.
gwert:
2. Converting the document to the DOCX format. The conversion will remove the button entirely.
Could you please share some more detail about this query? We will then provide you more information on this.

Hi,

Glad to hear that you logged an issue for this! And thanks for reacting so quick on the matter.

As for the DOCX problem, here are steps:

1. Use Word 2016 for Windows 8.1 to convert the DOC (see attached MACROBUTTON issue.doc) to DOCX format (see attached MACROBUTTON issue.docx).
2. Use Aspose.Words .NET component version 16.2.0.0, Runtime version v4.0.30319 to convert the DOCX file to PDF.

The PDF no longer contains the buttons (see attached MACROBUTTON issue.docx.pdf).

Thanks.

Hi Panos,

Thanks for sharing the detail. We have tested the scenario and have managed to reproduce the same issue at our side. For the sake of correction, we have logged this problem in our issue tracking system as WORDSNET-13411. You will be notified via this forum thread once this issue is resolved.

We apologize for your inconvenience.

Hi,

Any developments on this issue? Do you have any estimated/approximated date when the fix will be released?

Thanks!

Hi Panos,

Thanks for your inquiry. The issue (WORDSNET-13408) has been resolved and its fix will be available in June 2016 release (Aspose.Words v16.6.0). This version of Aspose.Words will be available in next month (July 2016).

Currently, WORDSNET-13411 is pending for analysis and is in the queue. Once our product team completes the analysis of this issue, we will then be able to provide you an estimate.

Thanks for your patience and understanding.

The issues you have found earlier (filed as WORDSNET-13408) have been fixed in this .NET update and this Java update.


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

Hello,

This issue is back in Aspose.Words 18.4.0…

Here is the doc file we are using for testing:
05_MACROBUTTON issue.zip (6.4 KB)

Is there anything we can do about this?

Best regards!

@gwert,

Thanks for your inquiry. We have tested the scenario using latest version of Aspose.Words for .NET 18.4 and have not found the shared issue. Please make sure that you are using Aspose.Words for .NET 18.4. We have attached the output PDF with this post for your kind reference. 18.4.pdf (14.2 KB)

Hi,

I attached the sandbox app that has the code we use for converting Word formats to PDF.
Aspose.Words.Sandbox.zip (10.9 KB)

Can you please take a look at it?

Best regards.

@gwert,

Thanks for your inquiry. We have tested the scenario and have managed to reproduce the same issue at our side. For the sake of correction, we have logged this problem in our issue tracking system as WORDSNET-16791. You will be notified via this forum thread once this issue is resolved.

We apologize for your inconvenience.

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