-
Notifications
You must be signed in to change notification settings - Fork 561
Office2021 #1030
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Office2021 #1030
Conversation
@@ -245,6 +245,9 @@ private static string NormalizeNamespace(in OpenXmlNamespace ns) | |||
{ "http://schemas.microsoft.com/office/spreadsheetml/2014/11/main", "x16", FileFormatVersions.Office2016 }, | |||
{ "http://schemas.microsoft.com/office/spreadsheetml/2015/02/main", "x16r2", FileFormatVersions.Office2016 }, | |||
{ "http://schemas.microsoft.com/office/word/2015/wordml/symex", "w16se", FileFormatVersions.Office2016 }, | |||
// Named 2013/main/command with "oac" ns prefix to avoid conflict with officedocument/2006/characteristics | |||
{ "http://schemas.microsoft.com/office/drawing/2013/main/command", "oac", FileFormatVersions.Office2016 }, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Where'd these come from?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a new ns prefix and namespace added retro actively to 2016, 2019 and in 2021 to include moniker types that were not included a few years ago.
@@ -454,7 +454,7 @@ public OfficeArtExtensionList(string outerXml) : base(outerXml) | |||
internal override void ConfigureMetadata(ElementMetadata.Builder builder) | |||
{ | |||
base.ConfigureMetadata(builder); | |||
builder.SetSchema(112, "extLst"); | |||
builder.SetSchema(114, "extLst"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Have you done the back and forth for this? We should really switch it out to use the proper schemas
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
these were offset by retroactive introduction of the moniker types for drawing. I don't think they'll impact the public API surface or at least with any breaking change.
Office 2021 updated types:
Label Information part support
PowerPoint Comments support
Excel Named Sheet Views support
Excel Rich Data enhancements
Word Comments Extensibilty part types
Document Tasks support in Word
Drawing Sketchy Shapes support