The attached files is a simple word document I use for my phone speed dial label. Both filess import result in wrong formatting behaviour. The import result from .docx format is quite odd. Both files were created with microsoft word 2010.
Created attachment 42631 [details] doc file
Created attachment 42632 [details] docx file
Reproduced on Mac OS X 10.6.6; LibreOffice 3.3 final; .docx looks really bad.
Do you have an image of what it should look like. docx is clearly wrong 3.3.2/Suse 11.0, don't know about doc.
(In reply to comment #4) > Do you have an image of what it should look like. docx is clearly wrong > 3.3.2/Suse 11.0, don't know about doc. Steve, here it is a screenshot of my ms word 2010 and a PDF printing of the file. I hope they helps.
Created attachment 45198 [details] MS Word 2010 layout view in reply to comment #4
Created attachment 45199 [details] pdf printing of the file in reply to comment #4
[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
Dear bug submitter! Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs. To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem. Yours! Florian
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.