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".
This issue is still present in Version: 5.0.1.2 Build ID: 81898c9f5c0d43f3473ba111d7b351050be20261 Locale: es-ES (es_ES) on Windows 7 (64-bit)
Migrating Whiteboard tags to Keywords: (bibisected) [NinjaEdit]
adding filt:doc keyword.
Looks like a duplicate. Left margin here is table spacing in Bug 80635. They can all be changed manually and it's correct then. *** This bug has been marked as a duplicate of bug 80635 ***
Created attachment 146508 [details] bugdoc saved as .docx also imported incorrectly Not a dupe of Bug 80635. Proof, when its bugdoc, , is saved as .docx by Word, writer *correctly* handles the margins.
Created attachment 146508 [details] bugdoc saved as .docx also imported incorrectly Not a dupe of Bug 80635. Proof, when its bugdoc,attachment 146506 [details] , is saved as .docx by Word, writer *correctly* handles the margins.
*** Bug 94950 has been marked as a duplicate of this bug. ***
Dear Gabriel, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Hi all, the issue still exists. Example document (act2.docx) opened in LibreOffice 6.3.3.2 (Ubuntu) show it truncated on right margin like in snapshot attached to this bug report. Best regards.
NOTE: there likely is something illegal about this document. I open it in Word 2003 and it looks good. Looking in Table Properties - Positioning, it reports a Horizontal position of LEFT of the MARGIN. When I press OK, it changes to look the way that LO imported it. So just viewing and approving the settings in Word changes the layout. Thus, I'm not sure this import bug is worth fixing - especially considering that it is complicated by emulating as an inline, non-wrapped table.
Dear Gabriel, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
the bug document looks the same as in MS Word in Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 5cd9de202765e243e41416802f3e4486b8a96f16 CPU threads: 16; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: ru-RU (ru_RU); UI: ru-RU Calc: CL threaded Closed as WFM (I think we should say "thanks" to Miklos)