Created attachment 142852 [details] PPTX containing the table which is not being shown in the converted pdf. When we are using LibreOffice to convert a pptx file to a pdf file, the resulting PDF is missing components. The command we are using to convert is: libreoffice5.3 --headless --convert-to pdf --outdir . filename.pptx The first slide in the PPTX has a table which is not showing up in the PDF file. We have attached the PPTX along with this. We tried opening the pptx using LibreOffice Impress but faced the same issue. The table refuses to appear in the converted PDF file.
On windows 7 x64 with Version: 6.0.5.1 (x64) Build ID: 0588a1cb9a40c4a6a029e1d442a2b9767d612751 CPU threads: 3; OS: Windows 6.1; UI render: default When importing, i'm not seeing *any* tables unless I grab a [field] text and drag downwards. Then suddenly a table becomes visible. Seems the borders are imported as 'Set No Borders'.
The original PPTX file was created in Microsoft Powerpoint. If you try opening it with Powerpoint, the table should show up. As per our project requirements, we need to convert all PPTX to PDF format. Looks like only the PPTX is causing this issue. "Seems the borders are imported as 'Set No Borders'." Might seem like a noob query but can you please tell me how to prevent the borders from being imported as 'Set No Borders'? (In reply to MM from comment #1) > On windows 7 x64 with Version: 6.0.5.1 (x64) > Build ID: 0588a1cb9a40c4a6a029e1d442a2b9767d612751 > CPU threads: 3; OS: Windows 6.1; UI render: default > > When importing, i'm not seeing *any* tables unless I grab a [field] text and > drag downwards. Then suddenly a table becomes visible. Seems the borders are > imported as 'Set No Borders'.
(In reply to MM from comment #1) > On windows 7 x64 with Version: 6.0.5.1 (x64) > Build ID: 0588a1cb9a40c4a6a029e1d442a2b9767d612751 > CPU threads: 3; OS: Windows 6.1; UI render: default > > When importing, i'm not seeing *any* tables unless I grab a [field] text and > drag downwards. Then suddenly a table becomes visible. Seems the borders are > imported as 'Set No Borders'. Can you provide an update on this?
Created attachment 143160 [details] PDF export from MSO 2013 Aakash: what you are asking of MM is precisely the bug. Someone has to fix the bug first. Win 8.1 32-bit MSO 2013 LibreOffice Version: 6.2.0.0.alpha0+ Build ID: e1a77d0affef507d597e7dceb5514073658332df CPU threads: 4; OS: Windows 6.3; UI render: default; TinderBox: Win-x86@42, Branch:master, Time: 2018-06-27_04:47:54 Locale: fi-FI (fi_FI); Calc: group threaded
(In reply to Buovjaga from comment #4) > Created attachment 143160 [details] > PDF export from MSO 2013 > > Aakash: what you are asking of MM is precisely the bug. Someone has to fix > the bug first. > > Win 8.1 32-bit > MSO 2013 > LibreOffice Version: 6.2.0.0.alpha0+ > Build ID: e1a77d0affef507d597e7dceb5514073658332df > CPU threads: 4; OS: Windows 6.3; UI render: default; > TinderBox: Win-x86@42, Branch:master, Time: 2018-06-27_04:47:54 > Locale: fi-FI (fi_FI); Calc: group threaded Can we assume this bug will be fixed in the next release of LibreOffice? If so, any idea when that might be?
(In reply to Aakash from comment #5) > Can we assume this bug will be fixed in the next release of LibreOffice? > If so, any idea when that might be? No we cannot as no developer has taken interest yet. If you want to hire someone: https://www.documentfoundation.org/gethelp/developers/
This table is made with Design in MSO. I guess it takes a whole table design support.
Dear Aakash, 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
Repro 6.4+
Created attachment 168904 [details] Screenshot of the original document side by side in PP and Impress This looks good since 6.4 after: https://cgit.freedesktop.org/libreoffice/core/commit/?id=2c3f7d4ee0a0b2bf6efc41670645bd361f1b76ef author Gülşah Köse <gulsah.kose@collabora.com> 2019-12-27 21:06:08 +0300 committer Andras Timar <andras.timar@collabora.com> 2020-01-07 14:49:50 +0100 tdf#107604 Handle predefined table styles.
*** This bug has been marked as a duplicate of bug 107604 ***