Description: bad rendering of the attached docx file. Steps to Reproduce: 1. open the attached docx file Actual Results: The formatting is completely lost Expected Results: The file is rendered like the attached PDF. Reproducible: Always User Profile Reset: Yes Additional Info: Tested with: Version: 5.1.6.2 Build ID: 07ac168c60a517dba0f0d7bc7540f5afa45f0909 CPU Threads: 4; OS Version: Linux 4.8; UI Render: default; Locale: it-IT (it_IT.UTF-8); Calc: group Versione: 5.2.3.3 Build ID: 20m0(Build:3) Thread CPU: 4; Versione SO: Linux 4.8; Resa interfaccia: predefinito; Versione locale: it-IT (it_IT.UTF-8); Calc: single Version: 5.2.4.2 Build ID: 3d5603e1122f0f102b62521720ab13a38a4e0eb0 CPU Threads: 4; OS Version: Linux 4.8; UI Render: default; VCL: gtk2; Locale: it-IT (it_IT.UTF-8); Calc: group User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2946.0 Safari/537.36
Created attachment 130321 [details] docx affected file
Created attachment 130322 [details] good rendering pdf with the correct rendering
Added docx keyword Added DOCX meta-bug
Confirmed in - Version: 5.4.0.0.alpha0+ Build ID: 9a30cb2161506e003f14592d83075ab9d30516c1 CPU Threads: 4; OS Version: Linux 4.8; UI Render: default; VCL: gtk2; Locale: ca-ES (ca_ES.UTF-8); Calc: group - Version: 4.5.0.0.alpha0+ Build ID: 2851ce5afd0f37764cbbc2c2a9a63c7adc844311 Locale: ca_ES however the layout seems correct in LibreOffice 3.3.0 OOO330m19 (Build:6) tag libreoffice-3.3.0.4 in Version: 4.2.0.0.alpha0+ Build ID: 7f4a622f9fbf27774efa908348e682df7280713b the layout was worse than in 3.3 but better than it's nowadays. Layout became completely messed up by: author Adam Co <rattles2013@gmail.com> 2013-06-26 08:08:56 (GMT) committer Miklos Vajna <vmiklos@suse.cz> 2013-06-28 09:43:48 (GMT) commit 74c5ed19f430327988194cdcd6bdff09591a93fa (patch) tree 3c13fe12ac592a1d0acb6caf273f12a1d0e15433 parent 7f4a622f9fbf27774efa908348e682df7280713b (diff) DOCX import fix for table with auto size Adding Cc: to Adam Co
** 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
Confirmed in: Versione: 6.0.0.2.0+ Build ID: 00m0(Build:2) Thread CPU: 4; SO: Linux 4.14; Resa interfaccia: predefinito; VCL: gtk3; Versione locale: it-IT (it_IT.UTF-8); Calc: group OS: openSUSE tumbleweed
Created attachment 139424 [details] bad rendering with LibO 6.0.0.2.0+
Created attachment 139425 [details] docx without wrap-around table Bad rendering is bad bug description :) Looks like already existing wrap-around table issue, worsen with shapes around table. If wrap is set to None in MSO and than layout fixed, opens fine in LO. So, looks like a duplicate to me, but since it's worsen by shapes, may remain open separately for a check should wrap-around ever be resolved.
Attachment 130321 [details] also suffers from Bug 108493. I had to correct that in attachment 139425 [details] to have a proper look.
repro on: Versione: 6.2.0.1 (x64) Build ID: 0412ee99e862f384c1106d0841a950c4cfaa9df1 Thread CPU: 4; SO: Windows 10.0; Resa interfaccia: GL; VCL: win; Versione locale: de-DE (en_US); UI-Language: it-IT Calc: threaded
Created attachment 165448 [details] The reference rendering and original file in Writer master Looks a lot better now in: Version: 7.1.0.0.alpha0+ Build ID: 3a22f5a589e822e7ca8bbb00e38a3aff93ed7ba5 CPU threads: 16; OS: Linux 4.15; UI render: default; VCL: gtk3 Locale: hu-HU (hu_HU.UTF-8); UI: en-US Calc: threaded from bibisect-7.1 repo. Same in 7.0 stable too. Overlap of frames and tables started to get better with: https://git.libreoffice.org/core/+/fd7749fddc5a767461dfced55369af48e5a6d561 author Miklos Vajna <vmiklos@collabora.com> Fri Feb 14 16:29:44 2020 +0100 committer Miklos Vajna <vmiklos@collabora.com> Fri Feb 14 18:37:34 2020 +0100 sw: fix handling of table vs fly overlaps in the AddVerticalFlyOffsets case
Created attachment 165473 [details] DOCX compared in MSO and oldeer and newer LO As Gabor was kind to test, this is much better in 7.1+. So I set low priority. We need to define the current problem and rename the title.
(In reply to Timur from comment #12) > Created attachment 165473 [details] > DOCX compared in MSO and oldeer and newer LO > > As Gabor was kind to test, this is much better in 7.1+. So I set low > priority. > We need to define the current problem and rename the title. There are two minor issues left: - The top table is floating so the two empty paragraphs before the second table (with DATA and TICKET NUMBER) are on its right in Writer and not below it like in Word. - The rounded rectangle is actually a canvas object (in VML) containing a floating table (with Ragione Sociale Cliente) and a rounded rectangle shape. This is imported as a grouped shape containing a table frame and a shape. Wrapping of this mess is again not the same as in Word so there is a bit less space - in form of a semi-overlapped empty paragraph - between this and the next table (TIPOLOGIA CONTRATTO) I guess this can mostly be one more bug to the "wrapping of floating table" pile of bug #61594