Syntax of measurement units in GNML

>is 8pt<        

The unit is specified explicitly in the tag. (recommended). Thus, it will always result in the same value, disregarding the default measurement unit.

>is 8000m<        

The unit is specified explicitly in the tag, and moreover, it's expressed in millipoints. Thus, not only that it will always result in the same value, disregarding the default measurement unit, but there will be no rounding errors, due to the recalculating from pt's to millipoints.

>is 8<        

The unit is not specified explicitly in the tag. Thus, it will result in the different value, related to the actual default measurement unit. Example: if the default vertical measurement unit was pt when you entered the >is 8< tag, and then two days later you change it to mm, >is 8< will behave as you've specified >is 22.7pt<.

To enter decimal units, always use the decimal point, regardless your regional settings.

>is 8.7pt<        

Right

>is 8,7pt<        

Wrong (must use the decimal point!)

When entering pc and cc units, you can use two decimal points:

pc.pt.part_of_pt

for example, 1.6.734pc = 1 pica, 6 points, 734/1000 of point

cc.dd.part_of_dd

for example, 1.6.734cc = 1 cicero, 6 didots, 734/1000 of didot

To avoid using two decimal points in a row and to use shorter unit names, you can select U.S.A notation in the GlobalConfig (EdAdmin4 > Applications Configuration > Client applications>UsaCoding = true). :

1p6.734 = 1 pica, 6 points, 734/1000 of point

1c6.734 = 1 cicero, 6 didots, 734/1000 of didot

When doing calculations with pc and cc units, have in mind they're not metric, but based on 12. Thus 4p4 + 4p6 is not 9p but 8p1.

Use the minus sign to indicate a negative measure.

-3in = 3 inch 'negative'.