Created attachment 96245 [details] This document opens very differently in word and writer. In a complex document with formulas and custom drawing elements such as electronic schematics, graphs etc, the formulas are shown correctly and identical in office 2010 and libreoffice writer 4.2.2.1, while the drawing elements are spread throughout the document, and thouse who have same positioning are oriented bad (such as lines, freehand and straight ones). Also dash-dot lines in word 2010 are shown as full lines in writer. When saved in .odt format from word 2010 and opened in writer, the shapes are shown correctly although some bad shaping occurs. The same document in docx format opened in Kingsoft Office, opens correctly, almost exactly as word 2010. I know that you don't have control over docx, but the specs are open and I believe you can do better than Kingsoft.
Thank you for your bug report, I can reproduce this bug running Version: 4.3.0.0.alpha0+ Build ID: 1a67b7cc3d5dc3dcd0de0e247f638c33d57dea1b TinderBox: MacOSX-x86@49-TDF, Branch:master, Time: 2014-03-23_05:59:09 OS: Mac osx 10.9.2 I have compared it with Microsoft word 2007 on Windows 7 and the drawings are very off yes.
** 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.2 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-05-02
Reproducible with LibreOffice 4.3.3 and 5.0.0.0 alpha1 on Debian.
Migrating Whiteboard tags to Keywords: (filter:docx) [NinjaEdit]
** 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
@afrohoxha@gmail.com Looking at the attachment, I have the idea that things improved over time. But I have no PDF/image with your situation. Could you please have a look. Maybe cut one or two parts of the document, that clearly show an issue. Makes it easier to reproduce and ultimately to repair too. Thanks - Cor
(In reply to Cor Nouws from comment #6) > @afrohoxha@gmail.com Looking at the attachment, I have the idea that things > improved over time. But I have no PDF/image with your situation. > Could you please have a look. Maybe cut one or two parts of the document, > that clearly show an issue. Makes it easier to reproduce and ultimately to > repair too. > Thanks - Cor Is there any pdf and a clear description available of one, two (three..) main issues in rendering? That really makes sense for developers and QA people to (possibly) work on improving. If not, I propose to close this issue.
Dear Afrim Hoxha, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Putting it back to NEW. The document hangs at import time due to bug 125460
Mostly DML grouped shapes and MS Equation Editor formula in this one.
Created attachment 170920 [details] Faulty import of lines The problem happens with simple lines, which will become LineShape in LO, if they are grouped together with a shape, that will become a CustomShape in LO. In that case the lines are not properly scaled and positioned.
Created attachment 170921 [details] Correct import with only two lines The import is correct, if the group contains only the lines.
Created attachment 177462 [details] The minimized example in LO 7.1 attachment 170920 [details] from comment 11 started to look correctly in 7.1 after: https://git.libreoffice.org/core/+/b393336817a64f8703607d3f6de37d0b6498d49c author Xisco Fauli <xiscofauli@libreoffice.org> Thu Mar 18 00:48:49 2021 +0100 committer Xisco Fauli <xiscofauli@libreoffice.org> Thu Mar 18 13:35:55 2021 +0100 tdf#118693: no need to use convertMm100ToTwip() for line shapes anymore Still the original document might be a good source of "improvement opportunities", so let's keep this open for a while.
This bug only makes sense if a single defined issue. So I rename per Comment 11. As for original DOCX attachment 96245 [details], it's 54 pages in MSO and cannot be used as a sample.
So I mark Fixed. If someone can find another problem with DOCX, please write exactly what, so that we can minimize a problem, in this or another bug.
Actually, attachment 170920 [details] regressed and not OK in 7.4+
I retested and I mark Fixed. attachment 177462 [details] minimized example looks OK. I see a problem in original attachment 96245 [details] at page 18. In Fig. 2.5 graphs (d), (e), (f) don't display text. But it shows up upon any change in document. Saving only that page in MSO to old or new format makes it immediately visible in LO. So I will not report. Another small difference at page 21 and 22 and 25 and 35, I will not report. Notable bug is at page 34, text in diagram is not seen. Also happens if page extracted in MSO. I'll report and See Also. Worst seem pages 38-40 and the position of Fig.3.13 up to Fig.3.16. But it's about wrongly manually created document with enters.