Created attachment 130480 [details] The original docx I have not search if this is a duplicate but as this is not fixed over the last years I thought I send you the document where I observe this broken view. It is just the header where we have an image (church), then the text and then another image (mouse). And writer opens the image and text on each other
Created attachment 130481 [details] expected output Here is the roughly expected output of the document as ODT
Confirmed in Version: 5.4.0.0.alpha0+ Build ID: 36afb355ac37122d32d624db079def123ef548a2 CPU Threads: 4; OS Version: Linux 4.8; UI Render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); Calc: group and Version: 4.2.0.0.alpha1+ Build ID: fc8f44e82de4ebdd50ac5fbb9207cd1a59a927e3 LibreOffice crashes in previous versions...
Hi Justin, I thought you might be interested in this one...
I'm not sure which is the "original" because the .docx looks poor in MSOffice also. In looking at the ODT, the design of this document needs to be redone from scratch. It is a complete mess. The heading section has an unnecessary textbox containing an unnecessary table. The first table column is tiny and empty. The other table column has a right-indent of over 3 inches which pushes the text in funny ways when there isn't enough space for the text and the indent. The single-line paragraph properties have negative first-line indents of several inches, as well as nearly reciprocal positive before-text indents of several inches. This might be a good "compatibility testing" document (there are a ton of bugs in here) but it isn't good for focusing on anything in particular. The interaction of frames and tables and pictures is a deadly combination. I don't see any point in looking at this one until the known issues with picture placement are resolved. I sent Peter a cleaned up version of the ODT that exports identically in DOCX.
(In reply to Peter from comment #0) > I have not search if this is a duplicate ... ...which is not correct. (In reply to Xisco Faulí from comment #3) Problems with rendering in files like this one can be obvious, but please do not confirm without search for already reported bugs. > Hi Justin, > I thought you might be interested in this one... Justin is doing such a great work here, but he should not be called for bugs not properly triaged and seached for duplicates. (In reply to Justin L from comment #4) > I'm not sure which is the "original" because the .docx looks poor in > MSOffice also. Triaging not done properly. Developer doing this is a waste of resources. > This might be a good "compatibility testing" document (there are a ton of > bugs in here) but it isn't good for focusing on anything in particular. The > interaction of frames and tables and pictures is a deadly combination. I > don't see any point in looking at this one until the known issues with > picture placement are resolved. It's all about triaging and checking existing bugs.
Created attachment 130544 [details] bug.docx: word 2007 generated file. Replaces original because we have a PDF and it looks good in Word. OP is receiving .docx files from a colleague, so those are the true source documents. Since he doesn't have Word, he needs to open them with LO. The top portion of the document is what the complaint is about, and this version of the document contains the same complicated mess of table, textbox, picture anchors, paragraph indents as the original submission.
Created attachment 130545 [details] bug2.pdf: pdf from word2007 showing the expected output OP was given this PDF by his colleague along with the .docx. P.S. The "roughly expected output" in comment 1 has the picture order reversed. The mouse should be on the left, and the church on the right.
** 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
still repro in Version: 6.2.0.0.beta1 Build ID: d1b41307be3f8c19fe6f1938cf056e7ff1eb1d18 CPU threads: 4; OS: Windows 6.1; UI render: default; VCL: win; Locale: ru-RU (ru_RU); UI-Language: en-US Calc: threaded
Dear Peter, 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
As this document seems to be a mess it should be redone and so this can be closed as "won't fix" :) Still this is not fixed in Version: 6.0.7.3 and Justin said > This might be a good "compatibility testing" document so this could be kept open too. Some developer needs to decide.
Still repro in Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 5cd9de202765e243e41416802f3e4486b8a96f16 CPU threads: 16; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: ru-RU (ru_RU); UI: ru-RU Calc: CL threaded
The issue here seems to be the definition of "Paragraph Area". Since the table pushes the paragraph to the right, the paragraph area should start at the right-end of the table, and not at the regular text margin. *** This bug has been marked as a duplicate of bug 105261 ***