YearLong Class
Date Block - Long Year Format.When the object is serialized out as xml, its qualified name is w:yearLong.
Inheritance Hierarchy
System.Object
DocumentFormat.OpenXml.OpenXmlElement
DocumentFormat.OpenXml.OpenXmlLeafElement
DocumentFormat.OpenXml.Wordprocessing.EmptyType
DocumentFormat.OpenXml.Wordprocessing.YearLong
Namespace: DocumentFormat.OpenXml.Wordprocessing
Assembly: DocumentFormat.OpenXml (in DocumentFormat.OpenXml.dll)
Syntax
'Declaration
Public Class YearLong _
Inherits EmptyType
'Usage
Dim instance As YearLong
public class YearLong : EmptyType
Remarks
[ISO/IEC 29500-1 1st Edition]
17.3.3.33 yearLong (Date Block - Long Year Format)
This element specifies the presence of a date block at the current location in the run content. A date block is a non-editable region of text which shall display the current date filtered through the specified date picture (see following paragraphs). [Note: The date block is a legacy construct used for compatibility with older word processors, and should not be produced unless it was consumed while reading a document – it is recommended that the DATE field is used in its place. end note]
A date block shall be displayed using the primary editing language of the host application, regardless of the languages specified in the parent run’s lang property (§17.3.2.20).
The long year format date block shall use a date picture of YYYY, retrieving the long year format for the primary editing language.
[Example: Consider a WordprocessingML run with the following run content:
<w:r> <w:t xml:space="preserve">This is a long date: </w:t> <w:yearLong /> </w:r>
This run specifies that a long year format date block must be placed after the text string literal This is a long date: in the document. Assuming that the host application’s primary editing language is English (Canada) and today’s date is 2006-04-12, this run would be displayed as follows:
This is a long date: 2006
end example]
Parent Elements |
|---|
r (§22.1.2.87); r (§17.3.2.25) |
[Note: The W3C XML Schema definition of this element’s content model (CT_Empty) is located in §A.1. end note]
© 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.