DOCX documents with footers in different sections cannot be viewed correctly. The footer of the first page is used for the whole document.
Created attachment 48379 [details] docx file to reproduce the problem
[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
The problem is reproducible with LibreOffice 3.5 Beta2.
Reproduced with LibreOffice 3.5.2. Some extra info: The footers in page 2, 3, 4 gets exported into a page style called Converted1. The problem is it never gets used. The first page has a continuous section break followed by a simple page break. As far as I know Writer don't really have a equivalent for the continuous section break. If a continuous section break appears in a document the next page might include a new header/footer which may or may not be linked with the previous header. If it would have been a "next page section break" then every thing would have worked as expected. I suppose this will be hard to fix without introducing an equivalent to continuous section break. I will attach a PDF created by Word 2010 so people without Word can see how it is supposed to look. PS. I did a short test converting this file to odt using Word 2010, let's say that it gave some interesting results.
Created attachment 60612 [details] pdf exported from Word 2010
It seems this is still an issue in LibreOffice 4.0.4.
Still here in LibreOffice 4.2.0.4 Build ID: 05dceb5d363845f2cf968344d7adab8dcfb2ba71 on Ubuntu 12.04.4 x86_64
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.