Phonetic form is marked as “deleted” in the comparison result file rather than being shown as “updated” or “added”

Aspose.Words Product Family
,
1

@yaroslaw.ekimov
In both character-level and word-level comparisons using Aspose (both on-premises and cloud versions), it appears that when a word is updated to its phonetic form, it is marked as “deleted” in the comparison result file rather than being shown as “updated” or “added.” It would be extremely helpful for us if this issue could be addressed and resolved in the upcoming release, along with the character-level comparison feature.

For further clarification, I have attached screenshots of both the expected and actual results. Additionally, I have provided the original and updated files for your testing.

Please kindly review and let us know if there are any possible solutions to fix this issue.

Snapshots:

Original text:

992×110 8.16 KB

Updated to phonetic text:

1026×102 8.64 KB

Expected result:

976×146 14.2 KB

Aspose on-premises char level comparison result:

1366×106 17.1 KB

Aspose on-premises char level comparision result in PDF format:

984×104 19.2 KB

Aspose cloud word level comparision result:

1572×74 24.2 KB

Testing files:
売買契約書 (changed).docx (934 KB)
売買契約書 (original).docx (484 KB)

2

I will create a separate topic for these requirements as they relate to Aspose.Words product. Because cloud product uses Aspose.Words functionality.

3

@Groot
We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.

Issue ID(s): WORDSNET-28016

You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.

4

@alexey.noskov
Thanks for creating the ticket.

It would be very beneficial for us if this issue could be fixed in the 25.4 release, alongside the character-level comparison feature. Is there any possibility of this being included, or is there a planned timeline for the fix?

5

@Groot Unfortunately, at the moment we cannot promise the fix will be included into 25.4 release. the issue is currently in the queue for analysis. once analysis is done we will be able to provide you more information.

6

@alexey.noskov
Thank you for the update.
I understand the situation and will await further information after the analysis is complete. Looking forward to your response.

1 Like
7

Hi @alexey.noskov, just wanted to check in on the status of the analysis for the issue. Any idea when it might be done or when we can expect an update?

8

@Groot Unfortunately, the issue has been postponed. It’s hard to understand MS Word logic here since there is bunch of nested fields and Aspose.Words field comparison is not currently good enough. So we have decided to postpone this issue and get back later after field comparison rework. Please accept our apologies for your inconvenience.