| Summary: | FILEOPEN : Incorrect docX import (frames border) | ||
|---|---|---|---|
| Product: | LibreOffice | Reporter: | jmgigandet |
| Component: | Writer | Assignee: | Not Assigned <libreoffice-bugs> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | jmadero.dev, kelemeng, libreoffice, philipz85, vmiklos |
| Priority: | medium | Keywords: | filter:docx |
| Version: | 3.6.7.2 release | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | interoperability | ||
| Crash report or crash signature: | Regression By: | ||
| Bug Depends on: | |||
| Bug Blocks: | 104461 | ||
| Attachments: |
frames in .docx file are not properly rendered in Writer
LibO 4.3beta vs ms word 2007 LibO 4.3 beta vs 4.2.4 Bug still present on 5.4.3.2 |
||
Well opening up the file in word 2007 has it as a textbox and not a frame, though LibO shows it as a frame. Created attachment 99816 [details]
LibO 4.3beta vs ms word 2007
Tested the LibO rendering on the latest releases of 3.6 - 4.2 and 4.3 beta, with 4.3 being a regression of the so-called frame's location. Created attachment 99817 [details]
LibO 4.3 beta vs 4.2.4
my reported LibO shape to frame bug 79289. Removed bibisectrequest and regression as the regression seems to be different than the original report ** 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.3 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-06-08 Tested on 4.4.3.2 (Os X 10.9 and Win 7 Pro 64). Still the same issue. Migrating Whiteboard tags to Keywords: (bibisectRequest) [NinjaEdit] Again removing bibisectRequest - please don't add it again to this bug. I explained why I removed it. This bug pertains to the frame around the text box - the position of the box is a separate issue which should be reported separately. Please don't conflate issues as it just makes them hard to track and even harder to find a developer to tackle the issue. ** 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 Bug still present in 5.4.3.2 (see attachment) on MacOSX 11 and Windows 7 X64. Created attachment 138359 [details]
Bug still present on 5.4.3.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 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 Bug still present in 6.1.3.2 (Win 7 Pro X64) We have duplicates. Not frames, it's callouts, only in older DOCX 2007, fine with newer DOCX. This bug is earlier but not properly reported or triaged so I'll duplicate it. *** This bug has been marked as a duplicate of bug 79267 *** *** This bug has been marked as a duplicate of bug 41466 *** |
Created attachment 96890 [details] frames in .docx file are not properly rendered in Writer Import of MS DocX documents with frames is not correct. Writer adds a border where there's none in MS Word. Saving the same document as .doc in MS Word, and importing it in Writer is ok.