Bug 132336 - Compare document on DOCX fails on footnotes/footer
Summary: Compare document on DOCX fails on footnotes/footer
Status: RESOLVED DUPLICATE of bug 71152
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
6.4.3.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-04-23 00:18 UTC by Jim Sowers
Modified: 2020-11-09 08:54 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jim Sowers 2020-04-23 00:18:32 UTC
Description:
I compared two Word documents (.DOCX format) with slight changes to content, footnotes, and footer. The changes in the main body were identified, but none of the footnote nor footer changes were captured.

Steps to Reproduce:
1.Create a Word .docx file that includes footer and footnotes.
2.Make a copy of it and modify or delete the footer and footnotes.
3.Run a Track Changes -- > Compare comnmand.

Actual Results:
The footer and footnote changes are not properly identified as such.

Expected Results:
All changes should be marked.


Reproducible: Always


User Profile Reset: No



Additional Info:
This form is confusing. You place the questions below the answer boxes. ??
Comment 1 Xisco Faulí 2020-05-11 07:53:45 UTC
Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. 
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided.
(Please note that the attachment will be public, remove any sensitive information before attaching it. 
See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.)
Comment 2 QA Administrators 2020-11-09 04:18:11 UTC Comment hidden (obsolete)
Comment 3 Timur 2020-11-09 08:54:17 UTC
Looks duplicate.

*** This bug has been marked as a duplicate of bug 71152 ***