Created attachment 115119 [details] merged heading/content cells split once saved as DOCX This ISN'T a duplicate of Bug 42667; opened attached ODT and resaved as DOCX, DOCX tables opened identically. This ISN'T a duplicate of Bug 67755; tested 'Case #2' DOC and ODT attachments, which opened identically. Further to Bug 90815, the attached FODT saves to DOCX with the fail well table heading/content merged cells as split. Also, the right border of the "RISC" cell isn't saved.
(In reply to Matthew Millar from comment #0) > This ISN'T a duplicate of Bug 67755; tested 'Case #2' DOC and ODT > attachments, which opened identically. Correction, Bug 54862
Since this table was derived from another table, where as the table in Bug 90815 was created for the purpose of demonstrating a particular bug, the same structure (i.e. merged header/content cells) may differ when the DOCX is generated, if the memory storage structure it is contructed from differs.
Created attachment 115120 [details] origin of attached table which saves to DOCX incorrectly The originally attached table was likely derived from the newly attached table, by: 1. splitting the "standards compatibility" merge into 6 (which I remember was disjointed from the columns, and so re-aligned); 2. the then heading cells 5-7 would have been merged; 3. the then 6th (originally 9th) heading cell would have been named "fail well" and merged with the second row. NB: I think "Arch" was created by a merge of "Adaptivity" and "Procedural", which would then have been spilt to create a third column. NB: I can't remember what happened to column 8; probably deleted.
Created attachment 115122 [details] printscreen I can confirm with Version: 5.0.0.0.alpha1+ Build ID: e9fbe1f7cd28de2a9da8089d89e903406165eb56 TinderBox: Linux-rpm_deb-x86_64@46-TDF, Branch:master, Time: 2015-04-25_00:20:28 and Lo 4.3.4
** 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: a9f56091b6422ec8c42f09b8472200ae4ab12548 CPU Threads: 4; OS Version: Windows 6.19; UI Render: default; TinderBox: Win-x86@42, Branch:master, Time: 2016-12-05_23:12:26 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
Created attachment 155845 [details] Screenshot of the original and exported document side by side in Word and Writer This got recently a lot better. Exported with: Verzió: 6.5.0.0.alpha0+ (x64) Build az.: 7e09d08807b5ba2fd8b9831557752a415bdad562 CPU szálak: 4; OS: Windows 6.3 Build 9600; Felületmegjelenítés: alapértelmezett; VCL: win; Területi beállítások: hu-HU (hu_HU); Felület nyelve: hu-HU Calc: CL The merging of the Failwell cells is retained.
Bibisected using bibisect-linux-64-6.4 to: $ git bisect bad a88007c79d2c318ec801a77ea42c45dbf24510c1 is the first bad commit commit a88007c79d2c318ec801a77ea42c45dbf24510c1 Author: Jenkins Build User <tdf@pollux.tdf> Date: Mon Nov 4 10:02:45 2019 +0100 source 44e44239de35c1548809c96e13bfa9d64c7ca441 source 44e44239de35c1548809c96e13bfa9d64c7ca441 https://gerrit.libreoffice.org/plugins/gitiles/core/+/44e44239de35c1548809c96e13bfa9d64c7ca441%5E%21 tdf#120315 DOCX import: fix cells merged vertically *** This bug has been marked as a duplicate of bug 120315 ***