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