🚀 go-pugleaf

zhaop,

Why have you made the airportCode element a marker? Considering your earlier question about running headers and footers, I wonder if it is because you want it to appear in the running header? Markers are text strings associated with a point in a document that do not display. Since you want the airportCode to appear in a paragraph, I recommend making it a container instead. Is there another element that contains the three you've listed? For example:

      <airport>
        <airportCode>ZBAA</airportCode>
        <airportThreeCode>PEK</airportThreeCode>
        <airportName>ADSB</airportName>
      </airport>

If so, define all four elements (airport, airportCode, airportThreeCode, and airportName) to be containers. Specify the desired paragraph format for airport. For the other three elements, provide a text formatting rule that defines them to be text ranges. Give airportCode a suffix (or airportThreeCode a prefix) of /. Give airportThreeCode a suffix (or airportName a prefix) of -.

If there is no element that corresponds to the paragraph, you can still make all three of the elements containers, but in the pagination properties of the first two, set Placement to RunInHead. In this case, you can insert the / and - delimiters as default punctuation for the run-in heads rather than as prefixes or suffixes. (You could still use prefixes or suffixes; both techniques produce the same result.)

For your running header/footer, where you currently use <$marker1> or <$marker2> to display airportCode, instead use <elemtext[airportCode]>.

--Lynne