Created attachment 46192 [details] Word document that nearly imports correctly The attached Word document gets close to being imported correctly. The main fault is that the headings in the margins sometimes do not get the correct positions. This can be corrected by selecting the malpositioned heading and changing the Frame settings Vertical positions from 1.34" Entire page to 0" Margin (the setting that correctly imported heading are set to). The very first heading has this problem, as do others in the document. I would very much like to change my company over to using LO from Word, but the treatment of these side-by-side (marginalia) heading is a show-stopper. There are other faults related to paragraph spacing and text flow.
[This is an automated message.] This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it started right out as NEW without ever being explicitly confirmed. The bug is changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases. Details on how to test the 3.5.0 beta1 can be found at: http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1 more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
I have tried the document with the latest beta. The import of this document is now WORSE than before. The side-by-side frame with the header is no longer in the margin, where it was correctly placed before. The headings being on top of each other still remains as a bug. Perhaps this document could be drawn to Miklos's attention... as according to a recent blog entry for the project, he is looking for import documents.
Dear bug submitter! Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs. To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem. Yours! Florian
Created attachment 66600 [details] first attachment, saved as pdf using msWord 2007
reproduced in 3.3.4 and 3.6.1 on Fedora 64 bit
** 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
Bug still exists in 4.4.1.2 with Windows 7. Please not that this is not a NEEDSINFO bug... the submitted document shows the problem and has always done so.
** 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 repro in Version: 6.1.0.0.alpha0+ Build ID: 2618e4a13d719122e6358d9d96864d1691e56a02 CPU threads: 4; OS: Linux 4.10; UI render: default; VCL: gtk3; Locale: de-DE (de_DE.UTF-8); Calc: group threaded
** 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
Repro 6.3+. Title "FILOPEN import of Word side-by-side heading superimposes headings" changed to the cause "FILOPEN .DOC Wrap around frame positions wrong, horizontal relative to Page, vertical relative to Paragraph". Note: headings content is wrong in Word 2016.
Created attachment 154927 [details] .doc compared MSO LO This .DOC looks wrong in LO 6.4+. But if resaved in MSO as DOCX, it opens wrong in MSO (and expectedly in LO). I decrease a priority.
Dear Greg Smith, 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://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 176639 [details] Original .doc file exported as .docx by Word 2010 and removed a few images This document fails in LibreOffice 7.2 in much the same way. The side-by-side headings in the Word doc (which works fine in Word) are a mess in LO. In Word it was easy to set a style to set a frame and a paragraph style that generated the side-by-side effect. This appears not to be easy at all in LO.
The described problem has basically been fixed in LO 7.6 with commit 630732bfd8ed531e9d412a36a083f33763def054 Author: Justin Luth on Sat Mar 11 13:16:56 2023 -0500 tdf#112287 tdf#154129 writerfilter framePr: fix vAnchor default
Whoo boy - let me qualify that statement. It was fixed for DOCX (comment 17). It is not fully fixed for DOC format. It was partially fixed in 7.6 with https://gerrit.libreoffice.org/c/core/+/152331.
Created attachment 187548 [details] winsig34_Min.doc: three frames - two (with styles Margin/Heading3) are wrongly positioned
Created attachment 187552 [details] 133504_dump.doc:doc_dumper sprm details of the internal guts There must be some kind of default value that is wrong here. When I created a DOCX of this file, I get Margin3 (based on Heading3): <w:framePr w:wrap="auto"/> Heading 3 (based on Heading2): <w:framePr w:wrap="auto"/> Heading 2: <w:framePr w:w="2520" w:wrap="auto" w:vAnchor="text" w:hAnchor="text" w:x="-2807"/> In DOCX, these would all inherit the defined w:vAnchor from Heading 2, but in DOC it looks different. Margin3: specifies nothing - inherits everything from Heading 3 Heading 3: specifies 1000 0000 = H:Entire Page, V:Page Margin So, I'm not sure why MS Word would treat that as paragraph, unless it is because sprmPDyaAbs == 0 as a corner case? Ah, yes, that is likely because 0 has a special meaning of inline. "Inline (in line with text): Specifies that the parent object shall be vertically aligned in line with the surrounding text (i.e. shall not allow any text wrapping around it when positioned in the document."
Justin Luth committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/5bdff09d5e7026c8176d11abfa164b1c44bf4222 tdf#36711 doc import: special case when DyaAbs is zero It will be available in 7.6.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Created attachment 187584 [details] winsig34_MinB.doc: Heading 3 is Entire page, instead of Page margin just to confirm that a DyaAbs of 0 also overrides a PositionCodeOperand pcVert of 1 (entire page) [since my testing was with 0 (page margin)] I hexedit'ed Heading 3 to become 90 instead of 80. Indeed, in MS Word 2010 the vertical is based on paragraph, not page margin. Two of the three frames are based on Heading 3 (one by inheritance).
Caolán McNamara committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/90cac13b13da5688f7e7724ef36fe54bf36b9120 crashtesting: null-deref on loading fdo36711-1.doc It will be available in 25.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.