? tag difference in settings.xml in 13.5.0 and 13.12.0 aspose version

Aspose.Words Product Family
1

Hi there,
I’m seeing the difference in node tags in the word docs generated by Aspose 13.5.0 and Aspose 13.12.0. The main difference I noticed is <w:doNotTrackMoves /> is not present in settings.xml file of documents generated by newer versions of Aspose.

Please suggest me why this is happening?

2

Hi Praneeth,


Thanks for your inquiry. Could you please attach your input/output Word documents and piece of source code here for testing? I will investigate the issue on my side and provide you more information.

Best regards,
3

Hi Awais,
We have some control documents generated via Aspose 13.5.0 and now we are using 13.12.0.

Now, we are seeing some changes in xml files of the word document.

I’m listing some of them as follows:

1. The settings.xml when generated via 13.12.0 doesn’t have <w:doNotTrackMoves /> node. It was present in settings.xml when generated via 13.5.0.

2. There are some node cutdown in headers and footers.xml. I’m noticing that the 

<w:rPr><w:rFonts w:asciiTheme=“minorHAnsi” w:eastAsiaTheme=“minorHAnsi” w:hAnsiTheme=“minorHAnsi” w:cstheme=“minorBidi” /> <w:color w:val=“365F91” w:themeColor=“accent1” w:themeShade=“BF” /><w:sz w:val=“22” /><w:szCs w:val=“22” /><w:lang w:val=“en-US” w:eastAsia=“en-US” w:bidi=“ar-SA” /></w:rPr> 
present in headers or footers .xml of 13.12.0. 

While <w:rPr><w:color w:val=“365F91” w:themeColor=“accent1” w:themeShade=“BF” /></w:rPr> 
when generated via Aspose 13.12.0.

We are seeing that Aspose has decided to remove
<w:rFonts w:asciiTheme=“minorHAnsi” w:eastAsiaTheme=“minorHAnsi” w:hAnsiTheme=“minorHAnsi” w:cstheme=“minorBidi” />
and  
<w:sz w:val=“22” /><w:szCs w:val=“22” /><w:lang w:val=“en-US” w:eastAsia=“en-US” w:bidi=“ar-SA” />
from the rPr node.

To summarize only color properties are retained in run properties of a paragraph and run fonts and size nodes are removed.

3. In styles.xml I’m seeing the extra pPr node and 2 attributes 

w:line=“276” w:lineRule=“auto”

in spacing node are added in styles.xml.

4. In glossary folder their is similar sort of difference in document.xml and settings.xml.

There are some more issues apart from above in 2010 documents which I’ll add with documents in this thread.

I’m interested in knowing why Aspose has decided to change their xml structure in newer versions of Aspose and what is the probability for the change in xml’s in future future versions. We are asking this because our control docs are failing due to the change in xml’s.

I’m hereby attaching two word docs generated by Aspose 13.5.0 and 13.12.0. Please have a look. Thanks.




4

Hi Praneeth,


Thanks for the additional information. Please also share the source code (attach a simple runnable Java application) that you used to generate these documents for testing.

Best regards,
5

Hello Awais,
I’m hereby attaching the java sample application and the sample document ComplexFirstEvenOddHeaderFooter.docx.

Let me tell you that we are applying the header footer formatting from the sample document to the Aspose newly created document.

The changes are appearing in the documents generated after applying the options.

Please use 13.5.0 Aspose.words jar and 13.12.0 Aspose.words jar file and check the xml differences.

In the example scenario we are not applying styles but when we do so the changes in styles.xml appears.

Please have a look. Thanks.

6

Hi Praneeth,


Thanks for the additional information. I will check this scenario and get back to you soon.

Best regards,
7

Hi Awais, Is there any update on this?

8

Hi Praneeth,


Thanks for being patient. I tested the scenario and have managed to reproduce these issues on my side. For the sake of correction, I have logged the following issues in our issue tracking system.

WORDSNET-9561: <w:doNotTrackMoves /> node is missing from output settings.xml
WORDSNET-9562: <w:rFonts> and <w:sz> nodes are missing from output header1.xml

Our development team will further look into the details of these problems and we will keep you updated on the status of corrections. We apologize for your inconvenience.

Best regards,
9
Hi Praneeth,

Thanks for being patient. Regarding WORDSNET-9561, our development team has completed the analysis of this issue and has come to a conclusion that this issue is actually not a bug in Aspose.Words 13.12.0. So, we will most likely close this issue as 'Not a Bug'.

This happens because previously Aspose.Words always used to write "w:doNotTrackMoves" attribute to the document (even during open/save an empty document) which was wrong. But, starting from Aspose.Words 13.11.0, Aspose.Words correctly preserves this attribute during open/save. Please check your input document, settings.xml and glossary\settings.xml do not have doNotTrackMoves attributes, that is why the output document does not have this attribute too.

Best regards,
10
Hi Praneeth,

Regarding WORDSNET-9562, our development team has completed the analysis of this issue and has come to a conclusion that this issue is not a bug in Aspose.Words 13.12.0 either. So, we will most likely close this issue as 'Not a Bug'. The latest version of Aspose.Words correctly preserves these attributes during open/save. If we can help you with anything else, please feel free to ask.
Best regards,