Bug 148268 - Fileopen PPTX: freehand drawing with the pen tool in ms office doesn't show up in impress
Summary: Fileopen PPTX: freehand drawing with the pen tool in ms office doesn't show u...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
6.4.0.3 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisected, bisected, filter:pptx
: 143218 156025 (view as bug list)
Depends on:
Blocks: PPTX
  Show dependency treegraph
 
Reported: 2022-03-30 13:24 UTC by almos
Modified: 2023-06-28 07:44 UTC (History)
7 users (show)

See Also:
Crash report or crash signature:


Attachments
presentation with drawing in it (60.74 KB, application/vnd.openxmlformats-officedocument.presentationml.presentation)
2022-03-30 13:25 UTC, almos
Details
presentation compared in MSO and LO (50.83 KB, image/webp)
2022-05-20 07:28 UTC, Timur
Details
presentation PPT (255.50 KB, application/vnd.ms-powerpoint)
2022-05-20 08:25 UTC, Timur
Details

Note You need to log in before you can comment on or make changes to this bug.
Description almos 2022-03-30 13:24:20 UTC
Description:
This drawing tool seems to be really popular now, LibreOffice should be able to handle it.

I think these are the InkML files in the ink directory of the pptx archive.

Steps to Reproduce:
1. Draw something in MS Office
2. Open the pptx in Impress
3. No profit

Actual Results:
It doesn't show up.

Expected Results:
It should show up.


Reproducible: Always


User Profile Reset: No



Additional Info:
No other information.
Comment 1 almos 2022-03-30 13:25:23 UTC
Created attachment 179210 [details]
presentation with drawing in it
Comment 2 V Stuart Foote 2022-03-30 13:48:57 UTC

*** This bug has been marked as a duplicate of bug 148152 ***
Comment 3 Timur 2022-05-20 07:28:26 UTC
Created attachment 180241 [details]
presentation compared in MSO and LO

This is not a duplicate. bug 148152 is for using digital pen, not for reading of files. I set this one to New. It's a kind of regression, something was there in 6.2, empty in 7.0 and 7.4+.
Comment 4 Timur 2022-05-20 08:25:38 UTC
Created attachment 180243 [details]
presentation PPT

Here is MSO saved PPT which opens in LO, somewhat lighter, maybe bug 138147.
This bug remains PPTX only.
Comment 5 Timur 2022-05-20 09:38:58 UTC
commit de307933b91f348e81f3594c0bfc36df9a2362f5
Date:   Thu Nov 14 08:41:38 2019 +0100
    source 956153105bbf900f3b20aea98338148cf545fa0e
    pre 65767523ba5ad8e974a3144b33ad0e9d627a53f7
author	Miklos Vajna <vmiklos@collabora.com>	2019-11-13
tdf#117658 PPTX import: fix duplicated math object handling

Not sure that this is a regression, but Mikloš please see.
Comment 6 Miklos Vajna 2022-05-20 10:16:01 UTC
This is essentially a missing feature. PowerPoint added a bunch of features PowerPoint 2010 into its p14 XML namespace in PPTX: we either read all of them (and discard the fallback) or we always read the fallback (and discard the real markup). To make this worse, we used to just read both branches, leading to duplicated results where we had import code to interpret both the real markup and the fallback.

The original use-case for this was to read only the primary arm of a a14 condition, but this also had the effect of reading only the primary arm of p14 conditions, since it's marked as supported.

p14 was declared as supported much earlier, in commit 1d75c2e5ed1df1b9e3ae733d9c8a2106701b67ae (oox: check for namespace in MCE is flawed, use a namespace list, 2015-11-08), so you could argue this is a regression from that commit. But really, what we should do is to just add support for ink annotations in Impress, to parse those InkML streams in ppt/ink/ink1.xml, which is currently a missing feature.

Thanks for the bisect, though!
Comment 7 almos 2022-05-25 19:47:43 UTC
Thanks for looking into this issue.
Comment 8 Justin L 2022-09-08 15:47:42 UTC
*** Bug 143218 has been marked as a duplicate of this bug. ***
Comment 9 Gabor Kelemen (allotropia) 2023-06-28 07:44:19 UTC
*** Bug 156025 has been marked as a duplicate of this bug. ***