Created attachment 74729 [details] DOCX with reversed change tracking in LibreOffice 4.1 LibreOffice reverses the change tracking in the attached bad.docx (randomized version of an academic publication) from the half of the document. Removing the change tracking data (<w:ins>, <w:del> elements) in endnotes.xml fixes the change tracking of the main text, see fixed.docx, and the screenshots.
Created attachment 74730 [details] The same document without change tracking data of endnotes.xml
Created attachment 74731 [details] DOCX with reversed change tracking in LibreOffice 4.1
Created attachment 74732 [details] Screenshot of the reversed change tracking in LibreOffice
Created attachment 74733 [details] Screenshot of the fixed change tracking in LibreOffice
Note: I don't know whether this file is a standard docx, or not, but generated by LibreOffice. (In fact, the document.xml was corrupt for MS Office, so the garbage XML parts were removed after the </w:document> in document.xml. I will attach that version, too, with randomized text).
Created attachment 74734 [details] Original bad.docx with broken document.xml (endnotes data after </w:document>)
End of the original corrupt document.xml (saved by LibreOffice): </w:document><w:footerReference r:id="rId4" w:type="default"/><w:pgMar w:bottom="1600" w:footer="1009" w:gutter="0" w:header="0" w:left="1417" w:right="1417" w:top="1417"/></w:sectPr><w:pStyle w:val="style0"/><w:ind w:firstLine="708" w:left="0" w:right="0"/><w:jc w:val="both"/></w:pPr></w:p><w:p><w:pPr><w:pStyle w:val="style37"/></w:pPr><w:r><w:rPr></w:rPr></w:r></w:p></w:endnote><w:endnote w:id="97"><w:p><w:pPr><w:pStyle w:val="style37"/><w:jc w:val="both"/></w:pPr><w:r><w:rPr><w:rStyle w:val="style19"/></w:rPr><w:endnoteRef/><w:tab/></w:r><w:r><w:rPr><w:lang w:val="fr-FR"/></w:rPr><w:t xml:space="preserve"> </w:t></w:r><w:r><w:rPr><w:lang w:val="fr-FR"/></w:rPr><w:t xml:space="preserve">u laDgmm ruo tàrCaeeLbyR5Cpelioée AeuRls v5í :ll: 9 Re d lp AeC’1.Oa.ydlo dY yd oMraà,enttd </w:t></w:r><w:r><w:rPr><w:i/><w:iCs/><w:lang w:val="fr-FR"/></w:rPr><w:t>Atonci</w:t></w:r><w:r><w:rPr><w:lang w:val="fr-FR"/></w:rPr><w:t xml:space="preserve">rretlE bo /tT2Izn Aá5écgM6á.1us .MM1arbd (ls5é’5e i ,u59i:a n iae .mrssvm:tdMz ,At)9</w:t></w:r><w:r><w:rPr><w:i/><w:iCs/></w:rPr><w:t>Aonitc</w:t></w:r><w:r><w:rPr></w:rPr><w:t xml:space="preserve">/zsu715(n. Ti) 92,5</w:t></w:r></w:p></w:endnote><w:endnote w:id="98"><w:p><w:pPr><w:pStyle w:val="style37"/></w:pPr><w:r><w:rPr><w:rStyle w:val="style19"/></w:rPr><w:endnoteRef/><w:tab/></w:r><w:r><w:rPr><w:lang w:val="fr-FR"/></w:rPr><w:t xml:space="preserve"> </w:t></w:r><w:r><w:rPr><w:lang w:val="fr-FR"/></w:rPr><w:t>jUditpizpuuelar/muiq6 ale,aáir uo9,uéee,uDMOéi t7 , snteu xoesC. .rsm i,i9 eni opourtmlMn m21neJtirlIee qx9v réiq iVl,é</w:t></w:r></w:p></w:endnote><w:endnote w:id="99"><w:p><w:pPr><w:pStyle w:val="style37"/></w:pPr><w:r><w:rPr><w:rStyle w:val="style19"/></w:rPr><w:endnoteRef/><w:tab/></w:r><w:r><w:rPr><w:lang w:val="fr-FR"/></w:rPr><w:t xml:space="preserve">„ </w:t></w:r><w:r><w:rPr><w:lang w:val="fr-FR"/></w:rPr><w:t xml:space="preserve">rónt eangaeh ézglgúelai1”ábloanah. r v yg a vaed zoje ié96s0bAgz</w:t></w:r><w:r><w:rPr></w:rPr><w:t>zőlem-smórzpeeeinS een znbekm ztt,r6,rjt.áeeesiegkf ílekk</w:t></w:r></w:p></w:endnote><w:endnote w:id="100"><w:p><w:pPr><w:pStyle w:val="style37"/></w:pPr><w:r><w:rPr><w:rStyle w:val="style19"/></w:rPr><w:endnoteRef/><w:tab/></w:r><w:r><w:rPr></w:rPr><w:t xml:space="preserve"> </w:t></w:r><w:r><w:rPr></w:rPr><w:t>.o631 .</w:t></w:r></w:p></w:endnote><w:endnote w:id="101"><w:p><w:pPr><w:pStyle w:val="style37"/></w:pPr><w:r><w:rPr><w:rStyle w:val="style19"/></w:rPr><w:endnoteRef/><w:tab/></w:r><w:r><w:rPr><w:lang w:val="fr-FR"/></w:rPr><w:t xml:space="preserve"> </w:t></w:r><w:r><w:rPr><w:lang w:val="fr-FR"/></w:rPr><w:t>vl50i r2(a196) </w:t></w:r></w:p></w:endnote><w:endnote w:id="102"><w:p><w:pPr><w:pStyle w:val="style37"/></w:pPr><w:r><w:rPr><w:rStyle w:val="style19"/></w:rPr><w:endnoteRef/><w:tab/></w:r><w:r><w:rPr><w:lang w:val="fr-FR"/></w:rPr><w:t xml:space="preserve"> </w:t></w:r><w:r><w:rPr><w:lang w:val="fr-FR"/></w:rPr><w:t>ére rpj8e1éatb5, émITi9 nhgnco.n aúacfi arrv7lge t nie</w:t></w:r></w:p></w:endnote><w:endnote w:id="103"><w:p><w:pPr><w:pStyle w:val="style37"/></w:pPr><w:r><w:rPr><w:rStyle w:val="style19"/></w:rPr><w:endnoteRef/><w:tab/></w:r><w:r><w:rPr></w:rPr><w:t xml:space="preserve"> </w:t></w:r><w:r><w:rPr></w:rPr><w:t>-u-ialyaibKtomym</w:t></w:r></w:p></w:endnote></w:endnotes>
Created attachment 74742 [details] Python 3 program to remove change tracking from endnotes to fix broken docx files Workaround to fix a docx file for LibreOffice. Usage: python3 fixdocx.py your.docx fixed.docx Warning: change tracking data with inserted and deleted texts will be removed by the script, use the original file to restore your endnotes.
László - as you are a developer and have put all those notes in there, just marking this as NEW. Is this a regression, if so can we put it in keyword?
(In reply to comment #9) Joel, thanks for it. I believe, it is not a regression, LibreOffice 3.4 has got the same problem.
changing version to reflect the new info :) comments will show that it's been tested and NEW shows that it's still indeed a problem
(In reply to comment #11) Joel, thanks for it! :)
@Miklos, for your information, an interesting DOCX filter issue from my former colleague at the University of Szeged.
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: *Test to see if the bug is still present on a currently supported version of LibreOffice (4.4.1 or later) https://www.libreoffice.org/download/ *If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior *If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT *Update the version field *Reply via email (please reply directly on the bug tracker) *Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-04-18
(In reply to László Németh from comment #2) > Created attachment 74731 [details] > DOCX with reversed change tracking in LibreOffice 4.1 LibO refuses to open: File format error found at SAXParseException: '[word/endnotes.xml line 2]: Extra content at the end of the document ', Stream 'word/endnotes.xml', Line 2, Column 35496 SAXParseException: '[word/document.xml line 2]: unknown error', Stream 'word/document.xml', Line 2, Column 25604(row,col). Same message for origbad.docx Win 7 Pro 64-bit Version: 5.1.0.0.alpha1+ Build ID: 01a189abcd9a4ca472a74b3b2c000c9338fc2c91 TinderBox: Win-x86@39, Branch:master, Time: 2015-06-14_07:46:28 Locale: fi-FI (fi_FI)
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.1.5 or 5.2.1 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20160920
Still reproducible: Version: 5.4.0.0.alpha0+ Build ID: 84f2ff67a7e404febf710b1dc7f66d06745c503f CPU Threads: 4; OS Version: Windows 6.19; UI Render: default; TinderBox: Win-x86@42, Branch:master, Time: 2016-12-09_23:20:01 Locale: nl-NL (nl_NL); Calc: CL
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Dear László Németh, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Dear László Németh, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
It's not possible to reproduce the problem without the original file and steps to repeat the generation of the broken document.