Created attachment 198205 [details] sample main text file I have two files, one is the main text and another is main text + its translation. When I compare the the two files using MSO, i get what i expect - the text which is common to both the documents is identified properly. But when i do the same with LO, i get a pretty poor result. Please see the files attached.
Created attachment 198206 [details] sample translation file
Created attachment 198207 [details] MSO Comparision
Created attachment 198208 [details] LO comparision
When reporting a bug, please: 1. use Compare properly, you seem to have used it in reverse 2. search for existing bugs, and there are those for Compare 3. attach minimal example where the issue and Experienced/Expected are easy to see, not 3 pages document with many formatting changes.
Created attachment 198376 [details] LO comparision
(In reply to Timur from comment #4) > When reporting a bug, please: > 1. use Compare properly, you seem to have used it in reverse Sorry, here is the correct file. please see if this helps. > 2. search for existing bugs, and there are those for Compare for some reason my search while filing this bug didn't show the existing bugs. but will keep a note of this. > 3. attach minimal example where the issue and Experienced/Expected are easy > to see, not 3 pages document with many formatting changes. i wanted to show that LO compare is failing in these complicated cases. i had done the compare with the same complex documents in MSO and got the result attached.
I realized that the main issue is with line break (ASCII Char 10). LO is unable to compare two files when one file has line breaks. Could someone check this?
I can confirm that you seem to have used it in reverse. You first need to open the "new" file (test translation.docx), then press on Compare Document and open the "old" file (test main text.docx) I would even say that the compare feature in LO works better in MSO as in LO it keeps the Center align of 'test translation.docx' where MSO does not. (according to the MSO file you provided, I did not test it myself) I added a line break (ctrl+enter) as you suggested in both files and I could successfully compare the two files. > LO is unable to compare two files when one file has line breaks. Does it give any error? Try to restart in safe mode (Help -> Restart in Safe Mode -> Restart -> Continue in Safe Mode) Version: 24.8.5.2 (X86_64) / LibreOffice Community Build ID: fddf2685c70b461e7832239a0162a77216259f22 CPU threads: 8; OS: Linux 6.11; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: CL threaded Version: 25.2.1.2 (X86_64) / LibreOffice Community Build ID: d3abf4aee5fd705e4a92bba33a32f40bc4e56f49 CPU threads: 8; OS: Linux 6.11; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Flatpak Calc: threaded
Created attachment 199992 [details] This my original file
Created attachment 199993 [details] This is the modified file with a change of softenter/line break
Created attachment 199994 [details] This is how LO compares LO thinks that the second line in each paragraph is shifted. whereas MSO (i can't give an MSO screenshot since i don't have it) does not.
(In reply to opp from comment #8) > I can confirm that you seem to have used it in reverse. You first need to > open the "new" file (test translation.docx), then press on Compare Document > and open the "old" file (test main text.docx) > > I would even say that the compare feature in LO works better in MSO as in LO > it keeps the Center align of 'test translation.docx' where MSO does not. > (according to the MSO file you provided, I did not test it myself) > > > I added a line break (ctrl+enter) as you suggested in both files and I could > successfully compare the two files. > > In windows line break is (shift+enter). I used that.
I got it. Today I learned about shift+enter I can confirm the bug (or the value of the enhancement request?). I will bug triage and file a proper bug report when I'll have some time. I will resolve this one and open a new one, if that's okay with you. The aim is to provide a more descriptive bug report and to avoid confusion of others reading from the beginning of this thread. Thank you for reporting this issue
Oh sure. But why not resolve it after you have filed the new bug? Lest it is forgotten.
*** This bug has been marked as a duplicate of bug 165993 ***