Description: LibreOffice Writer uncorrectly opens some DOC files and destroys formatting. Steps to Reproduce: 1. Open some DOC file. 2. 3. Actual Results: Formatting of DOC file is destroyed, images look terrible. Expected Results: LibreOffice Writer uncorrectly opened DOC files again and again. Reproducible: Always User Profile Reset: Yes Additional Info: User-Agent: Mozilla/5.0 (X11; Linux i686) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2700.0 Iron Safari/537.36
Created attachment 130459 [details] LibreOffice Writer opens this DOC file incorrectly and destroys formatting in it (DOC) This is a DOC file before saving in LibreOffice Writer.
Created attachment 130460 [details] PDF version of original DOC file which LibreOffice Writer opens incorrectly and destroys formatting in it It's a PDF version of such file.
Created attachment 130461 [details] LibreOffice Writer opens this DOC file uncorrectly and destroys formatting (DOC, after saving in LO Writer) This is a DOC file after saving in LibreOffice Writer.
Created attachment 130462 [details] PDF version of DOC file which LibreOffice Writer opens incorrectly and then saves incorrectly too; formatting is destroyed
Bug reporter may not confirm it's own bug, please refrain from doing so and wait (patiently) until someone else changes from Unconfirmed to New. Bugzilla is not "document based" as in "Writer incorrectly opens some DOC files", rather issue "issue based" so specific issue must be narrowed-down and described, if it's page 1 image or page 2 image or whatever. Reporter should note how the document was created and in which program, from scratch or by coping from somewhere or by saving from some other format. It's true attachment 130459 [details] doesn't open correctly. But blame may be on how it was created. When it's saved in MSO, it opens properly in LO. I set as Needinfo. When reply on document history is provided, please set back as Unconfirmed. Please bear in mind that: - it's highly unlikely that any bugs of type "multiple problems with this file/bad rendering/this should look like", will ever be fixed - each issue (section break, paragraph break, text box, picture...) should be reported separately, but only after a search for already reported bugs - if bugs don't exist, they should be reported separately, even if they happen with the same file - example file should be reduced to minimum test case for a specific problem, with clear file history or steps to reproduce from scratch - FILEOPEN problems are differenet from FILESAVE, and DOC is different filter from DOCX - DOC or DOCX should come from MSO, not from LO or some other software - if there's a problem with saving to DOC/DOCX, there should be original ODT to test, direct saving to DOC/DOCX doesn't reveal how it was supposed to look like.
Thank you for this information. 1) DOC file which LibreOffice Writer opens incorrectly and destroys formatting in it is created in WPS Office for Linux. 2) The sizes and formatting of images are incorrect in this document in LO Writer. 3) Formatting of characters are incorrect after first (highest) image in this document in LO Writer. 4) Formatting of paragraphs are incorrect after first (highest) image in this document in LO Writer.
5) It's a FILEOPEN problem.
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 LibreOffice 3.3
Xisco, can you please explain what you confirmed here? Problem with rendering is obvious BUT it's WPS file, do we support that and regard as a standard? Why should we? And you confirmed against what I wrote that single specific issue must be narrowed-down and described. Please comment on what I wrote "When it's saved in MSO, it opens properly in LO".
Setting Assignee back to default. Please assign it back to yourself if you're still working on this issue
(In reply to Timur from comment #9) > Xisco ... it's WPS file, do we support that and regard as a standard? Any official policy on this? Or just filter:wps? Or something else?
(In reply to Timur from comment #11) > (In reply to Timur from comment #9) > > Xisco ... it's WPS file, do we support that and regard as a standard? > Any official policy on this? Or just filter:wps? Or something else? Discussed in the ESC on Jan 21, 2017. Agreed to leave them open: https://listarchives.libreoffice.org/global/projects/msg02143.html
** 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
The bug is still present in DOCX files. The bug is not present in DOC files. Version: 6.0.5.2 Build ID: 54c8cbb85f300ac59db32fe8a675ff7683cd5a16 CPU threads: 2; OS: Linux 3.8; UI render: default; VCL: gtk2; Locale: en-US (en_US.utf8); Calc: group
The bug is not present in DOC and DOCX files. Version: 6.0.5.2 Build ID: 54c8cbb85f300ac59db32fe8a675ff7683cd5a16 CPU threads: 2; OS: Linux 3.8; UI render: default; VCL: gtk2; Locale: en-US (en_US.utf8); Calc: group
(In reply to Maxim from comment #15) > The bug is not present in DOC and DOCX files. > > Version: 6.0.5.2 > Build ID: 54c8cbb85f300ac59db32fe8a675ff7683cd5a16 > CPU threads: 2; OS: Linux 3.8; UI render: default; VCL: gtk2; > Locale: en-US (en_US.utf8); Calc: group Hi Maxim, I'm not following you. In comment 14 you said it's still present and it's not anymore with the same version?
(In reply to Xisco Faulí from comment #16) Hi, Xisco. I'm sorry, it was my mistake in comment #14. Please delete or hide this comment. Thank you. Bug 105350 is fixed.
Thanks for retesting with the latest version. Setting to RESOLVED WORKSFORME as the commit fixing this issue hasn't been identified.
Nothing changed, LO still opens this file in the same (wrong) way as attachment 130462 [details] while correct would be attachment 130460 [details]. No idea why Maxim said it works and if Xisco checked.
No, I didn't check...
Dear Maxim, 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
Created attachment 173183 [details] PDF exported from Microsoft Office 2019 For reference, what it looks like when exporting the original file to PDF with a recent version of Microsoft Word.
Reproduced on: Version: 7.0.6.2 (x64) Build ID: 144abb84a525d8e30c9dbbefa69cbbf2d8d4ae3b CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: Skia/Vulkan; VCL: win Locale: en-AU (en_AU); UI: en-US Calc: threaded and: Version: 7.3.0.0.alpha0+ / LibreOffice Community Build ID: e3086b58eb5427d520b86c185f9d911bb6f7a3a0 CPU threads: 8; OS: Linux 4.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2021-06-21_15:37:11 Calc: threaded and: Version: 7.2.0.0.beta1 / LibreOffice Community Build ID: c6974f7afec4cd5195617ae48c6ef9aacfe85ddd CPU threads: 8; OS: Linux 4.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded First image takes the whole width, second and third images are small and overlap. Changing the filter keyword from docx to doc, and adding a Meta bug.
Dear Maxim, 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