WordprocessingML

1. Components of WordprocessingML
• Main Document
• Paragraphs & Rich Formatting
– Runs
– Run Content
• Tables
• Custom Markup
• Sections
• Styles
– Paragraph
– Character
– Numbering
– Table
– Document Defaults
• Fonts
• Numbering
• Headers/Footers
• Footnotes/Endnotes
• Glossary Document
• Annotations
– Comments
– Revisions
– Bookmarks
• Mail Merge
• Document Settings
– Web Settings
– Compatibility Settings
• Fields & Hyperlinks
• Odds & Ends (Textboxes, Subdocuments, Extensibility)
Ecma/TC45/2006/060 (Rev.)

2. WordprocessingML – Fonts

3. Fonts
• Font face information can be referred to from
any run property set in a WordprocessingML
document
– On style definitions
– On runs directly

4. Font References
• Run properties reference the font face to be
used via the rFonts element
• For example, let's use the Arial Black font:

5. Font References
• The values in the attributes on the rFonts
element reference the font name on the
system
– So in this example, the font name we're looking
for (for Latin characters) is "Arial Black"

6. Font References
• You probably noticed that there were three
font attributes in our example:
• Why?

7. Font Types
• WordprocessingML stores up to four fonts to
be used on a run/style:
– Latin font
– Symbol (high ANSI) font
– East Asian font
– Complex Script font
• Each font type specifies the font for the part
of the run in that character set

8. Font Types Example
• So looking at the example earlier:
– All ASCII and High ANSI (Latin/Symbol) characters
in this run will use the "Arial Black" font
– All complex script character will use the "Arial"
font

9. Font Type Hints
• Some characters within a run are ambiguous
– They can either be rendered as either East Asian,
complex script, or ASCII characters
• This attribute value specifies a 'hint' as to
which character set to use for these
ambiguous characters

10. Font Type Hints
– At runtime, this information is gathered based
on the keyboard type used to enter the
characters
• If using an East Asian keyboard, hint to use the
East Asian font data
• If using a Latin keyboard, hint to use the ASCII font
data
• This ensures that the consumer displays the
characters using the most likely font slot

11. Font Table
• The rFonts element references optional font
substitution information stored in the font
table part:
– Implicit relationship from the document part
– Relationship type:
http://schemas.openxmlformats.org/wordprocessingml/2006/fo
ntTable
– Content type: vnd-
openxmlformats.officedocument.wordprocessingml-
fontTable+xml

12. Font Table
• Each item in the font table is defined using the
font element
• Stores information about each font for font
substitution
– Entirely optional, but producers should always
write out this information

13. Font Table Example
• Example: The font substitution data for Arial
Black

14. Font Substitution Data
• The following data is stored as reported by
the font in order to allow for font matching
when the specified font is unavailable:
– Alternate font name(s)
– Panose number
– Character set
– Font family
– Is this a TrueType font?

15. Font Substitution Data
• Font data (cont'd):
– Font pitch
– Supported code pages/Unicode ranges

16. Font Embedding
• As well, a use may choose to embed one or
more fonts into a WordprocessingML
document
– If I use the "Tristan Davis Rules" font, and I know
you don't have it, I can embed it so you see the
exact same font I used
• When a font is embedded, it can either be
embedded completely, or the subset for
characters in use in the document

17. Font Embedding
• Within the font table part, if a font is
embedded there are explicit relationships to
each font form needed:
– Regular
– Bold
– Italic
– Bold+Italic

18. Theme Fonts
• As well as standard font information, a run in
the document may need to store information
for 'theme fonts'
– Theme fonts are an abstraction of font name
information that allows the font usage to be
globally managed by the user
– Think of this as a "style for fonts" in the way that a
style relates to paragraph properties

19. Theme Fonts
• Theme fonts are specified using the theme
attribute variants in the rFonts element,
rather than the font name:
– Font and theme font are mutually exclusive
Theme fonts (there's no font called minorHAnsi)

20. Theme Fonts
• The theme fonts definition is stored in a
shared DrawingML theme part
• The syntax of the theme fonts definition
(shared by all applications that support
DrawingML theme data) will be discussed in a
DrawingML presentation

21. Disclaimer
This presentation is for informational purposes only, and should
not be relied upon as a substitute or replacement for Microsoft
formal file format documentation, which is available at the
following website: https://msdn.microsoft.com/en-
us/library/cc313118(v=office.12).aspx. Any views or opinions
presented in this material are solely those of the author and do
not necessarily represent those of Microsoft. Microsoft
disclaims all liability for mistakes or inaccuracies in this
presentation.