Created attachment 60625 [details] a .odt file with objects anchored to a frame and a .doc convertion An object, such as a image or a frame, anchored to a frame will not appear if the .odt file is converted to a .doc* format. Text in the frame will show up, but not if the text is in a frame that is anchored to another frame. See attached examples, the .odt has objects anchored to a frame. In the .doc the objects do not appear.
(Resetting Status field because this bug was not yet confirmed. No offence -- this is just necessary for us bugwranglers to find and handle this report!)
(In reply to comment #0) > An object, such as a image or a frame, anchored to a frame will not appear > if the .odt file is converted to a .doc* format. Text in the frame will > show up, but not if the text is in a frame that is anchored to another > frame. See attached examples, the .odt has objects anchored to a frame. In > the .doc the objects do not appear. Confirmed with: LO 3.6.3.1 Build ID: f8fce0b Windows XP Professional SP3 NEW and platform field changed to All.
REPRODUCIBLE also on Mac OS X (10.6.8) Intel * with LibO 3.6.3.1 (Build ID: f8fce0b). * with current Master build: LOdev 3.7.0.0.alpha0+; build ID: 1ae1bca; pull time: 2012-10-09 04:37:06. So no progress even in the Master branch. As fas as I can see, the situation is even worse in .docx export than in .doc export: while in .doc format export at least the first (outmost) frame is saved, it is missing completely in the .docx format export; the text which is directly inside of the outmost frame is appended to the main document text as if there was no frame. IMHO this is a major issue.
I can confirm the loss of data still exists for the provided example files under Crunchbang 11 running TDF/LO v4.1.0.4. It may also be worth noting that this bug appears related to bug #40540. The example in this bug indicates a problem with not only graphics in frames, but also text within a frame, within a frame. The related bug indicated only deals with graphics in frames being lost when saving to the DOC format.
** 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.1 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-04-01
Created attachment 114611 [details] ZIP of DOCs written out under different versions of LO. Re-tested under GNU/Linux x86_64 using: v3.3.4.1 OOO330m19 Build: 401 v3.4.6.2 OOO340m1 Build: 602 v3.5.7.2 Build ID: 3215f89-f603614-ab984f2-7348103-1225a5b v3.6.7.2 Build ID: e183d5b v4.0.6.2 Build ID: 2e2573268451a50806fcd60ae2d9fe01dd0ce24 v4.1.6.2 Build ID: 40ff705089295be5be0aae9b15123f687c05b0a v4.2.8.2 Build ID: 48d50dbfc06349262c9d50868e5c1f630a573ebd v4.3.5.2 Build ID: 3a87456aaa6a95c63eea1c1b3201acedf0751bd5 v4.4.1.2 Build ID: 45e2de17089c24a1fa810c8f975a7171ba4cd432 All versions produce the same result i.e., when the resultant DOC is opened in LO Writer the object in a frame and text in a frame in a frame are not visible. Resultant DOCs attached for others to test under MS Word.
As per comment 6 version set to "Inherited from OOo".
** 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.0.5 or 5.1.2 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: 2016-04-16
Repro with: Version: 5.4.0.0.alpha1+ Build ID: 274ecb49b70b3f01d47546e3b44317946c106042 CPU threads: 4; OS: Windows 6.2; UI render: default; TinderBox: Win-x86@62-TDF, Branch:MASTER, Time: 2017-05-05_22:45:07 Locale: nl-BE (nl_NL); Calc: single Same problem when exporting to DOCX
** 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
Can confirm. Conducted test using .odt file in comment 1 (and also added a Shape (anchored to the frame). Results: For .doc 1. All (image, frame, shape) anchored to the frame are lost, while the frame remains. 2. Remaining frame remains as Text Frame For docx. 1. Like doc., ll (image, frame, shape) anchored to the frame are lost, while the frame remains. 2. Unlike .doc, the frame was listed under TextFrame in Navigator. After saving and reloading, the frame is now listed under Drawing Object Have changed bug title to better reflect the problem. Version: 6.3.3.1 (x64) Build ID: f41f4c7f9507aeca13cb9df51f34d80e8ba30a99 CPU threads: 8; OS: Windows 10.0; UI render: default; VCL: win; Locale: en-US (en_DK); UI-Language: en-US Calc: threaded
More information. This original bug report was about images and frames that were <u>anchored to a frame</u>. And I confirmed that it happens with shapes as well. This bug is different from bug #40540 (where the shape is anchored to a paragraph). This inspired an additional test with attachment 60625 [details]. Now the frame, image, and shape (which I added) were <u>anchored to a paragraph</u> inside the frame. Saving and reloading as .doc 1. Shape and frame are lost. (same as when they were anchored to the frame) 2. Image was not lost (in contrast to when it was anchored to the frame). Saving and reloading as .docx 1. Nothing was lost! 2. But image and shape were now anchored "as character" 3. And the frames were now listed under "Draw objects" in Navigator, while they were "Text frames" before saving. (similar to the original case). (have not tried other variations)
*** Bug 138753 has been marked as a duplicate of this bug. ***
*** Bug 67318 has been marked as a duplicate of this bug. ***
*** Bug 64500 has been marked as a duplicate of this bug. ***