You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I'm using OpenXML SDK to disable font embedding and remove all FontParts in a presentation. Saving the document isn't resulting in [Content_Types].xml getting updated even though no more fntdata parts exist in the file.
@JessehMSFT after a little investigation, it seems that we don't actually have cleanup code to remove content type entries when removing parts. The SaveAs (or Clone in the current version - 3.0) appear to remove the content type entry but it's only because the content type doesn't exist in the newly created package before adding the remaining parts from the depleted original package. This is a design change request in the packaging or parts code to clean up content types entries after deleting the last part that uses a particular content type entry. I'm marking this as feature request enhancement and will investigate possible use of our features infrastructure to do the cleanup.
Describe the bug
I'm using OpenXML SDK to disable font embedding and remove all FontParts in a presentation. Saving the document isn't resulting in
[Content_Types].xml
getting updated even though no morefntdata
parts exist in the file.To Reproduce
Steps to reproduce the behavior:
Observed behavior
See EmbeddedFont - Copy.pptx for result.
When you inspect [Content_Types].xml, it still contains this entry:
<Default Extension="fntdata" ContentType="application/x-fontdata" />
Expected behavior
All
fntdata
parts have been removed. This entry is not nececssary.If I switch to a SaveAs to a new file instead of a Save, the
fntdata
entry is removed from the resulting file.If I open the file inside PowerPoint and let the app save, it also removes the unnecessary entry.
Desktop (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: