Test printing is important when you want to test a rule set using printed output rather than the PDF or HTML5 output used by the preview. Test prints go to a server printer, or can be returned to the browser (though they typically are not viewable by the browser and are just downloaded). Recent printers are remembered by the test print window, with a drop down selector.
Unix servers typically have printers referenced by piping to spooler commands, such as in the example below. On Windows, the printer can be a UNC (shared printer name). On both Unix and Windows, it can be a network address, entered as: "tcp:ipaddress" (i.e. tcp:192.168.1.45).
To test printing using Postscript, check the Print Postscript option. If the rule set redirects output, with an output command or setting the output$ variable, you can check the Disable output redirects option to force all output to the main test print device (a watermark is printed on pages that would have gone to the alternate device).
Finally, if any other uf100c command line options are required for testing purposes, you can enter them in the Other Options field. Note that to test Zebra output to a file or printer, add -p zebran (n is 6, 8, or 12 dots per mm) to the command line options to override the default pcl or postscript value.
Local Viewing is attempted if Output is not specified (or Browser is selected in the drop down). In this case, PCL output is converted to PDF using a server-configured GhostPCL, and Postscript output is converted to PDF using a server-configured Ghostscript.
