Hi there,

I'm using the SaveToPdf(string fileName) method in the Aspose.Words.Document class. The conversion from word to pdf is normally going really well, but for some documents the generated pdf file will have some unwanted metadata on top. It looks like custom properties set on the word document. I'm not sure why this is happening - so any suggestions to help me on this issue would be very much appreciated. For instance, is there any properties to set on the Aspose.Words.Document object to prevent this metadata from showing in the generated pdf file?

Attached to this post is the original word file, the generated pdf file after conversion and the unwanted metdata (highlighted).

Please let me know if any further information is needed.

Thanks and regards

Geir

Hi

Thanks for your inquiry. I managed to reproduce the problem on my side. Your request has been linked to the appropriate issue. You will be notified as soon as it is fixed. The problem occurs because there are SET fields in the header of the document.  

Best regards,

Hi Andrey,

Thank you for your reply.

I'm just wondering what the current status is on this issue? We have a customer who is waiting for this issue to be fixed, before they can go in production. Therefore it would be nice if we could give them an updated status.

Best regards

Geir

Hi

Thanks for your inquiry. Currently, I cannot provide you any reliable estimate. Please expect a reply before the next hotfix (within 4-5 weeks).

For now, as a workaround, you can try removing SET fields from your document before converting it to PDF. For example, see the following code:

Document doc = new Document(@"Test001\TheOriginalWordFile.doc");

RemoveSetFields(doc);

doc.Save(@"Test001\out.pdf");

===================================================================

public  void RemoveSetFields(Document doc)

{

    //Get collection of FieldStart nodes

    Node[] fieldStarts = doc.GetChildNodes(NodeType.FieldStart, true).ToArray();

    //Loop through all FieldStart nodes

    foreach (FieldStart start in fieldStarts)

    {

        // Skip further processing if start is not start of SET field.

        if(start.FieldType != FieldType.FieldSet)

            continue;

        // Remove all nodes between field start and field end

        Node curNode = start;

        while (curNode != null && curNode.NodeType != NodeType.FieldEnd)

        {

            Node nextNode = curNode.NextPreOrder(doc);

            curNode.Remove();

            curNode = nextNode;

        }

        // Remove field end.

        if (curNode != null)

            curNode.Remove();

    }

}

Hope this helps.

Best regards,

Hi Andrey,

Once again, thank you for your quick reply. And thank you so much for the proposed workaround - it works like a charm! :)

Best regards,

Geir

The issues you have found earlier (filed as 11158) have been fixed in this update.