Hello!<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />
Thank you for your interest in Aspose.Words.
I’d like to explain how joinRunsWithSameFormatting works and why it doesn’t help in some cases. This document optimization method finds and joins adjacent Run objects with equal attribute set except for editing session identifiers. If you intensively edit some fragment of text, even equally formatted from beginning to end, Microsoft Word creates many runs. You can see this in DocumentExplorer demo application or if you export such a document without calling joinRunsWithSameFormatting. These runs differ in only editing session identifiers. But there are some other cases:
- Runs can differ in other attributes that doesn’t affect HTML output.
- Runs can be separated by some other nodes that are not directly output to HTML.
In your case “North Carolina” and “Michigan” seem to be results of field evaluation. In the model they are separated by field start/separator/end nodes.
So joinRunsWithSameFormatting eliminates all redundancy in the document model while it might retain something in exported HTML. Really the method has nothing to do with export modules, it operates on the model. If you show me the source document I will tell you the reason and probably suggest a workaround. This behavior is a known issue and I’ll subscribe your thread to it. You’ll be notified when it is fixed.