Server Folders Configuration
Prev
Next

Server Folders Configuration

The dialog to configure the CUPS server. Different folders are to be set here. Normally you don't need to change anything in this section. In case you play around with fancy (TrueType, PostScript® or other) fonts on your system, this qis the place to do the settings for using those fonts when printing. Server folder settings include:


The dialog to configure the CUPS server: HTTP configuration
Executables

The root folder for the scheduler executables. By default this is /usr/lib/cups (or /usr/lib32/cups on IRIX 6.5)

Configuration

The root folder for the scheduler. By default, /etc/cups.

On the authors SuSE system, this is /usr/share/doc/cups. It contains all the HTML or PDF documentation for CUPS which is available through the Web interface at http://localhost:631/documentation.html

Data

The root folder for the CUPS data files. By default this is /usr/share/cups

It contains such things as banners, charsets, data, drivers, fonts, and pstoraster templates.

Temporary files

The folder to put temporary files in. This folder must be writable by the user defined on the previous screen. This defaults to either /var/spool/cups/tmp or the value of the TMPDIR environment variable.

Temporary Requests

The folder where request files are stored. By default this is /var/spool/cups

Font path

The place to configure the CUPS server for handling your fancy fonts (TrueType or PostScript®). CUPS will look here for fonts to embed in printfiles. This currently only affects the pstoraster filter, and the default is /usr/share/cups/fonts.

To specify more than one folder, list them with double colons as separator. Do it like this:

/path/to/first/fontdir/:/path/to/second/fontdir/:/path/to/last/fontdir/

For the Font path directive to work as intended, the application that wants to print needs to:

  • Either correctly reference its desired fonts in the header of the generated PostScript®

  • Or embed the font into the PostScript® file.

Referencing the font by name leaves it up to the RIP and print device to respect and actually use it. RIP or printer can only use the desired font, if it is available on the system.

In the case of a PostScript® printer, this needs to be a printer-resident font. If the printers doesn't have this font, it will try and replace it by an adequately similar font.

In the case of a non PostScript® printer, this is done by CUPS and its RIP-ing filtering system. CUPS will use the font path directive to grab the correct font when RIP-ing the PostScript® in the pstoraster filter.

In the case of a PostScript® output device, CUPS is just spooling the file (actually, it is passing it through the pstops filter for accounting or n-up purposes), not “working” on it. Therefore, if you print to a PostScript® printer it is solely the printer's responsibility to use the font asked for. It can't, if the font is neither loaded into the printer nor embedded in the PostScript®.

Prev
Next
Home


Would you like to comment or contribute an update to this page?
Send feedback to the TDE Development Team