The purpose of the prolog.ps file is to set up non-generic fonts. Applications use these predefined PostScript font names for printing. The prolog file must define at least the following font names for Desk Set Calendar manager and mp:
The following example uses these fonts to print the particular local character set specified:
100 100 moveto /LC_Times-Roman findfont 24 scale font setfont (Any text string in your locale) show
The Oracle Solaris localization kit provides a sample prolog.ps file for the Japanese environment. Alternatively, this file is found in the /usr/openwin/lib/locale/ja/print/ directory.
The following example shows how to add or change composite fonts in an existing prolog.ps file.
% (Foo-Fine) makecodeset12 (Base-Font) makeEUCfont %
You could define a composite font called LC_Base-Font, for example. LC_Base-Font might be a composite of a Foo-Fine font that contains a locale character set and a Base-Font. You do not need in-depth knowledge of PostScript programming to add or change a font.
The best way to create a prolog.ps file is to study the example version. In the example prolog.ps, two routines need to be written: makecodeset12 and makeEUCfont. The routine makecodeset12 sets the local font-encoding information. This routine might differ from locale to locale. The routine makeEUCfont combines the base font and the locale font to form a composite font. The creator of the prolog file should have good knowledge of PostScript in order to write makecodeset12 and makeEUCfont.
The prolog.ps file support is reserved for backward compatibility only. Do not create a new prolog.ps file for generating printed output for a locale. Use mp.conf instead.
The path for prolog.ps file is