AlwaysMergeEmptyNamespace-Klasse
Do Not Mark Custom XML Elements With No Namespace As Invalid.When the object is serialized out as xml, its qualified name is w:alwaysMergeEmptyNamespace.
Vererbungshierarchie
System.Object
DocumentFormat.OpenXml.OpenXmlElement
DocumentFormat.OpenXml.OpenXmlLeafElement
DocumentFormat.OpenXml.Wordprocessing.OnOffType
DocumentFormat.OpenXml.Wordprocessing.AlwaysMergeEmptyNamespace
Namespace: DocumentFormat.OpenXml.Wordprocessing
Assembly: DocumentFormat.OpenXml (in DocumentFormat.OpenXml.dll)
Syntax
'Declaration
Public Class AlwaysMergeEmptyNamespace _
Inherits OnOffType
'Usage
Dim instance As AlwaysMergeEmptyNamespace
public class AlwaysMergeEmptyNamespace : OnOffType
Hinweise
[ISO/IEC 29500-1 1. Ausgabe]
17.15.1.3 alwaysMergeEmptyNamespace (Do Not Mark Custom XML Elements With No Namespace As Invalid)
This element specifies whether custom XML markup specified via the customXml element which has no associated namespace shall be treated as an error and moved into a special error namespace (for the purposes of XML schema validation) when the document is opened. If this element is turned on, when an application determines that the current XML markup is in the empty namespace, those elements shall not automatically be moved into an error namespace.
If this element is not present in a WordprocessingML document than custom XML markup which has no associated namespace shall be treated as an error and moved into a special error namespace when the document is opened.
[Example: Consider a WordprocessingML document which should not automatically flag empty namespace XML as invalid. This requirement would be specified using the following WordprocessingML:
<w:alwaysMergeEmptyNamespace w:val="true"/>
The alwaysMergeEmptyNamespace element's val attribute has a value of true specifying that custom XML markup in the empty namespace must never be treated as an error. end example]
Parent Elements |
|---|
settings (§17.15.1.78) |
This element's content model is defined by the common boolean property definition in §17.17.4.
© ISO/IEC29500: 2008. Die oben aufgeführten Textauszüge wurden von Microsoft (und/oder den Microsoft-Vendoren) von Englisch nach Deutsch übersetzt, und im Rahmen von ISO wird keinerlei Verantwortung für diese Übersetzungen übernommen.
Threadsicherheit
Alle öffentlichen static (Shared in Visual Basic) Member dieses Typs sind threadsicher. Bei Instanzmembern ist die Threadsicherheit nicht gewährleistet.