Summary: | Footer from word file wrong | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | Bob Miller <rmiller> |
Component: | Writer | Assignee: | Not Assigned <libreoffice-bugs> |
Status: | NEW --- | QA Contact: | Jorendc <jorendc> |
Severity: | normal | ||
Priority: | medium | CC: | jeffdchang, rmiller, sasha.libreoffice, yfjiang |
Version: | 3.3.2 release | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | Confirmed:4.3.0.0.alpha0+:OSX10.9 Confirmed:3.6.0:Linux Confirmed:4.0.0:Linux Confirmed:4.0.0.3:Windows7 | ||
i915 platform: | i915 features: | ||
Attachments: |
Example word doc
pdf produced in MSWord 2003 |
Reproduced on LibreOffice 3.4 340m1(Build:103) for OpenSuse Linux. When you open the document on Word, it looks like pages 1, 2, and 4's footers are linked to each other, while page 3's is not. When you click the "Link to Previous" button under Design while you have selected the footer on page 3, the date will change to "09-01-2011", which probably explains why this occurs in LO Writer. Perhaps it is making the link by default, causing this buggy date. I am just curious as to why the date changes to a different one than the other three pages. So even though Word and LO bug up, it looks like the problem is caused by a faulty connection between footers across the pages. [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 Created attachment 56232 [details]
pdf produced in MSWord 2003
reproduced in LibO 3.6.0 master on Fedora 64 bit
Can't reproduce anymore using LibreOffice 4.0.0 with Linux Mint 14 x64. When I open this file I see a correct footer (as far I can see using the verification pdf). In edit-mode there are some kind of 'blue lines', but in 'print preview' or export as pdf they are not displayed. Therefore I mark this bug as RESOLVED WORKSFORME (not FIXED, because we don't know which commit fixed this bug). If this bug reappears or is still present in 4.0.0 or future releases, please feel free to REOPEN. Thanks for your time retesting. I hope this works also for you? Kind regards, Joren I am still seeing this in 4.0.0.3 on Windows 7. If you look at the footers on pages 1,2, and 4 they all read "07-01-2011" and on page 3 it reads "09-01-2009". All 4 are supposed to read "07-01-2011". Interesting bug. Can confirm that with LO Version: 4.3.0.0.alpha0+ Build ID: 5e01904de993caa3d497a8f6c82a846336e70eef TinderBox: MacOSX-x86@49-TDF, Branch:master, Time: 2013-12-06_02:05:01 I still see 2009 in the footer on page 3 while in MS Word 2011 on OS X I see 2011. Any dev willing to look into this? |
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.
Created attachment 49152 [details] Example word doc The attached word file has different even/odd footers as well as different first page footers. They all come from a template that is used. Somehow LibreOffice is choosing to use a different footer on odd numbered non first pages than word chooses. If you look at page 3 of the attached document in word the footer will have a date at the bottom right of "07 - 01 - 2011", if you view it in LibreOffice it will have a date of "09 - 01 - 2009". This date is from some much older version of the file/the template maybe? Either way the two should not choose different footers, this is incorrect. The wrong footer is not visible anywhere in word, and the problem still shows if you convert the file to docx (using word 2010). Converting to docx also really messes up the tables in LibreOffice, though obviously I need to file a different bug for that.