PDL principles and procedures

Command syntax

For the system to read and process any command you put in your JSL, you must place all elements in the proper order and use the correct symbol or amount of space to separate them.

Syntax rules

When you enter your PDL commands at the controller, workstation, or host keyboard, you must follow these syntax rules in order for the system to recognize the commands.

Abbreviations: Command and parameter keywords can be shortened to the first three letters; for example, POSITION may be entered as POS, OUTPUT as OUT, etc.

NOTE: The only exception to this abbreviation rule is the parameter FOR, which the system could interpret as FORMAT, or FORM, or FORMS. Therefore, be sure to use the full spelling to represent FORMAT or FORM(S).

Blank spaces: You may use blanks anywhere in the JSL except in keywords and constants.

Continuation lines: The DP EPS accept continuation lines in DJDEs. The following is an example of a DJDE using a continuation line.

NOTE: Use of continuation lines is not recommended because the results are unpredictable

Incorrect structure for DP EPS:

DJDE FONTS=(fn1,fn2,fn3,...,fn13,

DJDE fn14,fn15,fn16);

Valid structure for DP EPS:

DJDE FONTS=(fn1,fn2,fn3,...,fn13),;

DJDE FONTS=(fn14,fn15,fn16),;

End of a command: Place a semicolon (;) at the end of every PDL command.

End of a JSL: Use the END; command to signal the end of a JSL or other file such as a PDE, CME, or STOCKSET.

End of all JSLs: To signal the end of all JSLs, PDEs, CMEs, TSTs, or STOCKSETS that are being processed, enter END followed by a semicolon (;) twice, as shown below.

END; END;

1-12

Using LCDS Print Description Language

Page 40
Image 40
Xerox 701P21091 manual Command syntax, Syntax rules, Incorrect structure for DP EPS, Valid structure for DP EPS