I am using latest LO (4.1.2.3) on Win7. It is a relatively simple document, it opens fine in LO but when opened in Word (2010) the two pages are shown on top of one another
You should use DOC instead of DOCX… docx is not well supported by LO.
@Duncan, thanks for asking this in a separate question. I will mark your question up so you can post comments and hopefully edit your post to include a screenshot or similar. @Ljiljan, it may be the case that DOCX support is lacking in an area that affects this particular document, but there are many open bugs relating to DOC also. Moving forward, DOCX has more of a future than DOC, so in general I disagree with your statement.
Ljiljan, Thanks for your comment, I have also tried saving as .doc but with a similar result. The document does use tables and I see from other posts that tables cause issues for others also
@oweng I am using LO 4.0.5.2 for 9 months now and when saving in DOCX or PPTX, result is terrible. PPTX cannot even save simple text (in bullets)… both format, DOCX and PPTX are not capable to support drawings too… tables are ok as long as it is just simple table. However, DOC and PPT are perfect and not so many problems appear according to my usage of Impress and Writer…
@Ljiljan, thanks for clarifying. Your initial statement seemed very broad. I have marked your second comment up.
If you have tables in the document and the accurate rendering of this content is the main problem, then you have plenty of company. This is a list of currently open bugs for Writer+doc+table. Some relate to “table of contents” and most relate to how Writer renders a DOCX, rather than how MS Word renders a Writer generated DOCX. Even so it is a lengthy list.
This aspect of OOXML (tables) does not appear to have been addressed in any detail. Release v3.6 saw some work done on Table AutoFormats recording table-level properties (which I don’t think affected OOXML, but I could be wrong about that), and release v4.0 saw OOXML floating tables (with wrapping content) addressed. That is about it though, according to the currently available release notes. Release v4.2 (Feb 2014) is expected to see several OOXML table handling improvements, according to this developer blog post.
If you can provide greater detail about exactly what is the expected and observed behaviour, that would help narrow down the problem and clarify your question.