Seriously, before you make derisive comments on another software product, you should first make sure that you can't be blamed for exactly the same thing.
OOo, all versions since I_don't_know, have the same annoying bug in the export filter to Word (and import from Word as well, I suppose). It's in converting the page style if the Next page property of the page style definition is another page style, like in the First page, where the next page is set to Default. Every single time you convert a file with such page styles in it, the different header/footer definitions will disappear and you get a file with the same headers/footers for the entire document. And not because Word doesn't have a way to get the same effect - it's the Continuous section break that you can insert anywhere in a page but it will take effect at the start of the next page. It has been around since at the latest Word 97, but I think it was there even earlier. Anyone who converts a file from OOo to Word van easily spot this bug, and it's often reported at the community forum. But the developers probably think that this bug is trivial.

The attachment is a Word file (made with Word 2002). The second page gets a header with the text "This doesn’t show on page 1." It could read as well: "This doesn’t show in any current version of OOo or LO."

floris v aka Peter

Op 16-1-2012 21:23, Rob Weir schreef:
On Fri, Jan 13, 2012 at 4:14 PM, Simon Phipps <simon@webmink.com> wrote:
Hi Dan,

Your easy conclusion that LibreOffice is at fault is wrong. Please see

You'll see that this is indeed a reflection of a bug in MS Word that is avoided in OOo because of a bug in OOo 3.3 ("Files from OpenOffice.org Writer fail the validation at the OpenOffice validation site allegedly because the manifest:manifest (root) tag in the META-INF/manifest.xml file lacks a version attribute.")

Given this is a bug in MS Word, it is best avoided both in LibreOffice and in a future AOO release by using a format that MS Word handles correctly >such as .DOC or ODF 1.1, unless Microsoft issues a patch.
If a program does not meet user expectations then it is a bug.  If you
want to be compatible with Microsoft Office then you need to play by
their rules.  The existence of standards like ODF and OOXML does not
change the basic fact that interoperability is hard work.  It requires
testing.  It does not happen overnight. It is not merely the result of
an incantation that begins with the sacred syllables "ISO".

In any case Seeing responses like this from LibreOffice makes be very
optimistic about the future of Apache OpenOffice.  Whatever the cause,
the fact that LibreOffice ships with this problem shows either a
woefully inadequate QA program, or total indifference to real world
requirements.  Even testing a single LibreOffice document in Office
2007 would have shown this bug.  Is that too much to expect?

And if you prefer written specifications to testing, there is always
Microsoft's Implementation Notes on Office 2007, where they spell out
in great details what  they do and do not support in ODF 1,1:


LibreOffice could have prevented this bug by checking there as well.