Bug 106666 - Powerpoint 97 diagram OLE inserted into Writer. OLE inserted diagram text labels default to line spacing=1.0 instead of using originally specified per-label line spacing from powerpoint document.
Summary: Powerpoint 97 diagram OLE inserted into Writer. OLE inserted diagram text lab...
Status: RESOLVED DUPLICATE of bug 105046
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.2.5.2 release
Hardware: x86 (IA32) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisected, bisected, regression
Depends on:
Blocks:
 
Reported: 2017-03-20 17:34 UTC by tim
Modified: 2017-03-20 18:10 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
.ODT file containing OLE inserted diagram to show bug. (30.00 KB, application/vnd.oasis.opendocument.text)
2017-03-20 17:36 UTC, tim
Details
PPT97 file containing the diagram that is OLE inserted (76.00 KB, application/x-ole-storage)
2017-03-20 17:38 UTC, tim
Details

Note You need to log in before you can comment on or make changes to this bug.
Description tim 2017-03-20 17:34:15 UTC
Description:
However, I noticed that OLE objects inserted from Powerpoint 97 are rendered inaccurately, specifically, text labels in the original PPT97 diagram often have a fractional line spacing (usually somewhere between 0.4 and 1.2) but the PPT97 diagram once OLE inserted, while faithful in all other respects, renders the text labels with a line spacing of 1.0 regardless. Naturally, the OLE inserted PPT97 diagrams tend to look somewhat ugly.

I tried rolling back from 5.2.6 (5.3.0 will install but won't start) through all the latest issues of the minor point releases (5.2.6, 5.1.4, 5.0.3, 4.4.5, 4.3.5, 4.2.5) but to no avail, it seems that something in LibO's OLE capability was changed after 4.1.6. Did I miss something (couldn't find anything in the 4.2 release notes to say that OLE insert mechanism had been changed) or is there some option I need to set so that OLE insert works correctly?

Late breaking news: 4.3.5.2 seems to work OK on my simple ole_insert_libo_gt4.1_fail.test.odt file, the same as 4.1.6.2. But 5.2.6.2 still fails.

Steps to Reproduce:
1. Open ole_insert_libo_gt4.1_fail.test.odt in 4.1.6.2. Notice how in Figure 1 the divide symbol sits in the middle of the ENH circle on the right hand side.
2. Open ole_insert_libo_gt4.1_fail.test.odt in 5.2.6.2. Notice how in Figure 1 the divide symbol slides out of the bottom of the ENH circle on the right hand side. And how the ale red and cyan annotations drop into the blocks that they used to sit so nicely above.
3. Re-install 4.1.6.2 :)

Actual Results:  
Covered by Steps to Reproduce above. Most (all?) text labels in OLE inserted diagram have dropped down.

Expected Results:
Preserved the text label line spacing as per 4.1.6.2.


Reproducible: Always

User Profile Reset: No. It is reproducible in both a VM and a bare metal machine with different user profiles, so I don't think this is an issue.

Additional Info:
Everything else I have come across in LibO is frankly, utterly brilliant.
I am creating moderately sized documents (~30pp) with 30 or so OLE-inserted linked diagrams (from PPT97) and OLE-inserted linked graphics (PNG files).
I expect this will soon become 200pp documents with 200 linked diagrams and graphics. If this becomes unwieldy in LibO, it won't be a problem to re-structure my documents and drop back down to ~60pp per document.



User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:42.0) Gecko/20100101 Firefox/42.0
Comment 1 tim 2017-03-20 17:36:57 UTC
Created attachment 132034 [details]
.ODT file containing OLE inserted diagram to show bug.
Comment 2 tim 2017-03-20 17:38:31 UTC
Created attachment 132035 [details]
PPT97 file containing the diagram that is OLE inserted
Comment 3 Xisco Faulí 2017-03-20 18:10:38 UTC
Regression introduced by e42c05c1f96832572e525d85d89590f56f5a29dd which is the same as in bug 105046. Closing as RESOLVED DUPLICATED.
Thanks for reporting.

*** This bug has been marked as a duplicate of bug 105046 ***