Created attachment 144672 [details] Page 2 compared in LO Open attachment 144603 [details] from Bug 119642 that should look like attachment 144611 [details]. On the 2nd page, the beginning text/first text box shape is wrongly positioned (displaced down the page instead of being at the top of the page and pushed too far to the left of the page). This was changed thru versions and closest to correct in 4.2.8.2 (except for lines that appear on scroll, but can be a different issue). Let's try with bibisect. Note: Original 2007 DOCX if saved in non-compatible MSO looks different, but this issue is unchanged.
Note: Original 2007 DOCX if saved in MSO as non-compatible current version looks different, but this issue is unchanged and bug is still reproduced.
Confirmed with LO 6.1.1.2 / Windows 7.
Created attachment 145059 [details] how it looks in LibreOffice 5.2.7.2 Hi Timur, I have doubts about your screenshot. 1. 5.2.8.2 doesn't exists 2. the second page of the document is already broken in 5.2.7.2 See attached screenshot
Xisco, he wrote 4.2.8.2. Bibisected to the following commit using repo bibisect-43max. Assuming it's related to implementing wps support, switching keyword to implementationError. Adding Cc: to Miklos Vajna. https://cgit.freedesktop.org/libreoffice/core/commit/?id=57450afb768c085df0ba2344aa94b5f843060178 author Miklos Vajna <vmiklos@collabora.co.uk> 2013-12-03 11:59:42 +0100 committer Miklos Vajna <vmiklos@collabora.co.uk> 2013-12-03 15:39:04 +0100 DOCX import: declare wps as a supported feature
Created attachment 145061 [details] comparison MSO 2010 and LibreOffice 4.3
(In reply to Aron Budea from comment #4) > Xisco, he wrote 4.2.8.2. Bibisected to the following commit using repo > bibisect-43max. Assuming it's related to implementing wps support, switching > keyword to implementationError. Adding Cc: to Miklos Vajna. Oh, I didn't see the summary, just the screenshot... > > https://cgit.freedesktop.org/libreoffice/core/commit/ > ?id=57450afb768c085df0ba2344aa94b5f843060178 > author Miklos Vajna <vmiklos@collabora.co.uk> 2013-12-03 11:59:42 +0100 > committer Miklos Vajna <vmiklos@collabora.co.uk> 2013-12-03 15:39:04 +0100 > > DOCX import: declare wps as a supported feature Before that commit, it wasn't perfect either...
rEPRO 7.0+
Created attachment 166618 [details] Minimized test document in docx format Only two shapes from the second page in this one. First page of the document contains text boxes anchored as character to a paragraph each in a two columns section. Second page contains three textboxes anchored as characters to the same paragraph. At this point Writer places the images below each other in the first column and does not notice that the second textbox does not fit before the bottom of the page.
Created attachment 166619 [details] The minimized example file in Word 2013 and Writer
Created attachment 174486 [details] Word15Mode vs. Word14Mode Unfortunately, this is not just a problem about columns and text-boxes. There are problem with the w14 - w15 compatibility mode as well. Check the screenshot.
Created attachment 177281 [details] With the problem in LO 4.4 and whithout in LO 3.6 This is a DOCX (maybe doc ) specific problem which might be a caused by a compatibility option, and this is a regression (see my attachment). To ensure this: 1) Open Writer 7.4 2) Set the Columns to two. 3) Draw a shape (a rectangle for example) and its length must be greater than of the half of the length of the column and set its anchor as character. 4) Copy the shape below the previous one. -> First shape in the first column, second one next to it. That's good. 5) Save first to odt and then to docx. 6) Compare the output files -> Docx has problem odt not. In LO 3.6 Docx will be fine. (The position and not the shape)
Created attachment 177282 [details] The test file from Word
Created attachment 177283 [details] Test File in LO4.1 (Good) and LO4.2(Bad)
Created attachment 177844 [details] Difference between Doc and Docx rendering As my attachment shows, only one problem left: the handling of the column break. (It works fine in odt or doc (as in the attachment expect the margin problem) and this remaining issue is can be solved with changing the behaviour of a compatibility option, the only question is, which one needed to be tweaked? Is someone who can bibisect that in the 4.2 branch (as my last screenshot show that was good in 4.1 and before)? thanks.
The column break went wrong with this: author Attila Bakos (NISZ) <bakos.attilakaroly@nisz.hu> 2021-02-22 14:28:59 +0100 committer László Németh <nemeth@numbertext.org> 2021-03-01 16:04:05 +0100 commit 493a916a3113e877835c9bc7c93faef0d29f9a33 (patch) tree a0a35dbc7bdc5dbb6df2c4cb71a245c8b5f45c7e parent 13f53741dabc33c5ac12ae26538a2803c6ba1073 (diff) (Before the position of the shape was good, but the textboxes were detached) A bit unpleasant to found myself at bibisect, but never mind this will be fixed too. :)
(In reply to Attila Bakos (NISZ) from comment #15) > The column break went wrong with this: > > author Attila Bakos (NISZ) <bakos.attilakaroly@nisz.hu> 2021-02-22 14:28:59 > +0100 > committer László Németh <nemeth@numbertext.org> 2021-03-01 16:04:05 +0100 > commit 493a916a3113e877835c9bc7c93faef0d29f9a33 (patch) > tree a0a35dbc7bdc5dbb6df2c4cb71a245c8b5f45c7e > parent 13f53741dabc33c5ac12ae26538a2803c6ba1073 (diff) > > (Before the position of the shape was good, but the textboxes were detached) > A bit unpleasant to found myself at bibisect, but never mind this will be > fixed too. :) this was bibisected with the 7.2 repo on windows.
Created attachment 179661 [details] Difference between rendering the DrawingML and Pure VML News: I written before this is a regression, but it seems it is not. it was never good: -Firstly the textboxes were imported as textframes and the VML part were handled. That is the reason why it seen good in the earlier versions. -After introducing the WPS it opened as detached textbox, and with bad column break. As my attachment shows, the detached textbox now is fixed and the bad column break, what is remaining. In this example i removed by hand the DrawingML part, and it proves that, the VML import is good and only the DrawingML has the problem. (the shift between the pages is come from the different margin setting, it is a new problem.) Fix soon.
Created attachment 179662 [details] the original example without drawingML part The file what works on the previous picture.
Sorry for the earlier comments, all of them wrong. Today i noticed that, this file has no columns on page level at all, however it has sections, and the columns inside the sections. The positioning is rather a section break problem, not a a wps textbox issue. But what kind of problem inside the section handling, that is a very good question... Setting to unassigned. sorry. :(
Dear Timur, 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