PersonalReply Class
E-Mail Message Reply Style.When the object is serialized out as xml, its qualified name is w:personalReply.
Inheritance Hierarchy
System.Object
DocumentFormat.OpenXml.OpenXmlElement
DocumentFormat.OpenXml.OpenXmlLeafElement
DocumentFormat.OpenXml.Wordprocessing.OnOffOnlyType
DocumentFormat.OpenXml.Wordprocessing.PersonalReply
Namespace: DocumentFormat.OpenXml.Wordprocessing
Assembly: DocumentFormat.OpenXml (in DocumentFormat.OpenXml.dll)
Syntax
'Declaration
Public Class PersonalReply _
Inherits OnOffOnlyType
'Usage
Dim instance As PersonalReply
public class PersonalReply : OnOffOnlyType
Remarks
[ISO/IEC 29500-1 1st Edition]
17.7.2.13 personalReply (E-Mail Message Reply Style)
This element specifies that the parent style, when in use in the context of an e-mail message, can be used by default to format existing message text within the e-mail message when a new reply is generated. [Note: This setting does not provide any additional semantic about the style, but can be used in the context of e-mail to automatically format the contents of existing test in the e-mail message. end note]
If this element is specified on a style of any style type other than a character style, this element shall be ignored. If no style whose styleId matches the val attribute of this element exists or that style is not a character style, this element shall be ignored.
If this element is omitted, then the current style shall not be considered a message reply text style in the context of e-mail messages.
[Example: Consider a style defined as follows in a WordprocessingML document:
<w:style w:styleId="EmailText" w:type="character" > <w:name w:val="EmailText"/> <w:personalReply w:val="true" /> <w:rPr> … </w:rPr> </w:style>
This style specifies via the use of the personalReply element that this style is a style used to format existing message text in the context of e-mail. end example]
Parent Elements |
|---|
style (§17.7.4.17) |
This element’s content model is defined by the common boolean property definition in §17.17.4.
© ISO/IEC29500: 2008.
Thread Safety
Any public static (Shared in Visual Basic) members of this type are thread safe. Any instance members are not guaranteed to be thread safe.