Created attachment 102217 [details] original ms word document Problem description: Steps to reproduce: 1. open document (ms word doc 2003/xp) with a wide table inside it 2. export to pdf 3. view pdf document Current behavior: has a right truncated table Expected behavior: adjust table to page (in the original file, the table is inside page limits) Operating System: All Version: 4.2.5.2 release
Created attachment 102218 [details] exported document
IMHO the issue is not about PDF export... it's about file open... I mean the .doc has a table which is shown off-center and out of bounds in LibO so if you pdf export it you will obtain the same error in the resulting pdf can you confirm it?
Yes, as you sed, the exported pdf looks like the opened document (I realize that after report the bug), so, the issue would be opening the document. If I change the left margin to center the table, the document look ok and the exported pdf too. Can't edit the document by hand, my process involve convert programmatically different documents into pdf through Java-UNO interface. Thank you for your time.
thanks for the report - prolly already a problem in earlier versions too ?
Created attachment 102320 [details] comparative screenshot MS Word Viewer vs. LibO thanks Cor for summary notes change. I post here's a screenshot and results of my tests with older releases. that .doc file is correctly rendered in AOO 4.1 and LibO 4.0.6.2 bug appeared in 4.1.0.4 and persists in 4.4.0.0.alpha0+ Build ID: 95272e7e5b7e38753ab07dbd6503b7cfa2974842 TinderBox: Win-x86@42, Branch:master, Time: 2014-06-26_23:01:43 hence a regression of the 4.1.x branch. needs bibisecting if not already reported before... we should dig Bugzilla in search for duplicates.
commit 8fe8bd6c3b5b1a539b7370f8c457fa69c061d2de Author: Miklos Vajna <vmiklos@suse.cz> AuthorDate: Mon May 13 11:24:58 2013 +0200 Related: fdo#61594 SwWW8ImplReader::StartApo: don't always start a frame yet another one of those pesky Word floating tables...
I did see in version 3.5 too. (In reply to comment #4) > thanks for the report - prolly already a problem in earlier versions too ?
(This is an automated message.) It seems that the commit that caused this regression was identified. (Or at least a commit is suspected as the offending one.) Thus setting keyword "bisected".
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.