Bug 42482 - Importing PowerPoint with tables results in poor display
Summary: Importing PowerPoint with tables results in poor display
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
3.3.4 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-01 10:52 UTC by Greg
Modified: 2013-04-22 05:46 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Original PPT (51.50 KB, application/vnd.ms-powerpoint)
2011-11-01 10:52 UTC, Greg
Details
PPT orig screen shot (7.75 KB, image/png)
2011-11-01 10:53 UTC, Greg
Details
Result in LibreOffice (14.48 KB, image/png)
2011-11-01 10:53 UTC, Greg
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Greg 2011-11-01 10:52:28 UTC
Created attachment 53008 [details]
Original PPT

If a PPT file has an embedded table, the table borders do not seem to import properly (or be visible). See attached.
Comment 1 Greg 2011-11-01 10:53:07 UTC
Created attachment 53010 [details]
PPT orig screen shot
Comment 2 Greg 2011-11-01 10:53:32 UTC
Created attachment 53011 [details]
Result in LibreOffice
Comment 3 Theo 2012-02-13 01:34:42 UTC
I can confirm this bug with LO 3.5RC3 both on Mac an Windows Vista. Borders of tables in ppt & pptx do not display in LO3.5. They do in OOo3.3 and AO3.4 development snapshot r1240836.

Borders become visible if you click on the table to edit it, but disappear again after leaving edit mode.
Comment 4 sasha.libreoffice 2012-04-19 01:41:51 UTC
reproduced with attachment ppt in 3.3.4 and 3.5.2 on Fedora 64 bit and in 3.5.2 on Windows 7 32 bit
changing version to 3.3.4 as most early reproducible
Comment 5 Florian Reisinger 2013-04-21 06:25:09 UTC
Seems to work with Version 4.0.1.2 (Build ID: 84102822e3d61eb989ddd325abf1ac077904985)
Comment 6 sasha.libreoffice 2013-04-22 05:46:06 UTC
@ Florian Reisinger
Thanks for additional testing
Sorry, bug in latest release (version 4.0.2.2) it is still reproducible
IMHO we should not close bug until fix appears in release for users can verify result