# -GS:

This specifies the processing for PostScript specials, PS/EPS files, PBM files or BMP files.
The following specifications are possible. (Since this is an integer parameter, the following numbers are specified in the parameter file.)
If PostScript specials which contain PostScript codes can be ignored. This is indicated by adding 16 to the value of -GS: given in the following. In spite of this setting, PSfrag is usually interpreted.
0(Off): Ignore
1(On): Handles EPS/PS files, PS codes, PBM files, and the special commands related to PBM files. Ghostscript must be called. If it is not found, the process ends.
2(verbose): Handles EPS/PS files, PS codes, PBM files, and the special commands related to PBM files.
3(PBM): Ghostscript is not started.
If the corresponding PBM (or BMP) file is present, use that file. If it does not exist, skip.
In this case, the scale is changed by appropriate magnification or reduction even if the required Image data file and dot size differ.
The horizontal size is considered to be equal if the value rounded up to the byte width (8-dot unit) is the same.
4(exact PBM): Ghostscript will not be invoked.
If the PBM (or BMP) file containing the size exists, use it. If it does not exist, skip.
5(gssub): Ghostscript is not started.
As in 4, if the required image data file does not exist, the gs_exec.bat batch file that converts the EPS/PS file to a PBM or BMP file (read in by dviout) and the gs_exec$.ps PS file are created. The additional program ofgssub.exe is required.
If gs_exec.bat and gs_exec$.ps already exist, delete gs_exec.bat and gs_exec$.ps before starting when needed since the end of existing contents will be added to.
Since this batch file that is created converts only files that do not exist from among the required PBM files (or BMP files), if this batch file is started, starting with the next dviout, the PBM files (BMP files) can be directly read.
However, if images with different sizes are created multiple times from the same EPS file or direct PostScript codes are written in \special, they cannot be handled by the batch file that is created previously.