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
What exactly do you mean with your first point ("identify a section as a class ...")? The SectionProperties class represents a section. However, it certainly doesn't identify a section like the Paragraph class identifies a paragraph, because a SectionProperties instance does not contain the elements of a section. The w:sectPr element represented by a SectionProperties instance just marks the end of a section. Thus, "getting the paragraphs that compose a section" would add value.
Testing "if the section is a final section or not" is very straightforward. If it is contained in a w:pPr element (ParagraphProperties instance), it's not a final section. The final section is represented by a w:sectPr element the parent of which is the w:body element (Body instance).
Have you seen the functionality, SplitOnSections in DocumentBuilder.cs? You pass it an open WordprocessingDocument, and it returns N documents, each document containing one section from the source document.
From a philosophical point of view, we are going to be very careful before adding markup specific functionality into the SDK. Markup specific functionality might be better put in Open-Xml-PowerTools. (git repo coming soon). We're thinking of what to add to the SDK, but right now we have more than enough work getting some core issues addressed that apply to all of Open XML as a whole.
I think it would be great to add the support of sections, it should be possible to:
I'm ready to implement it if you think it's a good idea.
The text was updated successfully, but these errors were encountered: