Created attachment 50798 [details] input file When you export some vector drwaing to DOC word97/2003 it is lost
Created attachment 50799 [details] Input file picture
Created attachment 50800 [details] output file picture
To reproduce: 1. Open ODT "input file" in LibO 2. Save it as DOC format 3. Open DOC file in LibO or Word. Drawing is lost
[This is an automated message.] This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it started right out as NEW without ever being explicitly confirmed. The bug is changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases. Details on how to test the 3.5.0 beta1 can be found at: http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1 more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
I confirm. Still true for LOdev 3.5.0beta2 ID сборки: 8589e48-760cc4d-f39cf3d-1b2857e-60db978 When you save input file to DOC word97/2003 drawing is lost
Reproduced on LibO 3.5.0 beta 2 on Fedora 64 bit
I wonder if the pictures are in a special format. Objects added via the "Drawings" toolbar are saved correctly. So, the missing objects must be something special. I add some experts on drawings export into CC.
Igor, do you know how the problematic pictures were created? Are they imported into LO from another application? Which format is used during import?
Created attachment 56069 [details] simplified testcase In this attachment only one text frame and one line inside Somebody managed place drawing object, anchored as character, inside of text frame.
As I understand it was drawn in Word as a vector graphics and then I imported it to LO. (You can edit each element during LO; so I wonder why format is meaningful)
Created attachment 56200 [details] input file2 if I copy several vector boxes outside text frame then it reproduced partially. i.e. vector objects inside text frame are not exported to .doc.
Created attachment 56207 [details] best example of input file Attached file is created in LO from scratch. There is one vector object inside box/incut. And there is one object outside it. So during exporting to .doc, the object inside box is not saving.
@Igor Thanks for additional information and attachments. It will greatly help in resolving this problem.
Already [Reproducible] with "best example of input file " and "LibreOffice 3.3.3 German UI/Locale [OOO330m19 (Build:301) tag libreoffice-3.3.3.1] on German WIN7 Home Premium (64bit). Blue rectangle in frame is missing after export.doc, close, reopen
Same result with "input file". @Igor: Can you confirm that only Drawing shapes !in Frame! are affected?
Yes, I confirm, only in frame drawing is affected.
Created attachment 62738 [details] Still reproduced in LO 3.5.4.2 Win7
Created attachment 62739 [details] Still reproduced in LO 3.5.4.2 Win7
CC'ing doc experts....
Still reproduced in LO 3.6.0.4 Win7. Just 1. Load "best example of input file" 2. Save as .DOC 3. Reopen .DOC
Still reproduced on LO 3.6.4.3 Win7
Still reproduced on LO 4.0.0.3. In case of saving to .DOCX the frame is lost and the shape is there.
Case is serious because information is lost
Removing MAB. @Igor - policy is that we don't nominate our own bugs to MAB. If a QA member feels like this should be a MAB, they will place it on the list
Still happens in 4.1.3.2 Here are some easy step to reproduce without any special files 1. Create a new Writer document 2. Create a new Drawing 3. In the drawing, draw a rectangle 4. select the rectangle and copy it (ctrl-c) 5. in the writer document, paste the drawing (ctrl-v) 6. in writer, right-click the rectangle and select "Caption" 7. Click ok in the caption dialog 8. Save as a Word .doc document 9. Reload the file using File->Reload
Restricted my LibreOffice hacking area
No confirmation that this is a regression - removing regression. If it's a regression please let us know what version of LibreOffice this worked in. Thanks
** 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
Confirming with: Version: 5.4.0.0.alpha0+ Build ID: 33f5bc54aaa7fe7aa9335726e30f9c349155e04d CPU Threads: 4; OS Version: Windows 6.2; UI Render: default; TinderBox: Win-x86@62-merge-TDF, Branch:MASTER, Time: 2016-12-01_23:21:05 Locale: nl-NL (nl_NL); Calc: CL
still repro in LO Writer 6.1.0.2
Dear user6, 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
Confirm that the problem still exists. Followed procedure in comment 25. The area color is lost (because the shape is lost), and the caption moves to the top of the frame (because the shape is lost). Further information (and better procedure) 1. Do not need to make a Drawing document as described in comment 25, can just draw a shape into a new document. (but I tried both versions with same result). 2. Followed the procedure, while watching the "Navigator" window. a. Creating (or copying) a shape gives an Shape1 under Drawing Objects b. Inserting a Caption creates a Frame1 under Textframes c. Save .doc and reload. d. The shapes are now lost (i.e., do not appear in Navigator), but the text frames remain. 3. If the document is saved as .docx, then the shape is lost, but now the Frame1 moves from "Text Frame" to stand under "Drawing Objects" in Navigator. 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
*** Bug 139169 has been marked as a duplicate of this bug. ***
*** Bug 121510 has been marked as a duplicate of this bug. ***
Already in OOo 3.3, so inherited. Same as comment 12 in recent master build: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: fc6806c4be8585ce0d35a6b581bf8b3dbf858500 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded
(In reply to sdc.blanco from comment #32) > 3. If the document is saved as .docx, then the shape is lost, but now the > Frame1 moves from "Text Frame" to stand under "Drawing Objects" in Navigator. It makes sense to not be able to keep the shape anchored inside the frame, as the frame is converted to a drawing object when saving as DOCX. But I don't reproduce what you see: the shape is kept, just anchored to a page's paragraph instead. The DOC filter should do the same. (Note that Office 365 (online) also loses the shape on importing the ODT.)
*** Bug 121508 has been marked as a duplicate of this bug. ***