Adding a Viewer to a Package

If you specify Viewer as the item type on the Specify Item to Insert window, some additional fields appear in the Specify Item to Insert window.

1. In the Viewer Type panel, indicate whether the viewer type is HTML or Text.

2. Specify the type of data that the file contains and the data format of the file by selecting a value for the Mimetype field. For example, a mime type of image/gif specifies that the file contains an image in GIF format. A mime type of application/postscript specifies that the file contains application data that should be treated as a postscript file.

   You can customize the drop-down menu of mime types that appears for this field. The default field values are contained in SASHELP.PUBLISH.MIMETYPES.SLIST. You can add your own mime values to either of the following locations:

   • WORK.PUBLISH.MIMETYPES.SLIST
   • SASUSER.PUBLISH.MIMETYPES.SLIST

   You can write an SCL application to create a MIMETYPES.SLIST in the WORK.PUBLISH or SASUSER.PUBLISH catalog. For details about writing such an SCL application, refer to the SAS Component Language: Reference in the SAS Version 8 online documentation.

3. Identify the instance of the viewer that you want to include in the package. You can specify a viewer in either of the following ways:
   • Enter the name of the viewer file directly in the field to the right of the Select Viewer to Publish button.

   • Click the Select Viewer to Publish button to display the Open window that lets you navigate a directory structure so that you can locate and select the viewer that you want to include in the package. Select a viewer and click OK.

     Focus returns to the Specify Item to Insert window, where the viewer name appears automatically in the Select Viewer to Publish field.

4. Optionally, specify a description and a name/value pair.

   For details, refer to Describing an Instance of the Item.

5. You can optionally specify the encoding property in the Encoding field. Character-set encoding refers to how a host internally represents character data. Hosts that share common architectures represent character data identically. For example, UNIX hosts internally represent character data in ASCII-ISO format, z/OS hosts in EBCDIC format, and Windows hosts in ASCII-ANSI format.

   Under some circumstances–for example, when publishing and retrieving host architectures are different–you might decide to identify a character-set encoding that is appropriate for the retrieving host. This information is delivered with the published package. Translation occurs on the retrieving host, not the publishing host.

   For complete details about publish-and-retrieve encoding behavior, refer to Publish/Retrieve Encoding Behavior.

6. Once you finish specifying viewer options, click OK to return to the What to Publish tab.