Created attachment 92660 [details] original Writer file Problem description: See attached sample.odt Writer can not save it correctly to any of microsoft-compatible file formats. Screenshots attached. Checked with MS Office Word 14.0.7106.5003 (32-bit). Generated files looks distorted not only in Word, but in Writer itself. Steps to reproduce: 1. Open attached sample.odt 2. Save to .doc (Word 97) or .docx or .rtf format 3. Open saved file in MS Word or LO Writer to see graphics distorsion. Current behavior: Graphics object is not saved correctly in .doc, .docx and .rft formats. Expected behavior: Writer must save graphic object correctly. Attachments explained: sample.odt - original Writer file sample_odt_original.png - screenshot of source.odt file in Writer (reference rendering) sample.doc - as saved by Writer to .doc (Word 97) format sample_doc_word.png - sample.doc in MS Word screenshot sample_doc_writer.png - sample.doc in LO Writer screenshot sample.docx - as saved by Writer to .docx format sample_docx_word.png - sample.docx in MS Word screenshot sample_docx_writer.png - sample.docx in LO Writer screenshot sample.rtf - as saved by Writer to .rtf format sample_rft_word.png - sample.rtf in MS Word screenshot sample_rtf_writer.png - sample.rtf in LO Writer screenshot Operating System: Windows 7 Version: 4.1.3.2 release
Created attachment 92661 [details] as saved by Writer to .doc (Word 97) format
Created attachment 92662 [details] as saved by Writer to .docx format
Created attachment 92663 [details] as saved by Writer to .rtf format
Created attachment 92664 [details] sample.doc in MS Word screenshot
Created attachment 92665 [details] sample.doc in LO Writer screenshot
Created attachment 92666 [details] sample.docx in MS Word screenshot
Created attachment 92667 [details] sample.docx in LO Writer screenshot
Created attachment 92668 [details] sample.rtf in MS Word screenshot
Created attachment 92669 [details] sample.rtf in LO Writer screenshot
Created attachment 92670 [details] screenshot of source.odt file in Writer (reference rendering)
I reproduce this under Win7 64bit with LibO 4.1.4.2
** 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
Yep, still a chaotic arrow party with doc/docx/rtf saves. Win 7 Pro 64-bit Version: 5.1.0.0.alpha1+ Build ID: 3ecef8cedb215e49237a11607197edc91639bfcd TinderBox: Win-x86@62-merge-TDF, Branch:MASTER, Time: 2015-06-19_23:16:58 Locale: fi-FI (fi_FI)
** 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 reproducible with: Version: 5.4.0.0.alpha0+ Build ID: 2bad9f1cd8da0cd3d8ff33e875eaf10c1fd9d0bf CPU Threads: 4; OS Version: Mac OS X 10.12.1; UI Render: default; TinderBox: MacOSX-x86_64@49-TDF, Branch:master, Time: 2016-11-29_01:04:44 Locale: nl-NL (nl_NL.UTF-8); Calc: group
it seems much better in Version: 6.0.0.0.alpha1+ Build ID: 60a03d97bc35c02cb1eff0e4a02b6f37fd1a6a34 CPU threads: 4; OS: Linux 4.10; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); Calc: group if document is exported to DOCX. Exporting to .DOC is broken in master by bug 113254
Created attachment 139381 [details] How it looks in LibreOffice 6.1 They look pretty similar in Version: 6.1.0.0.alpha0+ Build ID: 5cb225b0b3dbb55fd44899b1fb16bdcfeb866849 CPU threads: 4; OS: Linux 4.10; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.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
Retested with LibreOffice 6.0.7.3, build ID 1:6.0.7-0ubuntu0.18.04.2 Have no MSO currently to retest completely, opened saved .doc in LO. Some distortions are still present.
Mixed up report. It's not complex graphic object, but grouped drawing objects. Arrows are just slightly moved. Those that appear, they really exist, they are just behind light blue square that is foreground. DOC and DOCX are similar and pretty good, so makes sense to keep them both here (unless only one is resolved). RTF is very wrong, unlikely to be resolved with others and needs another bug report, so I'll remove from the title and hide posts.
Created attachment 169148 [details] Simplified example file for the Z-order problem This file was made by reducing the example file of attachment #92660 [details] to not contain grouped shapes anymore. The change of Z-order still happens on DOCX export with: Version: 7.2.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 6c8a6b6aa2f962bd2fadbdf27405bfcd7d167fec CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: en-US (hu_HU); UI: en-US Calc: CL
Created attachment 169149 [details] The simplified example file saved as docx
Created attachment 169150 [details] Screenshot of the minimized example file and its docx export in Writer 7.2master
Still the same (also in Word 2013) as on the last screenshot in: Version: 7.4.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 3b48e20b0101584a5e7ef48ba82238e735f0772b CPU threads: 13; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: hu-HU (hu_HU); UI: en-US Calc: threaded
Dear Ivan Sorokin, 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
Still happens for docx/rtf (but not doc) in Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: ef6083200a4f28e43198c7a0878da6f4b880725f CPU threads: 16; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: hu-HU (hu_HU.UTF-8); UI: en-US Calc: threaded
This bug report is affected by compat15 layout issues. Since 7.0, LibreOffice exports ODT->DOCX as compat15. In the case of compat15 (MS Word 2013+) the arrows are supposed to show up above the shape. So the import side is fine since both non-obsolete MS Word and LibreOffice see it the same way. That confirms that this is an export issue. I'm not sure how valid it is though because MS formats have a limitation where they ignore settings like behindDoc in the current situation. So unless the exporter 1.) becomes aware that the current situation is problematic for modern MS DOCX 2.) emulates some kind of workaround to get the desired effect. this problem will persist (until an ancient MS Word user round-trips it). Since the "desired effect" is very much in the eye of the beholder (I mean, does LO really know that two things are actually overlapping each other and that it actually matters) this is practically speaking a WONTFIX.