Technical documents for protocols, computer languages, standards support, and data portability. The goal with Open Specifications is to help developers open new opportunities to interoperate with Windows, SQL, Office, and SharePoint.
Hi Ian Peterson,
Sorry this took so long but it's often like finding a needle in a haystack. I did find one thing that seemed to make PowerPoint happy in the end.
In slide1.xml and presentation.xml you had <custDataLst> blocks. They were both in what appeared to be valid locations per our schema definitions.
In presentation.xml on line 12, you had this:
<p:custDataLst/>
and in slide1.xml on line 194, you had this:
<p:custDataLst>
<p:custData r:id="rId1"/>
<p:custData r:id="rId2"/>
</p:custDataLst>
Although these looked to be in valid placement, when PowerPoint reported the error and then repaired, removing these was among the many changes it made. In isolation, I removed them and it made PowerPoint happy with everything else left alone from the original.
So while I don't have a full explanation as to why PowerPoint wanted them removed, I suspect that it considered them conflicting with the non-visual shape properties occurrence of custDataLst in slidelayout12.xml.
I hope this helps,
Best regards,
Tom Jebo
Microsoft Open Specifications Support