Software: Apache/2.0.54 (Fedora). PHP/5.0.4 uname -a: Linux mina-info.me 2.6.17-1.2142_FC4smp #1 SMP Tue Jul 11 22:57:02 EDT 2006 i686 uid=48(apache) gid=48(apache) groups=48(apache) Safe-mode: OFF (not secure) /usr/share/doc/ghostscript-7.07/ drwxr-xr-x | |
| Viewing file: Select action/file-type: How to use GhostscriptTable of contents
For other information, see the Ghostscript overview, the new user's documentation on previewers and, if necessary, how to install Ghostscript. Invoking GhostscriptThe command line to invoke Ghostscript is essentially the same on all systems, although the name of the executable program itself may differ among systems. For instance, to invoke Ghostscript on Unix: gs [switches] {filename 1} ... [switches] {filename N} ...
Note, though, that on a system with a windowed graphical user interface, it's common to use Ghostscript through a previewer, so you should read the section about previewers in the documentation for new users. Ghostscript is capable of interpreting PostScript, encapsulated PostScript (EPS), DOS EPS (EPSF), and -- if the executable was built for it -- Adobe Portable Document Format (PDF). The interpreter reads and executes the files in sequence, using the method described under "File searching" to find them. After doing this, it reads further lines of PostScript language commands from the primary input stream, normally the keyboard, interpreting each line separately. To quit the interpreter, type "quit". The interpreter also quits gracefully if it encounters end-of-file or control-C. The interpreter recognizes many switches. A switch may appear anywhere in the command line, and applies to all files named after it on the line. Many of the switches include "=" followed by a parameter. Help at the command line: gs -hYou can get a brief help message by invoking Ghostscript with the -h or -? switch, like this: gs -h (Of course, for "gs" use the right command for your system.) The message shows for this executable
SecurityGhostscript implements a full-featured programming language, with access to the filesystem and the ability to control a diverse set of devices. As such, there are potential security implications. The first line of defense is to use the security mechanisms provided by Ghostscript. If you're running arbitrary PostScript files (for example, those sent through email or downloaded from the Web), make sure to use the -dSAFER option. Otherwise, you are opening up your entire filesystem to potentially malicious code. By default, Ghostscript opens up read access to the entire filesystem. In general, if you're just viewing or printing documents, this does not pose a significant security risk. However, if there is a chance that the output of Ghostscript can leak sensitive information, also set the -DPARANOIDSAFER option. Note, however, that this option is incompatible with some scripts and wrappers, including gv and related viewer apps. We plan to make -dSAFER the default in future versions of Ghostscript. Since most people use Ghostscript to print and view documents, rather than to run scripts written in the PostScript language, this will provide additional safety with little hassle for most users. If you are using Ghostscript as a scripting language and need unfettered access to the filesystem, use the -dNOSAFER flag to signal explictly that you wish the PostScript code to have full access to the file system. Currently, this flag has no effect, but it will insure than your scripts execute as expected in future versions. While we've tried to patch all known security problems, there is no guarantee that we've caught them all. Ghostscript is a complex application written in C. Buffer overflows and other exploits remain a distinct possibility. Thus we recommend that, whenever possible, Ghostscript should run in a secure "sandbox" environment, making use of the security mechanisms of the underlying operating system. In particular, we urge GNU/Linux distributors to invoke Ghostscript from the print subsystem in a chroot'ed environment, and never as root. We will continue to be vigilant regarding security issues. As always, apply security updates promptly. Input from a pipeAs noted above, one normally specifies input with file names on the command line. However, one can also "pipe" input into Ghostscript by using the special file name "-" or "-_", for instance {some program producing PS} | gs {...options...} - These switches differ from a named file in two respects:
The difference between "-" and "-_" is that "-" may read the input one character at a time, which is useful for programs that generate input for Ghostscript dynamically and watch for some response, whereas "-_" reads the input in blocks, which is more efficient for ordinary (batch) execution. Selecting an output deviceGhostscript may be built to handle multiple output devices, and it normally opens and directs output to the first one built in. Ghostscript's gs -h help message lists the output devices known to the executable. Once you invoke Ghostscript you can also find out what devices are available by "devicenames ==" at its command prompt. A little more information about devices appears near the beginning of the files devs.mak (for drivers that are considered "part of" Ghostscript and are maintained by the maintainers of the main Ghostscript code) and contrib.mak (for user-contributed drivers) used to build Ghostscript. (If you got Ghostscript under the Aladdin Free Public License, the person or place from which you got it is also required to make the source code available to you; if you got it under the GNU General Public License (GPL), see the GNU General Public License for more information.) To use device xyz as the initial output device, use the command-line switch -sDEVICE=xyz Note that this switch must precede the name of the first input file, and only its first use has any effect. For example, for printer output in a configuration that includes an Epson printer driver, instead of just "gs myfile.ps" you might use gs -sDEVICE=epson myfile.ps Alternatively, once you invoke Ghostscript and have its own command prompt you can type (epson) selectdevice All output then goes to the Epson printer instead of the display until you do something to change devices. You can switch devices at any time by using the selectdevice procedure, for instance like one of these: (vga) selectdevice A third possibility is to define an environment variable GS_DEVICE with the name of your desired default device. The order of precedence for these alternatives, highest to lowest, is:
Printer resolutionSome printers can print at several different resolutions, letting you balance resolution against printing speed. To select the resolution on such a printer, use the -r switch: gs -sDEVICE=printer -rXRESxYRES For example, on Epson-compatible printers you have these choices:
Output to filesIf you select a printer as the output device, Ghostscript also allows you to control where the device sends its output. On DOS and MS Windows systems, output normally goes directly to the printer (PRN); on Unix or VMS systems normally to a temporary file for later printing. To send the output to a file, use the -sOutputFile= switch (for compatibility with older versions of Ghostscript, -sOUTPUTFILE= also works). For instance, to direct all output into the file ABC.xyz, use gs -sOutputFile=ABC.xyz The file name follows the PostScript convention that if a name begins with %, the name must be in the form %filedevice or %filedevice%file. The legal values of filedevice are system-dependent, but the following have consistent meanings across systems:
Note that because of this, if you want to specify a file name that actually begins with %, you must specify the %os% filedevice explicitly: e.g., for output to a file named %abc, you need to specify -sOutputFile=%os%%abc. Note also that on DOS and MS Windows systems, the % character has a special meaning for the command processor (shell), so you will have to double it, e.g., for a pipe on MS Windows, gs -sOutputFile=%%pipe%%cmd One page per fileYou can also tell Ghostscript to put each page of output in a separate file. To send output to a series of files each representing a single page, use in the filename the printf format specifier "%d" (or its extended form like "%02d"); for instance
As noted above, on DOS and MS Windows systems, you will have to double the % character, e.g., gs -sOutputFile=ABC%%03d.xyz Output to a pipeOn Unix and (32-bit) MS Windows systems you can use this switch to send output directly to a pipe. For example, to pipe the output to lpr, use the command gs -sOutputFile=\|lpror, as noted above, gs -sOutputFile=%pipe%lpr (doubling the % characters on MS Windows systems, as noted above.) You can also send output to standard output for piping in the usual way supported by the system: gs -sOutputFile=- -q | ...or, as noted above, gs -sOutputFile=%stdout -q | ... (again, doubling the % character on MS Windows systems.) In this case you must also use the -q switch to prevent Ghostscript from writing messages to standard output which become mixed with the intended output stream. Output to graphics file formatsFile formats like PCX and PBM are also "devices". When you select a file format as the "device", you must also specify an output file, for instance gs -sDEVICE=pcxmono -sOutputFile=xyz.pcx Here, as with printable files, you can use "%d" ("%%d" on DOS and MS Windows) to specify one page per output file. Bounding box outputThere is a special bbox "device" that just prints the bounding box of each page. You select it in the usual way: gs -dNOPAUSE -dBATCH -sDEVICE=bbox It prints the output in a format like this: %%BoundingBox: 14 37 570 719 %%HiResBoundingBox: 14.308066 37.547999 569.495061 718.319158 Currently, it always prints the bounding box on stderr; eventually, it should also recognize -sOutputFile=. Note that this device, like other devices, has a resolution and a (maximum) page size. As for other devices, the product (resolution x page size) is limited to approximately 500K pixels. By default, the resolution is 4000 DPI and the maximum page size is approximately 125", or approximately 9000 default (1/72") user coordinate units. If you need to measure larger pages than this, you must reset both the resolution and the page size in pixels, e.g., gs -dNOPAUSE -dBATCH -sDEVICE=bbox -r100 -g500000x500000 Choosing paper sizeGhostscript is distributed configured to use U.S. letter paper as its default page size. There are two ways to select other paper sizes from the command line:
Individual documents can (and often do) specify a paper size, which takes precedence over the default size. To force a specific paper size and ignore the paper size specified in the document, select a paper size as just described, and also include the -dFIXEDMEDIA switch on the command line. Changing the installed default paper sizeYou can change the installed default paper size in installing Ghostscript or later, by editing the initialization file gs_init.ps. Find the consecutive lines % Optionally choose a default paper size other than U.S. letter. Then to make A4 the default paper size, uncomment the second line to change this to % Optionally choose a default paper size other than U.S. letter. For a4 you can substitute any paper size Ghostscript knows. How Ghostscript finds filesWhen looking for initialization files (gs_*.ps, pdf_*.ps), font files, the Fontmap file, and files named on the command line, Ghostscript first tests whether the file name specifies an explicit directory.
If the test succeeds, the file name specifies an explicit directory and Ghostscript tries to open the file using the name given. Otherwise it tries directories in this order:
GS_LIB_DEFAULT, GS_LIB, and the -I parameter may specify either a single directory or a list of directories separated by a character appropriate for the operating system (":" on Unix systems, "," on VMS systems, and ";" on DOS systems). We think that trying the current directory first is a very bad idea -- it opens serious security loopholes and can lead to very confusing errors if one has more than one version of Ghostscript in one's environment -- but when we attempted to change it, users insisted that we change it back. You can disable looking in the current directory first by using the -P- switch. Note that Ghostscript does not use this file searching algorithm for the run or file operators: for these operators, it simply opens the file with the name given. To run a file using the searching algorithm, use runlibfile instead of run. Finding PostScript Level 2 resourcesGhostscript uses a completely different rule for looking for files containing PostScript Level 2 "resources": per the Adobe documentation, it concatenates together
To look up fonts, after exhausting the search method described in the next section, it concatenates together
Note that even though the system parameters are named "somethingDir", they are not just plain directory names: they have "/" on the end, so that they can be concatenated with the category name or font name. Font lookupGhostscript has a slightly different way to find the file containing a font with a given name. This rule uses not only the search path defined by -I, GS_LIB, and GS_LIB_DEFAULT as described above, but also the directory that is the value of the FontResourceDir system parameter, and an additional list of directories that is the value of the GS_FONTPATH environment variable (or the value provided with the -sFONTPATH= switch, if present). At startup time, Ghostscript reads in the Fontmap files in every directory on the search path (or in the list provided with the -sFONTMAP= switch, if present): these files are catalogs of fonts and the files that contain them. (See the documentation of fonts for details.) Then, when Ghostscript needs to find a font that isn't already loaded into memory, it goes through a series of steps.
If you are using one of the following types of computer, you may wish to set the environment variable GS_FONTPATH to the value indicated so that Ghostscript will automatically acquire all the installed Type 1 (and, if supported, TrueType) fonts (but see below for notes on systems marked with "*"):
These paths may not be exactly right for your installation; if the indicated directory doesn't contain files whose names are familiar font names like Courier and Helvetica, you may wish to ask your system administrator where to find these fonts. Adobe Acrobat comes with a set of fourteen Type 1 fonts, on Unix typically in a directory called .../Acrobat3/Fonts. There is no particular reason to use these instead of the corresponding fonts in the Ghostscript distribution (which are of just as good quality), except to save about a megabyte of disk space, but the installation documentation explains how to do it on Unix and on DOS (where you can also use Adobe Type Manager fonts). Temporary files
You can change in which directory Ghostscript creates temporary files by setting the TMPDIR or TEMP environment variable to the name of the directory you want used. Ghostscript currently doesn't do a very good job of deleting temporary files if it exits because of an error; you may have to delete them manually from time to time.
Summary of environment variables
CID font substitutionCID fonts are PostScript resources containing large number of glyphs (e.g. glyphs for Far East languages). Please refer Postscript Language Reference, third edition, for details. CID font resources are different kind of PostScript resources than fonts. Particularly they cannot be used as regular fonts. For doing this, CID font resourse first to be combined with a CMap resource, which defines specific codes for hieroglyphs (this allows to use same collection of hieroglyphs with different encodings). The simplest method to request a font composed of CID font resource and CMap resource is to code /CIDFont-CMap findfontin a PostScript document, where CIDFont is a name of any CID font resourse, and CMap is a name of a CMap resource, being designed for same character collection. The interpreter will compose the font automatically from the specified CID font and CMap resources. Another method is based on the operator composefont. For substituting CID font resources Ghostscript 6.53 and 7.0x provides the control file "CIDFnmap", which defines a CID font resource map. please refer "About CIDFnmap of Ghostscript" in CJK.htm. However, "CIDFnmap" will be replaced by "cidfmap" in Ghostscript 7.2x and later releases. Using Ghostscript with EPS filesEncapsulated PostScript (EPS) files are intended to be encapsulated in another PostScript document and may not display or print on their own. An EPS file must conform to the Document Structuring Conventions, must include a %%BoundingBox: line to indicate the rectangle in which it will draw, must not use PostScript commands which will interfere with the document importing the EPS, and can have either zero pages or one page. Ghostscript has support for handling EPS files, but requires that the %%BoundingBox: be in the header, not the trailer. For the official description of the EPS file format, please refer to the Adobe documentation in their tech note #5002. It is available from: http://partners.adobe.com/asn/developer/technotes/postscript.html To crop an EPS file to the bounding box: gs -dEPSCrop file.eps To resize an EPS file to fit the page: gs -dEPSFitPage file.eps To disable special processing of EPS files: gs -dNOEPS file.eps Using Ghostscript with PDF filesGhostscript is normally built (except on 16-bit DOS platforms) to interpret both PostScript and PDF files, examining each file to determine automatically whether its contents are PDF or PostScript. All the normal switches and procedures for interpreting PostScript files also apply to PDF files, with a few exceptions. In addition, the pdf2ps utility uses Ghostscript to convert PDF to (Level 2) PostScript. PDF files from standard inputThe PDF language, unlike the PostScript language, inherently requires random access to the file. If you provide PDF to standard input using the "-" or "-_" switch, ghostscript will copy it to a temporary file before interpreting the PDF. Switches for PDF files
Problems interpreting a PDF fileOccasionally you may try to read or print a *.pdf file that Ghostscript doesn't recognize as PDF, even though the same file can be opened and interpreted by an Adobe Acrobat viewer. This can happen when, for instance, a PDF file produced on a Macintosh is carelessly moved to another kind of system, leaving now-useless Macintosh-specific data before the standard header. Ghostscript can't read these files because they don't conform to the PDF standard, Adobe's Portable Document Format Reference Manual, version 1.2, which states: The first line of a PDF file specifies the version number of the PDF specification to which the file adheres.... [T]he first line of a 1.2-conforming PDF file should be %PDF-1.2. However, in an appendix the manual also says that Adobe Acrobat viewers are very liberal in their check for a valid PDF header. All viewers allow the header to appear anywhere in the first 1,000 bytes of the file. Ghostscript doesn't do this: it expects PDF files to conform to the standard, because that's how it recognizes them among other formats it handles, unlike Acrobat viewers which need deal only with PDF and can therefore afford to be more liberal with PDF. So if you encounter a file with useless characters before the header and you want to use it with Ghostscript, you can fix it by stripping the extra characters from before the standard header. The file should begin with exactly the characters PDF files are binary, not text, so be careful to edit the file as a binary, not as text. On Unix, after determining the length of the useless prefix string, which you can do with od, you can use tail to strip them off. For instance: od -c Macintosh.pdf | more ;# shows that %PDF occurs after 128 characters On PCs and other systems you can use the hexl program distributed with GNU emacs to convert the PDF file to editable text form. After editing, hexl can convert the text form back to binary. Notes on specific platformsUnixThe Ghostscript distribution includes some Unix shell scripts to use with Ghostscript in different environments. These are all user-contributed code, so if you have questions, please contact the user identified in the file, not Aladdin Enterprises or artofcode LLC.
VMS
Using X Windows on VMSIf you are using on an X Windows display, you can set it up with the node name and network transport, for instance $ set display/create/node="doof.city.com"/transport=tcpip and then run Ghostscript by typing gs at the command line. MS WindowsYou must add gs\bin and gs\lib to the PATH, where gs is the top-level Ghostscript directory. When passing options to ghostcript through a batch file wrapper such as ps2pdf.bat you need to substitute '#' for '=' as the separator between options and their arguments. For example: Ghostscript treats '#' the same internally, and the '=' is mangled by the command shell.ps2pdf -sPAPERSIZE#a4 file.ps file.pdf MS-DOSNote: Ghostscript is no longer supported on MS-DOS. This documentation is included for historical interest only. You must add gs\bin and gs\lib to the PATH, where gs is the top-level Ghostscript directory.
Note that when passing arguments to batch files (as above) and also with the DOS executable gs386.exe build with the Watcom C/C++ compiler, you must use '#' rather than '=' between a command line switch and its argument, because of a strange design decision in the Wacom run-time library. X WindowsGhostscript looks for the following resources under the program name ghostscript and class name Ghostscript; the ones marked "**" are calculated from display metrics:
X resources
Working around bugs in X serversThe "use..." resources exist primarily to work around bugs in X servers.
X fontsTo use native X11 fonts, Ghostscript must map PostScript font names to the XLFD font names. The resources regularFonts (fonts available in standard or ISO-Latin-1 encoding), symbolFonts (using Symbol encoding), and dingbatFonts (using Dingbat encoding) give the name mapping for different encodings. The XLFD font name in the mapping must contain 7 dashes; the X driver adds the additional size and encoding fields to bring the total number of dashes in the font name to 14. See the appendix "X default font mappings" for the full list of default mappings. Users who switch regularly between different X servers may wish to use the "*" wild card in place of the foundry name (itc, monotype, linotype, b&h, or adobe); users who do not switch X servers should leave the explicit foundry in the name, since it speeds up access to fonts. Ghostscript takes advantage of the "HP XLFD Enhancements," if available, to use native X11 fonts for fonts that are anamorphically scaled, rotated, or mirrored. If the changes have been installed to the X or font server, they are automatically used when appropriate. Using Ghostscript fonts on X displaysFont files distributed with Ghostscript can be used on X Windows displays. You can find full instructions in the documentation on fonts. X device parametersIn addition to the device parameters recognized by all devices, Ghostscript's X driver provides parameters to adjust its performance. Users will rarely need to modify these. Note that these are parameters to be set with the -d switch in the command line (e.g., -dMaxBitmap=10000000), not resources to be defined in the ~/.Xdefaults file.
SCO UnixBecause of bugs in the SCO Unix kernel, Ghostscript will not work if you select direct screen output and also allow it to write messages on the console. If you are using direct screen output, redirect Ghostscript's terminal output to a file. SwitchesUnless otherwise noted, these switches can be used on all platforms. General switchesInput control
File searchingNote that by "library files" here we mean all the files identified using the search rule under "How Ghostscript finds files" above: Ghostscript's own initialization files, fonts, and files named on the command line.
Setting parameters
Note that the initialization file gs_init.ps makes systemdict read-only, so the values of names defined with -D, -d, -S, and -s cannot be changed -- although, of course, they can be superseded by definitions in userdict or other dictionaries. However, device parameters set this way (PageSize, Margins, etc.) are not read-only, and can be changed by code in PostScript files.
Suppress messages
Parameter switches (-d and -s)As noted above, -d and -s define initial values for PostScript names. Some of these names are parameters that control the interpreter or the graphics engine. You can also use -d or -s to define a value for any device parameter of the initial device (the one defined with -sDEVICE=, or the default device if this switch is not used). For example, since the ppmraw device has a numeric GrayValues parameter that controls the number of bits per component, -sDEVICE=ppmraw -dGrayValues=16 will make this the default device and set the number of bits per component to 4 (log2(16)). Rendering parameters
Page parameters
Font-related parameters
Interaction-related parameters
Device and output selection parameters
Other parameters
Improving performanceGhostscript attempts to find an optimum balance between speed and memory consumption, but there are some cases in which you may get a very large speedup by telling Ghostscript to use more memory.
DebuggingThe information here describing the debugging switches is probably interesting only to developers. The -Z switch applies only if the interpreter was built for a debugging configuration. In the table below, the first column is a debugging switch, the second is an equivalent switch (if any) and the third is its usage.
Appendix: Paper sizes known to GhostscriptThe paper sizes known to Ghostscript are defined at the beginning of the initialization file gs_statd.ps; see the comments there for more details about the definitions. The table here lists them by name and size. gs_statd.ps defines their sizes exactly in points, and the dimensions in inches (at 72 points per inch) and centimeters shown in the table are derived from those, rounded to the nearest 0.1 unit. A guide to international paper sizes can be found at http://www.twics.com/~eds/paper/
*Note: Initially the B paper sizes are the ISO sizes, e.g., b0 is the same as isob0. Running the file lib/jispaper.ps makes the B paper sizes be the JIS sizes, e.g., b0 becomes the same as jisb0. Appendix: X default font mappingsStandard X serversRegular fonts AvantGarde-Book: -Adobe-ITC Avant Garde Gothic-Book-R-Normal--\n\
AvantGarde-BookOblique: -Adobe-ITC Avant Garde Gothic-Book-O-Normal--\n\
AvantGarde-Demi: -Adobe-ITC Avant Garde Gothic-Demi-R-Normal--\n\
AvantGarde-DemiOblique: -Adobe-ITC Avant Garde Gothic-Demi-O-Normal--\n\
Bookman-Demi: -Adobe-ITC Bookman-Demi-R-Normal--\n\
Bookman-DemiItalic: -Adobe-ITC Bookman-Demi-I-Normal--\n\
Bookman-Light: -Adobe-ITC Bookman-Light-R-Normal--\n\
Bookman-LightItalic: -Adobe-ITC Bookman-Light-I-Normal--\n\
Courier: -Adobe-Courier-Medium-R-Normal--\n\
Courier-Bold: -Adobe-Courier-Bold-R-Normal--\n\
Courier-BoldOblique: -Adobe-Courier-Bold-O-Normal--\n\
Courier-Oblique: -Adobe-Courier-Medium-O-Normal--\n\
Helvetica: -Adobe-Helvetica-Medium-R-Normal--\n\
Helvetica-Bold: -Adobe-Helvetica-Bold-R-Normal--\n\
Helvetica-BoldOblique: -Adobe-Helvetica-Bold-O-Normal--\n\
Helvetica-Narrow: -Adobe-Helvetica-Medium-R-Narrow--\n\
Helvetica-Narrow-Bold: -Adobe-Helvetica-Bold-R-Narrow--\n\
Helvetica-Narrow-BoldOblique: -Adobe-Helvetica-Bold-O-Narrow--\n\
Helvetica-Narrow-Oblique: -Adobe-Helvetica-Medium-O-Narrow--\n\
Helvetica-Oblique: -Adobe-Helvetica-Medium-O-Normal--\n\
NewCenturySchlbk-Bold: -Adobe-New Century Schoolbook-Bold-R-Normal--\n\
NewCenturySchlbk-BoldItalic: -Adobe-New Century Schoolbook-Bold-I-Normal--\n\
NewCenturySchlbk-Italic: -Adobe-New Century Schoolbook-Medium-I-Normal--\n\
NewCenturySchlbk-Roman: -Adobe-New Century Schoolbook-Medium-R-Normal--\n\
Palatino-Bold: -Adobe-Palatino-Bold-R-Normal--\n\
Palatino-BoldItalic: -Adobe-Palatino-Bold-I-Normal--\n\
Palatino-Italic: -Adobe-Palatino-Medium-I-Normal--\n\
Palatino-Roman: -Adobe-Palatino-Medium-R-Normal--\n\
Times-Bold: -Adobe-Times-Bold-R-Normal--\n\
Times-BoldItalic: -Adobe-Times-Bold-I-Normal--\n\
Times-Italic: -Adobe-Times-Medium-I-Normal--\n\
Times-Roman: -Adobe-Times-Medium-R-Normal--\n\
ZapfChancery-MediumItalic: -Adobe-ITC Zapf Chancery-Medium-I-Normal--
Symbol fontsSymbol: -Adobe-Symbol-Medium-R-Normal-- Dingbat fontsZapfDingbats: -Adobe-ITC Zapf Dingbats-Medium-R-Normal-- Sun OpenWindowsFor Sun's X11/NeWS one can use the OpenWindows scalable fonts instead, which gives good output for any point size. In this environment, the relevant section of the resource file should look like this: Ghostscript.regularFonts: \
AvantGarde-Book: -itc-avantgarde-book-r-normal-- \n\
AvantGarde-BookOblique: -itc-avantgarde-book-o-normal-- \n\
AvantGarde-Demi: -itc-avantgarde-demi-r-normal-- \n\
AvantGarde-DemiOblique: -itc-avantgarde-demi-o-normal-- \n\
Bembo: -monotype-bembo-medium-r-normal-- \n\
Bembo-Bold: -monotype-bembo-bold-r-normal-- \n\
Bembo-BoldItalic: -monotype-bembo-bold-i-normal-- \n\
Bembo-Italic: -monotype-bembo-medium-i-normal-- \n\
Bookman-Demi: -itc-bookman-demi-r-normal-- \n\
Bookman-DemiItalic: -itc-bookman-demi-i-normal-- \n\
Bookman-Light: -itc-bookman-light-r-normal-- \n\
Bookman-LightItalic: -itc-bookman-light-i-normal-- \n\
Courier: -itc-courier-medium-r-normal-- \n\
Courier-Bold: -itc-courier-bold-r-normal-- \n\
Courier-BoldOblique: -itc-courier-bold-o-normal-- \n\
Courier-Oblique: -itc-courier-medium-o-normal-- \n\
GillSans: -monotype-gill-medium-r-normal-sans- \n\
GillSans-Bold: -monotype-gill-bold-r-normal-sans- \n\
GillSans-BoldItalic: -monotype-gill-bold-i-normal-sans- \n\
GillSans-Italic: -monotype-gill-normal-i-normal-sans- \n\
Helvetica: -linotype-helvetica-medium-r-normal-- \n\
Helvetica-Bold: -linotype-helvetica-bold-r-normal-- \n\
Helvetica-BoldOblique: -linotype-helvetica-bold-o-normal-- \n\
Helvetica-Narrow: -linotype-helvetica-medium-r-narrow-- \n\
Helvetica-Narrow-Bold: -linotype-helvetica-bold-r-narrow-- \n\
Helvetica-Narrow-BoldOblique: -linotype-helvetica-bold-o-narrow-- \n\
Helvetica-Narrow-Oblique: -linotype-helvetica-medium-o-narrow-- \n\
Helvetica-Oblique: -linotype-helvetica-medium-o-normal-- \n\
LucidaBright: -b&h-lucidabright-medium-r-normal-- \n\
LucidaBright-Demi: -b&h-lucidabright-demibold-r-normal-- \n\
LucidaBright-DemiItalic: -b&h-lucidabright-demibold-i-normal-- \n\
LucidaBright-Italic: -b&h-lucidabright-medium-i-normal-- \n\
LucidaSans: -b&h-lucida-medium-r-normal-sans- \n\
LucidaSans-Bold: -b&h-lucida-bold-r-normal-sans- \n\
LucidaSans-BoldItalic: -b&h-lucida-bold-i-normal-sans- \n\
LucidaSans-Italic: -b&h-lucida-medium-i-normal-sans- \n\
LucidaSans-Typewriter: -b&h-lucidatypewriter-medium-r-normal-sans- \n\
LucidaSans-TypewriterBold: -b&h-lucidatypewriter-bold-r-normal-sans- \n\
NewCenturySchlbk-BoldItalic: -linotype-new century schoolbook-bold-i-normal-- \n\
NewCenturySchlbk-Bold: -linotype-new century schoolbook-bold-r-normal-- \n\
NewCenturySchlbk-Italic: -linotype-new century schoolbook-medium-i-normal-- \n\
NewCenturySchlbk-Roman: -linotype-new century schoolbook-medium-r-normal-- \n\
Palatino-Bold: -linotype-palatino-bold-r-normal-- \n\
Palatino-BoldItalic: -linotype-palatino-bold-i-normal-- \n\
Palatino-Italic: -linotype-palatino-medium-i-normal-- \n\
Palatino-Roman: -linotype-palatino-medium-r-normal-- \n\
Rockwell: -monotype-rockwell-medium-r-normal-- \n\
Rockwell-Bold: -monotype-rockwell-bold-r-normal-- \n\
Rockwell-BoldItalic: -monotype-rockwell-bold-i-normal-- \n\
Rockwell-Italic: -monotype-rockwell-medium-i-normal-- \n\
Times-Bold: -linotype-times-bold-r-normal-- \n\
Times-BoldItalic: -linotype-times-bold-i-normal-- \n\
Times-Italic: -linotype-times-medium-i-normal-- \n\
Times-Roman: -linotype-times-medium-r-normal-- \n\
Utopia-Bold: -adobe-utopia-bold-r-normal-- \n\
Utopia-BoldItalic: -adobe-utopia-bold-i-normal-- \n\
Utopia-Italic: -adobe-utopia-regular-i-normal-- \n\
Utopia-Regular: -adobe-utopia-regular-r-normal-- \n\
ZapfChancery-MediumItalic: -itc-zapfchancery-medium-i-normal-- \n
Ghostscript.dingbatFonts: \
ZapfDingbats: -itc-zapfdingbats-medium-r-normal--
Ghostscript.symbolFonts: \
Symbol: --symbol-medium-r-normal--
Copyright © 1996, 2000 Aladdin Enterprises. All rights reserved. This software is provided AS-IS with no warranty, either express or implied. This software is distributed under license and may not be copied, modified or distributed except as expressly authorized under the terms of the license contained in the file LICENSE in this distribution. Ghostscript version 7.07, 17 May 2003 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
:: Command execute :: | |
--[ c99shell v. 1.0 pre-release build #16 powered by Captain Crunch Security Team | http://ccteam.ru | Generation time: 0.0028 ]-- |