Calling Save changes Document

Aspose.Words Product Family
1

With 23.9.0 we see something like this:

    document = new Document(path);
    // traverse DOM 

    document.Save(path);
    // traverse DOM again

And the second time we traverse the DOM there are differences. Is this by design that calling Save() can change the internal representation of the document? Maybe it optimizes it or updates things?

Because you might imaging that Save() would not change the document at all, that it would just write bytes to disk.

2

@ResearchSquare Could you please attach your source and output documents here for testing? We will check the issue and provide you more information.

3

I will open a new private thread since it’s a customer file.

1 Like