Here in screenshots is an interesting distinction between original word .docx 2016 flow diagram and the two libreoffice versions of this, one saved as .docx the other .odt (seen on upper taskbar), I thought it was interesting the two outcomes and to inform you guys, any help with fixing this issue?
Created attachment 131649 [details]
Created attachment 131650 [details]
Created attachment 131651 [details]
*** Bug 106338 has been marked as a duplicate of this bug. ***
Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug.
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided.
(Please note that the attachment will be public, remove any sensitive information before attaching it.
See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.)
Could you please perform the test the opposite direction.
That is Save-as from MS Word to an ODF Open Document Text.odt document. Then open that into LibreOffice Writer. Better fidelity? Save and reopen either Word or Writer.
Created attachment 134969 [details]
Created attachment 134970 [details]
Thank you for your help, I have attached the vector diagram with picture and text, created in the latest MS Word and saved in both ODT and DOCX format, there are still issues opening these in the latest 5.4 LO release. I hope this helps.
Created attachment 134972 [details]
FAHR CASE docx.docx: tested with LO6 and looks good compared to your printscreen. Only issue I see here are black boxes - I doesn't see text in LO, and misplaced textboxes. When I open your file in word2010, the result is worse then in LO.
Created attachment 134973 [details]
Thank you for your speedy reply.
Please could you see the 3rd attachement as the reference image here. The inclusion of Word 2010 is intersting, it makes me think LO is more interoperable in this field with that gerenation of MSoffice products, which is interesting in it's own right I suppose, but not entirely relevant to this particular problem.
The vector image was created with Word 2016, and that is attached as the reference image above under "windows" (3rd attchment).
With regards LO6, I believe you're opening the docx file and this is no improvement over the prior 5.3 release's handling of the docx saved file, attached as a screenshot above (2nd attachement) "LO DOCX".
Issues, apart from the text you mentioned, are misplaced arrows. Again I ask you refer to the MS 2016 and not 2010 as the reference.
Of note, there has been improvement with the rendering of the ODT saved format of the same, from 5.4 (not attached, as you can generate yourself) in comparison to 5.3 (attched, 1st attachement), however it is still poor.
I hope this information is helpful
** 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!
Created attachment 166835 [details]
docx file compared MSO LO
This bug is wrong on all accounts. It started as Filesave but it makes no sense because Fileopen is wrong. Also, this is document-based bug but should be issue-based.
For attachment 134969 [details] MSO docx I add screenshot with 3 fileopen issues:
1. text box shape wrong position, regression from 6.0
2. images wrong position, regression from 6.1
3. 1-page opens as 3-page, same as 2.
Let this bug be about fileopen of 1 page with images position, per following bibisect in 6.1 Linux. Miklos, please take a look.
I opened bug 137850 for text box shape regression.
Date: Wed Feb 14 21:17:20 2018 +0100
prev source b13678b1e1d6f4cac548ae7e088b6030c31cf081
author Miklos Vajna <firstname.lastname@example.org> 2018-02-14 15:31:35 +0100
committer Miklos Vajna <email@example.com> 2018-02-14 20:21:57 +0100
commit 8b73bafbc18acb4dd8911d2f2de8158d98eb6144 (patch)
parent b13678b1e1d6f4cac548ae7e088b6030c31cf081 (diff)
tdf#115719 DOCX import: increase paragraph spacing for anchored objects
Once all resolved, new bug should be open for single issue in filesave, tested both for ODT and DOC and DOCX, only if not found existing.
No need to attach resulting documents, source is enough. Instead, screenshot comparison is advised.
Comment 10 is extremely important.
Any attempt to fix this bug must not break documents using an older compatibilityMode than 15. See attachment 166871 [details] for a compatibilityMode = 11 version of this document (from related bug 137850).
Adding NISZ team to the CC.
I know you guys have been doing a lot of work related to shapes/positioning. If you aren't aware that compatibilityMode can significantly affect that, then this document is a great proof example that it certainly does. So I hope you always keep that in mind as you work on more position stuff.
compare comment 3's Word2016 screenshot with comment 11's Word2010 screenshot.
*** This bug has been marked as a duplicate of bug 138782 ***