Syntax of XML output tags

Build 1501 on 14/Nov/2017  This topic last edited on: 24/Oct/2016, at 14:39

XML output tags use the standard XML syntax: the delimiting brackets are opposite of those in GNML, thus '<' is the opening bracket, and '>' is the closing bracket.

The brackets are entered in text as normal 'less than' and 'greater than' characters.

In the XML output, a #T placeholder represents the entire content formatted with the specified tag. On the following screenshot, #T in <p>#T</p> represents the text in the paragraph formatted with the paragraph style.

tags3

For the cascading styles, the number of #T placeholders must be one more than the number of #T placeholders in the GNML styles.

hmtoggle_plus1Examples of XML output tags

An example of a XML output string is:

<head>#T</head>. 

This correspond to any sequence of GNML tags which do not contain any Bell character @.

#T stands for the content after the GNML style.

The meaning of the <head> XML tag is expected to be defined in the CSS stylesheets or in XSL transformation on the server.

If the GNML style contains one #T placeholder for cascading styles, e.g. a headline style where a user inserts Bell to switch from bold to plain in the headline, then the XML output string has to contain two #T placeholders:

<head>#T<plain>#T</plain></head>. 

While blue #T, stands for the content after the GNML style, the yellow #T is the Bell placeholder.

If you want to have resulting XML with no style change, you can do also:

<head>#T #T</head>. 

Even in this case you need to provide the placeholder for the Bell. Otherwise, the justification error about "The paragraph contain X Bell(s) that are not needed" would be displayed.

If there would be more Bell characters, add one #T for each of them. Such syntax makes Bells mandatory.

The meaning of <head> and <plain> XML tags is expected to be defined in the CSS stylesheets or in XSL transformation on the server.

This is based on specific setting in the GN4.XSD schema, when the GNML tag name equals the XML element name, and GNML tag contains one optional Bell.

This assumes there's a photoCaption element in the GN4.XSD schema. If the element requires one Bell character, as in this example, the definition of the element has to include the definition of Bell element:

 <xs:element name="photoCaption">

   <xs:complexType>

     <xs:annotation>

       <xs:appinfo>

         <gs:_objectType deadlineGap="0" nameptt="&amp;a,ph&amp;n[1,2]" typeLink="single" mediaType="Text">

           <description>Photo caption</description>

         </gs:_objectType>

       </xs:appinfo>

     </xs:annotation>

     <xs:complexContent>

       <xs:extension base="txt">

         <xs:sequence>

           <xs:element name="xmlText" minOccurs="0" gs:storage="Ignore">

             <xs:annotation>

               <xs:documentation>Text XML structure. Not stored in the database</xs:documentation>

             </xs:annotation>

             <xs:complexType>

               <xs:sequence>

                 <xs:element name="p" type="p" minOccurs="0" maxOccurs="unbounded"/>

                 <xs:element name="credit" type="credit" minOccurs="0" maxOccurs="1"/>

                 <xs:element name="caption" type="caption" minOccurs="0" maxOccurs="1"/>

                <xs:element name="bell" type="bell" minOccurs="0" maxOccurs="unbounded"/>

               </xs:sequence>

             </xs:complexType>

           </xs:element>

           <xs:element name="ref" type="reference" minOccurs="0" gs:refer="img"/>

         </xs:sequence>

       </xs:extension>

     </xs:complexContent>

   </xs:complexType>

</xs:element>

An example might be a style photocaption, with the following structure:

>is 0<>f 133<>h 8.5pt<>ld 10pt<>paj<>ql<>fill ,,,,2<

where the >fill...< tag requires the Bell.

The XML output is:

<photoCaption>

In such case, the tag does not cause the formatting error related to the Bell character neither when it is used with the Bell, nor when it's missing.