<xsl:document> in Font

Create PDF-417 2d barcode in Font <xsl:document>

The <xsl:document> instruction creates a document node. The content of the document node is the result of processing the sequence constructor that the <xsl:document> instruction contains. After the document node has been constructed, its document element may be validated and assigned a type annotation based on the type or validation attributes, only one of which may be present. If the type attribute is present or if validation is strict or lax, the document must be well-formed (have only one element as a child and no text-node children). If the type attribute is present, the document element is validated against the named type. If the validation attribute is present, strip results in a type annotation of xdt:untyped for the element and all its element descendants, with its attributes and all the attributes of its descendants being assigned a type of xdt:untypedAtomic, while preserve preserves whatever type annotations are on the document element, its attributes and descendants. strict and lax result in a type annotation based on any top-level element declarations that have been imported into the stylesheet. If neither the type nor validation attribute is present, validation proceeds based on the element.

<xsl:document validation="strict | lax | preserve | strip" type="qualified-name" > sequence-constructor </xsl:document> See also <xsl:result-document>. From XSLT 2.0.

The <xsl:element> instruction creates an element. The name of the element that s created is determined by its name and namespace attributes. The name attribute gives the qualified name for the element, and the namespace attribute gives the namespace for the element. If the namespace attribute is missing, then the qualified name specified by the name attribute is used to identify the namespace for the element the namespace associated with the qualified name s prefix, or the default namespace if it doesn t have a prefix. Both the name and namespace attributes are attribute value templates, so their values can be calculated on the fly in fact, this is the only reason you should use <xsl:element> rather than a literal result element. If inherit-namespaces is present with the value no, the children of the new element will not have copies of any namespace nodes of the new element. If the use-attribute-sets attribute is present, then the attributes held in the attribute sets named within this attribute are added to the created element. Other attributes and the content of the element are generated as the result of processing the content of the <xsl:element> instruction. After the element has been constructed, it may be validated and assigned a type annotation based on the type or validation attributes, only one of which may be present. If the type attribute is present, the element is validated against the named type. If the validation attribute is present, the element is validated accordingly. strip results in a type annotation of xdt:untyped for the element and all its element descendants, with its attributes and all the attributes of its descendants being assigned a type of xdt:untypedAtomic. preserve assigns the element itself the type xdt:untyped but preserves whatever type annotations are on its attributes and descendants. strict and lax result in a type annotation based on any top-level element declarations that have been imported into the stylesheet. If neither the type nor validation attribute is present, validation proceeds based on the default-validation attribute on the <xsl:stylesheet> element. <xsl:element name="{qualified-name}" namespace="{namespace-uri}" inherit-namespaces="yes | no" use-attribute-sets="list-of-qualified-names" type="qualified-name" validation="strict | lax | preserve | strip"> sequence-constructor </xsl:element> See also <xsl:attribute-set>. From XSLT 1.0.

The <xsl:fallback> element provides alternative processing in the event that an implementation does not support a particular element. When an XSLT processor comes across an instruction that it doesn t understand (such as an XSLT 2.0 instruction or an extension element), it looks for an <xsl:fallback> element amongst its children. If it finds one, it processes the content of that <xsl:fallback> element; if it doesn t, it stops processing and the transformation fails. <xsl:fallback> sequence-constructor </xsl:fallback> See also element-available(). From XSLT 1.0.