a:font (Font Specification)

Description

\:font\ is the DrawingML element that specifies a font name for text rendering. It is defined in ECMA-376 Part 1 §21.1.2.3.4.

Font elements provide:

• Font family selection: Choose which typeface renders text
• Script support: Support for Latin, East Asian, Complex Script, Symbol fonts
• Fallback behavior: Define preferred font with alternatives
• Cross-platform consistency: Ensure text renders identically
• Semantic font roles: Differentiate font purposes (body, heading, code)

Font elements are typically used within:

• a:latin — Latin script font (Western text)
• a:ea — East Asian font (CJK text)
• a:cs — Complex Script font (Arabic, Hindi, etc.)
• a:sym — Symbol font (special characters)

Fonts differ from:

• Font reference (\:fontRef) — Theme-based font reference
• Bullet font (\:buFont) — Font for bullet characters
• Text properties (\:txPr) — Container for font and formatting

Attributes

Content Model

\:font\ has no child elements. It is a self-closing element.

xml <a:font typeface="Arial" pitchFamily="2"/>

Examples

Standard Arial Font

<a:rPr>
  <a:latin typeface="Arial" pitchFamily="2"/>
</a:rPr>
<a:t>Standard text</a:t>

using DocumentFormat.OpenXml.Drawing;

var rPr = new RunProperties();
var latin = new LatinFont { Typeface = "Arial", PitchFamily = 2 };
rPr.Append(latin);

var run = new Run { Properties = rPr };
run.Append(new Text { Text = "Standard text" });

Times New Roman (Serif) Font

<a:rPr>
  <a:latin typeface="Times New Roman" pitchFamily="2"/>
  <a:sz val="2400"/>
</a:rPr>
<a:t>Formal text</a:t>

var rPr = new RunProperties();
var latin = new LatinFont { Typeface = "Times New Roman", PitchFamily = 2 };
rPr.Append(latin);
rPr.Append(new FontSize { Val = 2400 });

var run = new Run { Properties = rPr };
run.Append(new Text { Text = "Formal text" });

Courier New (Monospace/Fixed) Font

<a:rPr>
  <a:latin typeface="Courier New" pitchFamily="1"/>
</a:rPr>
<a:t>Code text</a:t>

var rPr = new RunProperties();
var latin = new LatinFont { Typeface = "Courier New", PitchFamily = 1 };
rPr.Append(latin);

var run = new Run { Properties = rPr };
run.Append(new Text { Text = "Code text" });

East Asian Font (Chinese)

<a:rPr>
  <a:latin typeface="Calibri"/>
  <a:ea typeface="SimSun" pitchFamily="2"/>
</a:rPr>
<a:t>English and 中文</a:t>

var rPr = new RunProperties();
var latin = new LatinFont { Typeface = "Calibri" };
rPr.Append(latin);
var ea = new EastAsianFont { Typeface = "SimSun", PitchFamily = 2 };
rPr.Append(ea);

var run = new Run { Properties = rPr };
run.Append(new Text { Text = "English and 中文" });

Complex Script Font (Arabic/Hebrew)

<a:rPr>
  <a:latin typeface="Calibri"/>
  <a:cs typeface="Calibri" pitchFamily="2"/>
</a:rPr>
<a:t>English and العربية</a:t>

var rPr = new RunProperties();
var latin = new LatinFont { Typeface = "Calibri" };
rPr.Append(latin);
var cs = new ComplexScriptFont { Typeface = "Calibri", PitchFamily = 2 };
rPr.Append(cs);

var run = new Run { Properties = rPr };
run.Append(new Text { Text = "English and العربية" });

Symbol Font (Special Characters)

<a:rPr>
  <a:sym typeface="Wingdings" pitchFamily="2"/>
</a:rPr>
<a:t>✓ ★ ◆</a:t>

var rPr = new RunProperties();
var sym = new SymbolFont { Typeface = "Wingdings", PitchFamily = 2 };
rPr.Append(sym);

var run = new Run { Properties = rPr };
run.Append(new Text { Text = "✓ ★ ◆" });

Font Categories

Serif Fonts (Traditional)

Sans-Serif Fonts (Modern)

Monospace Fonts (Fixed-width)

Symbol/Dingbat Fonts

East Asian Fonts

Middle East/Complex Scripts

Pitch Family Attribute

Note: Pitch family 0 allows the renderer to substitute appropriate fonts.

Character Set Attribute

Font Hierarchy in Run Properties

Typical text formatting structure:

xml <a:rPr> <a:latin typeface="Calibri"/> <a:ea typeface="SimSun"/> <a:cs typeface="Calibri"/> <a:sym typeface="Wingdings"/> </a:rPr>

Office uses these fonts based on text script type:

• Latin characters → \:latin\ font
• CJK characters (Chinese/Japanese/Korean) → \:ea\ font
• Complex scripts (Arabic/Hebrew/Hindi) → \:cs\ font
• Special symbols → \:sym\ font

Font Fallback Behavior

When specified font unavailable:

1. Exact match: Use requested font
2. Family substitute: Use similar font (Arial → Helvetica)
3. Pitch substitute: Monospace ↔ Proportional
4. System default: Use OS default font

Best practice: Always specify fallback fonts in themes/defaults.

Web-Safe Fonts

Fonts reliably available on most systems:

Common Patterns

Standard Body Text

xml <a:rPr> <a:latin typeface="Calibri"/> <a:sz val="2000"/> </a:rPr>

Heading Font

xml <a:rPr> <a:latin typeface="Calibri Light"/> <a:sz val="4400"/> <a:b/> </a:rPr>

Code Font

xml <a:rPr> <a:latin typeface="Consolas" pitchFamily="1"/> <a:sz val="1800"/> </a:rPr>

Multilingual Text

xml <a:rPr> <a:latin typeface="Calibri"/> <a:ea typeface="SimSun"/> <a:cs typeface="Calibri"/> </a:rPr>

Compatibility Matrix

Font Embedding

When fonts embedded in document:

• File size: Increases significantly (100KB-500KB+ per font)
• Portability: Document renders identically on all systems
• Licensing: Embedding may violate font licensing
• Subsetting: Office can subset fonts (embed only used chars)

Relation: \:font\ specifies font name; embedding configured separately.

Notes

Element Characteristics

• Typeface specification: Identifies font by name
• Script-aware: Different fonts for different scripts
• Self-closing: No child elements
• Fallback-aware: Pitch family helps system select appropriate substitute
• Legacy: Charset attribute mostly historical; Unicode handles encoding

Best Practices

• Always specify \:latin\ font (most common)
• Include \:ea\ for any documents with CJK text
• Include \:cs\ for documents with Arabic/Hebrew/Indic
• Use web-safe fonts for maximum compatibility
• Test font rendering on target platforms
• Document font requirements in templates
• Consider font licensing for embedded scenarios
• Use theme fonts for consistency

Font Selection Strategy

• Corporate documents: Use branded fonts or web-safe alternatives
• Web content: Use web-safe fonts (Arial, Times, Verdana)
• Multilingual: Specify script-specific fonts
• Printing: Use print-optimized fonts (serif for body, sans for headings)
• Accessibility: Use highly readable fonts (sans-serif for screen)

Rendering

• Font rendering platform-dependent
• Character substitution occurs automatically
• Kerning and ligatures depend on font/OS
• Fallback fonts may affect layout
• Web rendering may use different fonts

Performance

• Font selection minimal file size impact
• Embedded fonts significantly increase file (avoid when possible)
• Font loading affects render time (minimal on modern systems)
• Caching reduces font lookup overhead