Skip to content

/ open-xml-docs

Permalink
Browse files
CI Update
  • Loading branch information
@VSC-Service-Account
VSC-Service-Account committed Aug 2, 2018
1 parent 28697b4 commit cd2698eda3067489d13e8d393218875e5806aa14
Unified Split
Showing with 928 additions and 541 deletions.
  1. +3 −2 docs/docfx.json
  2. +5 −5 docs/how-to-add-a-comment-to-a-slide-in-a-presentation.md
  3. +6 −6 docs/how-to-apply-a-theme-to-a-presentation.md
  4. +2 −2 docs/how-to-change-the-fill-color-of-a-shape-in-a-presentation.md
  5. +5 −5 docs/how-to-delete-a-slide-from-a-presentation.md
  6. +6 −6 docs/how-to-delete-all-the-comments-by-an-author-from-all-the-slides-in-a-presentatio.md
  7. +9 −9 docs/how-to-get-all-the-external-hyperlinks-in-a-presentation.md
  8. +6 −6 docs/how-to-get-all-the-text-in-a-slide-in-a-presentation.md
  9. +5 −5 docs/how-to-get-the-titles-of-all-the-slides-in-a-presentation.md
  10. +5 −5 docs/how-to-get-worksheet-information-from-a-package.md
  11. +4 −4 docs/how-to-insert-a-chart-into-a-spreadsheet.md
  12. +5 −5 docs/how-to-insert-a-new-slide-into-a-presentation.md
  13. +2 −2 docs/how-to-insert-a-picture-into-a-word-processing-document.md
  14. +6 −6 docs/how-to-move-a-paragraph-from-one-presentation-to-another.md
  15. +5 −5 docs/how-to-move-a-slide-to-a-new-position-in-a-presentation.md
  16. +5 −5 docs/how-to-open-a-presentation-document-for-read-only-access.md
  17. +1 −1 docs/how-to-remove-a-document-part-from-a-package.md
  18. +5 −5 docs/how-to-remove-hidden-text-from-a-word-processing-document.md
  19. +1 −1 docs/how-to-replace-the-header-in-a-word-processing-document.md
  20. +2 −2 docs/how-to-retrieve-a-list-of-the-hidden-worksheets-in-a-spreadsheet.md
  21. +6 −6 docs/how-to-retrieve-comments-from-a-word-processing-document.md
  22. +375 −0 docs/open-xml-docs/manifest.json
  23. BIN docs/open-xml-docs/media/Octocat.png
  24. BIN docs/open-xml-docs/media/OpenXMLCon_HowToConvertDOCMtoDOCX_Fig1.gif
  25. BIN docs/open-xml-docs/media/OpenXmlCon_CreateCharacterStyle_Fig1.gif
  26. BIN docs/open-xml-docs/media/OpenXmlCon_HowToReplaceStyles_Fig1.gif
  27. BIN docs/open-xml-docs/media/OpenXmlCon_HowToSetCustomPropertyFig2.gif
  28. BIN docs/open-xml-docs/media/OpenXmlCon_HowToSetCustomProperty_Fig1.gif
  29. BIN docs/open-xml-docs/media/a-theme01.gif
  30. BIN docs/open-xml-docs/media/odc_oxml_ppt_documentstructure_fig01.jpg
  31. BIN docs/open-xml-docs/media/odc_oxml_ppt_documentstructure_fig02.jpg
  32. BIN docs/open-xml-docs/media/odc_oxml_wd_documentstructure_fig01.jpg
  33. BIN docs/open-xml-docs/media/odc_oxml_xl_documentstructure_fig01.gif
  34. BIN docs/open-xml-docs/media/odc_oxml_xl_documentstructure_fig02.gif
  35. BIN docs/open-xml-docs/media/w-comment01.gif
  36. BIN docs/open-xml-docs/media/w-delparagraphs01.gif
  37. BIN docs/open-xml-docs/media/w-delparagraphs02.gif
  38. BIN docs/open-xml-docs/media/w-headerref01.gif
  39. +3 −0 docs/open-xml-docs/xrefmap.yml
  40. +116 −115 docs/structure-of-a-presentationml-document.md
  41. +13 −13 docs/structure-of-a-spreadsheetml-document.md
  42. +57 −55 docs/working-with-animation.md
  43. +15 −14 docs/working-with-comments.md
  44. +30 −30 docs/working-with-conditional-formatting.md
  45. +7 −9 docs/working-with-handout-master-slides.md
  46. +16 −14 docs/working-with-notes-slides.md
  47. +6 −6 docs/working-with-paragraphs.md
  48. +5 −5 docs/working-with-pivottables.md
  49. +38 −38 docs/working-with-presentation-slides.md
  50. +44 −44 docs/working-with-presentations.md
  51. +6 −6 docs/working-with-runs.md
  52. +13 −13 docs/working-with-sheets.md
  53. +19 −17 docs/working-with-slide-layouts.md
  54. +31 −30 docs/working-with-slide-masters.md
  55. +9 −9 docs/working-with-tables.md
  56. +23 −23 docs/working-with-the-calculation-chain.md
  57. +4 −4 docs/working-with-the-shared-string-table.md
  58. +4 −3 docs/working-with-wordprocessingml-tables.md
5 docs/docfx.json
View file
@@ -44,6 +44,7 @@
},
"fileMetadata": {},
"template": [],
"dest": "open-xml-docs"
"dest": "open-xml-docs",
"markdownEngineName": "markdig"
}
}
}
10 docs/how-to-add-a-comment-to-a-slide-in-a-presentation.md
View file
@@ -87,26 +87,26 @@ introduces the overall form of a **PresentationML** package.
> the entire slide masters used in the presentation; the notes master
> contains information about the formatting of notes pages; and the
> handout master describes how a handout looks.
>
> A *handout* is a printed set of slides that can be provided to an
> *audience*.
>
> As well as text and graphics, each slide can contain *comments* and
> *notes*, can have a *layout*, and can be part of one or more *custom
> presentations*. A comment is an annotation intended for the person
> maintaining the presentation slide deck. A note is a reminder or piece
> of text intended for the presenter or the audience.
>
> Other features that a **PresentationML**
> document can include the following: *animation*, *audio*, *video*, and
> *transitions* between slides.
>
> A **PresentationML** document is not stored
> as one large body in a single part. Instead, the elements that
> implement certain groupings of functionality are stored in separate
> parts. For example, all comments in a document are stored in one
> comment part while each slide has its own part.
>
> © ISO/IEC29500: 2008.
The following XML code example represents a presentation that contains
12 docs/how-to-apply-a-theme-to-a-presentation.md
View file
@@ -98,26 +98,26 @@ specification introduces the overall form of a **PresentationML** package.
> refers to the entire slide masters used in the presentation; the notes
> master contains information about the formatting of notes pages; and
> the handout master describes how a handout looks.
>
> A handout is a printed set of slides that can be handed out to an
> audience for future reference.
>
> As well as text and graphics, each slide can contain comments and
> notes, can have a layout, and can be part of one or more custom
> presentations. (A comment is an annotation intended for the person
> maintaining the presentation slide deck. A note is a reminder or piece
> of text intended for the presenter or the audience.)
>
> Other features that a **PresentationML**
> document can contain include the following: animation, audio, video,
> and transitions between slides.
>
> A **PresentationML** document is not stored
> as one large body in a single part. Instead, the elements that
> implement certain groupings of functionality are stored in separate
> parts. For example, all comments in a document are stored in one
> comment part while each slide has its own part.
>
> © ISO/IEC29500: 2008.
The following XML code segment represents a presentation that contains
@@ -181,7 +181,7 @@ be useful when working with this element.
> In this example, we see how a theme can affect font, colors,
> backgrounds, fills, and effects for different objects in a
> presentation. *end example*]
>
> © ISO/IEC29500: 2008.
The following table lists the possible child types of the Theme class.
4 docs/how-to-change-the-fill-color-of-a-shape-in-a-presentation.md
View file
@@ -86,7 +86,7 @@ introduces the overall form of a **PresentationML** package.
> represents the majority of content within a slide. Text and effects
> are attached to shapes that are contained within the <span
> class="keyword">spTree** element.
>
> [*Example*: Consider the following <span
> class="keyword">PresentationML** slide
@@ -111,7 +111,7 @@ introduces the overall form of a **PresentationML** package.
> In the above example the shape tree specifies all the shape properties
> for this slide. *end example*]
>
> © ISO/IEC29500: 2008.
The following table lists the child elements of the Shape Tree along
10 docs/how-to-delete-a-slide-from-a-presentation.md
View file
@@ -128,26 +128,26 @@ specification introduces the overall form of a **PresentationML** package.
> the entire slide masters used in the presentation; the notes master
> contains information about the formatting of notes pages; and the
> handout master describes how a handout looks.
>
> A *handout* is a printed set of slides that can be provided to an
> *audience* for future reference.
>
> As well as text and graphics, each slide can contain *comments* and
> *notes*, can have a *layout*, and can be part of one or more *custom
> presentations*. (A comment is an annotation intended for the person
> maintaining the presentation slide deck. A note is a reminder or piece
> of text intended for the presenter or the audience.)
>
> Other features that a **PresentationML**
> document can include the following: *animation*, *audio*, *video*, and
> *transitions* between slides.
>
> A **PresentationML** document is not stored
> as one large body in a single part. Instead, the elements that
> implement certain groupings of functionality are stored in separate
> parts. For example, all comments in a document are stored in one
> comment part while each slide has its own part.
>
> © ISO/IEC29500: 2008.
This following XML code segment represents a presentation that contains
12 ...to-delete-all-the-comments-by-an-author-from-all-the-slides-in-a-presentatio.md
View file
@@ -96,26 +96,26 @@ specification introduces the overall form of a **PresentationML** package.
> the entire slide masters used in the presentation; the notes master
> contains information about the formatting of notes pages; and the
> handout master describes how a handout looks.
>
> A *handout* is a printed set of slides that can be provided to an
> *audience* for future reference.
>
> As well as text and graphics, each slide can contain *comments* and
> *notes*, can have a *layout*, and can be part of one or more *custom
> presentations*. (A comment is an annotation intended for the person
> maintaining the presentation slide deck. A note is a reminder or piece
> of text intended for the presenter or the audience.)
>
> Other features that a **PresentationML**
> document can include the following: *animation*, *audio*, *video*, and
> *transitions* between slides.
>
> A **PresentationML** document is not stored
> as one large body in a single part. Instead, the elements that
> implement certain groupings of functionality are stored in separate
> parts. For example, all comments in a document are stored in one
> comment part while each slide has its own part.
>
> © ISO/IEC29500: 2008.
The following XML code segment represents a presentation that contains
@@ -173,7 +173,7 @@ introduces comments in a presentation package.
> presentation, but do not appear when a slide show is given. The
> displaying application decides when to display comments and determines
> their visual appearance.
>
> © ISO/IEC29500: 2008.
The following XML element specifies a single comment attached to a
18 docs/how-to-get-all-the-external-hyperlinks-in-a-presentation.md
View file
@@ -92,26 +92,26 @@ specification introduces the overall form of a **PresentationML** package.
> the entire slide masters used in the presentation; the notes master
> contains information about the formatting of notes pages; and the
> handout master describes how a handout looks.
>
> A *handout* is a printed set of slides that can be provided to an
> *audience* for future reference.
>
> As well as text and graphics, each slide can contain *comments* and
> *notes*, can have a *layout*, and can be part of one or more *custom
> presentations*. (A comment is an annotation intended for the person
> maintaining the presentation slide deck. A note is a reminder or piece
> of text intended for the presenter or the audience.)
>
> Other features that a **PresentationML**
> document can include the following: *animation*, *audio*, *video*, and
> *transitions* between slides.
>
> A **PresentationML** document is not stored
> as one large body in a single part. Instead, the elements that
> implement certain groupings of functionality are stored in separate
> parts. For example, all comments in a document are stored in one
> comment part while each slide has its own part.
>
> © ISO/IEC29500: 2008.
The following XML code segment represents a presentation that contains
@@ -166,13 +166,13 @@ introduces the **id** (Hyperlink Target).
> Specifies the ID of the relationship whose target shall be used as the
> target for thishyperlink.
>
> If this attribute is omitted, then there shall be no external
> hyperlink target for the current hyperlink - a location in the current
> document can still be target via the anchor attribute. If this
> attribute exists, it shall supersede the value in the anchor
> attribute.
>
> [*Example*: Consider the following <span
> class="keyword">PresentationML** fragment for a hyperlink:
@@ -200,10 +200,10 @@ introduces the **id** (Hyperlink Target).
> The target of this hyperlink would therefore be the target of
> relationship **rId9** - in this case,
> http://www.example.com. *end example*]
>
> The possible values for this attribute are defined by the
> ST\_RelationshipId simple type(§22.8.2.1).
>
> © ISO/IEC29500: 2008.
12 docs/how-to-get-all-the-text-in-a-slide-in-a-presentation.md
View file
@@ -94,30 +94,30 @@ specification introduces the overall form of a **PresentationML** package.
> to the entire slide masters used in the presentation; the notes master
> contains information about the formatting of notes pages; and the
> handout master describes how a handout looks.
>
> A **handout** is a printed set of slides that
> can be provided to an **audience** for future
> reference.
>
> As well as text and graphics, each slide can contain <span
> class="term">comments** and **notes**, can
> have a **layout**, and can be part of one or
> more **custom presentations**. (A comment is an
> annotation intended for the person maintaining the presentation slide
> deck. A note is a reminder or piece of text intended for the presenter
> or the audience.)
>
> Other features that a PresentationML document can include the
> following: **animation**, <span
> class="term">audio**, **video**, and <span
> class="term">audio<strong>, **video</strong>, and <span
> class="term">transitions** between slides.
>
> A PresentationML document is not stored as one large body in a single
> part. Instead, the elements that implement certain groupings of
> functionality are stored in separate parts. For example, all comments
> in a document are stored in one comment part while each slide has its
> own part.
>
> © ISO/IEC29500: 2008.
The following XML code segment represents a presentation that contains
10 docs/how-to-get-the-titles-of-all-the-slides-in-a-presentation.md
View file
@@ -98,26 +98,26 @@ specification introduces the overall form of a **PresentationML** package.
> the entire slide masters used in the presentation; the notes master
> contains information about the formatting of notes pages; and the
> handout master describes how a handout looks.
>
> A *handout* is a printed set of slides that can be provided to an
> *audience* for future reference.
>
> As well as text and graphics, each slide can contain *comments* and
> *notes*, can have a *layout*, and can be part of one or more *custom
> presentations*. (A comment is an annotation intended for the person
> maintaining the presentation slide deck. A note is a reminder or piece
> of text intended for the presenter or the audience.)
>
> Other features that a **PresentationML**
> document can include the following: *animation*, *audio*, *video*, and
> *transitions* between slides.
>
> A **PresentationML** document is not stored
> as one large body in a single part. Instead, the elements that
> implement certain groupings of functionality are stored in separate
> parts. For example, all comments in a document are stored in one
> comment part while each slide has its own part.
>
> © ISO/IEC29500: 2008.
This following XML code segment represents a presentation that contains
10 docs/how-to-get-worksheet-information-from-a-package.md
View file
@@ -40,8 +40,8 @@ this topic.

## Create SpreadsheetDocument Object

In the Open XML SDK, the **<span sdata="cer"
target="T:DocumentFormat.OpenXml.Packaging.SpreadsheetDocument">**SpreadsheetDocument****** class represents an
In the Open XML SDK, the <strong><span sdata="cer"
target="T:DocumentFormat.OpenXml.Packaging.SpreadsheetDocument"></strong>SpreadsheetDocument****** class represents an
Excel document package. To create an Excel document, you create an
instance of the **SpreadsheetDocument** class
and populate it with parts. At a minimum, the document must have a
@@ -84,9 +84,9 @@ The basic document structure of a **SpreadsheetML** document consists of the <sp
sdata="cer" target="T:DocumentFormat.OpenXml.Spreadsheet.Sheets">**Sheets**** and <span sdata="cer"
target="T:DocumentFormat.OpenXml.Spreadsheet.Sheet">**Sheet**** elements, which reference the
worksheets in the <span sdata="cer"
target="T:DocumentFormat.OpenXml.Spreadsheet.Workbook">**Workbook****. A separate XML file is created
target="T:DocumentFormat.OpenXml.Spreadsheet.Workbook">**Workbook**<strong>. A separate XML file is created
for each <span sdata="cer"
target="T:DocumentFormat.OpenXml.Spreadsheet.Worksheet">**Worksheet****. For example, the **SpreadsheetML** for a workbook that has two
target="T:DocumentFormat.OpenXml.Spreadsheet.Worksheet"></strong>Worksheet*<strong><em>. For example, the *</em>SpreadsheetML</strong> for a workbook that has two
worksheets name MySheet1 and MySheet2 is located in the Workbook.xml
file and is shown in the following code example.
@@ -102,7 +102,7 @@ file and is shown in the following code example.
The worksheet XML files contain one or more block level elements such as
<span sdata="cer"
target="T:DocumentFormat.OpenXml.Spreadsheet.SheetData">**SheetData****. **sheetData** represents the cell table and contains
target="T:DocumentFormat.OpenXml.Spreadsheet.SheetData">**SheetData**<strong>. **sheetData</strong> represents the cell table and contains
one or more <span sdata="cer"
target="T:DocumentFormat.OpenXml.Spreadsheet.Row">**Row**** elements. A **row** contains one or more <span sdata="cer"
target="T:DocumentFormat.OpenXml.Spreadsheet.Cell">**Cell**** elements. Each cell contains a <span
8 docs/how-to-insert-a-chart-into-a-spreadsheet.md
View file
@@ -162,7 +162,7 @@ introduces row (\<**row**\>) element.
> The row element expresses information about an entire row of a
> worksheet, and contains all cell definitions for a particular row in
> the worksheet.
>
> This row expresses information about row 2 in the worksheet, and
> contains 3 cell definitions.
@@ -215,7 +215,7 @@ introduces cell (\<**c**\>) element.
> This collection represents a cell in the worksheet. Information about
> the cell's location (reference), value, data type, formatting, and
> formula is expressed here.
>
> This example shows the information stored for a cell whose address in
> the grid is C6, whose style index is 6, and whose value metadata index
> is 15. The cell contains a formula as well as a calculated result of
@@ -261,11 +261,11 @@ introduces Cell Value (\<**c**\>) element.
> the cell is expressed directly in this element. Cells containing
> formulas express the last calculated result of the formula in this
> element.
>
> For applications not wanting to implement the shared string table, an
> "inline string" may be expressed in an \<**is**\> element under \<**c**\> (instead of a \<**v**\> element under \<**c**\>), in the same way a string would be
> expressed in the shared string table.
>
> © ISO/IEC29500: 2008.
In the following example cell B4 contains the number 360.

0 comments on commit cd2698e

Please sign in to comment.