| Line 44... |
Line 44... |
| 44 |
post-processing the output file using \code{ghostscript}.
|
44 |
post-processing the output file using \code{ghostscript}.
|
| 45 |
\code{bitmap} works in the same way using a \code{postscript} device
|
45 |
\code{bitmap} works in the same way using a \code{postscript} device
|
| 46 |
and post-processing the output as \sQuote{printing}.
|
46 |
and post-processing the output as \sQuote{printing}.
|
| 47 |
|
47 |
|
| 48 |
You will need \code{ghostscript}: the full path to the executable can
|
48 |
You will need \code{ghostscript}: the full path to the executable can
|
| 49 |
be set by the environment variable \env{R_GSCMD}. It this is unset, a
|
49 |
be set by the environment variable \env{R_GSCMD}. If this is unset, a
|
| 50 |
GhostScript executable will be looked for by name on your path: on a
|
50 |
GhostScript executable will be looked for by name on your path: on a
|
| 51 |
Unix alike \code{"gs"} is used, and on Windows the setting of the
|
51 |
Unix alike \code{"gs"} is used, and on Windows the setting of the
|
| 52 |
environment variable \env{GSC} is used, otherwise commands
|
52 |
environment variable \env{GSC} is used, otherwise commands
|
| 53 |
\code{"gswi64c.exe"} then \code{"gswin32c.exe"} are tried.
|
53 |
\code{"gswi64c.exe"} then \code{"gswin32c.exe"} are tried.
|
| 54 |
|
54 |
|