[Table of Contents] [docx version]
WordprocessingML Reference Material - Table of Contents
embedBoldItalic (Bold Italic Font Style Embedding)
This element specifies information about the embedded font storage for the bold italic form of a font, when it is embedded. This form is used when bold and italics are applied to a text run.
If this element is omitted, then no bold italic form of the font is stored in the document.
[Example: Consider a WordprocessingML document in which the Arial font has been embedded in the file. This status would be specified using the following WordprocessingML:
<w:font w:name="Arial">
…
<w:embedBoldItalic r:id="rId11" />
</w:font>
The embedBoldItalic element specifies that the embedded font targeted with the relationship with ID rId11 may be used to retrieve the bold italic form of the embedded Arial font. end example]
Parent Elements |
font (§2.8.2.10) |
Attributes |
Description |
fontKey (Embedded Font Obfuscation Key) |
Specifies the key which was used to obfuscate this embedded font. This key may be used to retrieve the embedded font for the purposes of viewing this WordprocessingML document only, using the algorithm described in §2.8.1.
If this attribute is omitted, then no key is provided for this font.
[Example: Consider a WordprocessingML document in which the Arial font has been embedded in the file. This status would be specified using the following WordprocessingML:
<w:font w:name="Arial">
The fontKey attribute has a value of {302EE813-EB4A-4642-A93A-89EF99B2457E}, therefore the embedded Arial font targeted with the relationship with ID rId10 may be retrieved if needed by using this key and the algorithm above. end example]
The possible values for this attribute are defined by the ST_Guid simple type (§2.18.39). |
id (Relationship to Part)
Namespace: .../officeDocument/2006/relationships |
Specifies the relationship ID to a specified part.
The specified relationship shall match the type required by the parent element: • http://schemas.openxmlformats.org/officeDocument/2006/relationships/footer for the footerReference element • http://schemas.openxmlformats.org/officeDocument/2006/relationships/header for the headerReference element • http://schemas.openxmlformats.org/officeDocument/2006/relationships/font for the embedBold, embedBoldItalic, embedItalic, or embedRegular elements • http://schemas.openxmlformats.org/officeDocument/2006/relationships/printerSettings for the printerSettings element
[Example: Consider an XML element which has the following id attribute:
<… r:id="rId10" />
The markup specifies the associated relationship part with relationship ID rId1 contains the corresponding relationship information for the parent XML element. end example]
The possible values for this attribute are defined by the ST_RelationshipId simple type (§7.8.2.1). |
subsetted (Embedded Font Is Subsetted) |
Specifies that the embedded font targeted by the id attribute has been subsetted. Subsetting is a mechanism by which only the glyphs used in the contents of this WordprocessingML document are stored in an embedded font, in order to prevent the file from becoming unnecessarily large from the use of a small number of glyphs from a large embedded font.
If this attribute is omitted, then the embedded font target by the id attribute shall not be handled as though it is subsetted.
[Example: Consider a WordprocessingML document in which the Arial font has been embedded in the file after subsetting. This status would be specified using the following WordprocessingML:
<w:font w:name="Arial">
The subsetted attribute has a value of true, therefore the embedded Arial font targeted with the relationship with ID rId10 shall be treated as a subsetted font. end example]
The possible values for this attribute are defined by the ST_OnOff simple type (§2.18.67). |
The following XML Schema fragment defines the contents of this element:
<complexType name="CT_FontRel">
<complexContent>
<extension base="CT_Rel">
<attribute name="fontKey" type="ST_Guid"/>
<attribute name="subsetted" type="ST_OnOff"/>
</extension>
</complexContent>
</complexType>