The GNML tags and parameters are embedded in two tag brackets.
These are special characters that look like ">" and "<", but indeed they're a special codes, and they get entered at once, by a single keypress.
The ">" character is an "opening bracket" and it "opens" a GNML tag. The "<" character is the "closing bracket" and it closes the GNML tag and all the parameters (if any).
The below example assumes you want to paint the text with the font with the GN4 ordinal number 9003:
>f 9003< A tag name comes first, then a delimiting space, then parameter. Wrong >f< 9003 Parameter is outside of tags brackets - it will be interpreted as text. >f9003< There's no delimiting space between tag name and the parameter: justification engine will look for the tag with name f9003. Each pair of brackets must contain only one tag. Do not enter more tags within the same brackets.
>f 9003<>hld 12pt< Each tag is within own set of brackets. Wrong >f 9003 hld 12pt< Two tags are within one set of brackets. If a tag has more than one parameter, type them all inside the same pair of tag brackets, as >auto 4,12pt,100,1,1,100,0pt,141.24pt<. |
To enter tag brackets, press F9 (unless changed in your custom configuration). Do not type the tag brackets by hitting the ">" and "<" keys on the keyboard. If you do this, the brackets will be inserted in the text, and they will be interpreted as if they were the characters "greater than" and "smaller than", not as the tag brackets. |
F9 is usually assigned to InsStartEndCmd system script, that uses the built-in command Text.InsStartEndCmd. Alternatively, use the Ted4 command Text.InsTedText ">tagname tagparams<", to insert a string with the standard characters ">" and "<", but interpreted as special tag brackets. |
•The "opening bracket" internal code is chr(1). •The "closing bracket" code is chr(2). You may need these codes when searching and replacing tags. To find >hld 12pt<, the tag syntax may be: Text.Find chr(1) & "hld 12pt","G-S-B-" |