Visual example:
The two documents:
Document 1:
Title Test 1
• Bullet 1
Document 2:
Title Test 2
• Bullet 2
Merging these two documents will result in this:
Title Test 1
• Bullet 1
Title Test 2
Bullet 2
I’ve added a test project with the two documents giving us trouble in attachments.
We’ve had a problem kind of like this one posted here which has been resolved already:
When inserting a document with a list- the list changes its number formatting - Free Support Forum - aspose.com
It was with numbers not bullets and so other documents were used to show the problem. But that shouldn’t make that much of a difference I think.
So why these two documents are giving us trouble, I do not have a clue.
Thanks in advance,
Kris
Hi Kris,
Thanks for your inquiry. Please use ImportFormatMode.KeepSourceFormatting to solve this problem. Using the KeepSourceFormatting option allows to make sure the imported text looks in the destination document exactly like it was in the source document. If a matching style already exists in the destination document, the source style is copied and given a unique name by appending a suffix number to it, for example “Normal_0” or “Heading 1_5”.
Best regards,
That’s not really an option for us because our customers use this function more than once, doing it like this will result in them having 12 normal styles after a while.
Which isn’t really a clean solution for them.
The styles are exactly the same so it should merge just fine.
Is there a way we can use the already existing style format which is defined in both documents and let one document use the style of the other.
Without duplicate styles and without having layout issues.
Thanks in advance,
Kind regards,
Kris
Hi Kris,
Thanks for the additional information. I tested the scenario and have managed to reproduce the same problem on my side. For the sake of correction, I have logged this problem in our issue tracking system as WORDSNET-9426. Our development team will further look into the details of this problem and we will keep you updated on the status of correction. We apologize for your inconvenience.
Best regards,
The issues you have found earlier (filed as WORDSNET-9426) have been fixed in this .NET update and this Java update.
This message was posted using Notification2Forum from Downloads module by aspose.notifier.