Help > Printing and Publishing > Setting Up for Print and Publishing > Choosing a Print Engine Setting for Local Publishing
  
Choosing a Print Engine Setting for Local Publishing
The list below describes some instances in which you may wish to set a specific print engine to publish your document, when your environment includes Arbortext Styler. Each one describes the settings you should make to use the required print engine for print preview, print, or publish to PDF actions in Arbortext Editor:
Use PTC Advanced Print Publisher (PTC APP) for publishing with new stylesheets, and PTC APP, FOSI or XSL-FO for publishing with existing stylesheets depending on their stylesheet setting - this is the default behavior for local preview/publishing of a document, no explicit settings are required.
Use a particular engine for publishing with both new stylesheets and existing stylesheets - set the print engine option in the Print/PDF tab of the Stylesheet Properties dialog box.
Use all print engines to test a single stylesheet, regardless of the current stylesheet setting - use the Arbortext Editor option set printengineoverride=app, set printengineoverride=fosi, or set printengineoverride=xslfo before the publishing action.
To subsequently undo the print engine override setting, use the command set printengineoverride=no.
You may be working in an environment where Arbortext Styler is not available. If PTC APP is set as the effective print engine for your stylesheet, the publishing process will use FOSI instead of PTC APP.
* 
The FOSI and XSL-FO print engines are on sustained support and do not receive enhancements or maintenance fixes. PTC APP is the recommended engine for print/PDF output.
Effects of Print Engine Selection on Print Preview Actions
If you wish to preview print output, take the following steps:
1. In Arbortext Editor, select the File > Print Preview menu option. The Preview dialog box is launched (see Preview Dialog Box for information).
2. In the Stylesheet field, select the stylesheet that will be used to support the preview action.
3. Note that the Print Engine field displays the print engine that is currently effective for your PTC Arbortext environment.
4. If the effective print engine for the Arbortext Editor environment or stylesheet is PTC APP, the document is published via PTC APP and is displayed in the PTC ALD Preview Window.
5. If the effective print engine for the Arbortext Editor environment is FOSI or XSL-FO, the appropriate publishing action is carried out and the document is displayed in the Pubview window.
Effects of Print Engine Selection on Print Actions
If you wish to print your document, take the following steps:
1. In Arbortext Editor, select the File > Print menu option. The Print dialog box is launched (see Print Dialog Box for information).
2. In the Stylesheet field, select the stylesheet that will be used to support the print action.
3. Note that the Print Engine field displays the print engine that is currently effective for your PTC Arbortext environment.
4. The appropriate publishing action is carried out on the server and the result is sent to the nominated printer on the client.
Effects of Print Engine Selection on Publish to PDF Actions
If you wish to publish a PDF of your document, take the following steps:
1. In Arbortext Editor, select the File > Publish > PDF File menu option. The Publish to PDF File dialog box is launched (see Publish to PDF File Dialog Box for information)
2. In the Stylesheet field, select the stylesheet that will be used to support the publish action.
3. Note that the Print Engine field displays the print engine that is currently effective for your PTC Arbortext environment.
4. If the effective print engine for the Arbortext Editor environment is PTC APP, the document is published to PDF via the PTC APP print engine.
If the effective print engine for the Arbortext Editor environment is FOSI or XSL-FO, the appropriate publishing action is carried out to generate the PDF.
5. If you checked the View PDF File option in the Publish to PDF File dialog box, the PDF is opened in Acrobat.